Reviews by Draconis

The first Grand Guignol I’m playing is also one that I tested, because it’s currently got only 12 ratings and I’d like to increase that number. This is another of Schultz’s Prime Pro Rhyme Row games, like There Those Dare Doze, based on rhyming alliterative pairs of words.

This one has some very helpful features that TTDD lacked, such as telling you when a command is half-right, or needs a homophone, and giving hints in return for good-but-wrong guesses. It means that coming up with a good pair feels good, and actually helps you in the game, even when it’s not the solution the author had in mind.

Unfortunately, the implementation of these features feels incomplete. Examining the help device, for example, only tells you how to turn it on—even when it’s already on—and prints “(hard to do without taking it, so you do)” every time, even when you already have it. It’s supposed to tell you when you have a command half-right, but sometimes didn’t, for no apparent reason. (I typed (Spoiler - click to show)PHONING FAE instead of PHONING FEY and got a generic error.)

The writing similarly feels a lot less coherent than in TTDD. The plot of that game was slightly absurd (which is to be expected from a wordplay game like this) but both the story and the geography made sense: you’re travelling in different directions to find other people, and convince them to help you wake the Prayer Pros in the Rare Rows.

This game is a lot vaguer, without much of an overarching structure or geography to connect its various areas. And while it has a lot more rhymes implemented than TTDD, I was still often annoyed when a perfectly good pair wasn’t recognized. (Or, in one case, caused an RTP: “TOE TALL” at the Woe Wall led to a division by zero.)

Finally, for a specific example, there’s a place where the author has clearly put a lot of effort into punishing players who use a bad word (you’re asked to find rhymes for “why witch” and the game tells you specifically not to insult the woman in front of you; if you do, the game snarks at you and crashes itself). But I have to wonder—who does this benefit? Whose experience is improved by this feature? The writing is nice and snarky, but wouldn’t it have been better to just leave the command unrecognized (as other unpleasant words are; you can’t rhyme “wee wight” with “she shite”, for example), and dedicate that effort to polishing the rest of the game? It reminds me somewhat of Graham Nelson going to great pains to hide “swearing mildly” and “swearing obscenely” from Inform 7’s index…which just made it really annoying to remove them if you didn’t want them, and didn’t really benefit anyone.

All in all, I had fun with it. The wordplay puzzles were great! And I think there’s a really solid, really fun game between CSDD’s user-friendliness and hint system and TTDD’s cohesive plot and well-arranged structure. I just wish it had been one game instead of two, because as it is, both of them felt slightly lacking.

The Singularity has come. The world (as you know it) will end in seven days. What will you do?

This is a melancholic, somewhat mournful short story with a choice-based interface. It has the odd interface gimmick that the first click on any link just distorts it into a blurred mess, and you have to click it a second time to actually do anything; I’m not sure what purpose this serves, except to make certain “click a link within three seconds or the game will do it for you” choices even more annoying.

Interface aside, I enjoyed the story a lot. You have seven days left to live. There’s only one choice: what will you spend those days doing? Going out and interacting with the people around you? Or staying in and trying to work on your art? Neither of them really means anything, in the end—neither your work nor your friends will outlive you. So what meaning will you make of them? The writing is sad and bleak, but also more than a little bit hopeful, in an existential way.

Like with Cell 174, this is a work that I’d call a short story rather than a game. The focus is really on the writing, and what it encourages the player to think about. If you knew this was the end of everything, that nothing in your world would exist a week from now, what would you want to be doing? What would matter to you? The game somewhat tries to offer an answer—if you try to (Spoiler - click to show)split your time between writing and socializing your character regrets it all at the end—and I somewhat wish it didn’t. But there is plenty to contemplate, all the same, and this work has a particular feel that’s unlike anything else in the comp.

You’re trapped in a nightmare. But not just a nightmare. Every time you wake up it just changes—you might wake up from being chased by a monster to find your lover crumbling to dust in your arms. (Always “your lover”, not gendered, which is a nice touch even if it sometimes makes for awkward writing.)

This is a choice-based horror puzzle game written in Ink. Your goal is to break out of the recursive nightmare you’re in, and at first it seems like a Groundhog Day time loop, where there’s one “correct” path through the tree of options that will set you free. But there isn’t; there’s something else you have to do.

