Ratings and Reviews by Mike Russo

So I know there’s a plethora of successful Sherlock Holmes games, from Infocom’s run at the great detective to those more recent 3D ones where he goes up against like Lupin or Cthulhu, but I’m not going to let that fact get in the way of my sweeping opinion: there’s no way to make a truly satisfying Holmes game, because you need to either make him too smart or too dumb. That is, either you limit the player’s agency and have him solve the case for you, because of course he’s a genius, or you subject Holmes to every one of the player’s idiotic flailings, making it a wonder he manages to tie his shoes let alone reveal the secret of the speckled band.

The way to dodge this conundrum is to have the protagonist be someone other than Holmes – typically Watson, sometimes, I am informed, a dog – and feed him information, so that once he has the data he needs he can make the great deductive leaps his fictional reputation requires. The Transformations of Dr. Watson takes this approach, putting the player in the shoes of Watson, at least initially, but forgets that this means Holmes doesn’t have to swap his deerstalker for a dunce-cap; sadly, this is the dimmest Sherlock has been since those Robert Downey Jr. movies where he mostly just got in fist-fights.

Making matters worse, the mystery here at issue would barely keep a single Hardy Boy busy for an hour. As the game opens, you as Watson are called to the house of a recently-deceased toff to pronounce him dead, though the game doesn’t exactly play things close to the chest when introducing the setup:

"His nervous smile and damp palm upon shaking hands betrayed his tension. “My father… passed away. Heart, I suppose,” he said hastily.

“'Sir Silas never complained of his heart,' the butler, Cavendish, retorted dryly, casting a quick glance at Alister. My medical intuition screamed an alarm."

The only thing that could make things more suspicious would be – well, Alister’s name oscillating to “Alistair” with no explanation, but I assume that’s just simple typos rather than further evidence of fraud. But the teacup with an oddly-bitter odor right next to the body sure does gild the lily.

In fairness, Watson doesn’t get the odor clue right away; first, his soul needs to transmigrate into the body of a cat so he can take advantage of its enhanced senses. Yes, there’s a gimmick here, and not one that was at all explained in my playthrough: after the treacherous Alister/Alistair bashes his head in with a cane, Watson’s consciousness shifts to inhabit a variety of other creatures, and he uses his newfound lease on life to draw Holmes’ attention to the clues once he arrives to check up on his missing friend.

It’s a bizarre if not unpromising gimmick, but there’s less here than meets the eye. Even once the prologue ends, the game is largely linear, with the few choices almost all having clear right and wrong answers – and again, since the mystery is so obvious, the fact that Holmes needs help at all just makes him look exceptionally slow on the uptake. At least there’s a bit of bathos to be wrung from the way the heir is able to intuit that he’s somehow managed to anger a menagerie that’s now bent on his undoing, leading him to seemingly-unmotivated reprisals that surely only incriminate him further. But unexceptional prose that’s a bit too adjective-happy combined with overly-slick AI art mean that there are few flowers to stop and sniff along the way to Holmes’ preordained triumph. It’s all laid on a bit too thick, we’re denied the conventional pleasures of a Holmes tale, and sadly neither gameplay or presentation are up to much. It’s enough to drive a man to cocaine.

Lately I’ve been getting back into Star Trek. There’s an element of nostalgia to it, certainly, that gets increasingly appealing as my age keeps ticking ever-upwards, and its optimistic vision of humanity makes for a nice change of pace from the evil currently consuming America. But actually the thing that I find most soothing about it is what’s been dubbed the “competence porn” angle: The Next Generation especially is a show where a bunch of high-functioning professionals confront challenging problems, hold meetings to brainstorm ideas and develop a plan of action, then despite whatever twists and turns the galaxy throws at them, save the day in 43, or at worst, 86 minutes (until DS9 came along and ruined things with its three-parters and seasons-long arcs). In this time of chaos, seeing people be good at their jobs is basically my ASMR.

The Tempest of Baraqiel cites golden-age sci-fi as its immediate inspirations, and its setting is far more militarized than the Federation: here, humanity is locked in a losing war against an implacable and cryptic race of crab aliens. But it definitely occupies adjacent territory. As a young exolinguist, you’re assigned to a warship and given a secret mission to decode enough of the aliens’ language to operate one of their weapons. Through a well-paced adventure that’s only a bit longer than a Star Trek episode’s running time, you’ll motivate your team, look for inspiration to get through blocks in your research, and yes, have a bunch of meetings with your superiors (in fairness, you can also get into a fistfight in a knock-off of the Enterprise’s Ten Forward bar, if you want). Kal Shem, the protagonist, is young and has some anxiety to living up to the example of his war-hero mom, but at least as I played him, he’s really good at sweating the details and playing the bureaucratic game – at least until things went off the rails in the endgame.

The game definitely puts its best foot forward, though. The custom choice-based interface is clunkily sleek in that 80s-sci-fi way, with low-poly 3D renders in the corner illustrating the ship and its locations (admittedly, I mostly stopped noticing it after the first scene – likewise, there’s a custom music system that I can’t offer an opinion on since I didn’t listen to it). There’s a fair bit of world-building to get through, but it’s managed with a deft hand, and if there are few sequences where characters explain things they both already now to each other, that’s part of the charm of old-school sci-fi – mostly the infodumping comes with some character backstory or a reasonable explanation for why someone needs seemingly-basic context. Some of these circumstances can feel a bit contrived, most notably the fact that Shem isn’t a specialist in this particular alien language, so he seems an odd choice for team leader. But his family’s military background means he’s seen as more reliable for an assignment that requires discretion, so I was willing to go with it.

