Reviews by Mike Russo

The rise of choice-based games to co-equal status alongside their parser cousins has had a lot of positive effects, in my view, among which is an understanding of the fact that under the hood parser games also operate on choice-based logic: the unlimited freedom of text input hides the fact that a game will only accept a limited, pre-programmed set of actions, which can then be likewise applied to a limited, pre-programmed set of objects. This isn’t to say that there aren’t real differences, as anyone who’s ever cursed at a guess-the-verb challenge in a parser game will attest, but it’s an interesting viewpoint that interrogates the conventional wisdom.

None of that applies when you’ve got a game based on riddles, though – sure, there are only a finite number of words in the English language, but if an author doesn’t implement all of them, that doesn’t undermine the illusion of mimesis: that just means there’s one right answer and a whole whole lot of wrong answers, and suddenly the parser really can offer a whole world of possibility. Of course, building your game around riddles is a risky move exactly because of this. While a wonky puzzle in the medium-dry-goods tradition might see a player shoving all sorts of odd objects at NPCs to see if they’ll accept a swap, or one focused on complex Myst-style machinery might lead to pushing and pulling of levers at random, there’s no way to attack a riddle via trial and error or make slow progress by solving other puzzles and clearing out your inventory first. A bad riddle will leave the player frustrated and running to the hints, grunting out “I never would have guessed that” as I seethe.

Yurf is a one-word parser fantasia that dares to run that risk, and I think mostly succeeds despite it boasting its share of bumpy patches. You’re a nameless faceless etc. adventurer journeying around an Alice-in-Wonderland-inspired kingdom in search of four card-suit-themed jewels, in order to – well, despite having played through the game twice (since completing it a first time unlocks a “boss mode” that remixes some of the puzzles), I confess I couldn’t quite tell you, though it seems to have something to do with unlocking a vault and reuniting the king of the day with his estranged spouse, the queen of the night? To say that the plot isn’t the point isn’t to undersell the enjoyable whimsy with which the world is sketched, though: although the broad outlines are familiar, down to specific quotations of Lewis Carroll, the various characters and environments are drawn with verve, from the mathemagical neighborhood where number is all, to the slyly grumpy tree, to the pirates plying the space-lanes between the earth and the moon. The sad-sack king is a particular highlight: you first meet him crying his eyes out while being force-fed pies, because, as he says, “having banished the Queen, I’m getting just desserts.” The parser puts a cherry on top of the gag, too, in how it expands your command CONVERSE to CONVERSE WITH THE WET WEEPING MOUND THAT IS APPARENTLY THE KING.

Speaking of that parser, as mentioned it only takes one word – all actions, no objects. That means that there’s only ever one thing you can examine, or one character you can converse with, at any location. Aside from compass navigation, those commands are in fact most of what’s available to you, save for a few special commands reflecting expanded abilities from obtaining some inventory objects. It works cleanly enough, but it’s not really enough to hang a puzzle around, which is where the riddles come in. Except for a few straightforward places where using the aforementioned items allows you to progress, most of the obstacles you encounter require you to answer some kind of riddle – helping an artist-cum-engineer decide what kind of bridge to build, say, or editing a bit of doggerel to become a compelling love poem. Some of these are quite good – I especially liked the first of the math-based puzzles, which puts a numeric twist on the hoary old “one guard lies, one tells the truth” gag – though others, predictably, were too out-of-the-box for me to figure out without a hint (I still don’t really understand how the solution to the Air to the Throne’s riddle is meant to work). But the good ones predominate over the wonky ones, enough so that I continued on to play through that second quest – it disables hints, though if anything I found the riddles a bit better clued the second time round, with the exception of that %$#@ Air guy.

Beyond the occasional wonky riddle, I did find a few bugs – most notably, I was able to sequence break since the game allows you to burn stuff before you find the tinder box that notionally unlocks the ability. I was still able to complete my playthrough, though, and I actually found that contributed to the enjoyably topsy-turvy vibe of the game. That lovely atmosphere, combined with Yurf’s ability to pull off those moments of inspiration where you come up with the answer to a riddle out of thin air and marvel that it works, makes for a pleasant sojourn in Wonderland indeed.

