Reviews by Wade Clarke

Ring Sculptors is a sci-fi / cyberpunk gamebook IF released for Nintendo Switch in 2024. It's an adaptation of a Polish gamebook by Tomasz Kołodziejczak, an author and game designer of some renown in his country. The title rings are those around planets, and in this game, the player selects a character from a roster of various hacker and mercernary types, then becomes a pawn in the machinations of rival space guilds, the Ring Sculptors amongst them.

The lore of this world seems juicy and interesting. Aesthetically, the game is attractive, with AI artwork that already looks typical but effective, and which works because very few scenes ever have to be shown more than once. The broody and glitchy audio soundscape also works. However, mechanically, the game makes no affordances for the kind of gamebook it seems to be when translating those mechanics into playability in videogame format, resulting in high frustration and repetition.

Ring Sculptors's core style is of a hard Fighting Fantasy gamebook, though without all the physical combat. What this means is high danger, lots of ways to lose, lots of die roll stat tests, lots of high stakes choices, lots of unpredictable consequences for actions. This can all be great perilous fun in an actual gamebook where you can cheat or reroll or keep your thumb in the last page as much or as little as you like, but Ring Sculptors the videogame misses all this.

There's no UNDO or RESTORE. Each death means a total restart, including going through the big linear passage at the beginning that precedes even the character selection stage. The stat check moments present as metaphorical black boxes, short bars which fill up before reporting POSITIVE or NEGATIVE. POSITIVE means you succeeded, which has a counterintuitive duality in that when you're being tested for things in life, POSITIVE is usually bad. And what die was rolled versus your character's MIND, BODY or EGO scores? The game hides this. I couldn't get any sense of the probabilities involved, and therefore of the worth of increasing any stat by, say, just one point. And this is a game with die-roll bottlenecks that can basically pass or fail your entire session.

This world of warring guilds and neuroimplanted weirdos seems really interesting, and the story could get away with leaving most of it mysterious, but given that the player's mission comes down to one typical exploration of an abandoned outpost on one planet, the lore is being wasted.

There's also a time pressure mechanic in the planet section, but whenever I was asked to choose how much Oxygen to spend on a particular activity, I couldn't work out what happened. Either I didn't understand the interface, or it's bugged, or it's not actually a choice but an automatic drain of your stat in accordance with the duration assigned to the activity, in which case the amount involved should have been declared along with the choice (and probably was in the book version). The prose is also careless at such moments, referring to wasted time in a way that really makes it feel like it's the player's fault.

I can't compare the game to the Polish source material, but as a gamebook videogame, Ring Sculptors is a big miss which doesn't avail itself of any of the wiser choices made by previous gamebook to videogame translations. This is a shame because the Switch seems a good venue for this type of game. It was attractive enough to hold me for a few plays, then I realised I wasn't prepared to try again with so much pointless repetition and bottleneck randomness.

(This is an edited version of a review that first appeared in my IF blog during IFComp 2024.)

My clinical-sounding and admittedly cynical summation of House Of Wolves by Shruti Deo might be, "Depression Quest but shorter and with you forced to suffer at others' hands as well." I had predicted what kind of experience was ahead when the first choice I picked of three basically said, "You can't do that yet, pick a different choice." Then the second choice I picked said, "You can't do that either, pick a different choice."

This is a Twine piece with an unclear metaphor that could be about being completely depressed, broken and non-functional, hiding these facts from the world, and also being in an environment of zero care or flexibility, and where you are forced to go against your own wishes in terms of what you want to do, or when, or even what to eat. This manifests as having a round of chores to do each day, forced eating supervised by an unspecified They at night, and the visiting of three other storylets on the way.

The storylets were the best parts, I thought, because they offered specificity. They approached character and situation. Learning, friends, college, those kinds of things. Returning to the House Of Wolves at night returns the prose to a pained but too generic dirge of hopelessness. That is what I most disliked about this piece in the end, its non-specific version of all-out hopelessness. I have made this same criticism of many other works of this type over time.

I don't understand the wolf metaphor of the title. It would be disingenuous of me to say I have no idea what it could be about. The trouble is it, and the work, could be about almost anything. Conformity. Vegetarianism. Mental illness. Abusive families. Society. Hunting (wolves hunt). Pack mentality. Metaphorical realism. Symbolic fantasy. What is actually going on with the protagonist? I found no motivation or evidence to throw down in any particular direction. Specifics can suggest forms and forms can suggest specifics. House of Wolves is in the grey zone of this relationship.