Baraqiel’s approach to interactivity is also nothing fancy, but well done. There’s a high density of choice – there are very few passages where you just click “next”, and there are both a reasonable number of what seem like significant branch points where you can take a different strategy on your research assignment, and more low-key choices that are either cosmetic, or might have a mild impact on your team’s opinion of you. Interestingly, you’re not restricted to making choices for Shem alone; from time to time you can pick actions for another character, sometimes even an antagonistic one. I was typically too gun-shy to lean into creating conflict in these situations – like I said, that’s not what I go to Star Trek for – but it’s a nice option for players more interested in orchestrating an engaging story than getting by with a minimum of fuss.

As for the prose – well, would you be surprised to learn that it’s largely straight-ahead, but well-crafted? The one distinctive note is that many of the characters use Yiddish slang, like dybbuk or macher; I’m not sure whether a passage I missed laid out the in-universe reasons for it, but it’s a touch I enjoyed (I also know enough Hebrew to understand that “Shem” means something like “name”, which is apropos enough for a game centered on linguistics).

There were a few small flies in the ointment as I played – most notably, the save/load system bugged out, recording only the first time I pushed the save button and not any of the others, meaning that when I tried to rewind a late-game choice to explore other options, I got sent nearly back to the beginning. Meanwhile, only one of Shem’s teammates gets much in the way of characterization. Still, I was having quite a good time as I headed into the game’s third act, which serves as the endgame – but unfortunately that’s when things started to fall apart. The methodically-paced research process suddenly leaped ahead with one flash of insight after another, not all of which made much sense, including a final revelation that seemed hard to swallow <spoiler((surely if the alien language was crafted to be comprehensible over the static of interstellar communications, the humans would have already had to understand and craft a similar solution to this problem when they encountered it over their centuries among the stars?))</spoiler). The climax also forces a conflict with one of Shem’s superior officers who I’d managed to cultivate a solid relationship with; I was deeply confused by why Shem suddenly seemed to be edging right up against mutiny for what appeared to be no good reason, regardless of trying to pick the more conciliatory options. And the ending passage I got was exceedingly compressed and anticlimactic – while the game seemed to be building up to a moment when you’d actually communicate with the aliens, or at least operate their weapon, neither of those came to pass, and the scant few paragraphs that tie off the game were also sufficiently ambiguous that I wasn’t sure what was meant to have happened, or why.

My guess is that the author ran out of time as they got to the end of what’s by any measure a big, responsive, and high-production-value game – it wouldn’t be the first time that’s happened to a first-time Comp entrant, and it certainly won’t be the last. So even if Tempest of Baraqiel’s final act lets it down somewhat, there’s still more than enough competence on display in the majority of its runtime to scratch that meetings-and-science-and-space-adventure itch.

Readers, a confession: I fear I was not a very fun child. Case in point, even when I was little I never much liked cotton candy. Sure, it looks pretty and it’s good enough on first bite. But there’s just so much of it, and every bite is exactly the same – the same unidimensional sweetness, the same airy-yet-claggy texture, with nothing to liven up the monotony of the march to the soggy cardboard at the end.

OVER is much more enjoyable than a stick of cotton candy, so this is an unfair simile with which to open this review. It’s got some characters who eventually grew on me, a nicely-granular look at the enervating logistics of a big family vacation, and entertaining period details. But I also found it way too long for what’s ultimately a simple story whose themes, characterizations, and gameplay don’t have much depth; at half the length, they wouldn’t wear out their welcome, but at over two hours, the candyfloss has time to turn to a gummy paste in the mouth.

Here’s the short version: a 19-person family goes on vacation to an unnamed theme park that is 100% Disneyworld, and over the course of five days, the two main characters – both queer women, one a 20-year old whose name the player supplies, the other a maybe-late-thirties aunt named Lou – come to grips with the ways they’ve allowed the demands of their big, homophobic family to push aside their need for autonomy and love, against a backdrop of low-key child-mediated mayhem and ubiquitous walkie-talkie use serving as a metaphor for garbled communication and the possibility of surprising connections. Everybody gets on each others’ nerves, everyone’s trying to convince themselves they’re having fun when there’s little authentic pleasure on offer, and just as Disneyland is a pleasant but generic façade over a grim capitalist reality, so too do the rituals of a loving family cloak disapproval, sharp elbows, and bigotry. Fortunately, both the 20-year-old and Lou happen across idealized love interests who offer an escape (though you can’t see how both of their stories resolve, since you have to choose just one to follow into the climactic sequence, which retroactively renders much of the slow buildup of the path not taken superfluous).

That’s not a bad story, but it’s not an especially complex or novel one to support a game that ran me well over two hours to get through. Characters are almost all slotted into a one-dimensional good vs. bad continuum, except for the children who are such non-entities they’re not even allowed names (this is a game with a lot to say about parenting and nothing to say about parenthood). There are a few small choices the player can make to affect the story, but they come infrequently and late – I mostly just remember them being of the form KISS LOVE INTEREST/DON’T KISS LOVE INTEREST. Instead, most of the gameplay consists of deciding which of the characters to follow for the next piece of narration, which always left me feeling like I was missing out on the full story (a feeling exacerbated by the game occasionally calling back to events that I hadn’t seen happen, or even been mentioned). And as for the plot, there’s not much that happens for the first three or so days of the five-day running time, besides the slow establishment of the character dynamics, low-key introductions to the love interests, and (in fairness) a kid puking on the awful grandma’s shoes – and things only pick up slightly in days four and five.

All that means that playing OVER can feel enervating, something the prose definitely contributes to – it’s wordy, and intentionally evades detail:

