A toolkit for open-world gamebook design

The earliest true gamebook (with rules, that is, and disregarding mere multiple-choice texts) was probably Steve Jackson's Death Test in 1978. That allowed players to backtrack and visit the same location multiple times, but throughout the 1980s the main evolution of gamebooks detoured down a different branch with series like Fighting Fantasy, where the arrow of narrative time pointed in one direction. It wasn't until 1995 that the first open-world gamebooks appeared -- followed by silence until, decades later, series like Steam Highwayman and Legendary Kingdoms took up the torch. Finally it seems that open-world gamebooks might be becoming the dominant form.

I have been sent a succinct and comprehensive toolkit for open-world design that would-be gamebook writers will find very useful. Not just would-be writers, either; I've been doing this since the last millennium and even I found it had some handy tips. You can find that toolkit here. The author prefers to be known only as Ruth, so I will respect her anonymity, though it can only be a matter of time before her own open-world gamebook series appears.

In the Vulcanverse books, when I used what Ruth calls Local Changes, typically I'd include another entry:

So you’d arrive at the location and be presented with the situation that could lead to a change. If you complete that correctly you’re told to turn to the original location and tick the box. Then you get a one-off scene that explains the change and assigns any relevant keywords. If you return to the location subsequently you go to X*A which is the location in its changed state.

Regarding keywords, it’s worth differentiating (and incidentally I say this with 20/20 hindsight) between keywords used as logic flags to denote that an event occurred (“a tidal wave hit the city”) and keywords used to indicate a current state (“the city is in ruins”). In Vulcanverse I could have used keywords and titles respectively for those two functions. I didn’t, which meant that sometimes I’d remove a keyword that was no longer applicable, only to realize later that I’d still like to know if the player had originally had that keyword. Eg if I complete a quest for the king and so he makes me the court champion, even if later on I lose the court champion keyword I still need to have the keyword that says I did the quest. (I'll discuss flags and states in more detail in a future post.)

Regarding rules mechanics generally, I keep promising that next time I’ll create an object-oriented rule set so that I could keep track of, say:

• having one’s face stolen by a mujina
• getting cursed by a fairy to have a donkey’s head
• acquiring blue skin
• being body-swapped into another form

Variously those conditions could mean:

• You’re not recognized by somebody who should know you
• You’re mistaken for someone else
• You are treated differently from other people (potentially in several different ways)

In Fabled Lands I ended up filtering for all those statuses every time I asked the player to check them, whereas if they had been properly organized I could simply have asked, “If you have a status that is listed as transformative and uncanny, go to X”.

Similarly with equipment, where it is useful to have a generic way of identifying whether something can be used as a weapon, or has a blade, or reflects like a mirror, or is made of iron, and so on – rather than having to list the items for each applicable function (such as “if you have the polished shield, the silver mirror, the jade looking-glass…”). Ruth's Multi-Function Item tool covers that one, and could be extended to keywords describing the character’s current status to solve problems like the altered-face one above.

Vulcanverse also used the Current Location feature, a box on your adventure sheet where you record a section number that you are routed to after the current subquest you're on is complete. This allows for encounters to happen at different points around the world, for instance when you're acting as go-between carrying love tokens from Eros to Psyche in The Hammer of the Sun. The Current Location can be used for a lot of things, a common example being when you have a wandering NPC whom the player has to meet up with from time to time, because the different stages of the player's dealings with the NPC don't have to be tied to the geography of the world. You just tell the player to record a Current Location number when the subquest is triggered, then when the next part of their interaction with the NPC (or whatever) is done, you send them back to the Current Location and they resume their travels.

I was going to compile a list of gamebook design resources, but they are many and scattered far and wide. Here are a few to get started. If you know of any others, link to them in the comments.

• "Writing gamebooks" on Lloyd of Gamebooks
• "Wamt to write a gamebook?" on Lloyd of Gamebooks
• "Fetch quests" in the Steam Highwayman books
• "Ambush sequences and the noted passage mechanic" in Steam Highwayman -- which, now that I've seen the article, I realize features the same tool that I call current location (Martin's nomenclature describes it better!).
• "Learning from better gamebooks" on Rand Roll

And while we're on the subject of gamebooks, the Blood Sword 5e hardcover book has just been released in the UK and US. You can buy it at Orc's Nest or from GMS Tabletop Games. The book is a complete 5e roleplaying campaign based on the gamebooks and features some absolutely top-notch design, writing, artwork and production. If you're starting to think about Christmas presents, it's the perfect gift for the avid gamer in your life. Just be aware: they're going to need a bigger stocking.