IFComp 2025 review: my creation by dino

my creation by dino is a short (10 minutes) parser game (the IFComp website incorrectly said it was Twine but I have emailed them about this) in which the PC is a dad stuck in bed in a rickety house with his crying baby. You would never guess this from the cover art, a design which will only resonate if you complete the game.

Endlessly crying babies raise human hackles at a primordial level, so the game's temporal depiction of that common experience of shuffling around a room one can't leave while the crying can't be stopped is likely to knife (or knife anew) anyone who tries it, in spite of major implementation gaps. It's clear my creation hasn't had a testing round or received any technical advice, but I commend the author for bringing a story like this to the parser format on their own. Other gains can come in future.

It's important to say there's ultimately more to the game than the screaming baby. If that had been the whole thing, it would be an uninviting ask of players to say the least. It's tough as is. But there is more. I will discuss the more with complete spoilering in the remainder of the review.

The PC's in the bed and the baby's in a nearby basket, crying. Where the geography of the parser model really works for this game is making the bed into the PC's world. For reasons not made clear until the end, the prose indicates the PC is in physical pain and inhibited in movement, so each NORTH, SOUTH etc. drags them, with effort, to another section of the bed. The efforts are described. On the one hand, the idea of thinking about compass directions while moving around a bed is absurd. Obviously we're not meant to be thinking about them, they're just the stock method of movement in a parser game. For a new author to program up some replacement terminology would be a big ask, so in this case, it shows dino working with the strengths of the format, but also the need to bend the format's stock trappings to the game. In prose, it's also effective for the bed world that the game's opening paragraph is written in the third person (the rest of the game is in typical parser second person) offering a bird's eye view of the situation:

"He is lying in his bed, in his bedroom, in his own crooked little house with small windows, single glass, overlooking other crooked houses;"

The cut from this intro text into the "middle of the bed" location, the change of scale and pronoun and person, all act together like a magnifying glass zooming in on the PC's situation, where suddenly one bed seems giant.

The geography of the bed isn't respected in the programming, though. There's a constant mismatch between what's described, what can be acted on, where things are. This doesn't block progress – the game is too small for that – but it does interrupt the spell of the fiction and so reduce its power. One inadvertent side-effect was that I was chuckling at my gauche handling of such props as the baby or the basket, but at the same time I experienced a kind of remote terror in handling them. Like, god, I hope the game won't let me DROP the baby in any bad way.

I was surprised when, having found a copy of the novel Frankenstein near the bed, I typed READ BOOK and was suddenly hit with an almost 700-word excerpt. This moment broke the dirge of the baby situation and made me re-engage afresh. I also admit that my kneejerk reaction to the idea of reading Frankenstein to a baby was laughter, but I remembered a second later, of course you can read anything to a baby with a chance of soothing the baby. Reading Frankenstein to this baby is the "winning move". It leads to another text block, this one almost 800 words, in which the dad monologues to the restful baby.

The monologue drops the details of the story into place. It's not a twist, but narratively it has some of the functions of a twist of a short story. The dad's in pain in bed because he's had gender-changing surgery, but before that he gave birth to the child. The monologue muses on their possible future and their future relationship. It's certainly a breather after the oppression of game-long crying, and the dewy-eyed intimacy of the moment feels real. In the context of what's come before, which gave away little, and only a little bit at a time, 800 words straight up  inevitably feels expositional. That's how I/we typically respond to story structures and lengths after we've encountered enough of them. But the monologue doesn't feel expositional in a "nobody would say all this" kind of way, and I think that's more important. It reads authentic and illuminates the sketched character of the dad. The value of Frankenstein is now also apparent, its tale of human creation and unusual birth and an outsider human in an unusual body resonant with the PC's experiences.

I valued my creation more after playing it and after thinking about it than during the playing, at which time the implementation was kicking the atmosphere every few moves. Even implementation can't stop a baby crying baby, though.

IFComp 2025 review: Temptation In The Village by Anssi Räisänen

Temptation in the Village by Anssi Räisänen is a parser game adaptation of an unfinished short story by Franz Kafka. That story is dated 1914. Temptation took me 30-40 minutes to complete and my review discusses it in full.

Räisänen explains in the ABOUT that the game begins as a faithful adaptation of the story followed by his own expansions on it in the spirit of Kafka. The result is the experience of a Kafka tale manoeuvred to suit the parser format. Psychologically focused within the PC, it is atmospheric and works very well. The methods for the adaptation are interesting but uncomplicated, and they drew my attention back to some fundamental qualities of the parser format and their effects. The story is certainly as existential as one expects from Kafka, but it doesn't have the unrelenting heaviness of something like The Trial. Its feet are in naturalism and it's set on a village farm.

The opening paragraph of the game acts as a kind of benchmark. It depicts the PC experiencing what psychologist Abraham Maslow termed "the peak experience", the feeling that life is infinitely interesting and exciting, and potential-filled:

"One summer, as evening falls, you arrive in a village you’ve never been to before. You’re struck by how broad and open the roads are. Tall, old trees stand in front of the farmhouses. It has been raining recently, the air is fresh, everything delights you."

This experience will soon be defused by the PC's dealings with a roster of unhelpful and sometimes unintentionally sinister village characters. In my reading of the game, the elaboration of the move to or away from this psychological high point is the frame for what happens in the story.

I need to preface the rest of this review by saying that at the time I'm writing this, I haven't read any Kafka. Being a literary type, I know a lot about Kafka from secondhand reading, the zeitgeist, and the overused and under-understood adjective "Kafka-esque". The experience of Temptation meshed with specific qualities I expected from Kafka. It features absurdity and an uncertain prosecutorial atmosphere, and though there are no real bureaucracies in it to confound the PC, the minor hierarchy of the farm's running amounts to a version of one.

The story begins with the PC wandering in the countryside when they come across a farm. Looking for shelter and work, they start to enquire about both, and are soon running afoul of ambiguously helpful/unhelpful locals. A villager suggests the inn might suit, but also points out it's been turned over to a cripple the local community was obliged to provide for. The cripple and his wife can hardly manage the inn, so the inn stinks and ends up providing for nobody. The villager man and his wife hang about the dithering PC, following him at a distance for no good reason and seeming both menacing and foolish in doing so.

