The Stack

So, let’s talk story. You’ve got this nameless city, ruled with an iron fist by one Thomas Malik, who keeps the city in an illusion of perpetual daylight. To sustain his magics, he secretly abducts travellers and extracts their souls, rendering them insane. He earnestly believes that everything he does is for the best. Opposing him is a Gnostic sect led by one Evaine, who might possibly be heir to the dynasty of Queens who ruled the city long ago, although I never found any definitive confirmation of this, and strongly suspect that there is none to be found. Malik’s enforcers are hunting for Evaine on the grounds that she’s a rebel and a terrorist, but in the end you learn that the two of them have some personal history together, which makes it seem like the whole city is in the grip of some kind of twisted lover’s spat or something. In a way, it reminds me of Aeon Flux.

As with most heavily plot-based adventures, reaching the end is not difficult: if you just keep plowing ahead wherever the plot guides you, important events will keep occurring until you reach the last important event, which is the ending. But it’s striking that you don’t have to do it this way. Usually, “plot-based” means highly linear and skimpy on simulation, both of which stem from an author’s decision to give priority to their one preimagined storyline over player choices, but that is emphatically not the case here. For example, there’s a point in the story when Malik asks for the player’s help in finding Evaine. In my first play-through, I took him up on it. I suspected that Malik was the bad guy by then, but accepting missions is what you do in these games.  The option to refuse a mission is, in nearly all games, a fake choice; if you choose it, the game will either find an excuse to force the issue or just end. Playing from the beginning a second time, I tried putting up a sterner resistance to Malik in order to see what would happen, and was surprised that he let me go. If I didn’t want to help him, I could just walk away and try to cope with the mysteries of the city on my own. It did not break the plot, although the decision would certainly have consequences.

The only part where player agency really goes away is at the very end, which is a little ironic, because the solution to the final puzzle is precisely to assert your agency, to refuse to be railroaded into doing what the game tells you to do.

City of Secrets is a text adventure by Emily Short, written on commission for a band that wanted it as an extra on their CDs (although this plan fell through for various reasons). It’s one of the few games on the stack that I did not, technically, buy.  It was never for sale; it’s freely downloadable from the Interactive Fiction Archive.  However, I did purchase the feelies, and that gives me the same sense of commitment-to-play as if I had paid for the game itself.

Feelies are tangible objects from the gameworld, a tradition dating back to Infocom and still indulged in from time to time. I purchased the CoS feelies back in 2003 because I enjoyed Emily Short’s previous works and wanted to do my part to support their production. Then I played the game for about fifteen minutes, got intimidated by how much information it was throwing at me, and didn’t get back to it until now.

I shouldn’t have been intimidated. Although the game possesses a great deal of depth of detal, it does a good job of keeping the player from getting lost in it. Plot-crucial information is often available from multiple sources, so it’s seldom if ever necessary to ransack a particular NPC’s entire dialogue tree or read every book on a shelf. This is contrary to adventuring habits, but once you’re used to it, it’s quite liberating.

As to the content: it’s set in a fantasy world with both magic and high technology, trains and robots and illusions.  The player character is a visitor to a big city who gets ensnared in a conflict between the city’s possibly fascist ruler and a mysterious rebel, both of whom are magicians. There are plots and counterplots. One of the first things that I learned was that I had been drugged, although the drug turned out to be an antidote for another drug.

I’ll say more when I’ve completed the game.  Despite the author’s estimation that it takes about three hours to play, I’m about five hours in now, probably because I spend so much time poking at inconsequential details, an activity which the game rewards.