I’ve never dug that deeply into Text Adventure Literacy Project games, mostly just because I’m already fairly overcommitted when it comes to IF, so it’s interesting to see a game initially intended for that event crop up in ParserComp instead, if only to provide a look at how one veteran author might introduce IF to new players. Beyond its well-implemented tutorial, The Samurai and the Kappa provides a few simple but mostly appealing characters, manageable medium-dry-goods challenges, a world that’s enjoyable to explore, some slightly ill-fitting logic puzzles, an old-school maze that’s not too hard to flail through with trial and error, and a happy ending – seems like a pretty good way of getting your feet wet to me.

You play a Tokugawa-era samurai era who’s fed up with life as a courtier and has take to wandering the countryside looking for work. After spending the night in a small village inn – the business of paying for a room, taking a bath, having dinner, and retiring for the night constitutes the tutorial section – the plot kicks in when you’re approached by a peasant who asks for your help rescuing a kidnapped child from an evil turtle-spirit. There’s a nice mix of historicity and fantasy to this premise; the Kappa’s folklore feels authentic, and SAK does do a good job of weaving in period-appropriate detail so that the world never feels generic and rewards poking at the scenery. Admittedly, it wears its research a bit heavily – implementing three separate pieces of your clothing feels a bit much, and while I enjoyed the density of scenery, some of the descriptions feel like they could have come from a textbook:

The shimenawa is a special rope that’s woven from hemp and tapers towards each end. It’s suspended below the rafters of the haiden to denote its sanctity or purity.

Still, I enjoyed the care taken with the game’s setting and atmosphere, so this is a mild complaint.

The process of rescuing the child is enjoyable too. You need to learn the kappa’s weaknesses from several characters across the game’s small map, and while dialogue is mostly kept short and to the point, they respond to a wide variety of potential topics. For the most part progress depends on solving two puzzles – there’s a Nurikabe, which is a sort of Slitherlink or Picross-style exercise in coloring a grid, and one traditional logic grid. The game’s itch.io page provides feelies to make solving them more convenient. I found them satisfying to work through, though writing down all the different clues and then alt-tabbing into a logic grid tool to laboriously work through them did take me out of the story. The final set of challenges are resolutely in-game, though, and focus on taking advantage of what you’ve learned about the kappa’s likes and dislikes, and even when these are a bit esoteric, I never had any trouble getting the parser to understand what I was saying.

…and I really wish that I could end this review here, saying that SAK is a fleet, puzzle-focused adventure with nice period details and a pleasant story. Alas, I can’t end the review without addressing the inclusion of one disastrously ill-advised bit of content. The game earns its “adult content” content warning by virtue of your interactions with Mokuko, the maid who works at the inn in the tutorial section. When you first enter, the innkeeper suggestively indicates that you can avail yourself of some extra “service” for one additional silver coin. The implication is made clear when, after your meal, Mokuko asks “if you require any extra ‘service’.” As far as I can see there’s no option to simply decline the invitation – the tutorial text butts in here to say “when someone mentions something interesting, you should ask them about it. In this case, ASK MOKUKO ABOUT SERVICE.” And when you do, well:

Mokuko parts the folds in her kimono in a suggestive manner to reveal the cleavage of her petite breasts. The poor girl looks like she’s barely out of puberty.

You see, this is Mokuko’s description:

Mokuko is very pretty, but she looks too young to be a maid. You wonder how old she is.

And when you ask her about her age:

“I’m 16 sir, but I’m very experienced.”

It’s a small mercy that you don’t have the option of going to bed with her, as you automatically decline politely and go to bed. Any relief I felt at that point was undone by the fact that the game then told me that I had a hard time getting to sleep because of the noise from the guest next door having sex with his maid (per the author this is meant to be a brand-new character, but as this other maid is never seen or mentioned in the game I had no idea she existed and assumed Makuko was serving the other guest as well).

So this is a game that forces you to think about the sexual exploitation of a 16 year old girl. And it gets even worse – I think there’s a reasonable implication from the excerpts mentioned above that Mokuko is lying about her age, and she tells you this if you ask her about herself:

"I’ve been working here for two years. I’ll make sure you have a pleasant experience in our humble little inn.”

So actually this is a game that forces you to think, at minimum, about the sexual exploitation of a 14 year old girl.