"The lines were long and dark, most line games were rendered inoperable, and tiredness made them all skirt around conversation. The kids talked about their plans for the coming days, which rides were high priority repeaters and which they barely felt the need to do once. The mom’s, Marian, and Lou talked about the weather, how poorly they had all packed, how nice it was to get away from home for a little while. Charlotte asked her mom about work, and they discussed some previously relayed story’s newest developments. Lou hadn’t heard that story, and didn’t feel like listening to a saga start to finish at the moment, so she asked Margot if she’d read any good books lately. It was a thing they had bonded over in the past, though their tastes weren’t similar, by any means, they both appreciated texts that were unusual, that you wouldn’t necessarily find on any of Oprah’s lists."

There’s a reason the author adopted this style, I suspect – with its busy-ness, its focus on logistics, and its monomaniacal fixation on form and allergy to substance, it clearly has some resonance with the Disneyworld experience it depicts. That same logic applies to OVER’s length, too – the brutality of long exposure to this place, and this family, is precisely what’s ground down Lou, and what the 20-year-old eventually comes to see as an existential threat. So subjecting the player to this very much furthers the work’s artistic aims. And it’s clear the author is writing from experience, and can include some wry or winsome detail when desired:

"A dramatic sobriety falls over her, so dramatic that it almost feels like she’s actually drunk, and she clenches her fists together tight enough to make crescent-moons in her palms with her fingernails, matching the sliver of moon in the sky."

It’s also the case that quantity can have a quality all its own, and by the end I did have some fondness for the sympathetic members of the cast. While Lou is a straightforward character not drawn with as much specificity as I’d have liked (I don’t need a ton of backstory, but there are a couple sentences towards the end that imply that she’s never actually been in a relationship, and if that’s true that should probably have been mentioned earlier), I still wish I’d been able to see how her story turned out, since after long exposure to her travails I couldn’t help but root for her. A fling with a hot, understanding bartender, which seemed to be where she was heading, won’t cure all ills but it certainly wouldn’t hurt, and it would have been a fun note to end on.

So there’s definitely enjoyment to be had in OVER, but it can’t overcome the fundamental mismatch of scope and richness: as the game itself argues, a week is way too long to spend in someplace as simple and cloying as Disneyworld, so better to make it a day trip or go to Rome instead.

The surrealist IF game about trauma is a sufficiently well-represented subgenre that by this point I have a standard bit of patter I trot out for my reviews: these pieces often have spikily compelling writing and can be engaging on a sentence-by-sentence basis, but they also run the risk of being too idiosyncratic to resonate with the audience, as it’s very easy for an author to present snatches of imagery, language, and events that are incredibly personally meaningful, but which lack enough context to ground them in lived experience. No matter how great your prose or vivid your imagination, if the player can’t connect to what they’re reading, there’s a limit to how much impact your game can have.

Slated for Demolition is a very good Twine game in this vein, and as if to prove how little I know, one of the two things holding it back from being really great is that at a climactic moment, it reaches for universality rather than staying rooted in the subjective. At least the other thing is the more conventional challenge of underexplaining a key metaphor.

Before circling back to those issues, though, it’s worth dwelling on the ways that Slated for Demolition really works. While the subject-matter here is pretty familiar – early-20s anomie interrupted by sexual assault – the authorial voice is immediately confident, equally at ease describing the bleakness of a late-night suburb, the degrading consequences of alcohol dependence, and magical-realist irruptions of beauty and terror. The sentences have rhythm, the anecdotes have enlivening details, and the tone never stays stuck too long in one place, preventing the player from being desensitized through repetition. An example, more or less at random:

"Once when you were 18, you went to a party and drank your entire personality away all night long. You managed a few passed-out hours of sleep, and then you had to wake up and go to work for the early shift.

"It was your turn to stock the freezers. You knelt on the hard concrete floor, gingerly placing TGI Fridays-brand meals and trying your hardest not to vomit absolutely everywhere."

The gameplay also knows how to change things up. The overall structure is that of a quest, or a shaggy dog story – you leave your house in search of a Slurpee, but compulsions keep dragging you into more errands, and memory drags you back into reveries, leading to distinct set-pieces as you pass a long dark night of the soul. Some of these involve straightforward choice-based branching, but others require the player to move through or explore a persistent space; a stand-out vignette is more or less an extended puzzle, as you try to figure out which apartment an acquaintance lives in when all you know is the building’s address.

This kind of variety could risk undermining the game’s sense of progression, but one of its conceits is that in each scene, you’re collecting items to satisfy an obscure shopping list you find in your pocket. While the significance of each is typically unclear, wanting to complete the collection kept me engaged in the details of what was happening even in the strangest of the sequences, and provided a sense of pacing across the game’s almost-two-hour running time (the list is also rather forgiving – even if you miss something, just before the endgame you’re given a chance to zoom back to pick up the items you lost).

That endgame is where Slated for Demolition attempts something surprising and audacious, which I can’t help admire even though it didn’t quite work for me (I admire it enough to spoiler-block it, in fact, but the short version is that it makes a move for the universal rather than the particular, when the particular had previously served it very well indeed). (Spoiler - click to show)After doing a lot of work to situate the player in the protagonist’s subjectivity and revealing the details of the traumatic event exerting its gravitational pull throughout the rest of the game, the protagonist begins a ritual to attain closure – except before performing it, the player is invited to think about some pain they’ve experienced and use the ritual structure to fill in details for their own exorcism. It’s a lovely idea for bridging the gap between author and player, and I made a good-faith effort to engage with it, but I found the exercise deeply uncomfortable, because it felt like I was overwriting the protagonist’s, and perhaps the author’s, experiences with my own. Trauma is trauma, to a certain degree, but as the rest of the game demonstrates, the specific details of what was done by whom, to whom, and how, make an enormous difference – and that’s especially the case when dealing with sexual assault, given the role gender and power dynamics play. For some players, I’m sure, the details of the ritual would resonate deeply and the memories it evokes would be congruent with the game’s themes. But for me, even making the attempt felt like overstepping.

