Reviews by Wade Clarke

(This review is an edited version of one originally posted to my blog during IFComp 2025)

valley of glass, a lyrical-leaning and extremely short parser game, was the first I chose to play from the IFComp 2025 crop because I liked the blurb. When I say it is extremely short, I mean that it seems incomplete, a stub of an experience. I expect most players will experience it this way.

The blurb opens 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."

Playing, it's clear the author was not aware of Inform typicalities. X ME replies "as good-looking as ever" and no exits are listed. Testing the directions, I discovered that a geographical and/or memory-based blockage existed in three of the four main ones, and that they implied puzzles I expected 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 sense that yes, it could be considered a legitimate ending, as vague as it was about all things other than that a workday was 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 found. They comprise the start of a character who has memories, possessions which add to that character (the clothes), others which are unexplained (the fruit), and a few locations recalling memories. The lyrical bent of these things is something, but there's not really a game here and not enough resolution of what is to convey much else.

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

my creation is a short (10 minutes) parser game 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.

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 this 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 the author 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.