I am really at a loss to understand why this is here. Is it the case that maids at roadside inns like this engaged in sex work, that they were pimped out by their innkeepers, and that they were sometimes teenagers? I’m no expert on the period here, but I’m certainly willing to believe it. Authenticity is certainly no reason on its own to have included something like this, though – the setting here departs from reality in innumerable ways, and reflects the author’s editorial judgment about what to include and what to elide. And it’s not as though this is a plot element that has any narrative significance or connection to the rest of the story in any way; it’s just a throwaway incident that’s the definition of gratuitous.

I’m no prude and I’m not opposed to “adult” or sexual content in IF by any means. But there are certain topics that, if you include them in your game, now your game is about them whether you want them to be or not. I can certainly imagine playing a game that engages with this topic in a nuanced way and creates space for Makuko’s subjectivity, but this is the Samurai and the Kappa – no room for her here. At best, the child sexual abuse is meant to be an interesting historical detail and a way of underlining the manly self-restraint of the protagonist, while at worst it’s meant to function as an enjoyable moment of titillation. Either way, it was a profound mistake to include it, and it comprehensively soured me on the rest of the game.

It’s unfair to Project Postmortem to compare it to The Mysterious Cave, a pretty-but-buggy Adventuron game that consists of one basic puzzle and takes five minutes to play. I didn’t run into any bugs in this tale of academic skullduggery, and while the plot is neither especially novel nor robust – you’re tasked with tracking down a report showing that the research underlying a thesis with big economic potential was falsified, and then need to escape the vengeful postdoc when he comes gunning for you – it at least exists to provide a motivation for the action. The custom parser works well enough, modulo some slight infelicities of implementation, like few objects having descriptions and OPEN FOLDER getting the response “you can’t open the folder” while X FOLDER gets you “You open the folder and skim the contents…” And there are some pleasant features to counterbalance those small bits of awkwardness, like a fun menu-based system for interacting with computers that winds up pivotal to the game’s puzzle.

There’s the similarity and the awkwardness, you see: this is another one-puzzle game (maybe one and a half if you count “unlock the filing cabinet with the plainly-visible key”). The puzzle itself is okay, I suppose – you need to create a distraction to slip through the fingers of the blood-crazed academic, taking advantage of some cutting-edge capabilities of the computer network (Project Postmortem appears to be a nineties period piece, so don’t get too excited). It’s not especially challenging, since there aren’t any red herrings or potential alternate paths to throw you off, and it’s a bit silly that even if you don’t quite get the timing right, you can try again with no penalty, but it’s hard to fault a game for being merciful. Still, between the short playtime, the straightforward gameplay, the underdeveloped plot, and the unremarkable prose there’s as little here to praise as there is to condemn; as one episode in a larger thriller, I might consider it an effective setpiece, but it’s not really up to the rigors of standing on its own.

Free Bird’s blurb conveys at best a profound ambivalence about its value: of this short game functioning as a proof-of-concept for a Python IF system, the author says “I never liked it very much,” admits that “the program is inferior to Inform and other parser game creation tools in almost every way”, and closes by saying “I wouldn’t recommend this game or my attempt at a Python interactive fiction ‘library’ to anyone.” Oh, and unlike any of the myriad Python-based IF games I’ve wrestled with, the installation instructions flat-out tell you “it’s not user-friendly.”

Well, that last part is indubitably right – despite my aforementioned track record of snake wrangling, it still took me a solid fifteen minutes to figure out how to get it running (protip: you don’t need to download anything manually to install the required PyGame library, just type in the command prominently featured on the website and Python will take care of the rest). And it’s not surprising to me that one person dabbling at a project can’t rival the multiple decades of effort that have given rise to the Inform ecosystem – I’m not at all qualified to assess how well it works as an authoring environment, but while the system here boasts a reasonably solid parser it also has some foibles even once it’s up and running. The text was blurry on my machine with no obvious way to sharpen it, the scroll function didn’t work for me on either keyboard or trackpad, and the innocuous command SING TO KEY seemed to crash the game, for example. It’s better than many custom systems I’ve played, but there was never a moment where I wasn’t thinking “I wish I were playing this in Inform or TADS.”