My other complaint is that the strongest image in the game didn’t cohere in a satisfying way. I also don’t want to spoil this too much, but the blurb and cover art give away that every once in a while, the protagonist feels like she’s dissolving into pasta and red sauce, and while that sounds silly, in fact it’s written to be the most upsetting piece of body horror I’ve come across in years. I was delighted by how much these sequences made me squirm, but while there are a few hints for how they connect to the game’s broader concerns, the hints are rather thin and ultimately the metaphor doesn’t connect very neatly with the title and framing idea about a house fated for destruction. It’s a textbook example of surrealism that needs a bit more connective tissue, so while Slated for Demolition definitely challenges my theory for what makes these kinds of games succeed, at least I don’t need to throw it out entirely.

I’ve been at the IF-reviewing game for a while now: over twenty years stem to stern, and even if you discount the interregnums it still comes to about a decade. There’s been a lot of opportunity over all that time to interrogate my methods and their foibles, so I feel like I’m generally pretty self-aware about how I approach reviews. But there remain a couple of black holes that still lurk within this otherwise-well-surveyed galaxy, jealously guarding the secrets yet concealed within their Schwarzschild radii (forgive the tortured metaphor, my son’s been into space stuff lately so it’s all been top of mind). The one apposite to this, my final review of the Thon, is the mysterious ability some games have to make me stick to my first ending rather than replay them.

It’ll shock no one who’s followed my reviews that I have a bit of a completionist streak – OK, I’ve exhausted literally bit of content for every Assassin’s Creed game that came out before my son was born, down to finding all those stupid feathers that were floating over Venice in AC2 and clearing every map icon, however mundane, in Origins and Odyssey, so perhaps “a bit” is a misnomer. So it’s probably unsurprising that if a piece of IF advertises itself as having multiple endings, or significant branch points, my natural inclination is to check those out, and that inclination is even stronger when I’ve decided to review something; obviously an analysis informed by an understanding of a game’s structure and the full range of its narrative possibilities is going to be more incisive! Of course, I’m not slavish about this, if a game is super long or there are options that I’m just deeply uninterested in (see, e.g., “evil” paths), I’m more likely to be one and done. But when playing a short game that clearly signposts that it changes quite a lot based on player choice, and that maintains a minimum level of quality such that a replay feels like it would be reasonably rewarding, I’m typically happy to do so. Except every once in a while I just don’t feel like it, for reasons that I think aren’t *just* laziness but remain frustratingly hard to pin down.

Whew, we’ve finally circled around to Blood and Sunlight. This is a short Ink game that’s part of a series (I haven’t played any of the others) focusing on Zach, the vampire PC, and Lyle, his lover. This installment sees them firmly coupled up, but seemingly still in the early stages of the relationship, facing a milestone: there’s a party at Lyle’s place where Zach is meeting their family, it gets late, and Lyle asks Zach to stay the night, which he’s never done before. The dilemma isn’t about sex, to be clear – Lyle conks out a little too early for that to be on the table – but about Zach’s vampiric nature: Lyle doesn’t (yet?) have blackout curtains or any of the other niceties the discerning Nosferatu arranges for their lair. Fortunately, Zach isn’t the kind of vampire who’ll burst into ash if they catch a stray ray, but sunlight is enough to cause discomfort and nausea, so there are reasons beyond potentially-fraught interpersonal dynamics to hesitate to sleep over.

All of this is well explained within the game, even for a newcomer to the series – I felt like I had a solid handle on the characters’ respective personalities (Zach is a bundle of anxiety, Lyle is gentle and solicitous; Lyle’s family members are very much secondary but still manage to be appealing) and a clear view of the situation. Details of their backstory don’t really come on-screen, but given that those are probably the purview of the other two games, that’s fair enough. I will admit that I wanted a bit more worldbuilding on how exactly vampirism is meant to work, especially given that the treatment of sunlight is idiosyncratic – in particular, I wasn’t sure whether feeding generally entailed some form of predation or if ethical vamping was a thing, since that would have helped me get a better handle on how much of Zach’s angst is due to his personality rather than his situation – but all things being equal I feel like a lighter touch is better than a heavier one on this score.

Speaking of things that are light or heavy, there are a lot of choice points in what’s a reasonably slight vignette: beyond narratively important ones like deciding whether or not to accede to Lyle’s entreaties, you’re given quite a lot of scope to define Zach’s attitude and mood. These tend to range from more self-loathing ones, where you draw back from others’ attempts to reach out to you, to happier choices where you disbelievingly accept the love and care that you’re offered (as I said, Zach is angsty, you understandably don’t get completely low-key options).

It’s all well-presented, in prose that’s unshowy but evidences a good eye for detail and foregrounds emotion:

"You both get up, and Lyle laughs when they notice your pajamas, informing you they were a gag gift from Daph. You let them hit the bathroom first, and you pull on yesterday’s clothes, glancing yourself over in Lyle’s mirror afterward; that whole no-reflection thing is as much a lie as the burn-up-in-the-sun shit. Your eyes are a little hollow, the corners of your mouth drooping. You put on a smile, grinning so hard it becomes macabre, and when your face goes slack again you look a little less dour. Then, too antsy to just sit and wait, you crack the door."

