I’m currently partway through playing and analysing Paul Partington’s Temple of the Skull God, a 2024 independent gamebook. It’s the subject of this month’s 100 Endings Reading Club on Discord and I’m using it as the third test case for a structural analysis I’m developing. It’s a great gamebook, with a clear debt to Fabled Lands and the open-world structure, a pirates/mesoamerican setting with perhaps the occasional escapee from Isla Nublar thrown in. There’s an elegant game system, called GNAT, codewords, tickboxes, an inventory of themed items – and not too many, either – and above all, it’s fun. It’s an adventure gamebook, not a reader-punishment tool or a painful proof of concept!
But while I’m logging all the conditions and links, I’ve noticed a neat and very efficient little pattern that Paul has used to build his world. In a gamebook like this, there has to be some system to govern re-visiting locations, but also something to make them feel memorable and distinct from one another. He does it like this:

What you’ve got here is a three-passage conditional guarded location. You can reach the location from multiple other passages and when you arrive, the first thing you read is a tickbox query. This is empty by default, so on you read.

In this sort of location, the author has stationed some sort of guard – a monster, animal or character who attacks the reader. A simple combat check (often as simple as the one illustrated here) has two outcomes: death – in which case, the adventure is over and no outward link is needed – or victory – in which case the box at the head of the passage is ticked and the player sent on to a subsequent passage. This follower (labelled A.2 in the top diagram) can describe how the guard is overcome, any side-effect on the player and then provide them with some reward for overcoming the enemy – loot of some kind. This passage is then really an event bundled into the location, and the original passage, which is a combat, is an event passage masquerading as a location.
A.2 concludes with options to travel on – normally a spatial choice – and fits back into the network of navigational passages that form an open world.
However, when revisiting Location A, the tickbox, which indicates that the guard has already been overcome and that the loot is already plundered (that’s efficient!) diverts the reader from A.1 to A.3, which is a vanilla location passage without any event, but with the same exit options as A.2.
It’s not rocket science but I think the lock on accessing the loot behind the guardian combat and the smoothness of the tickbox check make this among the most efficient possible ways to introduce guarded locations into an open-world gamebook. Paul uses it about 9 times in a 573-passage book, so it doesn’t become obvious and repetitive, and there are a few variations.
Anyway, it’s certainly a little piece I’ll consider employing myself on my next adventure in this style. Steam Highwayman doesn’t tend to have guards hanging around waiting for you to kill them and take their loot, but it really suits any sort of exploration adventure or dungeon.
If you’re interested in some of my other gamebook structure analyses, you could take a look at this post from February 2025, when I was thinking about Fetch Quests (and writing them into Princes of the West.