On the flip side, though, I wasn’t thinking that just because those languages are more robust, but because I was having a good time with Free Bird and would have preferred it if the author had had more time to flesh out the content rather than work on building a new platform. Often in this kind of situation the demo game is an afterthought, a bland bit of dungeoneering crafted as a showcase for the world’s blandest medium-dry-goods puzzles. Not so with Free Bird, which starts as its protagonist – an immortal avian spirit – is freed from a millennium-long imprisonment by the slow passage of time finally eroding away the runes by which it was bound by a long-dead sorcerer. It’s an evocative setup, rendered in evocative language – I couldn’t copy and paste the text so you’ll largely have to take my word that the prose is really good, but I did jot down the phrase “they chained you in a miserable cell of bitter iron” as a representative example.

Beyond the setup, the puzzle-solving also has a distinctive flair: as implied in my crash-bug report above, since you’re a bird-god, your primary way of interacting with the world is through your songs. Weak as you are, SINGing at a particular object might only give it the weakest of shakes, but these small tweaks and nudges, properly deployed, allow you to navigate a compellingly realized set of ruins. The puzzles here are all ones a seasoned adventurer will have seen before, and the general environment is of course likewise familiar, but there are lovely details that put an endearingly novel spin on even so hoary a chestnut as obtaining a light source. While the game does lose some steam at the very end – after a paid of well-done puzzles where you learn some backstory about your captor and reclaim a greater measure of your magical power, the final sequence just sees you unlock a door with a key to reach an abrupt victory screen – it definitely still left me wanting more. As a proof of concept for Python as a major-league IF platform, Free Bird is, as advertised, a failure, but as an indicator of its author’s skill at making games, it’s a secret success.

It is nothing short of miraculous that Andrew Schultz has now made eight large, robust games centering on a very specific bit of wordplay that, to my knowledge, no one else has ever picked up on: transforming one two-word phrase to another, rhyming one by substituting a different initial phoneme (as in the b-to-g swap in the title). What’s more miraculous is that, though as always I struggled with it and there are some noticeable bugs, it might actually be my favorite of the bunch?

The gameplay here is much the same as previous installments: after a framing plot establishes stakes, you’re turned loose on a medium-sized world stuffed to the gills with the aforementioned rhyming pairs. The name of each location usually provides the starting blocks: typing in a successful rhyme for that might bring a new object into the scene, give you an inventory item, open up a path to a neighboring area, or just give you brownie points that allow you to skip a puzzle when you get stuck. Items and characters also usually can be poked at through the wordplay mechanic, allowing you to progress still further. There aren’t any traditional parser actions implemented besides movement, keeping the game focused on what it does best, and as per usual there are a large variety of hints, help functions, and other supports that let you know when you’re on the right track with a rhyme, list out common English sounds if you’re stuck for something else to try, and let you know when you’ve exhausted all the essential tasks in a particular area. This is a gameplay structure that can be quite challenging – after an hour, I find I’m muttering nonsense to myself as my brain leaks out my ears – but the games always go out of their way to be friendly to the player, the hitting on an unlikely rhyme that the game recognizes, and uses to spin a good joke, is delightful.

BBGG is a standout in the serious because of its the theme: this time out, you’re a gnome tasked with assembling the fixings for a feast, and you’ve got a checklist of foods and utensils guiding your progress. Beyond being pleasing in its own right, the theme also helps keep the various events that happen from feeling too unmoored from each other – in previous games in the series, it sometimes felt to me like the consequences of successful actions were essentially arbitrary, determined more by a syntactic validity than any other logic, but this time out there’s reason to go with most of the rhymes. The theme also helps guide your guessing in more productive directions: if you know you need to find some salad, it’s easier to jump to CHOOSE CHARD from LOSE LARD (not a real example, obviously that would be a terrible puzzle).

Unfortunately, in its current form BBGG is more than a little buggy. These games often see multiple updates and releases, so I’m confident they’ll be ironed out eventually, but for now, I found a couple of places where obvious placeholder or bug-testing text got spat out in response to what I thought was reasonable input, and the hint system seemed to get a bit confused in places. Most problematically, I also hit what I think is a progress-blocking bug that blocked a valid answer from being successfully processed, meaning that I couldn’t enter the endgame (Spoiler - click to show)(I couldn’t get the game to accept SPOON SPIED, even after I’d primed the GOON GUIDE with PRUNE PRIDE, which per the walkthrough should have been all that was required). Still, by that point I’d had a solid couple of hours of fun, and these aren’t the kinds of games where seeing the plot conclude is a major draw – much like a meal, the enjoyment is in the process of consuming it, rather than in getting to the end.