It all adds up to a satisfying, nicely made game, albeit in my first playthrough it felt a bit slight – I generally stuck to the choices that saw Zach accepting Lyle’s overtures and making a reciprocal effort to connect with them, and while that course did have some bumps along the way, notably some barfing and a need to push down feelings of inadequacy, it felt decidedly low-drama both in terms of conflict and outcomes; by no means was Zach and Lyle’s relationship transformed by these events, it just took a solid but small step forward.

I suspect that players who leaned into other versions of Zach would find their experience quite different, however: a vampire who slinks home alone or awkwardly runs out first thing in the morning would likely see this night as more of a turning point, potentially threatening this promising relationship or just offering a poignant reminder of the ineluctable curse of undeath. If I felt like my playthrough was low-drama because the main takeaway was that Zach just needs to relax a little, well, those other playthroughs are presumably right there.

And yet that’s all speculation, since I left things there. Objectively, there’s no real reason I can give for not exploring my options: I sincerely think the game would change a bunch, and my opinions would be more well-rounded, if I gave it another whirl, and I enjoyed my first go-round so I’m pretty sure I’d like a second, too, even if I’d be spending more of it wincing at Zach’s refusal to get out of his own head. But, well, see above – after hovering my cursor over the “restart” button a couple of times, I didn’t wind up clicking. I guess even if you’re usually a pretty responsible person, there are times when just going with the flow still somehow feels like the right thing even when you know objectively it’s not. And if I can’t figure out why that is for myself, it’s easy to sympathize with Zach for being in the same boat.

I have an odd relationship to floods, which is to say, I don’t actually have one. I’ve experienced earthquakes and hurricanes, seen a tornado, had to evacuate my home because of a wildfire, missed my wedding rehearsal due to mudslides, and hunkered down through more blizzards than I can remember before I decamped to Southern California (they’re way better than the fires). There are more exotic natural disasters beyond these, of course, but I’ve seen movies depicting avalanches and tsunamis and volcanos so there I at least have some second-hand associations of terror. But floods? I’ve never actually been in one, and they don’t present an especially cinematic prospect, unless a dam breaks or something. As a result, while I intellectually know they’re awful – witness all the recent deaths in Texas – I don’t have much of a visceral response to them. If anything I think the images of flooded towns can seem oddly peaceful, the ordinary landscape of roads and buildings transfigured.

So I vibed with The Deluge’s take on the theme: the nameless protagonist is forced by a flood to leave their home, but leaving everything and everyone behind doesn’t seem entirely unwelcome. This is a meditative game, the danger universally acknowledged but never actually approaching, allowing plenty of space to contemplate mistakes and paths not taken and consider what might come next. This choice-based game isn’t exactly parser-like – there are no compass directions, no inventory you can check, and no puzzles besides some order-of-operations stuff and one unique challenge I’ll circle back to later in this review – but you do have freedom to explore, ranging from your apartment to your old haunts to the outskirts to which you’ll eventually have to escape. There aren’t many direct conversations or anything you’d think of as an action sequence, but there is a lot of environmental storytelling, effectively narrated in a voice that focuses more on conveying sharp, concrete detail than providing a complete backstory for your character:

"The bed is unmade. You imagine yourself half-asleep, safe, warm, and as perfectly content as a stretching cat. You imagine the body beside you, reaching out instinctively for you without fully waking up."

This extends to the effects of the flood, too:

"You’re only halfway down the least-used of three stairwells when you realize the extent of the damage. Puddles slosh at your feet; a vaguely riparian odor drifts up from the basement below you."

There were times when this studied fuzziness of plot did present a slight obstacle; it seems like the protagonist has complex history with a lot of former lovers, friends, and family members, and since none of them are given names I sometimes had a hard time keeping them straight. But obfuscating the details helps reinforce the central vibe, of a mountain of regrets and guilty relief at being forced to leave them behind. It also means that when something does snap into focus, it gains additional power: there’s a charged conversation with an ex that really stands out, for example.

The gameplay, meanwhile, also meshes nicely with the theme. You can’t get everywhere from everywhere, and there are interactions that are only available on repeat visits or after you’ve gone someplace else first, which means that you spend a lot of time circling around the same ground, slowly building up to making your escape. There’s a list of things you need to accumulate before you’re able to finally go, some physical, some more nebulous, though I didn’t find a way to check these other than trying to leave, which made the transition to the endgame feel bit more abrupt than I would have liked (on the plus side, it was exactly as enigmatic as I liked). There’s also that odd gameplay mechanic I mentioned above – let’s spoiler this: (Spoiler - click to show)when I tried to find the key to my uncle’s boat, at first I thought I was stuck due to a bug that only let me toggle between two passages, rather than allowing me to retreat back to town when it didn’t turn up. I actually alt-tabbed for a minute to jot down some notes in frustration – but then when I alt-tabbed back, suddenly I’d found the key! I think this is a real-time mechanic that reveals the key after you’ve let the page stay up for a certain amount of time, which is formally interesting, but felt like an odd choice to me – the game doesn’t otherwise use timed text, I don’t think, and without that telegraphing I almost got annoyed and restarted the game! It’s something that I think is neat in isolation, but I’m not sure is a great fit for this game in particular.

That’s really the only discordant note I found in The Deluge, though – it’s otherwise a very coherent work, embedding some universally-relatable emotions in a distinct, and distinctly-presented package. It didn’t make me afraid of floods, but it did help me inhabit their aftermath with more clarity than I had before, making a case for rising waters as a pregnant metaphor worth dwelling on, regardless of their real-world dangers.

