Let Them Eat Cake

A humble village! You, a new baker's apprentice! Why, there's a miller, farmer, priest and all that sort of thing! Sadly, a barrow-boy, hauling whatever they haul in barrows, and the old lamplighter are not in on the act. But you do what you can. The cake can't be too fancy. There's a system of barter and trust, roughly, with even a system of credit if someone can't pay just now. For instance, the farmer has given all their eggs to the priest, who is willing to swap for something later. It's understood that you help people carry or unload sacks, since you're so young. The font is a cheery cursive, and there are appealing graphics. Picturesque, indeed! You even get to type in your own name and the name of a cat you meet in a script font, which also appears at the game. This and the postcard-ish boxing of text gives an almost cutesy feel.

It will stay that way, as long as you don't get too nosy. The moment you do, though, sordid layers get peeled back. You find things you find in a trough, or in the baker's recipe book, or even around the nice old lady who assures you the "POISON" jar is not where the sugar is. So absent-minded! There are plenty of ways to get killed, but the game assures you there are lots of endings. I got 15 out of 8, presumably to reinforce the "more than meets the eye" angle. This sets us up for a potentially neat play/explore/replay cycle where we do eventually manage to explore everywhere and find interesting deaths. Another look at the cover art makes you realize something odd. That shadow is the wrong shape and color. Oh dear!

Unfortunately the technical side is a bit lacking. There are a few loops. If you click on "credits" at the end, you're kicked to a page with no way back. With little time left to judge IFComp initially, I threw in the towel, quitting while I was ahead. An individual playthrough is relatively quick, though there is a lot of overlap that seems unavoidable with the main quests--if you explore too much, you die and have to start over. So I quickly experienced a bit of dread looking through what I needed to. Maybe I didn't map what pitfalls were where carefully enough.

As-is, I got the "good" ending the second time, and I was invited to a faux-idyllic town gathering choose someone to be the Reign. They weren't happy about it. I'll invite you to play to find out why. So the cake got baked and eaten, which counts as a success. But I do think that, if there are different endings based on who is the reign, that's all a bit much to grind through repeatedly to see them. I wasn't quite curious enough to click through repeatedly.

This is a tricky one. UNDO all over would allow the player to lawnmower the end and know too much too soon, but blocking it out made exploring tedious. I'd suggest a compromise where, once you've made it to the gathering, you can click through "get the milk" and so forth on replay, to cut out a lot of unrewarding repetition. There'd be some leeway for the author on whether or not they should nudge the player to say hey, you're done here.

Let Them Eat Cake feels like a relative tap-in to fix some features to make it even more playable post-comp (the bugs mentioned,) and perhaps there's a good way to streamline different parts you've already seen or at least to indicate that the reader has done everything they can in a certain branch. So perhaps a one-two punch of post-comp releases would be good, one for maintenance, and one to smooth out seeing all of the village and all the deaths. Goat Game is a good example of how to invite lawnmowering without driving a player crazy or making them feel they aren't doing much. LTEC does seem worth the challenge, both for us and the author, though I haven't checked since my first try! It has a strong sense of setting, and while I saw what I reckon are a few errors in translation, those aren't nearly enough to sway a very favorable opinion of it. It definitely achieved "worth looking at" status, and I like the pace at which secrets were revealed to a player who poked around.