(Spoiler - click to show)You need to use information from each nightmare in the others. When you’re being chased by a monster, you can run into a tattoo parlor, which reminds you of matching tattoos you and your lover got—and those tattoos are how you break out of the nightmare where they fall apart into dust. This works especially well in Ink, which keeps a transcript of all your past choices for you to consult.

The “aha!” moment of figuring out this puzzle was very cool. Unfortunately, the end result didn’t feel much different from “find the one correct path”. I just couldn’t figure out how to use the clues I was given: (Spoiler - click to show)my lover wanted to go to the church and then get coffee, but the solution isn’t to go to the church or the coffee shop, it’s to go behind the church. In hindsight I can see how this makes sense, but while playing, I ended up lawnmowering the last nightmare (trying each option one by one) until I came across the one that worked.

All in all, it’s a very cool idea, and I like the sort of horror on show here—it’s different from anything else I’ve played in this comp, and offers very satisfying catharsis. But my experience would have been a lot better if the clues had been a little bit clearer, and some of the red herrings removed. I understand why some red herring options need to exist, for the puzzle to be satisfying instead of “click this link to win”. But I ended up giving up on the right answer to the final puzzle because those red herrings made me think I was on completely the wrong track.

It’s a beautiful day in the mansion, and you are a horrible ghost. A new owner has just purchased your ancestral estate and is about to bring their awful corporeal biological presence into it. You have five hours to make the house as spooky as possible and put a stop to this!

This is a lighthearted choice-based optimization game. As you roam about the mansion you find various spooky tricks you could play on the owner; each increases the “spookiness” of the house by a certain amount, but each also costs a certain amount of time. The goal is to get the maximum spookiness in the five hours allotted.

It’s not an especially difficult optimization problem—you only have one resource to worry about, so you just need to choose all the haunts that have the best spookiness-to-time ratio—but I enjoyed the tone and the writing a lot. I played this with some of my family and they loved the ghost’s analysis of their various little tricks, and the different endings you could get with different levels of optimization. This one is definitely getting a high rating from me.

This one appears to be the third in a series I haven’t played, but hopefully it stands on its own. It takes the format of a text conversation, with messages from your contacts appearing one by one, and you choosing how to respond. The visual presentation is quite sleek, though I honestly wish it had been simpler—I spent a long time waiting for text to slowly fade in, even when it’s a choice for me to click rather than a message from someone else, and the messages floating around in different directions and bumping into each other was mildly distracting. Sometimes I could scroll down too far and leave the whole conversation behind; other times the messages were cut off at the bottom and I couldn’t scroll down any further. The background music was atmospheric, though I turned it off after a little bit.

(The flow of this review is different from the rest because I keep tabbing over to work on this while I wait for the messages to appear. It takes a while.)

Interface issues aside, this is a spooky little short story told through online chats. Your mother messages you to say that your friend has arrived, and is waiting in your room. Then your friend messages to say they got delayed on the train. So who, or what, is it that your mother just let into the house??

Sadly I found the climax less compelling than the premise. (Spoiler - click to show)Your friend’s doppelganger starts messaging you in Zalgo text and sending you uncanny pictures from the internet. I’m not sure if the bathos was intended or not, but it ended up feeling like a bit of a letdown after the spooky premise. I somewhat wish the entity itself had been left in the background, rather than messaging you directly, because only hearing about it secondhand could keep it both scary and vague at the same time.

I enjoyed this one, but I wish the climax had kept up the spooky atmosphere from the beginning.

From the description, this one seems to be a parser puzzlefest written in Inform 7. You’re a 12-year-old trick-or-treating on your own for the first time, and perhaps inadvisably decided to knock on Old Man McGuffin’s door. He chose “trick” and left you with a strange device that traps you in a time loop: after seventeen turns, you’re reset to the start of the game.

Unfortunately, I think this is the first Petite Mort I can’t solve on my own. I like the idea a lot, but the implementation just confuses me too deeply. I started making a map, and ended up finding a loop that I can’t reconcile: going north, west, south, west, west from the front yard brings you back to it again. I found a way to leave the device behind (put it in the box, close the box, drop the box) but it keeps being described as in my hand. “Fields of rustling corn” are an impassible barrier, while “an impenetrable line of trees” is an exit you can use.

