Rabbit's IFComp 2026 Reviews

The Very Last Night I Spent at Ethelred Estate (Kai DeJesus)

Played on: 8th September
How I played it: Online via the IFComp ballot
How long I spent: 30mins for three playthroughs, only one of which reached an ending

SPOILER WARNING: I’m going to give away the main reveal of the game here, i.e. the reveal related to the content warnings.

Unfortunately The Very Last Night I Spent at Ethelred Estate has got some problems. There are some great flourishes here, especially in its experimentation with the player character’s frame of mind, but it’s badly hampered by a lot of textual errors and game logic issues, including a game-breaking bug. (I’ll explain later, but if you want to play before reading this, I think you need to choose “celebrate a life” instead of “celebrate a union” near the beginning if you want to reach an ending.)

Ethelred Estate is a 15-minute gothic horror story, framed as a dream-slash-flashback to the player character’s final night at their former home. At a family gathering, we learn that the prosperity of our bloodline comes at a terrible cost, the life of each generation’s first unborn child; that is, we are about to miscarry. The events of the game see us drifting through a family gathering, alienated, waiting for the inevitable.

It’s a devastating and morbid concept, and framing it as a dream allows for a lot of latitude with the idea. I really like what the author does with narrative voice here. Ethelred Estate is made in Texture, and many of its decision points prompt you to drag an adjective onto the player character’s behaviours. The most significant of these completely recontextualise the player character’s response to the information; for example, instead of reacting with the expected amount of grief to the news that we are soon to lose our child, you can instead respond with relief that we won’t be carrying the child to term, which changes the tone of some future passages significantly. Clever little bits of wordplay also mutate the tone; a reference to cockroaches can either be literal, in which case we flee a vermin-infested room, or metaphorical, in which case we find ourselves despising our party guests. Given the short nature of the game and the suggestion that this is a recurring dream which changes every time, we are pushed to play multiple times and experiment with different responses, and so we drift through all sorts of different mental states, wandering from one scene to the next, never quite sure what we’re truly feeling. This is neat!

However… We have quite a lot of technical problems with the actual text, which makes it a struggle to parse what’s going on, perhaps more so than intended. There are quite a few grammatical and syntactical issues – missing words and the like, things that suggest that the game wasn’t given a proper proofread. I’ll forgive the past/present tense slippages because they add to the dreamlike swirl of scenes and the uncertain flow of time that the game is going for, but I’m not certain they’re intentional. Some choices of phrase are infelicitous and feel parodic, such as a scene in your father’s office which outputs “I find a copy of our financial records, in the red, red, red like blood” - that extremely blunt simile and its clumsy parallel between the family curse and the family finances read like a joke. There are issues with the game logic throughout as well, so that scenes don’t quite progress properly. A few times, we have a binary choice where both options produce similar text but only one progresses the story, leaving to repetition and odd pacing. Here’s the output of a scene where you’re prompted to both kill and spare your child, but where both need to be clicked, causing the scene’s cliffhanger to be doubled up:

I steel my resolve. I have little time. I must do this now. But before I can, I hear my baby cry. And then I hear a scream.

But I cannot kill him. I cannot. I cannot. And I cry for the child, for all the children sacrificed to this awful curse. Then I hear a scream.

Worse yet, there is that game-breaking bug which I think a few judges have run into already. Early in the game, you’re prompted to choose whether you’re celebrating a union, in which case the narrative is set against the backdrop of your own wedding, or celebrating a life, which puts you at your brother’s funeral. However, in both routes the game eventually places you in a church with your brother lying in state, which implies that the brother’s funeral happens no matter what. In that scene you’re prompted to “listen close,” and from my experiments it looks like the game softlocks at this point if you’re celebrating a union, but progresses with a Next arrow if you’re celebrating a life. This is just my guess, but it seems like Ethelred Estate only has an ending and game logic written for the funeral path, and when you’re shuttled onto it from the wedding path, you haven’t made the choices that set up the variables that the game wants to read for the funeral, so it can’t continue. If you were celebrating a life all along I think you don’t get stopped - I haven’t run every contingency to make sure, but that life/union choice seems like the most likely culprit. So it’s an avoidable bug, but it’s only avoidable by making the right choice ten minutes beforehand, and either way it’s not a great bug to have.

It’s a shame, as there are some cool tricks here, but I can’t recommend Ethelred Estate in its current state. There’s still plenty of time in the comp, so hopefully the author can do a late testing and proofreading pass and get the game updated for the rest of the voting period.

9 Likes