When learning something new, the most important factor – I’d argue bigger than native ability or quality of instruction or anything else – is often enthusiasm. No matter how quickly things click, you’ll invariably run into road-blocks, and no matter how fun developing one aspect of a skill might be, there’s always going to be something else that’s a slog. Sure, all those other things, skill and good teachers and so on, can reduce the friction so it’s easier to power through, but you still need that motive force to keep you moving even as things get tough. And beyond overcoming obstacles, enthusiasm can have active virtues too: even the most jaded critic can be charmed by a roughly-hewn work if the palpable excitement of creation comes through.

The thing is, though, enthusiasm can only take you so far. A short game with all the flaws of inexperience can still leave a positive impression if it’s fleet enough to end before those flaws weigh down its exuberance. But if things drag on too long, the nitpicks start to pile up, the bubbly energy starts to feel exhausting, and the jaded critic (hi, it’s me!) loses track of what perked them up about this thing in the first place.

Quotient: the Game could have been engineered in a lab to illustrate the principle. The ingenuousness of its spy-thriller-meets Zork premise wins it a smile, which is only deepened by the cornball appeal of its love of junk food and Ohio pride (seriously, your jet-setting spy can go to Oxford, DC, “Africa”, outer space – or Cleveland and Cincinnati). And there are some solid puzzles that help keep the momentum going. But over the course of this two to three hour game, the constant in-jokey references to Dr. Who and Star Wars start to grate, the lack of adequate player direction or clueing lead to floundering, and the weight of minor bugs and small implementation threatens to overwhelm the fun stuff. Most of Quotient’s issues are ones first-time authors have to deal with (especially those who don’t benefit from a lot of pre-release testing); it’s just a shame that so much time and energy appears to have gone into this debut when it’s likely that the lessons learned from completing a game would help the author write something a lot tighter the second time out.

On to specifics: Quotient self-consciously invokes Zork with its setup: you’re outside a house, with a leaflet promising adventure to come, and a scoring system that rewards the accumulation of treasure as much as progression of plot. But this is no fantasy pastiche: instead we’re in the realm of a technothriller, as you play a new recruit to the eponymous spy agency, tasked with … well, it’s not really clear from the outset. One of the first challenges I faced with Quotient is that the game seems to assume you already know about the important characters, the world, and the basic outline of the plot – there’s some exposition, but almost always it left me with more questions than answers. Not getting bogged down in details until the player’s invested in the game can be a powerful technique, but here the other shoe doesn’t really drop. Like, once I solved enough puzzles to be admitted to the spy agency as a probationary agent, I finally got a mission briefing, which read as follows:

"Welcome to the team. Your mission involves two things. One is simply treasure hunting. This will earn points toward your rank. While we were setting up this training mission, a real mission came in. This is the second and most important part of your mission. The Lion has escaped and interfered with Cassie’s time experiment. We need your help on this mission. It’s critical we help Cassie complete her experiment. All of our agents are already working it. There is no time to explain more, you’ll have to figure out the rest as you go."

I eventually groped my way towards a fuller understanding of the premise: the aforementioned Cassie is a scientist working on a future-prediction machine that uses quantum computing, but a villain stole the magic crystal that powers the device, so you have to track him down and take it back. The game doesn’t end at that point, though – to my surprise – as you then need to help Cassie complete her experiment. Each of these steps is either underexplained (exactly what the experiment is, or what it requires, isn’t really spelled out) or overexplained (I got a few updates from Florian about how to find Robert well before I had the slightest idea of who either of those people were).

As a result, it’s most natural to treat Quotient as a treasure hunt – just wander around, solve puzzles because they’re there, grab whatever’s nailed down. And on that score it works OK! Here’s where the enthusiasm really tells; the game is palpably excited to show you around such tourist attractions as the National Mall, Oxford University, and downtown Cincinnati. In the farther-flung locations, the narration is very much lifting up the Wikipedia highlights and flubs a few minor details (I’ve lived in DC, and the geography there is slightly off in a way that kept wrong-footing me). But the local Ohio stuff elevates what sure seems like it must be the author’s favorite diner, and the allegedly-famous Cleveland sign. The gonzo would-a-teenager-thing-this-is-cool sensibility is also in best display in this section, like when you get this readout on the current British PM:

"Prime Minister Jason Stevenson is an experienced leader with a deep understanding of European state affairs as well as genetics. He is a skilled martial artist and has been known to relax in front of a videogame at times."

The puzzles are also pleasantly moreish, for the most part. There are two mazes and some unmarked exits, and some of them rely on completely arbitrary clues, like a deck of cards that for some reason spells out the steps required to complete a high-tech feat of engineering, but on their own terms, that’s fine. There are some password challenges, a couple straightforward inventory puzzles, dark areas that require a flashlight – it’s all basic but goes down easy.

Well, it goes down easy until it doesn’t. At what I think is about the 2/3 mark of the game, my progress slowed substantially – I wasn’t sure where I was supposed to go or what I was supposed to be doing, and I’d run out of puzzles that I could easily figure out how to solve. There are some in-game hints, but they tend towards the cryptic, and don’t account for stuff you’ve already done, but I was able to use them to grind through a few more puzzles, albeit these ones felt more arbitrary than the earlier ones (Spoiler - click to show) (I’m pretty sure praying in the National Cathedral made a laser pop out of the floor; if that’s explained anywhere, I missed it), and threw the unhelpful nature of the thinly-implemented NPCs into sharp relief (after I’d recovered the crystal she was looking for, why didn’t Cassie unlock the door to her lab instead of making me fly halfway across the world to try to dig up a keycard?). And then I hit a wall when I realized I’d soft-locked myself by fiddling with a much-earlier puzzle (protip: don’t put anything into the lighting tube you want to get back).