“Your goal is to navigate through the forest, solve puzzles, interact with characters, and ultimately discover the truth about your identity,” claims the blurb for The Mysterious Cave, and none of that is technically untrue. You do navigate through a forest – though the map is only four locations connected by a linear road, so this is less compelling than you’d think (there is some nice art, though, par for course for an Adventuron game). As to the next bits, they plurals are a bit misleading, since it’s more the case that you solve one puzzle and interact with one character: the only objects that are implemented are a tree and the mushroom growing on it, and the only character is a nameless guardian barring your way into the eponymous cave who monologues that he’s hungry when you examine him, and the only way of interacting with him is to solve the one puzzle, which is giving him the as-it-turns-out-poisoned mushroom to knock him out (I suppose “don’t eat the obviously sketchy mushroom” might qualify as an additional half-puzzle). And once you go past him and enter the eponymous cave, the game does say you now remember who you are – but it ends before it deigns to let the player in on the secret.

So much for truth in advertising, but bar the admittedly-lovely pixel illustrations, it’s very hard to find anything here to catch a player’s interest; the gameplay, as discussed above, is about as minimal as a work of IF can attain, there’s almost no flavor text to speak of, and despite how stripped down it is there are still some noticeable bugs (the game starts with an Adventuron setup error message, there are typos in the first location’s description, and the guardian keeps saying he’s hungry even after he’s unconscious – maybe he’s talking in his sleep?) As an exercise to learn a new authoring system, I can see the value here, and the presentation really is nicely done, so I’d be happy to play a full game from the author, but the solution to the enigma of the cave is that it’s just a glorified tech demo.

The legends surrounding King Arthur loomed large to the medieval mind: as the so-called “matter of Britain”, they made up one of the three primary literary canons of the Christian world, using an idealized world of chivalry to reflect on humanity’s weaknesses and the pursuit of the divine. Today, of course, the social milieu of the original stories is quite foreign to us, but there’s still a fascination in the tragic fall of Camelot, a mythic frisson from coming close to a strand of culture that’s so old, and meant so much. So I was excited to learn that the eponymous blade in Return of the Sword is Excalibur; your nameless protagonist is tasked with recovering it and returning it to the Lady of the Lake, tying off a loose end in (some versions of) the myths and participating in the cycle of death and renewal to which they allude.

I was less excited that I didn’t learn this from the blurb or intro text of the game, though, but rather by reading an unprepossessing letter that was in my starting inventory; you need to check out the optional lore documents to reveal that the artifact you’d been commissioned to find for the batty coot who hired you is fricking Excalibur! Said coot, the memorably-named Jedediah Strangeblossom, gives you the job because you did a solid for his friend, who’s got the still more implausible name Ezekial Throgmeister: this, I think, is a reference to the author’s 2022 IF Comp entry, The Alchemist, and in fact Return of the Sword shares more than a few similarities to that and other games he’s made. It’s written in the author’s custom system, for one thing – it’s retro-looking but fairly solid, with a robust parser, some nice though unnecessary bells and whistles like custom macros, and one longstanding foible which is that you need to take items out of containers before you can examine or otherwise interact with them. For another, it boasts a magic system that seems a close cousin of the one from 2023’s Have Orb, Will Travel, aping not just the memorize-from-spellbook-then-cast system but even the names of particular spells. The structure also echoes the hub-and-spokes designs of those other games – here there’s an underground chamber with a dial that allows you to pick one of five different standard adventure-game settings to teleport to (a castle, a cave, a church…) once you unlock each with a different plot-token coin. And the puzzles, which are a mix of codes, object manipulation, and spell-casting, are all old-school in design but vary from bluntly telegraphed to fiendishly recondite, just as in those previous entries in the loose series.