The main way such events are managed in the game is just by allowing or blocking directional movements at different times. The player is forced to twitch and dawdle about the first location, being invited in one direction, finding that way blocked by NPCs or their ideas, invited in another, finding it now blocked too for new narrative reasons. For the most part, these methods get around the need for any conversation mechanic. When I first tried to speak to the villager, I was briefly led astray by the ALAN engine's default help message regarding ASK PERSON ABOUT THING, which prompted me to think (with great relief) that I wouldn't have to use such a command at all, since all the characters thus far had been speaking spontaneously. It turned out later that I did have to come up with ASK MAN ABOUT ... so my least favourite IF mechanic struck again, forcing me to the walkthrough for one command.

The divisions of parser game turns and locations suits Kafka's and Räisänen's unhelpful NPCs. The prose of Temptation conveys an inner psychological process, not just a series of standalone vignettes about place. The PC enters a room, is often prohibited from performing actions by implied social customs or just the silence of others (how strange it would be to go to ask an old couple for a room for the night, find them at dinner, but also that they're prepared to sit there ignoring you in the half-dark while eating porridge) and must work out what to do to unstick the situation. The prose indicates a normalcy, or at least non-rudeness, in the PC, that is tested by others who seem to be unthinkingly rude or just not thinking.

Even children have an air of menace in this story. They awaken and encircle the PC in unison when they hear the sound of a dog barking at night:

"It is too late; suddenly, all around you, you see the children rising up in their white nightshirts as though by agreement, as though on command, and eye you closely."

There is the sense of conspiracy amongst others, never verified or verifiable. It just emphasises that the PC is the PC and cannot know others' thoughts, yet he keeps trying to balance what he guesses those thoughts might be against his own standards.

Where Kafka's story ended in the night, Räisänen continues to the morning with the PC's enquiries regarding work. A young man seen earlier on a wall, where he was inviting the PC onto the farm in what modern folk would describe as a passive-aggressive manner, now submits the PC to a pre-work test:

"It would make a great impression on the master if you mowed the tall grass south of the house. There is a scythe in the old barn... Another thing you could do is move the big trunk from the old barn to the new barn."

The PC thinks this man seems like a foreman, and speculates he might even be the son of the old farmer, but chooses not to ask about either of these things. The player's more traditional adventuring skills are now drawn on to bring the farming tasks to a close, at which point the man asks one more thing:

"... remember seeing those fallen cherry blossoms in the garden? You could go and glue them back onto the tree branches. I am sure the master would appreciate that very much."

The PC's realisation that the man has been pranking him and wasting his time is accompanied by another; that the PC himself has been behaving in a blindly obedient manner while on this farm.

Similar incidents sprinkled throughout the game have led to this point. As a player, I recalled my own following of all the suggestions made by the first villagers outside the farm in spite of them not actually being helpful. However, I didn't realise that the old couple I'd found eating porridge on the first evening had never even offered me a room until I reviewed my transcript. I had just felt they had, then I'd gone off and lain down on a pile of straw to sleep. The so-called foreman never indicated who he actually was, or why he might have had any real authority over me, yet the PC had behaved in a manner as if he had.

Given that this is the conclusion to the fully original portion of the game, and that it weaves together the prior contents of Kafka's short story so well, I think the integration is excellent, and the story has a thematically and psychologically powerful conclusion.

The man's prank isn't the final word, though. Recalling the peak experience of the protagonist in the first scene, that hard-to-share delight he experienced at everything, I'm aware of the distance travelled from that moment to his humiliation at the hands of the foreman. The game has shown that the PC got here by careless small steps in the face of uncertainties, and certainly lost his way after that first moment. Peak experiences can feel like accidents. Abraham Maslow ended up assuming they were. Writer-philosopher Colin Wilson later explored the phenomenon in literature and in reality. He wrote about the true value of these experiences, their nature, what we can do to try to bring them about, what we can do to try to recall them, or avoid losing them or moving too far away from them. Temptation ends with a turn back towards the potential of the opening high point:

"But even in this desolate moment, you know that one day you will find a place that truly belongs to you, no matter what it takes - and it will be somewhere entirely different from here."

For the evolution of the PC, this is the right move. The game casts most of its situations in Kafka's socially adversarial light, so there are practical implications we can take from the story, or be reminded of, about how more assertiveness may be needed in dealing with such situations, and with self-proclaimed authorities, if we aren't to be given the runaround like the PC is in Temptation.

Given my lack of Kafka-reading, I don't know if Kafka ever ended stories with what you might call a positive vector. By reputation, my guess is that he wouldn't have. On the other hand, if he'd trafficked down in Samuel-Beckett-like levels of wilfully stupid pessimism, I'm sure I'd have heard about that.

Temptation in the Village is interactive, but not in the sense that the player could have warded off all those unhelpful people. There's a journey to go on here and the interactions highlight opportunities to think about it. The player is subjected to the old "You can't go that way" message a lot – in situation-specific prose, of course – but that message is existential, not just physical. The PC chooses not to go that way, now. Why? Probably because they're being too careful to try not to offend any of the uncaring NPCs.

What is the Temptation of the title? I have no idea. Some googling suggests there aren't solid ideas out there regarding Kafka's original piece. It was an unfinished fragment, after all. I think some mystery is always a good thing.

IFComp 2025 review: Willy's Manor by Joshua Hetzel

Willy's Manor by Joshua Hetzel is a good-natured puzzling-in-a-house parser adventure, no more and no less. The blurb's concept of the PC being a producer for a TV show called Celebrity Houses is the game-unimportant excuse to subject them to a test organised by novelty-manufacturing eccentric Willy in Willy's extravagant manor. In other words, you enter the manor and solve all the adventure game puzzles inside. Willy has a box which dispenses lightly riddly questions whose answers are objects. Put your object-answer in the box, pull the lever and see if you're right to get the next puzzle. It took me about 45 minutes to complete the game using the in-game HINT command seven times. There are some typos, it lacks proofreading polish, and sports the odd non-critical bug, but it works.

The character of Willy is built up during play in his absence. There are lots of photos in his house showing moments from his life that either amused him or were important to him. These include shaking hands with the president of the USA and laying out whoopee cushions. Other notes and books and bits and pieces pay out anecdotes about the man. He comes across as a thoroughly nice and quite nostalgic chap, a Willy Wonka (I assume the main inspiration) without the dark bits. So while it's his house that's supposed to be the subject of the PC's interest, it's really Willy's life that the player seems to be analysing during the course of the puzzling. I don't recall the game specifying Willy's age, but it does all feel like an exercise in looking back in fondness. Ultimately it felt good in its emotion to me, if in danger of being a little cloying on the way.

The game is not technically a limited-parser one but it is one of those that lists all the commands you might need in its HELP section. It doesn't exploit a wide range of actions, sticking to the basics and adding a few custom ones. The in-game graded hints can be called on generally or in relation to specific items, and worked well for me. A couple of times, one of them in the case of a word riddle, I continued to enter HINT until I got the explicit answer.

I'm not sure the manor is as bizarre as the blurb suggests. There's definitely one fantastic section you'd not find in a house, but otherwise it's mostly traditional rooms and halls. It pays to EXAMINE everything. A lot of items don't appear until the PC first notices them. Most puzzles involve you observing the quality of some item and matching it to the riddle answer Willy's box is asking for at the time. A few puzzles in the fantastic section involve more elaborate work, and actually I kicked myself in this area for not being more observant of the environment. I felt I spoiled a good puzzle mechanism with the hints; I blame IFComp haste.

The very last puzzle exasperated me a little as it relies on the player having either a good memory of details of their game, long scrollback that they can review, or a transcript. After wracking my brain I was able to extract from it the needed data. There is a satisfaction in the last room in reviewing Willy's various nostalgic memories, this scene amplifying the overall theme of the game.

Willy's Manor is a little rough-edged and the prose isn't remarkable, but there are lots of puzzles and some good puzzles. The indirect focus on the character of Willy adds an angle to distinguish this arbitrary-puzzling-in-a-house game from the many similar ones out there.

IFComp 2025 review: Not so Happy Easter by Petr Kain

Not so Happy Easter 2025 (NSHE) is a humourous, light horror adventure originally written by Petr Kain in the Czech language. The author's translation of it to English debuts in IFComp 2025. The platform is the ZX Spectrum, one of the most popular 8-bit microcomputers in Europe and the UK in the 1980s, so you need to use an emulator to play it. I used and can recommend Retro Virtual Machine (RVM) which I've used for ZX text adventures before.

I found NSHE to be compelling, well designed and a lot of fun, so I would say to players, yes, it is worth the effort to get the emulator and play it if you're prepared to take that little bit of time to get into (or re-tap) its 8-bit mindset. It has some contemporary design sensibilities like an absence of random deaths and "walking dead" situations, and I also particularly enjoy retro-platformed IF that is set in the present day (unsurprising, as I made one of my own). NSHE offers the anachronistic delights of cell phones, Teslas and QR codes rendered via technology which predates their existence. As an Australian, the game was also culturally interesting for me. It has some local slang, the Czech currency and other European touches which might be inconsequential if you live there but are nice transporting details if you don't.

Note: I don't think the game's playtime estimate of half an hour is accurate. Bringing my retro-adventuring skills to bear, it took me 83 minutes to complete without hints. I don't know if it would be physically possible to get through it in half an hour at the accurately emulated game's sub-5Mhz speed. Commands have processing time, text doesn't appear instantaneously and you can't type too fast or characters are missed by the buffer. It's possible that on a different emulator, you may be able to overcrank a little, but RVM offered me real speed or an impossible-to-manage warp speed. On the plus side, I discovered you only have to type the first two characters of any word to be understood. The great danger for modern players is that L is not short for LOOK here but for LOAD, which will fastload a fastsaved game! To LOOK, either type LOOK or R (Refresh?)

Having recently commended the blurb for valley of glass, at least for its ability to draw me, I think NSHE has a good one too, and which is an accurate tonal harbinger of the game's content:

"You invented a simple adventure game for the kids in the town, where they had to solve simple puzzles and look for chocolate eggs. They solved nothing, they found nothing, and three of them got lost somewhere."

I especially like that second line conveying the mildly exasperated cynicism of the PC voice. The good thing is that that voice doesn't become overly cynical during play. 8-bit games of the day could be snarky at the expense of the game's narrative or atmosphere, and still can be if they emulate that tone, but I found NSHE to be sitting in a good spot. My own feeling of achievement in solving its 75 points worth of puzzles was not undermined by cheap one-liners. Those puzzles involve the PC's search for the missing kids with the goal of avoiding being drubbed by angry parents. There are a handful of F-bombs dropped and some described violence, but contextually there's not much of it and no gratuitousness.

The game starts in a town, and with this section being more open than what comes later, it's potentially a little more difficult, or at least less aimed. I found the key to success is to continue to make your rounds. The environment is mildly dynamic (e.g. there's a bus stop, and a bus that doesn't come immediately, and NPCs who come or go in response to events) but this is a game where repeat visits to locations and retrying actions over time can pay off. Once you've observed this, the fact that the roster of locations isn't too big works for you, as does the limited verb set. The game gives a complete list of verbs if you ask for VOCAB. Anything that can't be expressed with a more specific verb can be effected with USE A, or USE A ON B. There's lots of technical help, too, in the form of colour-coded feedback and the marking of interactive props with inverse text. Such features help prevent the wasting commands on things that aren't implemented.

The post-town adventure which takes place in spookier wilderness is where the game gets denser. This is well-performed classic adventure gaming with lots to do in a small number of locations, some back-and-forthing and the potential for new ideas and uses for such diverse items as an electric bike or a rubber duck to pop into the player's head. I finished with a score of 71/75, interpreting a few actions I performed as gaining bonus points, so there must have been some more that I missed. You can check your SCORE at any time en route.

Overall, Not so Happy Easter 2025 is a solid and solidly 8-bit adventure touching with humour on the tropes of modern life, still managing to exercise a bit of a PC voice and attitude through terse-leaning writing, and which does what it can technically to smooth play.

IFComp 2025 review: valley of glass by Devan Wardrop-Saxton

valley of glass, a lyrical-leaning and extremely short parser game by Devan Wardrop-Saxton, was the first IF I chose to play from the IFComp 2025 crop because I liked the blurb. However, when I say it is extremely short, I mean that it seems incomplete, a stub of an experience. The author may view it as complete – I don't know – but I expect that most players will not experience it that way. My review describes potentially everything in the game.

The blurb for valley of glass starts like this:

Here you are again, walking the North Road in a rare moment alone before another day of your seven years promised to the village blacksmith.

This called to my mind the English folk song The Blacksmith, the first track on both of Steeleye Span's first two studio albums, which I like very much, and I expected to find a broadly similar vibe here.

I assumed the PC was a woman, both because of the song and because of the line in the blurb "promised to the village blacksmith" which I read as being about marriage. When first examining my inventory, I found I was wearing "A heavy woolen coat made for a man twice your size." Then I wasn't sure. Perhaps the seven years I promised were of hard blacksmithing toil? If I was a woman, the coat description sentence was ambiguously written, though admittedly the blurb pointed out it was a borrowed coat; but that's the blurb. That info should be in the game if confusion is to be avoided.

My speculations continued. The blurb continued, "seven years until you may reunite with your love, the Black Bull of Norroway." Now I was thinking woman again, because the Black Bull of Norroway sounded like the kind of entity a woman betrothed to a blacksmith might instead pine for. What cinched the deal for womanhood were my boots: "Plain leather-soled boots that first belonged to your eldest sister, then your second-eldest sister, and now you." To play devil's advocate and suggest the boots might have been passed from sister to brother felt like a stretch atop all the other bits of info.

I thus find myself walking on the road in the game's first location. It's clear the author is unaware of Inform typicalities. X ME replies "as good-looking as ever" and no exits are listed. Testing the directions, I discover that a geographical and/or memory-based blockage exists in three of the four main directions, and that they imply puzzles I expect to solve. e.g.

But until you’ve won your iron shoes from the blacksmith, you’ll never make it past the first few switchbacks.

The southern location was a village. Here, no compass directions worked, so I tried IN. That provoked the end of the game. I had to run the ending a number of times before I got the feeling that yes, it can be considered a legitimate ending, as vague as it is about all things other than that a workday is beginning.

I couldn't locate a blacksmith, forge, shoes, or anyone or anything else, except some jewelled fruits in my inventory, polishable with the cloth I had. My instinct, when stuck in certain kinds of parser game, learned back in the day from Infocom's Wishbringer, is to try squeezing or breaking things I'm holding. BREAK worked here, reducing my jewelled fruits to detritus, but also indicating that this was probably a mistake.

Those are the far extents of the game that I've found. They comprise the start of a character who has memories, possessions that add to that character (the clothes), others that are unexplained (the fruit), and a few locations recalling memories. The lyrical bent of these things is something, but there's not a game here and not enough resolution of what is to convey much else.

Given that I harped on the blurb, I should also point out that valley of glass's synopsis did describe it as "a reimagined moment alone from the folktale Black Bull of Norroway." Moments aren't long, unless you're in Inception. I personally anticipated a certain vibe here because of my acquaintance with Steeleye Span's take on a folk tale, but I expect most other IFCompers won't have that. Perhaps my review describes my process of acclimatising myself to the scale of valley of glass, which I had misapprehended. It never promised me puzzles or greater length, though it presented four geographical nodes that I could have sworn were going to lead to puzzles. I still don't think there's enough detail here to convey the import of the promised moment.

IFComp 2024 review: The Triskelion Affair by Clyde Falsoon

In spite of being the buggiest game I've played this IFComp – though admittedly I have not played many – The Triskelion Affair still held my interest and/or pulled me through. This parser adventure posits the player as a "medieval detective" (quoth the blurb) tasked with finding a magical item hidden in a church. Perhaps, in retrospect, the key piece of information to take from the blurb is this description: "Inspired by the classic dungeon-crawl adventures of yore." And not this other one that says, "Sword & sorcery", which feels wrong. And also not the paradoxical thrust of the whole blurb, which is that you will only get into deeper trouble if you don't explore diligently. I think it's actually the opposite, that by exploring diligently, you will advance in the game and thus unavoidably get into deeper trouble, the nature of adventures in general. That first note about the dungeon-crawl adventures of yore 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.

(cover art by Ian Yarham, Geograph (2024-08-18))

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 on 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. I've found it hard to put my finger on exactly why. I certainly find abandoned church settings inherently creepy and fascinating. There's a sense in this game that there's no overt threat, and that the environment shouldn't be hostile, but 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 to be really buggy. Increasingly so towards its conclusion, where even room names degenerate into exposed Inform code. All the way through, there's almost always just one way to do a thing that's frictionless. Every other way is troubled, missing, leads in disambiguation circles, or suffers from spelling errors or no synonyms. Most alternate obvious uses for objects are not catered to. I've experienced hundreds of games in this state by now in my gaming and reviewing career. These games just needed testing. How this one's state will sit with each player is unknown to me. It's easy to imagine players tossing in the towel due to a lack of trust. Once I'd established the level of bugginess, I didn't hesitate to turn to the walkthrough when needed, or just break out saved games to repeat actions that I had no faith the game would let me repeat without cutting off future success.

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.

IFComp 2024 review: Winter-Over by Emery Joyce and N. Cormier

After enjoying The Killings in Wasacona (KIW) so much, I got wind that another Twine IFComp game, Winter-Over by Emery Joyce and N. Cormier, might present a similar experience, and a comparable one for reviewing purposes. It does and it does. Were you to read no more of this review, what I would say about Winter-Over is that it's fairly dense and challenging on various fronts, and even with the help of its excellent auto-taking Notes feature and character summaries, it's probably best approached not in a hurry, and with mental resources to spare.

The game's sublimely atmopsheric cover image is a real photograph that looks unreal, and this primes the player to enter the strangely cloistered reality of Pickering Station in Antarctica. The PC is Pickering's "mechanic, handyman, and general jack-of-all-trades", and they've brought along their somewhat edgy brother, Daniel. This makes for a complement of about fourteen working at the station, a mixture of men and women, scientists and maintenance staff. When one of them murders Daniel, the PC is driven to try to solve the case themselves because the New Zealand Police are ten days away.

The game's title refers to Winter-over syndrome, a kind of stir craziness particular to workers enduring the long (two thirds of the year) winters at the Earth's poles. The irritableness, depression and aggression from the syndrome potentially affects the behaviour of all the characters in this game. Having paranoid characters trapped in a dangerous situation in the Antarctic immediately recalls John Carpenter's film The Thing (1982), and the game acknowledges this and dispenses with any need to dwell on it by having copies of both The Thing and its same-named 2011 prequel present in the game's rec room video library. This gesture says: You know about The Thing, we know about The Thing. Let's just continue.

Winter-Over (WO) presents as a more cerebrally veiled mystery than KIW. This grows out of its more restricted setting, and the fact that its PC is not letting on, while questioning suspects, that Daniel's death is suspicious. It's being passed off as an accident. Characters and geography tended to be tied together in KIW. You would explore the map, meet different characters and speak to them on their own turf about their experiences. Memories were easier to anchor because each interviewee could be visualised in a particular place. In WO, all the characters work and live together in a finite space. Their work is interconnected. They are not met in discrete venues but roam the station. You will meet almost every character in every location at some point. In fact, a challenge is just working out where particular characters will be at given times when you need to speak to them. It is all challenging; remembering who's who, what to go back and ask someone about, or whom to spend more time with to butter them up. These elements would allow a player to investigate smarter on a replay, though.

WO also offers considerably less commentary on physical environment than KIW, which makes sense as WO's environment is closed and more uniform. This puts the focus on the character dialogue and the PC's thoughts on their interactions. It's a tricky balance keeping dialogue sufficiently lively while also indulging enough repetition that the player can grab onto some routines. While it is a bit drab to be given the exact same questions to ask every major NPC, it means the answers can be more easily compared, even as a samey feeling does threaten the first few questioning sessions.

The characters perhaps need more tics to enable them or their interrelated pecadilloes to be distinguished in the long run. Again, it's tough when they have to frame themselves almost without action, just by responding to similar questions asked repeatedly. It is exciting when you find something that will allow you to goad more out of someone you've already met, whether that something is revelations from a security camera, info about their medical problems or evidence of their handedness (the killer was not a lefty). But just finding a target character can be tough. If you haven't developed their schedule, which is collated for you in the automated Notes section as you play, you can spend many game days trying to encounter them again.

There is some dense plotting in WO, and while I always enjoyed learning new things during play, and feeling the tension of the looming deadline, events often felt like they were floating away from me. I couldn't find people I needed to find, or the PC would become too sleepy and need to take a break, or an exciting one-off event would occur (e.g. the lights go out) that would interrupt both my physical progress and train of thought.

Perhaps this is all less stressful if you consider, going in, that you might need to play again. Given the level of detailed I uncovered, I wasn't sure if I'd be prepared to try again (at least during IFComp) if I didn't succeed. The thought was more stressful than warming. I'd not acquired a sense of how important saving the game would be, either. Maybe I still don't have one. I don't think you can die during the investigation, but can you identify any landmark moments? The investigation is all cumulative. And there is ultimately a lot to enjoy, from the mystery and revelations, and the claustrophobic atmosphere, to the odd violent shock or attack upon the PC.

Comparing it to the broadly similar KIW, I enjoyed KIW more for its varied presentation of characters and the possibilities presented by its skill system, but both games offer a stiff mystery challenge coupled with a lot of helpful features. Both can be replayed. I think KIW offers more replay appeal.

IFComp 2024 review: The Killings in Wasacona by Steve Kollmansberger

Minor tech note: Planet IF seems to display a white gulf at the head of my blog post if I add a graphic, so I may not share the cover graphics of reviewed games any more, or I may at least experiment with placing them at the bottom of the posts instead of the head.

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. I picked Analyst because (a) I liked the sound of it and (b) Claudio Daffra recommended it in his review on intfiction.org (link to that review)

In my experience, games where you have to solve crimes by producing solutions are extremely 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 really 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 rising to a level of strong perceptiveness that I'd have liked to have seen more of:

"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 ever 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 lots of 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.

(Cover art by the game's author using DALL-E 3)

IFComp 2024 review: House Of Wolves by Shruti Deo

...

(cover art by Mango Azalea)

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 correctly predicted what kind of experience was ahead when the first choice I picked from three offered 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 mostly metaphorical(?) Twine piece that looks to me 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, unsatisfactory eating supervised by some unspecified They at night, and visiting 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 heartfelt but too generic prose of the dirge of hopelessness. That is what most annoyed me about this piece in the end, its non-specific version of hopelessness. I know I've made this same criticism of many other pieces of this type over time.

I also didn't understand the wolf metaphor. I am extraordinarily glad it all ended on a note of hope, but it doesn't actually feel like it should. There's not much hope on the way, so the end feels like a deus ex, and I view this shape as the outcome of both thematic and writing problems.

Paradoxically, content warnings don't have to evince much detail before I find fault with them, and this piece's were highly detailed and did it no favours. Too long, too much detail, robbing the piece of surprise, overstimulating the listed effects before they'd even been attempted to be executed by art. Shopping-listed out of their context, I felt worse from the content warnings than I did from the fiction itself. This is a reminder of one of many reasons I don't believe in what are called trigger warnings, or overly specific content warnings. I believe they make people over-believe in their own vulnerabilities. They do that and they spoil stuff, too.

House Of Wolves was plainly not my cup of tea, and I regard its trajectory as unsatisfactory, but it does have a simple grace of execution and presentation on its own terms.

...

PS (September 9)- Having written, "I don't believe in what are called trigger warnings," in the review, I thought afterwards this isn't a personal belief issue, and I should not be treading diplomatically like that and framing it as one. Shouldn't we believe or not believe in the usefulness of these warnings (in a broad context, that they have spread to) based on the best scientific evidence? I used to work at the Medical Journal of Australia and I am interested in evidence from good research.

I googled the topic anew with "is there any scientific evidence for trigger warnings". The results of a series of peer-reviewed articles and meta-analyses clearly sum up the answer in 2024 as "no". I tried to coax google to produce an opposition to these results, "a scientific study that supports trigger warnings". There isn't one. This is not contentious. There are effects from trigger warnings, they just don't help people's mental health. The most consistent finding is that being presented with them and reading them generates anticipatory anxiety for most people.

Anyone can find all of the same research I found with any google search on this topic, as it is all of the multiple front pages, but here are a few specific links:

A Meta-Analysis of the Efficacy of Trigger Warnings, Content Warnings, and Content Notes (in Sage, from Clinical Psychological Research, 2023)

Typology of content warnings and trigger warnings: Systematic review (PLoS One, 2022)

Helping or Harming? The Effect of Trigger Warnings on Individuals With Trauma Histories (in Sage, from Clinical Psychological Research, 2020)

Trigger warning: Empirical Evidence Ahead (Journal of Behaviour Therapy and Experimental Psychiatry, 2018)

Spring Thing 2024 - Wade Clarke Roblox game prize information

(Perma outcome update: This prize was chosen by Vance Chance, and I developed the Roblox platforming adventure game River Rescue Obby as a spinoff from their Spring Thing 2024 game Dragon of Steelthorne. River Rescue Obby was released in August 2024.)

I'm listing here the details and conditions of a prize I'll be offering for Spring Thing 2024: a custom Roblox game based on your Spring Thing entry.

If you choose this prize, here's what happens:

I'll try your Spring Thing game. If I decide it's possible for your game, I (maybe with help from my nephew) will build a simple Roblox game based on your entry, or at least the first room or a prominent thing from it. We have a lot of Roblox building experience between us.

Qualifiers for this prize: I say "game" loosely! It will probably be an environmental toy you can walk around in. But you never know, it might have an objective to reach, or health, or a time limit, or a baddie chasing you, or a physics joke. It might be a reproduction of a location. We'll try to make something of charm based on your game, spending a week max to do so.

If you don't know Roblox, it's free to join, and the game will be pretty G-rated and explorable by anyone on Roblox at any time (which, there being millions of Roblox games, will mostly be you and people you let know about it. Plus the odd random visitor.) You'l be able to share a link to the game wherever/however you like. People only need to have a Roblox account to visit it.

* If you pick the prize, and I try your game and decide I can't produce something satisfying based on it within a week, don't be offended. Roblox suits some things and some subject matter a lot more than others. I'd let you know my decision quickly so you can pick another prize instead.

Music for IFComp 2023 entry Barcarolle In Yellow

Since I've been prioritising my creative energy for making Andromeda Acolytes, something I've been missing is producing music.

After playing Victor Ojuel's giallo IF Barcarolle In Yellow (my review here) I was inspired to produce for it an opening credits track. I'm reproducing the style of music made for these films in the mid-seventies in Europe, so the production is reverby, toppy but not airy, not bassy, a bit cacophonous and a little strangled.

The track mp3 is downloadable from this intfic.org post (no joining required if you aren't a forum member)

IFComp 2023 review: Barcarolle in Yellow by Victor Ojuel

I've currently time to play only a few IFComp entries each year. I try to start with a horror game that speaks to me. This year, the game that's plainly shouting at me is Barcarolle in Yellow by Victor Ojuel.

Cover art by Ara Carrasco

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 review, I hope it's one that can help other players to 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.

* If you don't want to read a review of the game before playing it, but would like to know a little about the giallo genre before you do, you can safely read the About giallo in general section.

* Anyone can also read the Spoiler-free play advice section before playing. In fact, I recommend you do read that before playing!

* Otherwise: The review following those sections is not a spoilery review in terms of what the game would consider to be its surprises. It describes the initial scenes of the game, the nature of the game and story overall and the kinds of tasks the PC will be involved in during the game. It lists some specific ways the PC can die and describes the nudity that's in the game. It says nothing about the content of the ending but something about the nature of the ending.

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 the Barcarolle cover shown earlier in this post to this real poster for The Girl Who Knew Too Much (1963)

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 (NSFW trailer) or 1980s-set Crystal Eyes (NSFW trailer). 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 (NSFW trailer). 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 really 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.

Spring Thing 2023 music prize details

This post offers a few more details about the Spring Thing 2023 prize I'll be offering than will be able to fit on their screen.

The prize is a music commission. I'll compose and produce something for you, or derive something from unreleased recordings I have if they're the ideal match and you like 'em, for your chosen purpose, which can be pretty much anything.

Previously the prize was chosen by the receiver (in IFComp). In the Spring Thing context, it's received randomly. In the IFComp context, I did things like make music for games people were making, or a theme track for a cable TV show.

I specialise in instrumental and electronic music, but can do or wrangle many styles and things, so long as you don't want vocals.

Here are my Restrictive Clauses!

• If you get this prize, you have to call it in within a year of claiming it. If we haven't made the music within the year, the coupon evaporates.
• For non-commercial use, the purpose can be almost anything. For commercial use, the piece can contribute to some creative project you've made or are making. I can decline if the purpose is hazardous, inscrutable or commercially murky, etc.
• Length is a limitation, but up for reasonable negotiation in context. For instance, some electronic or ambient music can be made quite long in the same time it would take to produce a shorter piece in some other kinds or genres. Composing to vision also takes more time.

Links to my music

• My long-term electronic music project is Aeriae:

( Peril Triage is my most recent EP of new stuff. DE is a live set. Victris is my most recent album.)

https://aeriae.com/

https://aeriae.bandcamp.com/

• Some other pieces I've made in different genres can be found on the following Bandcamp page:

https://wadeclarke.bandcamp.com/

of which, the ones listed below were actually for IF games:

Black Giant (sci-fi theme)

Andromeda 1983 (C64 style in-game)

Kerkerkruip (Diablo-esque)

Leadlight Gamma (horror, eclectic)

Ghosterington Night (cheesy spooky)

Music Room Inform source code (from Cragne Manor) now public

Chill: Black Morn manor board game. The map reminds me of Cragne Manor.

Andrew Plotkin maintains a nice webpage hosting Cragne Manor Inform source code files that have been shared publicly by their authors. The other day I sent him my 30k-word source for room M1F5, The Music Room, so it can now be downloaded from or viewed (in easy-to-read format) on the page. Obviously, the source is completely spoilery for the location. A few observations on it:

• I opened ten other sources at random and I guess one thing I can say about mine is it appears to be the most commented of the sources. This will help if you want to try to follow it much, because the room transforms amongst eight different guises during play. The phrases "wadrick-pack-the-new-room" and "wadrick-unpack-the-old-room" teleport people and objects in and out as the player moves through the different sub-rooms.
• There are thirteen rules in the source intercepting all the actions (I could find!) that a player can use to launch a vital object into a room at a vital moment in order to stay alive.
• There's also a reasonable amount of code (in "Section - Wider world rules") diverting/suppressing every alternate path to conversation. Tons of paths had been added by a coordinators-supplied conversation extension that may be great in its own right, but which I recall they ultimately regretted adding, because it created so many potholes for authors. My problem was that with the extension in place, Inform constantly harped on the topic of the vomit object I'd created. If someone was allowed to type ASK in my room, the game would immediately print "(about the vomit)", and as funny as that was for a few minutes, it was more genuinely an annoyance. So I moved aggressively on the whole issue.

Andromeda Acolytes Kickstarter planning notes available

During my 2022 Andromeda Acolytes Kickstarter, I said on the intfiction.org forum that once the campaign was over, I would share my planning notes. I've now done that (they comprise a a ten-page PDF of about 4700 words) in a post on the forum along with some explanatory notes.

IFComp 2022 review: Nose Bleed by Stanley W Baxton

Nose Bleed by Stanley W Baxton, 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. I don't think the first game I've tried in any previous year's Interactive Fiction Competition has made me feel ill so quickly, so after a fashion, this was a good start.

I'd say that if nose bleeds, or blood coming out of your body in general, either in prose or as animated spatter on the screen, or from the cover image below, are likely to make you ill, then both this game and my review are likely to make you ill ill. You have been warned.

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. I am not a psychiatrist, but I have been incapacitatedly socially phobic (two-and-a-half decades ago – treated over years, ultimately left behind) and this looks to be the psychological terrain of this game. Also, 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. Or of the most spectacular nose bleed I ever experienced second-hand as an adolescent, where I was in a car with two sisters, and one of them started jetting from the nose in time with the pumping from her heart. The streamers of blood would hit me whenever the car turned a corner. As much blood gets all over the prose in Nose Bleed. It piles up on the on-screen choices and nothing can stop it. The PC doesn't even try basic techniques I'm aware of like pinching the nose while tilting the head back, though they do come up with the head tilt alone.

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 I'll give it time to percolate. The game's overall design is excellent, 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. I kept thinking as I played, "Surely, it stops here," but I was repeatedly wrong.

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. In Nose Bleed, the blood literally gets in between you and the interface.

Andromeda Acolytes at $9200 of $14k with 54 hours go go!

If you've yet to back and/or promote, we're obviously entering the crunch time, so please don't delay in backing and/or promoting as suits your life situation.

Tell people you're backing a sci-fi game on Kickstarter and it's nearly there. And you can tell them in person or on socials or forums or wherever!

Here's the main link again:

https://www.kickstarter.com/projects/wadeclarke/andromeda-acolytes-a-state-of-the-art-sci-fi-text-adventure

I'll also link you to my latest backer update to let you know where my head's at. Note that if you're already receiving my direct Kickstarter updates and remember me quoting The Phantom Menace, you've read this update.

Here are two other IF Kickstarters I'm backing right now...

(I'd share some graphics but my graphics are screwy on Planet IF at the moment, so I'm leaving them out until I hear back about that)

Stereotypical

Did you know that Scott Adams (through his company Clopas LLC) is also Kickstarting a game at the moment? The Kickstarter for ios/Android game Stereotypical finishes soon after mine. I am backing the project and have faith in the pitched base game described on the page, though I don't think the campaign video is very good. There's also a community element involved in the creation of the game. Check it out yourself:

https://www.kickstarter.com/projects/wadeclarke/andromeda-acolytes-a-state-of-the-art-sci-fi-text-adventure/posts/3588864

Grimfel

I'm also backing Adam Frank's Grimfel, a fantasy Interactive Fiction/Visual Novel hybrid "about your character's gruelling journey through the age of great desolation""(!). I really like the aesthetic he's developed for the game. It offers base content and then ongoing scenarios. If you like these kinds of stories, and in a dark and not-fey mode, check this one out!

https://www.kickstarter.com/projects/grimfel/grimfel-grimdark-fantasy-interactive-fiction-visual-novel/

Andromeda Acolytes Kickstarter passes $6500 – About the IF Competitions, Kickstarter prep and avoiding the Stanford Prison Experiment

The Andromeda Acolytes Kickstarter has passed $6500!

I've been speaking to backers and getting some very nice feedback, too.

There are eight days to go to reach $14k as I type this. If you hadn't thought about backing me before, I obviously wish to stir that thought in your mind. What I'm making is ambitious, and you'll also be helping to raise the monetary water level for all IF. HERE'S THE PROJECT LINK.

What might also sway you:

Today, I'm going to tell you about the IF competitions I ran that preceded the Kickstarter, because they're actually the wildest part of this whole thing. And since they weren't actually directed primarily towards those already involved in IF, they're the part that most of this audience might know least about.

Kickstarter Prep and IF Competitions

... I started on the Kickstarter prep a year and a half ago. The biggest challenge in these things is trying to establish a community or critical mass before you begin, including a sizeable chunk of people who are initially strangers to you.

I built a Discord server and programmed it with teams, a community-building idea described by Mike Rose of No More Robots (games) in a 2019 GDC talk shared to me by Dan Fabulich of Choice of Games. Dan is the gent who got me to take my Kickstarter prep seriously. So in equal seriousness, I'm grateful to him, while in Joke Land, my constitution wants him to pay it restitution.

To the competitions. I decided to invent a version of what had been proposed in the GDC talk that would be appropriate for IF. Also, I wouldn't be stirring up a crowd for a game release as was being done in the GDC talk, I'd be stirring one up for a Kickstarter. And finally, I wanted whatever I did to not resemble the Stanford Prison Experiment, which one audience member at the talk jokingly compared its proposed methods to.

So at this point I was venturing into unexplored territory. I began by vetting IF games to find ones suitable for use in competition. This was hard because most don't use scoring, most have walkthroughs, and those that do use scoring are often too old school. I eventually chose

1. Captain Verdeterre's Plunder by Ryan Veeder – a newbie-friendly time-limited scoring game whose highest score had never been established

2. Napier's Cache by Vivienne Dunstan – No score involved, but it's a character and story driven game of the kind I am pitching myself, and I regard it as the best example of this kind of game that is easiest to play. And

3. Necron's Keep by Dan Welch – A totally unheralded D+D game that frankly I believed only I knew about, at least in the IF circles I frequent. Not newbie-friendly at all, and with bugs, but detailed and lots of fun, and a good last comp discriminator.

I then contrived with the authors and keepers of these games to temporarily hide their help materials from the internet. (Except in the case of Necron's Keep, whose author I've never been able to contact. Logistically, that was okay. I was plainly the world's foremost expert on the game at the time, apart from its author.)

I set up servers with these games on them, and autorecording of player transcripts on the servers. Discord didn't offer certain user ID functionality I needed, so I had to build a Discord bot for that and keep it running 24/7. My friend Andrew Schultz was the Python brains behind this. I created text-adventuring boot camp materials. I solicited and promoted the competitions around the internet, ran them over three weeks and awarded the prizes. This segued into a beta test of the game on Steam, which segued into the Kickstarter launch.

However, the number of users who'd showed up in the Discord was factors below what I wanted, needed or expected. I had to nix the map-making and poetry-writing competitions around Napier's Cache, and reach back out to IF veterans to compete in the case of Necron's Keep, as I hadn't been able to build up a new player base that was in shape to tackle that game. This last detail shows I overestimated how far I could bring people in three weeks. As disappointing as all this was, other good things came out of it that were of a non-numerical nature. Acquaintances were becoming more like friends. Some IF folk spontaneously offered knowledge, advice or help. The Necron's Keep competition was a lot of fun and brought an unheralded game to people's attention. And my promotions created a general awareness of what I was doing in gaming circles relevant to this project.

All I've described above is completely outside the Kickstarter itself. That's a whole other set of work. Integrating and dealing with Steam, too, is a whole other set of work. When my Steam beta test broke on launch, Steam took 36 hours to reply – 75% of the time the test was initially planned to run. Dealing with Apple is also work. I am now an Apple developer, too. I have to keep my certifications up to date and notarise my app each time I rebuild it for Steam.

The strangers-to-community-build is the big element of the pre-campaign I could have tried again from other angles. I (or anyone) could have spent an infinite amount of time at this phase until I'd worked it out. Solving this for a mature, pure prose IF game remains a puzzle. But what I'd already tried was such a massive amount of work, and had cost me so much time, I didn't want to spend more time. I wanted life to go forward, so I began the Kickstarter.

In terms of how I've promoted the campaign from day to day and the manner in which it's grown correspondingly, I'm really pleased with my work. If the campaign doesn't reach the target I set, I think it will really just be because I didn't build a high enough pre-backership, that critical mass I keep referring to. I took some extraordinary actions to try to develop it but they didn't pan out. Nevertheless, here I am!

So don't delay, back Andromeda Acolytes today.

Andromeda Acolytes Kickstarter a week in: Approaching $5000

I've raised more a third of the game's pledge target in a third of the time. $4800+ towards a pure text adventure in 2022 is a very good look, and I've had strangers compliment me on the ground campaign.

Bendy-downy graph trends say that the pledge completion percentage should be ahead of the time passed percentage at this point if you're to ultimately succeed. So while success isn't an impossibility, it's the less likely outcome. I won't talk about this kind of stuff at length now. I'll just say that I have learned a tremendous amount about promotion and Kickstarters over the lead-up and the doing, and I plan to share my experiences, and my 30000 word+ to-do list covering the last year and longer, when this is all over.

My exhortation to you all: Be or Stay excited and help me get a text adventure over the line!

In my most recent backer updates, I shared two very different pieces of original music I had up my sleeve for the title page, the first classical organ, the second all electronic, and some in-game prose about the character who composed the first piece.

I've also created a Spread The Word page (Aaron Reed's Kickstarter was the template) with practical advice, plus all the beautiful banners and screenshots you might want to see/share/use.

I've been blasting the main artwork around the place so often, for this post I thought I'd use the teaser artwork:

Andromeda Acolytes Kickstarter is live!

My exciting news is that today I launched my Kickstarter for my sci-fi text adventure Andromeda Acolytes:

Here's the page:

https://www.kickstarter.com/projects/wadeclarke/andromeda-acolytes-a-state-of-the-art-sci-fi-text-adventure

I'm running the Kickstarter campaign for three weeks. I think the resulting game will be a novel and exciting one, bringing longer form character POV to a parser-driven adventure while keeping the sci-fi, puzzling and mystery elements that define the Andromeda games initiated by Marco Innocenti in 2011's Andromeda Awakening.

If this is something you'd like to see realised – or you suspect you'd like to see it realised but perhaps need a bit more seduction via the information-richness of my Kickstarter page – please visit that page. I hope you'll back me! And don't forget to spruik the link to anyone and anything you think might be interested.

In this blog and in Planet-IFfy circles, it's a relief that I don't have to sell the idea of a text game or interactive fiction in the first place. I thought I might instead say something about the first chapter of the game, which I've released as a playable demo:

https://wadeclarke.com/ifdemos/andacdemo/

I had minor nerves that this chapter might not be showy enough for the Kickstarter. The early chapters introduce different PCs, one per chapter, and in each case the chapter begins during what is a normal day in the life of that PC on the planet Monarch. If you're familiar with the scale of recent parser games, you might already note that it's not usual for a parser game to introduce PCs at such length.

Also, I'd say the first PC, Korhva, is the least demonstrative and most reserved of the cast. This makes her a little more challenging to write, and maybe harder to get a handle on.

Nevertheless, the first chapter is the starting place for the story, so I never really considered using anything else. It's also technically strong. I started this work in 2019, so the first chapter's had more testing than any other.

If you back the game or spread the word or help me in any way, I offer you my sincerest thanks.