So yeah. At the one hour mark, I’d have said that I was enjoying the silly, giddy ride that Quotient has to offer, but at the three hour mark, I was mostly just frustrated. None of my complaints are mortal ones, I don’t think, and again, they’re incredibly common among first-time authors – assuming the player will know what they’re doing because it’s obvious to the author, missing that some puzzles don’t have nearly enough clueing or motivation to allow the player to solve them, going for a larger cast of shallow characters rather than just a few more deeply-implemented ones, and not quite enough time polishing and fixing bugs that arise when the player doesn’t do quite what’s expected. Unfortunately Quotient goes on long enough that its early promise does have time to curdle into annoyance. The good news is that usually second-time authors quickly learn how to avoid these mistakes – it’s just that for both author and player, there can be an advantage to getting to that second game sooner rather than later.

I am not a J-horror fan, or even a horror fan in general, but there is one clip from a mid-aughts entry in the genre (I think it was called Pulse, but I am 100% not looking it up to check) that lives rent-free in my head: a guy goes into a sub-basement, hears something weird, and at the end of this dark hallway, sees a strange figure standing there in the shadows. Slowly, slowly, it starts to walk towards him, with this hideously unnatural gait, almost falling once before it gets its limbs back under control. He’s rooted to the spot, just watching as it gets closer, and closer, and closer, mesmerizing in the inevitability of its languid approach.

I don’t know how the sequence ends – I honestly hope it’s just a jump-scare, because that would be the least-scary of the alternatives? – but I find it terrifying; being forced to inhabit the same world with something uncanny for so long, with no choice but to linger on the details of how wrong it is, makes my blood run cold. It’s horrible! But in a really compelling way.

A House of Endless Windows pulls off a similar trick: while this kinetic novel plays coy at first, dancing around details of backstory and context, it’s clear from the get-go that there’s something deeply wrong in this family – the alienated child (that’s our narrator), the pushy mother, the absent father – even before a new arrival shatters the prevailing chilly détente. But then the player understands more about what’s happened to create this situation, and engages with the mysteries surrounding the newly-arrived housekeeper, and the effect is slow-motion torture: the situation feels untenable, even as nothing overtly threatening is happening, the danger and trauma masked behind stilted dialogue and a refusal to acknowledge the reality that everybody knows lies beneath the surface.

Don’t get me wrong, there is a plot, stuff does happen, but the vibes are really what make A House of Endless Windows so arresting. You get a sense of the contortions the main character has made of his life in order to hedge defenses around himself almost immediately:

The sooner I complete the chores, the sooner I can start on homework. The sooner I start on homework, the more time I have to study.

Or:

I yell as loud as I can. It’s a pitiful, quiet yell.

The writing is finely calibrated, getting us in the head of Pierce, our damaged, precocious protagonist, while writing dialogue that isn’t quite naturalistic but still manages to feel plausible. Here’s an exchange between him and his friend Avery:

Pierce: Do you believe me?
Avery: Well, I can’t imagine you’re lying about it.
Pierce: That’s not the same as you believing me.
Avery: No. It isn’t.

It’s clear this awkwardness is intentional – there are a few flashbacks that take Pierce back to a time before things in his family were quite so broken, and his mother’s dialogue is notably warmer than it is in the present. There are also a few well-earned moments where the possibility of emotional engagement at least flickers into possibility, even if it’s never quite achieved. But they gain their power from the contrast they draw with the rest of the game, where Pierce is typically passive or frozen, observing that things aren’t right but unable to take action to correct them. Indeed, his lack of conviction is a major character point: he takes refuge in the rigidity of mathematical proofs, but finds he can’t even conjure enough faith to assume the axioms to be true – indeed, while contemplating the possibility of a higher power, he says he “prefer[s] this to the other options. And yet, it’s unsatisfying. I don’t like it. The proof, when I write it out, looks weak and flimsy.”

This is very internal horror, in other words, which is a good fit for the deliberate pace at which the plot doles out its revelations. For all that I think there was probably room for the climax to go a bit bigger and provide a sharper contrast with the slow-burn of the rest of the story, I found those middle bits, where Pierce knows more than you but not enough to be able to make sense of what’s happening, very effective. I’m no more eager to revisit A House of Endless Windows than I am that clip of a ghost walking down the hallway, but I think it’s going to stick with me just as long.

It’s not often that I’m stymied by a piece of IF – especially not one as slight and apparently straightforward as Return to Home. This short parser game starts with your car blocked by an unexpected detour on your way back from work; rather than drive around to find another route, you decide to cut through the countryside and walk home. This isn’t a perilous adventure where you need to cross raging rivers or make your way through a forbidding forest – there’s a hill, sure, but the weather is fine and the danger is non-existent. Nor is it a set of brain-teaser, with no puzzles to speak of beyond a couple of Easter eggs to be found if you stray slightly off the short path home (the whole game is about a dozen rooms). Structurally, it resembles a so-called “walking simulator”, but where games in that genre balance their mechanical simplicity with detailed backstory and lush environments, Return to Home is matter-of-fact; most descriptions have a sentence or two of simple prose, without much in the way of scenery, and there’s no lore or hidden trauma to pick up on (or if there is, wow did I miss it!)