While I generally had a good time with the Alchemist, and thought there were some high points in Have Orb, Will Travel, Return of the Sword worked less well for me. Some of this, I think, could just be familiarity breeding contempt – there’s a charm in the author’s sensibility, but it’s not my favorite aesthetic, and even for those who enjoy this stuff more, surely just referencing Adventure’s Witt’s End without an accompanying joke or subversion feels pretty stale. Some of it could be the puzzle design, which wrong-footed me enough times – as with the pin that’s clearly meant to attach two wheels, but which won’t work unless you use trial and error to rotate the wheel into the single configuration where it’ll fit, with no clues provided or even an indication of what exactly is going wrong – that I probably wound up overusing the hint system even for solvable conundrums. And some of it is surely due to the game’s general unpolished and loosely-designed vibe: there are unmarked exits, parser oddities I don’t remember in the author’s previous games (UNLOCK DOOR WITH KEY indicates it doesn’t fit, but simply UNLOCK DOOR opens it up in a jiffy), two of the four spells in your spellbook appear to be useless, and there’s a room that includes an “escritore” as part of its furnishings but of course no such thing is implemented, it’s just a typo for “escritoire.”

The biggest issue I had with it, though, is the way it squanders what could have been a compelling, elegiac premise. The cavalierness indicated by putting the backstory in a missable infodump continues to the game’s kitchen-sink fantasy milieu: besides the aforementioned Colossal Cave easter egg, you find a complex electronic scale system in a clergyman’s vestry, solve a riddle straight out of Tolkein, and have as your key nemesis not Mordred or Morgana, but instead a Hammer Films vampire. Far from being an Arthurian game, that’s just one of a dozen flavors sprinkled over the staid gameplay, with little concern for cohesion apparent anywhere. The overall effect is of an overcaffeinated teenager running a marathon DnD game for their friends – they’ve long since outpaced their prep, so now they’re just throwing any nerdy stuff they can think of into the pot. In fairness, that’s not too far off of how the Arthur stories got their start, with a variety of authors taking the basic story framework and adding various bits of previously-independent legends to create enough unmotivated crossovers, dubious retcons, and long-delayed sequels to rival the MCU. But even at their bouillabaissiest, effective writers in that tradition stuck to the key themes: this is just a mishmash, and the puzzles aren’t enough to save such a muddled narrative.

Dear reader, I must make a confession: I am not at all good at the hard-as-nails old-school throwback adventures that seem to be the predominant offerings of the current ADRIFT scene, and while I respect that different folks enjoy different strokes the vibe is generally too masochistic for me to enjoy. But then every once in a while, I’ll be playing a game like Race Against Time and think to LOOK UNDER a piece of furniture only to find that there is a hidden keycard down there and I’ll feel a little reward-jolt, and I kind of get it: a view of the pleasures that could be mine if I were king of the pixelbitchers.

I’m not, of course, and it didn’t take me too long to get out of my depth, but the game is agreeable enough about offering hints and keeping things zippy. The plot is standard text-adventure stuff: there’s a deadly plague loose on a space station, and only you are a bad enough dude to plumb its charnel halls and set off the self-destruct mechanism. There aren’t any twists or living characters on offer, so it’s strictly a medium-dry-goods affair, with a classic set of numeric keypads, powered-down elevators, locked chests, and broken mechanisms standing between you and victory. The map is relatively contained and straightforward to navigate, and the threatening atmosphere is established through efficient prose and a minimum of unnecessary detail, which helps keep things focused on the puzzles – because you’ll have to EXAMINE, SEARCH, and as mentioned, LOOK UNDER every implemented object to make sure you’ve got what you need to progress (the game politely informs you of this fact, at least).

Most of the game’s obstacles are pleasingly organic – by which I mean they seem like natural consequences of the situation, like a mechanism being bent by a scientist’s death throes, though there is a door blocked by a crush of bodies, now that I think about it. A few do feel excessively gamey, though, most notably (Spoiler - click to show)Dear reader, I must make a confession: I am not at all good at the hard-as-nails old-school throwback adventures that seem to be the predominant offerings of the current ADRIFT scene, and while I respect that different folks enjoy different strokes the vibe is generally too masochistic for me to enjoy. But then every once in a while, I’ll be playing a game like Race Against Time and think to LOOK UNDER a piece of furniture only to find that there is a hidden keycard down there and I’ll feel a little reward-jolt, and I kind of get it: a view of the pleasures that could be mine if I were king of the pixelbitchers.