I was glad (in a broad way) that it ended on a note of hope, but really, it didn't feel like it should. There's not much hope on the way, so the end feels like a deus ex.

This piece gives Trigger warnings. They are exhaustive for its short length, and really do it no favours. Too long, too much detail, robbing the piece of surprise, overstimulating the listed effects before they've even been attempted to be executed by art.

There is also a paradox with warnings that encompass the whole of something of this size that they amount to a message saying, 'If you relate to any of this (the entire listed content of the game), maybe you shouldn't play this game.' Which is taking the target audience and turning them away.

House Of Wolves is plainly not my cup of tea, but it does have a simple grace of execution and presentation on its own terms.

(This is an edited version of a review that first appeared in my IF blog during IFComp 2024.)

The Killings in Wasacona (KIW) by Steve Kollmansberger is a thoroughly involving and suspenseful police procedural murder-mystery game in which the player, a fresh FBI graduate, is tasked with unravelling the reasons behind an abruptly rising bodycount in the eponymous town. It comes as a choice-clicking Twine with some minor graphical embellishment in the form of maps. It also utilises a skill mechanics system. Whenever the agent's skills are challenged, the skill test is delivered transparently as a die roll, with the modifiers and results announced. The player can pick from various classes at the start to decide where they'd like their skill emphases to be.

In my experience, games where you have to solve crimes by producing solutions are challenging to beat. They're probably as difficult to create. Players will perceive all kinds of patterns in everything, assuming they get much of the everything – it's often part of the game design that just getting the information is half the challenge – and they can divine wild solutions that are rarely what the game wants when it's piper-paying time. Often these solutions can't even be inputted, leading to frustration or disappointment.

KIW pretty much avoids all these problems. It has tight mechanics that focus the player on the clue-gathering, prose that summarises what the clues might mean in relation to clues already gathered, and it offers an ultimate refresher on gathered evidence.

The game's writing mode has a Visual Novel kind of feel. I don't refer to graphics. I mean that the characters are perhaps a little overlit. They speak with a touch too many exclamation marks, a touch too much exposition and too many gestures. This isn't my preferred mode, but by the end, I realised I probably actually needed this extra illumination in order to have been able to take in the amount of info the game was dispensing. The prose is efficient, at times perceptive:

"The house is clearly lived in, but with the deferred maintenance one might expect from a single person trying to keep up with the demands of life and inflation."