So it’s hard for me to evaluate the game’s success according to its design goals, since I have a hard time articulating what I think those are – it seems content to just be a low-key experience, not in a hurry to impress anything in particular on the player. There are some small grammar and spelling issues in the prose, but English isn’t the author’s first language, and since the writing isn’t reaching for the stars I didn’t find these minor slips had much impact on my enjoyment. The one thing I can say about Return to Home is that I think it’s a game that enjoys that it’s IF. Most of the Easter eggs point to classic-era games (I picked up references to Curses and Once and Future/Avalon, though there were a couple I know I missed), and beyond that, by stripping the parser game down to its bare essentials, it made me slow down and be more mindful of what I was experiencing: moving through a map, reading a few sentences of narration, enjoying the way that a minimum of effort would frequently turn up a new bauble, without needing to worry about what I was supposed to do with it. Playing Return to Home was a gentle way to spend five minutes connecting with as unpretentious a piece of IF as you can imagine, and I guess that might just be the entire point of the thing.

It’s a truism that RPG sessions are often way more fun to experience than they sound when you describe them to people who weren’t at the table. And it’s a truism because it’s true – even I, gentle reader, have seen an interlocutor’s eyes glaze over while telling them some totally awesome story about the Satyr I played in this Changeling game back in undergrad. Descriptions that sound great when improvised come off flat when it’s part of a presumably-rehearsed narration. Out-of-character friendships liven up the banter that can feel lame shorn of that context. The drama of uncertainty, of not knowing which way the dice are going to fall or what lurks behind that nondescript door, is way more intense to experience first-hand than hear about second-hand.

(Seriously, though, Harry Dedalus was the coolest fae in the San Jose Court, the stories are great).

The Sword of Voldiir is a choice-based game that touts its origin in a tabletop DnD campaign, and it’s a case in point. It’s definitely got some shaggy charm, with a cast of NPCs who seem to enjoy hanging out and razzing each other, and solid pacing that keeps the narrative ticking along. But the fantasy world and quest plot are mostly generic, the RPG-inflected mechanics aren’t that engaging, and the whole thing, especially the prose, is in need of some polish – I only played the free demo rather than shell out for the full version, so perhaps there’s a significant uptick past the parts that I was able to play, of course. But while I definitely would believe all the original participants of the tabletop game had a great time, on this evidence you kind of had to be there.

I’ll take my first and third critiques together, since they wind up reinforcing each other. While there are some flashes of originality in the character creation section – the races on offer are human, half-elf, and siren – the setup is one you’ve definitely seen before, with your character hired on to accompany three NPCs on a mission to recover the titular artifacts: the reasons, and its powers, are underexplained, as are the personalities of your crew (there’s a sidebar with some biographical info: the first one’s “quick-witted, smart, and conniving,” while the second is “intelligent, rather quiet, and alert”. The poor fighter, meanwhile, just gets some middling backstory, with no actual characterization listed. The story does go through some twists and turns, but there’s little narrative groundwork laid, so it can came off feeling like just one thing happening after another, and each incident is a trope you’ve definitely seen before (the one exception is the bit where you’re able to track down a bandit because she gave her real name, and declared the magic items she was carrying to customs, upon entering a city).

The classics are classics for a reason, of course, but making them sing is down to execution, and here’s where the omnipresent typos, eyestrain-inducing dark-red-on-black color scheme for links, and leaden prose prevent Sword of Voldiir from going down as indulgent IF junk-food. There’s just a little too much friction, a few too many details that jar – like the party members setting up a fire in the middle of an enclosed cave without worrying about smoke inhalation – and a few too many scenes that seem to be included out of a sense of obligation rather than because there’s anything compelling about them. Here’s a sequence where you check in on a companion after arriving at an inn:

“What have you been up to?”

“People watching.” She nods to the people sitting all across the dining room. “Interest folk who come here. I always enjoy watching them.”

“That’s fair enough. Have you seen anything interesting?”

“Plently.” She lets the conversation die there.

(There’s a pick-which-NPC-to-spend-time-with mechanic that appears that it eventually leads to a romance – I played the field to try to get to know all of them a bit, so in fairness it’s possible that if I’d stuck with one they’d start opening up a bit more).

As for the second item on the bill of particulars – I like RPG-style mechanics in IF, but Sword of Voldiir’s implementation doesn’t leave much room for the player. You do get randomly-rolled stats for your character, which I dig, and they do influence how some of your decisions play out, as well as coming to the fore in a couple of combat sequences. But their impact is obfuscated, as dice are only rolled behind the scenes, and your role in fighting is just to pick whether to use magic or weapons at the outset, with no information given about the options, and then click through turn by turn to see whether you die. There are various ways to make these kinds of mechanics legible to the player, from the simple expedient of showing the results of die-rolls, to graying-out options that aren’t available to you due to your build, or signposting where you’re getting more information because of a skill or background – and the RPG elements of the game would be stronger if some of these strategies were pursued. Heck, even the non-RPG bits suffer from a lack of player agency, with many choices literally coming down to picking which of three doors or passageways to go down, sans any context to make this anything but a stab in the dark.

Like I’ve said, all of this is stuff that would be eminently forgivable if it came up around the gaming table on a Thursday night – all the players would know what was going on at the system level, the low-key world building and action-oriented plot could make for a fun beer-and-pretzels experience, and the fact that the characters all talk about being “stoked” and curse a lot would just be an indication that the group is unwinding after a long day at work. Even the choose-a-door-any-door bits would indicate someone is about to have fun doing some graph-paper mapping! But it’s hard to make a tabletop campaign work as IF without deeper-seated changes than what Sword of Voldiir has to offer; adaptation, rather than direct translation, is what can breathe life into old grognard stories, and there’s not quite enough of that on offer here.