I’m not, of course, and it didn’t take me too long to get out of my depth, but the game is agreeable enough about offering hints and keeping things zippy. The plot is standard text-adventure stuff: there’s a deadly plague loose on a space station, and only you are a bad enough dude to plumb its charnel halls and set off the self-destruct mechanism. There aren’t any twists or living characters on offer, so it’s strictly a medium-dry-goods affair, with a classic set of numeric keypads, powered-down elevators, locked chests, and broken mechanisms standing between you and victory. The map is relatively contained and straightforward to navigate, and the threatening atmosphere is established through efficient prose and a minimum of unnecessary detail, which helps keep things focused on the puzzles – because you’ll have to EXAMINE, SEARCH, and as mentioned, LOOK UNDER every implemented object to make sure you’ve got what you need to progress (the game politely informs you of this fact, at least).

Most of the game’s obstacles are pleasingly organic – by which I mean they seem like natural consequences of the situation, like a mechanism being bent by a scientist’s death throes, though there is a door blocked by a crush of bodies, now that I think about it. A few do feel excessively gamey, though, most notably . But this is part of the draw for people who like hard puzzles, I think – thinking “what would make sense in this world” will get you started on most of them, but the target audience probably thinks it’s an advantage to have a few challenges where you need to think creatively about your inventory without being too fussed about narrative plausibility. All told I got through about the first half of the game while using only a few hints, but had regular recourse to the walkthrough after that, which feels reasonable for the genre.

The implementation is likewise a mixed bag; I didn’t run into any bugs, but there are some nice conveniences, like a type-in-the-date puzzle that allows you to use either US or European date/month conventions. But while it’s nice that there’s a simple UNLOCK command, I only realized that would work after spending five minutes trying and failing to type stuff like SWIPE GREEN FOB KEY ON EASTERN FOB READER in a way the parser would understand, stuck in disambiguation hell.

I’m ending this review with a conventional copout that I really hate: if you like this sort of thing, this is the sort of thing that you’d like. Race Against Time is too challenging, requires too much unmotivated trial and error, and offers too little to players other than pure puzzle-solving gameplay to recommend to people outside its target audience. But it is sufficiently well put together to give a lay player a sense of the appeal of this style of game, I think, which is not always guaranteed. But this is part of the draw for people who like hard puzzles, I think – thinking “what would make sense in this world” will get you started on most of them, but the target audience probably thinks it’s an advantage to have a few challenges where you need to think creatively about your inventory without being too fussed about narrative plausibility. All told I got through about the first half of the game while using only a few hints, but had regular recourse to the walkthrough after that, which feels reasonable for the genre.

The implementation is likewise a mixed bag; I didn’t run into any bugs, but there are some nice conveniences, like a type-in-the-date puzzle that allows you to use either US or European date/month conventions. But while it’s nice that there’s a simple UNLOCK command, I only realized that would work after spending five minutes trying and failing to type stuff like SWIPE GREEN FOB KEY ON EASTERN FOB READER in a way the parser would understand, stuck in disambiguation hell.

I’m ending this review with a conventional copout that I really hate: if you like this sort of thing, this is the sort of thing that you’d like. Race Against Time is too challenging, requires too much unmotivated trial and error, and offers too little to players other than pure puzzle-solving gameplay to recommend to people outside its target audience. But it is sufficiently well put together to give a lay player a sense of the appeal of this style of game, I think, which is not always guaranteed.

I am, generally speaking, an optimist. Some of that’s just the fruit of being born with a lot of privilege and a brain that knows what to do with serotonin, I suppose, but it’s also by choice: many years ago I came across a bit of Karl Popper arguing that nobody knows what the future will bring, or what will move it one direction rather than another, so we have an obligation to hope for a better world and act as though the little things each of us can do might bring that hope a bit closer to reality. That was persuasive to me and so I try to live into it, but I’ll confess that some days it’s harder than others, like for example the end of Supreme Court terms and when I play a Perplexity game.

I’ve been reviewing games using this engine since 2021 – this is the fourth, by my count – and while the pitch for a parser system that allows the player to use natural language input remains compelling, the reality is still so stubbornly far from the promise that reader, I begin to despair. Like you’re told your goal here is to order lunch at a diner for you and your vegetarian son, but when you say to the maître d’ “I would like to get some lunch,” the game butts in to say “I don’t know the words: lunch.” That’s small beans compared to this exchange with the waiter, though (the question marks are the prompts for player input):

?:my son is vegetarian

my son is not veggie

?:my son is veggie

I don’t know the words: veggie

?:my son does not eat meat

I don’t know the words: eat