KIW follows a cycle where turns usually take up an hour of the day, and there are on average five locations or people available to visit on any turn. The player can choose from amongst all the necessary tasks for the investigation: Visiting crime scenes, the morgue, the local college, interviewing other officers, interviewing townies, following hunches, even just driving around at random to see what hits. (Remember that Ted Bundy was twice caught red-handed by randomly patrolling officers in cars, just because they thought he was acting suspiciously, so don't neglect this option.)

KIW emphasises efficient use of the player's time, and a clock up in the corner creates a pleasurable suspense and urgency, even though technically, the game is generous in allowing you to get a lot done. The amount of apparently cross-referenced knowledge of the player's progress, used to cue developments in the prose, is also impressive. The game state looks to be complex but the game knows its state, and the player's. (Don't get me started on games that don't know their own state.)

Perhaps the only incident I found too unrealistic, and disconnected from other events, was when I was given the opportunity to accuse only the second officer I spoke to on the case of actually murdering the apparent drug overdose victim whose corpse she'd found – just because this officer displayed a prejudicial attitude towards drug dealers. With great bloody-mindedness, I took the game up on this offer. I admit I only did this because I'd yet to realise that the presentation of the skill-testing options (the first one had gone great! I'd had +3 on my roll) seemed to endorse them. Big font, imperative mode. I then realised all the choices appear this way. Lesson learnt, I botched this accusational die roll with a -6 modifier and thoroughly pissed off officer Amanda. However, I don't think Clarice Starling would have entertained this option in the first place.

There's finite time to solve the crimes, and when that time is up, the player chooses their solutions from an incredibly detailed menu of possibilities, considering the gathered evidence for each case in handy point form. Perhaps this has been done before, but I've not seen it, and it seemed a great compromise of all the systems involved. It helps the player a lot, but also doesn't make it at all easy to just guess solutions if one's not on the right track.

The results screen is also fun, showing how the player's outcomes fare against everyone else who's played the game. I felt very positive during my investigation that I was handling KIW at an above average skill level for me re: this genre, but my outcomes were all those shared by the majority of players to date, probably indicating my averageness. I didn't feel bad about this. The Killings in Wasacona is a game with a lot of details, but which makes those details accessible. It made me feel the pressure of the investigation, the opening of possibilities, of mysteries, the thrill of discovery, the possibility of solution – and still give that final reminder that yes, solving crimes is hard. I think future crime-solving games could take leafs from this one.

(This is an edited version of a review that first appeared in my IF blog during IFComp 2024.)

In spite of being the buggiest game I played during IFComp 2024 (caveat - I played fewer than ten of sixty-seven ) The Triskelion Affair still held my interest and/or pulled me through. This parser adventure posits the player as a "medieval detective" tasked with finding a magical item hidden in a church. The blurb says the game is "Inspired by the classic dungeon-crawl adventures of yore." This reins in a range of the game's content and approaches, which could otherwise be described as being all over the place. They still coalesce into a setting of some atmosphere and focus in the last third of the game, which takes place in an eerie abandoned chapel.

The parser voice is a mixture of straight reverent description, replete with details of the different architectural features of churches such as the apse and narthex, and personalised snark of the kind parser games have refined over the years but which is going out of style unless you label your game Old School. A rewrite of core parser cues, like asking the player "What do you do?" every turn, and the inclusion of numerous gags, like wacky doggerel for tombstone epitaphs, or erecting mausoleums to Crowther and Woods of Adventure fame, give the sense of the author's presence. I don't know that the two voices are at war with each other, but they certainly comprise a tonal switch that is thrown rapidly and repeatedly between settings A and B during the course of the game. There's also the odd personal exhortation; typing GET ALL produces: "That’s too much burden for one person, and there’s stuff you don’t want to deal with. Try examining the thing first. Explore! Otherwise, what’s the fun?"

This particular message was a handy cue for me to poke at things for poking's enjoyment and sake, which was the correct attitude to take in retrospect. Much of the game's contents and geographical presentation remind me of a MUD's, which aren't usually designed for single players, or for puzzle-solving. The room description of each of a large graveyard's sections consists of a brief note about which sector the player is in, followed by the same general graveyard description. A game warden's hut is chock-full of takeable described stuff that is ultimately of no use for the player's quest. Having taken it all, I ended up leaving it strewn all over the donjon because there's also an inventory limit, albeit a generous one.

I found the chapel part of the game particularly involving. There's a sense in this game that there's no overt threat, and that the environment shouldn't be hostile, but that there is and it is, anyway. Everyone's left or died. Broken furniture barricades hint at scary troubles. The church is full of ritualistic paraphernalia, the volume of it suggesting numerous stressful prop-based puzzles are ahead (What am I going to do with an explodable canister? With the northern lantern? The southern lantern? The third lantern whose direction I forget? The stack of parchment? The highly suspicious blank parchment? The multiple candleholders? etc.) yet that's not the case. Somehow all of these elements apply an overhead weight, an idea of a past and of a world and kingdom outside, all the better to make you feel stuck in this weird holy place picking at some minor mystery like it's a cog in something bigger.

There's also a lone RPG fight with a zombie, easily won, but just make sure you pick up and wear again anything the zombie tore off you during the melee!

As my opening declared, I found the game buggy. Increasingly so towards its conclusion. All the way through, there's usually just one frictionless way to do a thing. Every other way is troubled, missing, leads in disambiguation circles, or suffers from spelling errors or no synonyms. I've experienced hundreds of games in this state by now in my gaming and reviewing career. These games just needed testing, as does/did this one.

Triskelion also opens with a tutorial. It feels funny and friendly, but already shows many of the implementation omissions. The second command demanded in the whole game seems to be SALUTE. This immediately returns, "What do you want to salute?" Come on, game. The guy who just saluted me. It's also off-target in emphasising a lot of eating, which is unimportant for this game, and a decent amount of communication by the dreaded ASK/TELL system, which is also, mercifully, completely unimportant for this game beyond the tutorial.

The Triskelion Affair feels like a lot of buggy, parser-loving parser games I've played before, but it comes on friendly, even if the tutorial's off piste, and the church section ultimately pulls together to menace with atmosphere. Whether you will get that far in spite of all the bugginess is not a prediction I can make in general.

Disclaimer: I tested the Amstrad CPC version of Ghostship Delgado.

At the time I wrote this review, I hadn't previously played many Quill-created games. This is probably a symptom of cultural differences in IF traditions. My understanding is that The Quill made its strongest impacts in the UK and Europe. I'm Australian.

Ghostship Delgado is a 2024-new game produced with The Quill, initially for the Acorn Electron and BBC Micro, then ported to the Amstrad CPC, which was the version I tested and played in emulation. The game is split into two parts, with a password granted at the end of part I opening the second half.

The game's PC, George Pike, falls asleep on his rented yard and wakes on the deck of an old abandoned ship, along with his dog Ruffles. The adventure starts sparse to establish the geography and abandoned status of the ship, then gets busier below deck. There are nautical-themed puzzles, mechanical ingenuity puzzles, helpful and unhelpful animals, and backstory bits to read.

The Quill's parser is a small-vocab one, but it's reassuring knowing that USE will handle most tricky situations, the way it often does in Quest adventures. The tech is old school but the design aesthetic isn't; you can't wreck your game unknowingly and there aren't any time-limited resources. Locale descriptions are thorough and good at cueing the puzzle brain. The player should certainly be thorough in EXAMining stuff. There are a good number of items to be found behind other nouns.

For me, the island-set part II of the game is the more exciting one. It's bigger and with varied terrain, creating opportunities for more atmosphere in the writing and more spread-out puzzles. The backstory is developed further from part I, with the player involved in something of a spiritual quest.

The post-script is especially satisfying. A lot of two-word parser games just finish with THE END, but this one has a thoughtful afterword that is designed to please.

Ghostship Delgado gives a fresh performance of old-school adventuring without a lot of the hassles, and has a wraparound of more narrative than usual for such games, too. It also comes with feelies, and quality instructions and set-up docs.

(This is an edited version of a review I originally published in my blog during IFComp 2023)

I usually start any IFComp by playing a horror game that speaks to me. In 2023, the game that was plainly shouting at me was Barcarolle in Yellow by Victor Ojuel.

This parser adventure is an IF take on the cinematic subgenre known as giallo, in which I have some expertise. So even if this turns out to be my only IFComp 2023 review (spoiler alert - it did) I hope it's one that can help other players appreciate the qualities of this game in the context of its source material. I'm sure Barcarolle will entertain anyone who enjoys a hectic, lurid murder-mystery thriller with violence and some sex/nudity, for that's what it is, but I can still imagine a lot of "What was that about?" questions regarding some of its content in the minds of players who've never encountered a giallo or giallo-like before.

About giallo in general

Giallo is Italian for yellow. In Italian publishing, there's a history of classic mystery novels being released in cheap editions with distinctive yellow covers and sensational cover art. Their success led to newer pulp mysteries being published in the same style. When these stories began to take cinematic form, directors quickly turned to producing original murder-mysteries inspired by them, but with a modern outlook. These films were more psychologically-focused, erotic and horrific than the books that originally inspired them (though sometimes not more so than the covers that inspired them) and often featured innovative audiovisual styling, gore, nudity, and a high body count. This kind of film became known as the giallo and was at its international peak of popularity in the 1970s.

The majority of giallo came from Italy, followed by Spain. Some were coproductions that shared Italian and Spanish actors and production crew. The film's casts were often studded with internationals. In Barcarolle in Yellow the heroine PC, Eva Chantry, is English (according to her passport) and is off to shoot a giallo in Venice when the game begins.

The name and cover art for Ojuel's game are on the mark in their pastiche quality. Compare Barcarolles cover art to the real poster for The Girl Who Knew Too Much (1963) (link to the poster from the film's wikipedia page.

The Girl Who Knew Too Much (1963) poster
The international success of one particular giallo, Dario Argento's The Bird With The Crystal Plumage (1970) set off a copycat trend in the naming of these films. Numbers, animals and colours featured heavily. As did salaciousness. Consider these titles:

Lizard in a Woman's Skin (1971)
Cat'O'Nine Tails (1971)
The Red Queen Kills Seven Times (1972)
Strip Nude for your Killer (1975)
Watch Me When I Kill (1977)
Five Dolls for an August Moon (1970)
The Bloodstained Butterfly (1971)

It turns out that a barcarolle is a kind of Venetian gondolier's song. And for a giallo IF initially presenting to a giallo-unfamiliar audience, the colour yellow is an obvious choice.

Giallo, as they were unto themselves in the 1970s, aren't really made any more. Some thrillers have giallo-like elements, but never enough to fully qualify them or give them the giallo feel. What we do see produced today is the occasional hyper-loyal giallo pastiche, like the 1970s-set Abrakadabra or 1980s-set Crystal Eyes. Abrakadabra and its trailer are so amazingly accurate, I genuinely thought the film was a giallo from the 1970s when I first saw the trailer; the film was released in 2018.

Finally, one of the giallo masters from the day, Dario Argento, is still alive, and brought out a brand new giallo in 2022, Dark Glasses. For all its flaws, I still think it's his best film for a long time.

Spoiler-free play advice

The game uses few verbs, and mercifully, all talking is achieved just with a TALK (PERSON) command. All commands needed to play are listed in the HELP. The key advice I can give is to WAIT whenever in doubt, as many scenes progress on their own, TALK TO (PERSON) whenever still in doubt, save frequently (though UNDO is also your friend) and finally, pay attention to your wardrobe. It's both fun in an IF sense to change your clothes, but it also turns out to be policed in a practical sense by this game. Wear whatever your commonsense tells you is appropriate for whatever task you're about to undertake.

About Barcarolle in Yellow

In this giallo adventure set in 1975, the player takes the role of Eva Chandry, an actor whom the credits describe as starring "as herself". The credits are interwoven with the game's opening turns set in a police station, where an interview with Eva is beginning. Eva often finds that life is like a performance, or that life reminds her of her art more often than the other way around. Thus the game is presented to the player within the frame of it being a film, and is also about a film actor appearing in a giallo film to be shot in Venice.

Giallo films often blur the lines between reality, dreams, imagination, and false memories of the seen and heard, but they rarely enter the postmodern. Barcarolle in Yellow throws in a foregrounded fourth wall element that adds to the pleasurably discomforting pressure the game is always applying through its prose. Is the game reality the true reality? Or does that lie in some layer above or below what Eva experiences? What she does experience is all the mayhem of filmmaking, typically chaotic giallo plotting, and being the target of a mask-wearing killler in Venice, the same way her character is stalked in the script.

Killers in giallo films are often motivated by Freudian traumas from their past. As often, the traumas are revealed to the audience in piecemeal flashbacks cued by the developing investigations of the murders. While I'm used to giallos going back, I laughed when Barcarelle went way back (to 1862) and to another country (USA) in what appeared to be its first flashback. In its typical rug-pulling style, this was revealed to be a scene from a Western Eva was acting in.

Overall, Barcarolle in Yellow turns out to be a dangerous and tricky game, with frequent physical threats to the PC, death on the cards and numerous abrupt changes of place and reality. However, it also has a strong, often linear trajectory that keeps it from being too hard. I found most difficulty stemmed from under-implementation. It doesn't cater to enough synonyms and possibilities for the amount of prose there is. This combined with a few timing-critical scenes makes for some frustrating passages. On the plus side, the THINK command will almost always point the player in exactly the direction they need to go. I didn't use THINK on my first playthrough, but used it a lot on the second to shore up identify-the-noun moments that had repeatedly held me up.

As the attractive Eva, the player must get around an excitingly compressed version of Venice, occasionally act in the film she's in (by following its script!) investigate the stalker who appears in both Eva's life and the film, and manually handle her wardrobe. Cue giallo-typical nudity, both appropriate (having a shower) and justifiable but glamourised (being nude in a prolonged dream, except for a mask). This being a giallo, the game comments, via Eva's thoughts, on the way the camera observes the female body through an exploitation film lense.

There are a lot of entertaining scenes and tricks that toy with agency as an IF player, as a woman PC and as an actor in a film. The world of the game is as aggressively sexist and sexual as many giallo films were, and those films already experimented a lot with people's roles. The agreed-upon prototype giallo is Mario Bava's The Girl Who Knew Too Much (1963) which foregrounded, in one stream of the genre, a kind of outsider female experience. The American heroine in that film takes a holiday in Rome, witnesses a murder there and eventually solves it. Eva is Barcarolle's outsider protagonist. She visits a city in another country to shoot a film and also has to play a tourist in that film. The player even has to shoot photographs during Eva's acting scenes.

Some giallo could be very gory, with particularly outré deaths that are now regarded as proto-splatter-film. Barcarolle hits these genre notes, too. It features a knife murder committed through the eye, a speedboat attack and a hanging by designer scarf. The fresh and well-informed performance of so many giallo notes in the game is impressive.

Giallo films were ultimately open to exploiting any dimension of cinema sensation they could in their commitment to producing involving, shocking, thrilling and twisty murder-mysteries. Bigger twists and shocks were better, even if they didn't make a lot of sense. Some giallo were tightly plotted, others lurching shock machines, but most had their eye on overall audience satisfaction. This hectic quality can be perceived in Barcarolle in Yellow, too. Some of the game's shocks involve unexpectedly sudden endings or upendings, or the placement of moments of fourth wall breakage. There are in fact multiple endings to the game that riff on the bizarre nature of solutions to giallo murder mysteries; I found four endings so far and can tell there's at least one more.

I've played a couple of Victor Ojuel's other games over the years. They both featured vivid or innovatively-realised geography, and that's true again of Barcarolle's handy version of Venice. The games also needed more implementation work to my eyes, and that's also true of Barcarolle. Because I like this game very much, I would also like to see a solider version of it, without all the excess line breaks, with the typos cleaned up and all those synonyms added and programming beefed up to remove the bumping-against-the-walls moments. However, with its strong hint system, Barcarolle won't leave a player stranded if they do hit the walls, and that's more important for today and for players' IFComp experience with the game. I also appreciate what programming an IF game as event-driven as this one is like.

In conclusion, I highly recommend Barcarolle in Yellow. It shows great and affectionate knowledge of the films and related cultural milieu that inspired it.

I played a Commodore 64 version of Castle Dracula. The original BASIC game was published in CLOAD magazine, later distributed commercially by Microdeal and much later received further porting attention to other systems.

This adventure shares the most typical set-up for 8-bit Dracula adventure games: It plonks you roughly outside the castle and tasks you with going in and killing Dracula. I don't know the source of the flavour-adding blurb text concerning your missing wife but it goes unreferenced by the game.

For what was originally a magazine game, Castle Dracula has a big map. It is otherwise perhaps the epitome of elbow-grease-requiring two-word parser adventuring. The defining annoyance for the modern player is that almost nothing has a description if you EXAMINE it. If nothing's worth examining, then all you have is the ability to collect objects, or to try to VERB them on rooms and objects. There are no additional nudges towards solutions beyond the initial prose presentations of anything.

Again, this kind of solving-it-in-your-head approach is the bread and butter of a lot of games of this type. I found it too tedious in this one. For instance, there's a plank. There are so many great things you could think of doing with the plank (smack a zombie or hunchback or annoying suit of armour with it, build a ladder, cross a pit) and none will work or give much feedback except the correct ones performed with the correct verbs in the correct locations. And there are a ton of locations, so even just testing one idea across the board is too much slog.

There's also an inventory limit (leads to huge back-and-forthing on the map), some finite supplies (fortunately not the light source!), a slightly mazey forest, and one command that's crucial for more than one puzzle and which I'm not sure I'd have come up with myself. If you want a single bit of advice for Castle Dracula in general that will really improve your experience, here it is: (Spoiler - click to show)GIVE doesn't work, but OFFER does.

I'm a (blood)sucker for all things Dracula. This one has a good Dracula setting with forest and church and castle, but is otherwise more a haunted house adventure with a cute attitude; as well as the zombie, you'll meet a Quasi Quasimodo. And when I say meet, I mean he'll be present in a room a the same time as you. Communication is beyond the scope of this game. You can refer to him as QUA because only three letters are read by the parser.

I recently read Robert Louis Stevenson's novel Treasure Island for the first time. As is often the case with far-reaching, pop-culture-influencing entities when one finally experiences them, the source material wasn't quite what I expected. I'd anticipated a lot more looking for the treasure, rather than that activity being confined to the last twenty percent or less of the book. I probably didn't expect such strong characterisation as I found, either. And X does mark the spot, but I don't think anybody actually says, 'X marks the spot.'

These musings sent me back to replay the Apple II version of Scott Adams's second adventure, Pirate Adventure (1978). Doing so in 2023, I'm interested in looking at the game from a few atypical angles rather than thoroughly overall, as the typical ones are well covered by now.

The first thing that stands out about Pirate Adventure is its setup. The player doesn't start the game in a fantastic world or scenario, but in a flat in modern day London. It's their finding in this flat of a copy of the novel Treasure Island that prompts the adventure. An annotation in the book says, "Long John Silver left 2 treasures on Treasure Island". In a sense, the player is really picking up the gauntlet left by the characters of the novel, as if the novel's events were real in this world.

After a bit of puzzle-solving, the player gets from the flat to the adventure proper's island setting by magic. In this light, the fact Adams put the flat in London when he could easily have set it in his home country, or just anywhere else, is a nice atmospheric touch that reflects the way the novel itself begins in England.

The sharp-eyed player will note that the first island visited is called Pirate Island, not Treasure Island, so they won't be surprised that there's no treasure there. Pirate Island is the setting for the majority of the game, and what happens here is all about getting the player ready for their expedition. It's also a home to all the trappings of the novel: rum-drinking pirates, talkative parrots, and the machinations of the tide. These elements make it easy to feel transported in time as well as place, but it's clear the player's still in the present, or has always been in the present, due to the presence of objects like sneakers and water-wings. I don't know how much the author thought about the sense of the whole, but there is a kind of anachronistic time mashup going on in Pirate Adventure. Of course, there's no way for the game to offer any comment on its own setting; there's no RAM available to allow more prose that could do so. It's up to the catalogue of things in the game alone to suggest or create the whole aesthetic.

There are two talking characters, the pirate and the parrot, and though neither says a lot, what they do say amounts to important cueing (of state changes) and hinting. The pirate exhibits enough independence of mind to be a solid NPC. While he offers sailing advice, he also has his own schedule, sometimes needs to be bribed or cajoled, and might tell you to get "THAT ACCURSED THING" off his ship before he'll set sail. In having so many functions that delineate bits of the story, indicating when something's begun or ended or is ready or not ready, the pirate might be the first entity in an Adams game who really makes time in that game progress as a function of the story and puzzle-solving.

The final trip to Treasure Island was exciting for me. Though the island's only a few locations, those locations (including a deserted monastery) suggest mystery and danger of the kind I'd hoped to find more of in the source novel. A joke set up much earlier in the game gets its payoff when the player tries to sic a certain animal on the deadly mambas, and there's also a false anticlimax of the kind that's extremely satisfying in any big treasure hunt story, where the player is temporarily led to believe they've done all that work for nothing.

The side-effect of the pragmatism of scoring in Adams's games can be a degree of inscrutability in the ones that have few treasures to find. All treasures are worth the same amount, and the total for all treasures is always 100 points, whether there are two or ten. In Pirate Adventure, there are two, so essentially the player's score remains at zero until the last five percent of the game, at which point it will become either 50 or 100. Very few players would stagger all the way back to that flat in London with only 50 points. It's a bit strange to me that Adams kept this system in place, but perhaps after Adventureland, he figured that most of his games would make (more) use of it, and it's true that most do.

Pirate Adventure seems to have a bit of a reputation as an easy Adams game. I don't think I ever found it necessarily easier or harder than most, but I suppose that its manner of grouping puzzles into what could be called sub-quests (e.g. the whole of Pirate Island is about gathering the resources needed to leave Pirate Island) means the player's attention isn't split across myriad tasks with completely unrelated solutions, the way it can be in the more danger-oriented treasure quests like Adventureland. If half the game or more is devoted to one larger task, concentration on that task gathers, and belief in that aspect of the story and world gathers, and maybe that's why this is ultimately a particularly charming Adams game.

(This is an edited version of a review I posted in my blog during IFComp 2022)

Nose Bleed is a clicking-choice-based story with graphic elaboration – ostensibly about social anxiety – that elicited a combination of visceral nausea and hysterical laughter from me; a pretty strong combination for a ten-minute (to play) game.

The player-narrator of Nose Bleed works in an office. They're meant to be doing something with spreadsheets but they feel barely capable. The details of the work, or indeed of anything but the narrator's flustered mental space, and later, their spectacular nose bleeds, are omitted by the game. Their headspace and the negative self-talk going on in there are the main event – the content warning says "social anxiety". In the protagonist's distorted mindset, they expect to be negatively evaluated by others all the time. The narration is a spiral of feeling incompetent, incapable, distressed, depressed, and wanting to flee situations.

When the PC's nose starts to bleed during the work day, it comes in like a metaphor for their anxiety. It starts, it can't be stopped, it seems uncontrollable, others can see it and evaluate them negatively as a result. The bleeding gets worse. The PC is invited to an event they can't get out of, and the blood keeps-a-coming. Choices about what to do next are made by dragging words on the screen to nouns that light up. The actions tend to be basic ones that are either ineffectual (rub nose) or fobbed off upon selection by the protagonist's own self-defeating brain (apologise).

What makes Nose Bleed so nauseating is the way the blood is animated on screen. The paper-white backdrop is stained first by a single streak, then as spots that appear, and finally as an unstoppable animated splatter that follows the cursor about. Coupled with selectable prose options like "Lick" (the blood off your lip) the effect of all this was to begin to induce in my arms that strange weakness that precedes blood-related nausea for me. And then I began to laugh. The whole thing was reaching the intensity of a skit where a patient sits in a waiting room while geysering blood. As much blood gets all over the prose in Nose Bleed. It piles up on the on-screen choices and nothing can stop it.

Nose Bleed's finale has a kind of twisting escalation that reminded me of a David Cronenberg film or two. I'm not sure what meaning I ascribe to the very last event in the game, but the overall design is very good, moving quickly from banal office work and equally banal thoughts, via the start of a typical nose bleed, through the discomfort of being unable to stop the bleed, to an eventual wittily programmed and (to me, hilarious) graphical geyser.

If all that animated blood is in danger of having an eclipsing effect, I could say that having all one's thoughts eclipsed by one panicky thing is like social phobia, after all.

(A version of this review first appeared in my blog during IFComp 2020.)

SOUND is sufficiently small (for me, a few minutes per play) that my whole review amounts to a spoiler:

In the text-on-black Twine SOUND a woman known as Orange seeks treatment for her stutter and communication problems from one Doctor Thee. The doctor is a sailing champion and island dweller. An island is the venue for the therapy. The prose follows a conversation between Orange and the doctor in which neither is necessarily the point-of-view character. I was interested to note I identified, functionally, with the doctor, just because the doctor was the interrogator, but technically the links that change the progression through the conversation can fall to either character.

There is something a bit cute about the dialogue and the situation. Orange's anecdotes of work difficulties are realistic but the actual prose isn't quite. It reminded me of serious-leaning dialogue delivered by videogame or Manga characters. They say 'Haha,' and someone winked at some point.

Orange posits a theory of sound (that may validate her stuttering) that the doctor appreciates as new. It also seems to be bound up with semiotics. While she doesn't just go and say "semiotics", she does talk about the disconnection between sign and signifier in the supermarket aisles, even though she doesn't use the words "sign" or "signifier", either. It's unfortunate that in this precision-requiring moment, the prose is just a bit off. I'm not sure if it's the proofreading, or English is the author's second language or something else.

Fortunately, the outcome is unaffected, and it's the most interesting part of SOUND. It seems that Orange's theory transforms reality (if only all theories were this easily actualised!) and the IF's words rearrange and repeat on the screen to create the effect. The links wander, as well, but this is no "find the correct link to click" moment – this is indeed, the end of SOUND. And for me, it falls in the right spot that is specific enough to the story, and also abstract and poetic enough to be satisfying without over or under-doing anything. It did prompt me to think on it in a manner outsized to the conversation's face content, and the coda text suggests a beginning for the new communication ("You embark to find that voice") and, cleverly/eerily, is exactly what the game's blurb promised, because that is SOUND's blurb.

This IF is so short I replayed a couple of times to see the other elements and to experiment with the end screen. The repeat plays also improved my overall understanding of the conversation. It's not like it's complicated, but in general I find it hard to keep track of who's speaking during long direct speech outings. SOUND is brief and the payoff is good. A multiplication of effect at the end of something (and definitely not its opposite) is always a fine way to go out.