With hints, I managed to solve it. I like the puzzle, but the implementation gets in the way frustratingly often. Some important actions persist across time loops, like (Spoiler - click to show)PULL ROPE, and give confusing error messages if you try them after already doing them on a previous loop. McGuffin expects you to say “trick or treat” when you find him later, and prints the same text as at the beginning, but doesn’t reset the loop. Using commands that are slightly off, like (Spoiler - click to show)SHOW BOX instead of GIVE BOX, does nothing. I like the game, but the implementation issues keep me from really recommending it.

Epistolary IF! I always love it when a piece makes use of the medium in a clever way.

This is a Twine work where the classic “click links to change their text; click other links to move on to the next page” represents the process of editing a letter. The story is told through the general outline of each letter; you can write and rewrite certain passages to your liking, then send it off. The story then advances to the next letter, a week or two later.

The protagonist is Helen Compton, recently married, writing letters home to tell her sister about her marriage. I’m slightly ashamed to admit how long it took me to realize what story was being adapted here, because in hindsight there were so many clear indications—in other words, I was as clueless as Helen about who her new husband was.

There are a few different endings you can get; I found three, and I think the first one I got (before I went back and chose “all the first option”, “all the second option”, and “all the third option”) was the best. The writing was excellent, it used the medium in a clever way, and the length and pacing were top-notch. This might be my new favorite to win the comp.

This is a ChoiceScript game set in Imperial Constantinople, which I think means it’s somewhere between ~400 and ~1400 CE—my knowledge of history is unfortunately much weaker than my knowledge of historical languages! You’re a sea captain named Peter, a guest at a high-society party thrown by your friend Demetrios, entertaining “merchants draped in cloth and woman with intricate veils, scholars sitting straight, Imperial administrators proudly sporting their badges of office”.

All of them speak exclusively in rhyme, and look down on you for not being able to do the same. Your goal is to tell them a story that will satisfy them. (The rhyming seems to represent some sort of linguistic difference: at one point a friend of yours abandons rhyme and “shift[s] down into the common register”. It’s a neat touch, because it makes the high-prestige register sound both difficult to execute and faintly absurd, which is presumably how Peter sees it.)

The story you tell them is, unfortunately, very short. You get one real choice to make during it—which is an interesting one! And the writing is certainly engaging.

But even after a couple different playthroughs, I was left wanting more. The four-hour deadline puts tight limits on how much writing can be in a Petite Mort game, but I wish a little more of it had been dedicated to the story itself, and a little less to the frame narrative. Both the high society of Constantinople and the strange affairs happening out at sea are fun and engaging, yet the overall impression I’m left with is that I want a proper serving of either one, rather than just a little taste of both.

P.S. I was tempted to write this in rhyme, but decided it’d take too much time. I might have to try again later, when I’m done with my duties as rater.

This is a work that I’m not quite sure how to describe. It’s a very short parser game written in Inform 7, and it’s quick to play—usually over in just a couple of turns. You’re riding in a buggy (as in the type of cart), in pursuit of a mysterious foe.

I recommend playing it, because it’s hard to say much more than that without spoiling its central conceit. So go do that first. Or, if you don’t care about spoilers:

(Spoiler - click to show)The core of this game is puns. The game is buggy, in the sense that it’s got (intentional) typos and also in the sense that that’s what you’re riding. You’re as good-looking as Ever (your brother Everett), and you can jump on the spot fruitfully (catching a branch of crab-apples). You think there’s a Suchthing around, but you can’t quite see it. The fourth wall is thin here, and every message the parser produces is also happening in the world itself.

This is another short game, where getting an ending takes only a couple turns but there are plenty of different endings to find, and I think that’s the right structure for it—its brand of surrealness would get old if it were drawn out much further. Though I do wish I could eventually find out what we’re pursuing.

This one is more interactive poetry than interactive fiction: a sequence of stanzas hyperlinked together, with additional lines that show up when you click particular words. It’s a genre that I haven’t seen much of before, but one that seems very well-suited to Twine’s format.

It’s about gay vampire lovers, which I adore. The writing is quite nice, and the poem overall is short but sweet. It feels like it’s just the length it should be.

I want to comment more on it, but unfortunately I’ve never been great at this type of criticism—I can write a lot about my feelings on different types of gameplay, but that’s not especially relevant here. So I’ll conclude by saying simply that I enjoyed it, and quoting a passage I especially liked:


only you love him the way
a wound bays for the knife
a raw socket misses the tooth
restless tongue probing
cavernous ache.