Trying to couch your input as regular English sentences simply does not work – even as simple a phrase as ORDER TOMATO SOUP makes the parser throw up its hands in despair. What does work is single-word input: typing TABLE, MENU, SOUP to indicate what you want, which of course any existing parser engine under the sun can manage. It’s hard to hold this against the system, truly – natural language processing is quite difficult, from what I understand! But still, pushing the player to try to use complete sentences sets expectations the game can’t come close to living up to, while the blurb’s promise that it’s a good way for English learners to practice their language skills feels frankly irresponsible. Judged as a game, meanwhile, there’s basically nothing here – the only thing resembling interest is that you have a terrible waiter who needs too be reminded to hand you a menu and then prompted to tell you the specials – with no details to speak of and the world’s most basic prose.

In my previous reviews of Perplexity games, I’ve generally wrapped up saying some variation of “hopefully the system’s authors will keep fine-tuning things so it works the way it’s advertised to do,” but after three years, it’s hard for me to see any improvement on this front (at least the lag that I remember afflicting the earlier games appears to be a thing of the past). Perhaps it might be time to bring this experiment to an end? That’s maybe an unfair sentiment – and one certainly biased by the fact that the game doesn’t appear to end, so I spent a final ten minutes frustratedly typing BYE and LEAVE and I’M GOING and EXIT to the maître d’ who kept asking how he could help me today over and over like a robot – and I’d love to be proved wrong! But I’m not optimistic.

Oh, and the cover image is an AI-generated picture with myriad issues – beyond the standard-issue nightmare fingers, there are light fixtures hanging off of others, a double-handled coffee mug, an olive oil bottle standing in for wine, and a robot with only one eyebrow – and no attribution. Can we please stop doing this?

Quick, close your eyes. Now imagine the most prototypical adventure game puzzle you can think of – not any specific iconic one from the classics of yesteryear, nor the dreary ones you’ve done a million times like the get-the-key-out-of-the-keyhole bit, just the Platonic ideal of a classic text adventure puzzle. Once you’ve got it, you can open those eyes (how have you been reading this?)

This exercise doesn’t admit of wrong answers, of course, but I’d submit that there’s a single most-right one: there’s a monkey, and you need to give him a banana so he’ll give you his wrench. I don’t think I’ve encountered this specific scenario presented quite so baldly before, but when I ran across it in Mystery Isles, I recognized its totemic power. And in fact the whole game is like this, in its stripped-down, old-school-yet-friendly glory: you could call it Text Adventure: the Text Adventure and wouldn’t be far off. You’re marooned on a desert island, you see, and to escape you’ll need to construct a makeshift torch, unearth pirate treasure, climb a tree, and offer up multiple food items as bribes (it’s not just the monkey); it’s all presented in breezy, unadorned prose and will either take you forever – because there are a couple of puzzles that are real head-scratchers – or ten minutes, and fortunately there’s a hint function included so you can choose your own adventure on that front.

Much as I enjoy ParserComp as a space for experimentation, it’s also clearly a place to play the hits. Even given its limited ambitions, though, Mystery Isles could have stood for several additional rounds of polish, because the implementation is fairly rough. Beyond the aforementioned underclued puzzles – there’s a bit where hitting a big rock with a little rock turns the little one into a makeshift axe, which is not how flint-knapping works, and the business of how exactly you’re meant to get the banana out of its tree doesn’t give much for the player to go on, not even confirming the existence of actual bananas in said tree – there are plenty of niggles and small bugs. Items don’t always disappear from the inventory once used, once you solve a puzzle to obtain an object you might need to resolve it to pick them up again should you drop them, there’s a spurious north exit mentioned in the jungle description, and the hint function is welcome but gets a bit confused towards the end (Spoiler - click to show)(it kept wanting me to relight the torch after I’d already obtained the map, which I believe at that point was both useless and impossible).

This is a short game, so even game-breaking bugs are quick to recover from, at least, but the lack of any credited testers really shows: there is no parser game so simple that it can be credibly released without independent beta testing, in my experience. There’s a lighthearted simplicity to Mystery Isles, and a certain ramshackleness can be part of the charm of such things – only as I’m writing this am I wondering about the plural in the title, since there’s just the one as far as I could see – but classic premises and design don’t need to be matched by creaky implementation.