(This is a lightly-edited version of a review I posted to the IntFiction forums during 2023's IFComp).
There’s a longstanding tradition in parser IF that authors should eschew the generic USE verb. The conventional wisdom, which I ascribe to, is that there are two major reasons for this: on the player’s side, it removes much of the fun of playing a parser game if you can just mindlessly spam USE X or USE X ON Y without actually thinking through a potential solution, and on the author’s side, you wind up with one mega-verb that can function radically differently in different contexts, which can make debugging really tricky, and can paradoxically make implementation even more work, as the player might expect USE to work as well as whatever more bespoke actions might be needed to resolve a challenge. After playing CODENAME OBSCURA, a spy-themed Adventuron game that’s an intentional 80s throwback, I can adduce a third rationale for avoiding USE: I, specifically, am very bad at figuring out when to try it, such that I had to go to the walkthrough three separate times to figure out what I was missing, and each time it was because I’d attempted everything but USE.
Admittedly, I expect the Adventuron parser to be a bit picky in the best of circumstances, and in each case, it was immediately obvious what to do once I got unstuck, so I shouldn’t pretend my repeated oversights about USE were that much of a barrier to enjoying the game. It makes a winning first impression, efficiently setting up a silly James Bond plot (you’re a secret agent working for an organization called TURTLE, visiting a town in Northern Italy to foil the plans of a German Count who’s stolen a diamond from England and is in league with the Sicilian mafia) and charming with lovely, colorful pixel art. The picturesque opening quickly segues into an action set-piece and then a simple escape puzzle, before setting the player loose to tackle the meat of the game.
There’s a lot to do, from visiting a witch to infiltrating a costume party to breaking into the compound where the Count is building a doomsday weapon. The map is reasonably open, but there’s typically only one or two puzzles where you can make progress at any point in time, which could be frustrating if the game world was much bigger, but CODENAME OBSCURA just about gets away with it. Speaking of the puzzles, they’re typical medium-dry-goods affairs; there’s perhaps a bit too much repetition, with three different blocked-off areas requiring you to WEAR something and/or SHOW something to gain entry, and one sequence where you solve a puzzle to find a password which allows you to find a combination which allows you to find a code, but they’re generally straightforward enough – save for a computer puzzle that combines unclear instructions with a bit of timed text to make for a fairly irritating barrier.
Speaking of annoyance, that USE issue is a real one, however, and bespeaks a game that has a very particular idea of how it wants you to interact with it. There are relatively few actions implemented – despite sound being important at several points, the player can’t ever LISTEN – American spellings for common commands aren’t accepted (PET vs. PAT, PUSH vs. PRESS), there are lots of items that you can’t examine until you pick them up, and it wasn’t just the USE case where I had to play guess-the-verb (the worst offender was a bit where you have to manipulate a part of a statue, and only one very precise syntax will work). CODENAME OBSCURA also does the default-Adventuron thing of bluffing when you try to interact with or examine an object that’s not actually implemented – it just says “you notice nothing special” rather than admit it doesn’t know what you’re talking about – and then makes the problem worse by retaining that same “you notice nothing special” default description for several game-critical items. I suppose that thinness of implementation is part of the game’s intentionally retro vibe, but a bit more testing could have helped the author strike a better balance between that lo-fi feel and player convenience. Likewise, I twice ran into a bug that led to the game hanging and not accepting input; fortunately, I was able to simply reload the webpage and seamlessly pick up from where things went off-track, but it was nevertheless kind of a pain (that’s why I’m attaching three transcripts).
For all these complaints, I did enjoy my time with CODENAME OBSCURA; it’s a far friendlier old-school puzzler than The Witch, and it’s got more meat on its bones than Magor Investigates…, so it did scratch an itch – and I say that as someone who doesn’t have any nostalgic attachment to the old two-word parser games that it mimics. I’d say it needed a bit more time in the oven, but from the blurb it sounds like the author’s been working on the game off and on since 1987, which is quite the gestation period; still, a little more testing and refinement to sand off some of the unintentionally rough edges – and provide alternatives for the USE-allergic among us – would be quite worthwhile.