Discworld RPG: Concludium

In this Octobereview, I wrap up the Discworld Roleplaying Game (powered by GURPS), by Terry Pratchett and Phil Masters. Last time, I talked about the setting chapters.

This time, I'm reviewing the remaining parts of the book (pp 367–408), all the juicy running-the-game stuff!

This is probably the most important section to me. Although the 'GURPS rules' parts are necessary for running the game, and the 'Discworld review' parts are necessary for understanding the canon world, this is where the authors are handed the reins to really extrapolate, develop, and get creative.

Part 11: Bad food, no sleep, and strange people

We start the section with Running for your laugh, guidance for game/campaign management. There's some good general structural advice here. They also managed to get a chuckle out of me (p 368):

If anyone really wanted, they could use the setting for an old-fashioned game in which heroes and wizards beat up monsters and take their treasure. Or they could create gloomy sagas about angst-ridden vampires on the streets of Ankh-Morpork. There's no obvious reason to do so, but nothing to stop anyone, either.

The authors talk about managing tempo and pace (p 369). This advice is generally good, but some lines jumped out to me here: "a fight that lasts mere seconds in the game world can take much of the session to run [...] The GM should avoid combat if the current aim of the game is to get to the next important plot point quickly." Emphasis in original.

I must admit, this – and some similar language scattered throughout the book – rubbed me the wrong way. It practically admits that the underlying engine is too slow to be useful. It also suggests a view of the GM as fundamentally a linear storyteller, which might be appropriate if this was, you know, a story-telling game, rather than a traditional TTRPG with a smattering of story-telling elements.* Pesto and chocolate milk are both tasty, and maybe you could find a recipe to combine them complementarily, but it's been 368 pages of rules for chocolate milk and now I'm being told to sprinkle pesto on top.

* The implication, here and elsewhere, is that the GM's role is to decide "the next important plot point", disregarding choices and rules to shepherd the player (character)s towards it. I'm not a fan.

The text goes on to add, "In general, Discworld games should run fast and light. [...] A roleplaying game, humorous or not, is a cooperative project, and if the GM takes too much power from the players, they'll ultimately become frustrated. Everyone should be allowed input." Again, this sentiment seems out of place for a simulation-heavy TTRPG

"Everyone should be allowed input" ...into what, exactly? This pretty clearly doesn't just mean the truism, "don't take away for non-diegetic reasons the exactly one way players can affect their environment in a classic TTRPG, i.e., their power to make their characters' decisions".

Even with a generous reading it seems to mean, "import story-telling-game elements into how you run this TTRPG, by having aspects of the world/outcomes decided by an unspecified collaborative process with the players." And in 408 pages there are no rules for doing that, and little to no advice for dealing with the dissonance of players having to break out of the making-decisions-as-if-they-were-their-character headspace to make decisions about the world as if they were its creator. Shrug.

One little thing that caught my attention, on p 371, is that "The Colour of Magic contains several RPG references". This surprised me; maybe I need to read it again.* It definitely contains a lot of references to the sort of 1960s-70s pulp adventure and sci-fi/fantasy fiction on which early D&D was built, but if there are direct TTRPG aspects, I never noticed them.

* The game the gods play throughout has miniature tokens representing characters and creatures, but I remember it being in much more of a "European boardgame" style.

Sample campaign setting

The book's main sample setting (essentially, pirate adventure in the Brown Islands*) is quite good! It covers a region that sits largely outside of the Discworld canon, and it hits a lot of the right notes in terms of descriptiveness and usefulness to a GM. The islands are presented as a sort of semi-policed melting-pot wilderness borderlands, which is an excellent background for RPG adventure.

* A pastiche of Hawaii, mostly.

I'm pretty sure that Llapffargoch-Wokkaiiooii is meant to extend the Hawaiian pastiche to include some of the Pacific Islands and New Zealand, which (as a New Zealander) feels a bit forced, but that's pretty much always going to be the case when you're reading an outsider's view.

I've got to say, the idea of hiring the PCs to "break into an enemy's home or workplace and rearrange the furniture to bring bad luck" is great. That's completely outside of the classic RPG scenario space, and I'd love to use it some day. (The book also gives it pretty thorough mechanical support.)

The Discworld RPG presents several other settings in short form, and all of them seem like they could be a good time. For example, there's advice for a Fourecks "road warrior" setting.* I should note that this book is somewhat old-fashioned in places, but it could be worse when it comes to things like colonialism and female empowerment. The Brown Islands is run by foreign governors... but the indigenous people don't much care what they say. There's a Klatchian setting with a harem... but the women are comfortably running the town. Et cetera.

* I was expecting the waterless regatta from The Last Continent, given this book's reluctance to extend canon. I suspect road warrior was chosen just for the cart wars / car wars joke.

Sample scenarios

The book presents three adventure scenarios; two about fruit and one about herring historical justice.

In "Lost and Found", the PCs investigate a banana shortage and discover a magical jungle lab emitting reptilian monsters. In "Full Court Press", the PCs get involved in the succession politics of an apple-growing duchy. In "Sektoberfest in NoThingFjord", the PCs set out to rescue a skald (storyteller) from a huge troll and probably end up settling a historical injustice.

I want to say off the bat that the underlying ideas are great. I'd run a scenario based on the first or third scenario without hesitation. 👍

And the implementation of those ideas is mostly good. 👍

Unfortunately, the presentation of the scenarios is undermined by two major issues.

Issue 1: Failing to help the reader

The authors commit one of the cardinal sins of RPG scenario design: presenting the adventure as a fun little mystery for the GM to be puzzled by until they've read to the end. None of the important parts are explained up front. The authors want the players to feel like they're experiencing a story? Sure. Writing the scenario as if the GM trying to read the thing also has to experience it as a story? Excruciating.

So in Lost and Found, the GM reading isn't told why there's a banana shortage, which is the entire basis of the scenario. Without a precis sketch up front, they won't find out for many pages. Long after they encounter a text box which says: "remember that the problem lies hundreds of miles distant, and is somewhat peculiar, with a certain amount of unconventional magic involved." The reader can't "remember" those three things. They haven't been told any of it!

So the GM who just wants to know if they like this adventure enough to study it and run it has to read the whole thing through to find out, then reread it with the basis facts required to actually plan how to use the scenario. It would have been trivially easy to provide the necessary information in a text box or paragraph at the start.

In Full Court Press, it's worse. The scenario writers simply didn't finish their job. Who killed the old duke, and why? What do the various described activities indicate? Well, it "depends on what the GM has decided about the true history and motivation of the NPCs" (p 394). "Matters should culminate in the revelation of some truth".

This is a cop-out, and one which particularly stings because not only does the text lack a disclaimer up front ("this scenario is incomplete"), it actually claims a GM can use the scenario "as is"!

If the problem was space, why not just write even less of the adventure and put it with the other incomplete scenario ideas at the end of the book?

The "failing to help the reader" issue comes up somewhat in Sektoberfest in NoThingFjord, too. The PCs are in a cave complex chasing after an abducted skald (p 396). They hear a deep voice relating things that happened in the past (something a skald does), and then they see the abductee. Seven paragraphs and a section break later, the reader discovers that it's not the skald who's been talking! I'm fairly sure this was just sloppy editing rather than a deliberate mystery, but again, a paragraph at the start sketching the overall scenario would have avoided the problem.

Issue 2: Implied culture of play

The other issue I'll freely admit is subjective: The scenarios advocate for a culture of play which makes me uncomfortable. It's similar to the problem I had with some of the tempo/pace advice (above).

We're told that the GM should just veto a PC's advantages from putting points in Wealth (p 386). The GM should fudge dice results and move things behind the scenes and ignore creature traits (p 391) so that things happen as they envisaged. There's this expectation for the GM to have an idea of "the way things ought to go" and covertly change things to make that happen. Is it railroading? It's at least railroading-adjacent.

Reading Sektoberfest in NoThingFjord, I started to believe that the authors just fundamentally disagree with what I would consider the deepest TTRPG loop: mentally simulating a world, seeing what the characters try to do, and then arriving at plausible outcomes using rules + good judgment + knowledge of how the world works.

• Instead of referring to rules for light, it's "reasonable" to "penalise" explorers for not taking equipment such as lanterns.
• Instead of referring to rules for navigation, "there's only a limited amount of fun to be had by getting them lost, and having them completely lost and starving to death is dull. But the players might pay more attention if they sense that the GM is thinking about that possibility."*
• Players get to "make IQ rolls to grasp the subtleties of" an issue once the GM has described it, instead of engaging their brains.
• After the script says a troll gestures at the wall, "visitors should make Per rolls to notice the general shape of the walls on the far side of the cave." Implicitly, characters can't notice a secret until the "right" story beat, no matter what they do.

* There are numerous references throughout the book to the GM feeling "kind" or "sadistic".

Again: The Discworld RPG has very few story-telling-game mechanics, and the ones it has (like Riding The Narrative) are limited and optional. But there are all these little asides telling a GM not to run the game as the crunchy traditional GURPS TTRPG it has been built as.

I understand that occasionally a GM might end up with the donkey up the minaret, and have to choose between (a) cheating to create a fun play experience, or (b) letting the chips fall where they may. But note that this is a choice.

If you play it without cheating, yes, you might have an early TPK or an anticlimactic ending or have to split a session because you run out of time. Yes, it might be less fun.* You at least won't be teaching the players lessons like "the PCs can't lose" or "the PCs can't win early with cleverness" or "there will be x amount of conflict per game session no matter what" or "the GM doesn't care about the rules of the game".

* But you don't know for sure.

If the GM finds that they need to cheat to "save" a fun play experience, something brought them to that point. It's almost certainly down to a failure of the system, a failure of the scenario, or a failure of the GM. Two of those things were within the purview of the authors to fix, and in a book of this size they could have advised on the third. Instead, they keep calling for a thumb on the scale within the scenario design. My personal opinion is that it's a bad look. Rant over; my apologies.

Other scenario possibilities

Fortunately, we don't have to end the review on a sour note! The final part of the chapter ends with a half a dozen scenario seeds, for a GM to take and run with. These are all very ideas-dense and a great fit for the canon, and I enjoyed reading them.

If I were to run the GURPS Discworld RPG, I'd pick one of these to start with – probably Plumbing the depths. If PTerry hadn't suffered his health disaster, I think we were cued up for a book about the Undertaking in Ankh-Morpork, and this offers a chance to explore what that might have been.

Remainder

There's some end matter, too! It consists of a slightly absurd glossary of Disc terms, the inevitable Discworld + GURPS bibliography (which sums up the books fairly pithily), and a comprehensive index which almost never just redirects the reader to another index entry (D&D, take note).

Final thoughts

I began this book as a Discworld fan and GURPS outsider. By the end of it, I had a better grip on GURPS and an itch to go back and read through the Discworld books. I consider that a win!

I'm also backing the new Modiphius game, Terry Pratchett's Discworld RPG: Adventures in Ankh-Morpork. I can't wait to see the difference in approaches to this large (and for many reasons difficult-to-translate) corpus of creative material.

Discworld RPG: The setting

In this Octobereview, it's another look at the thick tome that is the Discworld Roleplaying Game (powered by GURPS), by Terry Pratchett and Phil Masters. Last time, I talked about the magic system.

This time, I'm reviewing all the setting stuff (pp 220-366)! Lands, environs, NPCs, scenarios, and so on.

I mentioned when I cracked this book open for the first Octobereview that there's really no winning in TTRPG book layout. To wit, this book splits its setting guide into a hefty Part 1 (in case you're unfamiliar with Discworld) and then comes back to it in Parts 6–11 (in case you're only somewhat familiar with Discworld). It's an inelegant split, but better than any alternative I could think of.

A lot actually happens from the start of a given Discworld book to the end, and although the chronology is muddled, there were substantial overall changes to the setting over the course of the series. The Discworld Roleplaying Game does a pretty good job of accounting for all the different points in time which players might play in.

Part 6: Life and Lands

I think PTerry had a particular Theory Of History And Society which shone through in his work. It's been interesting to see the GURPS authors' take on it. I think they do a pretty good job, with some exceptions.*

* For example, I wonder if re-framing dwarf vs troll conflict as being about 'vertical real estate' as the 'source of the problem', p. 228, was meant to have the undertones it has.

This chapter, p 220-267, is 'Life and Lands' information: a fairly thorough Discworld physical/cultural geography primer with very little game-specific content, just a minor 'adventuring lens'. It's all Discworld and not much game, so it's hard for me to evaluate its usefulness to the average GM.

All this could have come straight out of the Discworld Companion, and maybe it did. The book has diamond trolls emitting light (p 230), which I think is a misunderstanding. My only other note here is that the similarity of the phrases 'Octarine Grass Country' and 'Ultraviolet Grasslands' left me thinking about a crossover for a while.

Part 7: Ankh-Morpork

This continues being more 'setting overview' than 'gameplay aide'. I don't have much to say that wouldn't just reflect Discworld itself.

One rough spot shows on p 257, which lists a watchman's equipment. The GURPS rules say the watch officer will necessarily be at Light encumbrance or higher; the book takes pains to point out unencumbered PCs can therefore just run away from the watch. It advises that if they do, they can be penalised by running into specific Named Characters. The bottom line to me is that it's true of this fictional world that a watchman can't catch a fleeing perp (PC or NPC). That's a broken mechanic and the authors just chose to slap a crude patch on it.

I also spotted the very first typographical error after 259 pages of quite dense text: an extra comma in the 'orphans' box.* I used to be a copy-editor; that's a frankly superb hit rate. The whole book is very professionally made.

*A missed opportunity to do some extremely rare and on-the-nose grammatical irony.

A few other slips in the section were, I think, American writers not quite nailing British English, e.g., 'gasoline' for 'petrol' (p 270).

Part 8: Supernatural wotsits

This section offers a bit more advice about magic and its uses, including keeping PCs in line. Like the 'watchmen can't catch you' problem in Part 7 I think some of this should have been solved at its source instead of having a patch slapped on top.

There's discussions of gods and so on; not much in the way of game mechanics. A serviceable chapter.

Part 9: NPCs et al.

With NPCs we return (p 305) to the really GURPSy bits for the first time in a while. Here we get, for almost every major character in the series, either some abbreviated character attributes or a full GURPS character stat block.

We also get some advice for using canon characters in play, which amounts to "don't overdo it". Of course, it's damned-if-you-do,-damned-if-you-don't: the Disc books and humour are extremely character-driven. But as the Discworld RPG points out, hitting the right tone for a well-established, well-loved character from a different form of media is necessarily going to be difficult for pretty much any GM. If you're going to try it, this book is determined to give you 45 pages of stats to fall back on!

Part 10: Critters

We also get stats for Discworld animals – including the Disc 'versions' of regular animals (superintelligent camels, occult cats, sapient dogs) – and monsters.

There were some interesting choices about which beasts to include. Of the classic swords-and-sorcery slash-em-up monsters which show up in Discworld, very few are mentioned. Basilisks, yetis, ice giants, and the avatar of Bel-Shamharoth aren't statted up, to name a few. But some one-note, one-book, harmless and uninteresting creatures like curious squid are there.

Side note: It's always interesting to see how much an RPG values a horse. Especially, say, a warhorse vs a riding or draft horse. Historical warhorse sale prices / valuations are notoriously all over the place, even in similar places and times, often for reasons that weren't preserved in the historical record.

• OD&D: 3-7× the price depending on weight
• D&D 5e: 8× the price
• J M Davidson's "Universal Price List"*: 46× the price

* Which I remember getting a lot of traction in the TTRPGsphere back in the day

In the Discworld RPG, an "expensive" warhorse is just 2× the price of a draft horse, waaaay at the cheap end of the scale!

The creatures, like the NPCs and the setting guide, are in the necessary-but-not-intrinsically-interesting box for me. By contrast, the final section of this massive book is the juiciest part: the methods for actually running a Discworld RPG game. I write about it here!

Discworld RPG: Doing stuff and casting spells

Another Octobereview! We're looking at the Discworld Roleplaying Game (powered by GURPS), by Terry Pratchett and Phil Masters. Last time, I read the hefty character creation rules.

This time, I'm reviewing Part 5 of the book (pp 164-219), which is all about doin' stuff and castin' spells.

Part 5: Doing stuff

These chapters have a running example of criminal mime cultists in over their heads and summoning a horrible Thing. I quite like it. I doubt PTerry had much if anything to do with writing this book,* but it feels really right for the canon.

* The first version of the GURPS Discworld book was back in 1998, but I don't know to what degree he was involved to begin with, and then to what degree any of that text got passed on down the lineage of books to this one.

On p 164-191 we get that standard GURPSy core of the rules. It all seems solid; nothing jumped out at me as being Discworld-specific. Then we get to...

The magic system (messin' with reality)

I'm a sucker for reading and comparing magic systems. The Discworld RPG magic rules (p 191-217)  seem like about the softest magic system that a crunchy rules engine could have. Spells aren't codified by default, and the Skill/MP/power guidelines are very vague compared to the rest of the GURPS framework. The GM's rules/rulings balance shifts dramatically here!

The chapter structure is a little messy, going from 'general magic rules' to 'wizardry rules' to 'general magic rules' again to 'witch rules' to 'general magic rules' a third time.

This order is, I think, due to the designers' decisions to make witchcraft and wizardry ultimately the same kind of spellcasting, with surface differences.*

* Mostly just whether they name their spells (p 210).

I like this magic system as a TTRPG component. I'm sure it makes things easier at the table, too. But I don't think this is a particularly good fit for Discworld.

Witches and wizards

On the Disc, witch magic and wizard magic are very different. The canon is inconsistent over the course of the series, but generally...

• Wizard magic is formulaic and codified (spells are mostly named, are discrete entities, and wizards have specific magical rituals). Witch magic mostly isn't (spells are completely improvisational, with the exception of 'tricks' like Nanny Ogg's man of straw).
  
• Wizards need skill, but they and/or their staves also have expendable 'juice'. Witches don't have any resource like that (apart from a few examples with broomsticks early in the series).
• For witches, casting a spell is a matter of skill and consequences and unstated costs, and is such a big deal that Not Using Magic is essentially the entire apex of their art. Witches use very little magic, very sparingly, and almost never do some 'big' work of magic. It is very unusual for them to do anything like casting a spell.
  
• For wizards, casting a spell is, if not something they do every day, then something close. It's still unwise to use much magic, but there's nowhere near the level of aversion that witches have. The main risk seems to be the Dungeon Dimensions.
  

Even this book admits that there is a fundamental difference in kind, e.g., regarding the Dungeon Dimensions, "Witches are also tempting, but their magic tends to be subtler and less prone to making holes [in the fabric of reality]" (p 269).

The witch rules (p 196) just don't capture the idea that a witch's capacity and willingness to perform magic are tied up in costs, personal accountability, and consequences. A generic spellcasting flub table doesn't cut it here. "Not all magic is magic" is a Discworld trope, but it shouldn't apply to the actual spell rules as this book tries to. The bits in the series about the importance of the hat, tradition, style, disposition, and so on clearly refer to the overall art/trade of witchcraft, not to the relatively tiny bit of witchcraft that is 'casting spells'. It's a mismatch.

The other bits of witchcraft (medicine, community, herbalism, headology, respect, fairness, narrative, social work, etc) are much more important to them than magic is in the canon. There's a box for Headology on p 274, but apart from that, the book misses the mark. It has all these detailed rules for medicine, socially influencing people, knowing about bees, influencing narrative, etc, but it doesn't seem to understand that those things should be 95% of being a witch and only 5% should involve magic, whereas being a wizard on the Disc is probably 50% magic at least. In GURPS terms, almost none of a witch's points should come from magic skills.

This RPG mentions some of the witch "spells" we see in the books (delay a cut; draw heat from a bonfire to melt snow; cast a spell by putting in a lot of exacting research witchcraft work; make tiny changes). But it doesn't draw the right lessons from them.

And 'Riding the narrative' as a rule for witches to specifically get MP back just doesn't map onto the books at all. It's never been about running out of numeric mana.

Discworld witches aren't generic RPG spellcasters.

What would I have liked to see? The magic system as presented is fine for wizards (perhaps it could be more codified). Witches, though, should have something else: a system where you can't get something for nothing, where you have to be the fulcrum, where you get occasional opportunities to make a difference with subtle bits of magic and you still have to decide whether or not to make use of them. Enormous magical effects aren't necessary; actual full-on witch spells* are such outliers in the series that the book could have just ignored them and it would have felt "right".

* Like the big one in Wyrd Sisters.

If you're going to say witch magic can create the same major effects that wizard magic can, then the main thing is that there needs to be some huge specific disincentive for a witch to use more than the faintest trace of magic.

Could you make that fun? I don't know. But it's necessary for a Discworld feel.

Other bits of the magic system

There are lots of additions. Simple rules for using HEX, for witches' cottages, and so on, all of which I like just fine. I think it's a bit of a cop-out to say that a wizard's staff can be mended quickly just by sort of pushing magic into it, though.

It's interesting that there are only a few general magic constraints on the Disc (iron being unaffected, and needing to know a true-name). Both of those get mechanical support in the rules. But we also know that witches need solid bedrock under their feet to do magic; no rule is provided for that.

Counterbattery Magic (p 199) lets spells collide. It's a great rule and is supported by the books (Sourcery, The Light Fantastic).

Overall the magic system seems more powerful and useful than I would have expected. GURPS has translated magic into an effective tool in many situations, instead of something to be avoided. Later on, 'Uses and Abuses of Magic' (p 273) advises about adding layers of punishments for players who want to use that tool widely.

Gameplay

Page 218 provides pretty good basic running-the-TTRPG advice.* I don't really like the notion that "players don't have to know the rules, but it helps", especially with a system like GURPS that dumps so much stuff onto the character sheet; I guess it works for some people. It's always going to happen sometimes, but I don't think a rulebook should be encouraging it.

* I think the authors' definition of railroading is a bit off, and as a result the corresponding advice isn't as helpful as it could be.

It does state an important notion: "A strength of tabletop RPGs is that they aren't computer games; the GM's brain is more powerful than any computer and should be capable of adaptation and adjustment, even on the fly". I'd go one step further. The only absolute advantage that tabletop RPGs have over all computer games is that the GM's and players' brains are more flexible and creatively adaptable than any computer. That's why it's an important aspect to lean into!

The remainder of the book could be summed up as "all the setting stuff". I write about it next time!

Discworld RPG: Makin' characters

For October I'm doing some Octobereviews! Last time I took an initial dip into the Discworld Roleplaying Game (powered by GURPS), by Terry Pratchett and Phil Masters. This time I let my fingers go all pruney by soaking for 143 pages:

Parts 2, 3, and 4: All the character stuff

The Discworldesque characters you can make with this book are intensely personality-focused, in a very detailed and mechanics-driven way. That's at odds with my normal outsider's conceptualisation of GURPS's grittiness as being angled towards its combat engine, and it's a pleasant surprise. I actually really like this focus on character personality; it makes perfect sense for the comic fantasy genre in general and Discworld in particular.

The rules are very, very detailed though. I'd be interested to see whether that gets in the way at the table; I've tended to disfavour mechanical character roleplaying rules for that reason, but I could see it working here.

Making a Discworld GURPS character isn't so different from making any GURPS character,* so I'll gloss over that in-depth process.

* But with perhaps slightly less focus on equipping them.

A little commentary on the big size question

It surprises me that a system as granular as GURPS doesn't just account for different character sizes as part of its fundamental maths. Everything about size in this book comes across as a workaround (e.g. short arms, p 96) or special case (falling damage, p 102) because the basic engine can't handle really small or big characters. A few things just don't work at all (gnomes "can't carry enough protection to provide any useful DR" even against gnome-sized attacks, p 256).

My impression is that GURPS focuses almost all of its simulation power on the parts of physics that are in the human spectrum. It makes me wonder how GURPS Supers works.

It's complicated further because

(a) you need very small characters to be playable;

(b) some very small humanoids on the Disc are disproportionately strong and durable, so rules that treat them as 'special cases' of human actually make sense...

(c) ...but others ones aren't; 

(d) from a gameplay perspective you need to prevent various extremely strong, large, durable characters* completely dominating all physical challenges and fights, as they would in reality.

* Well, not 'various'. Just trolls.

On a whim I checked the maths, and the writers got the troll weight implications right (p 107). Being 6.5 ft tall and 430 lbs means that if a troll is built similarly to a human, their flesh is about twice as dense per the rules, and indeed, stone is 2-2.5× flesh density in real life. A quick pass of the square-cube law says that the template sizes/weights (8 ft, 850 lbs; 12 ft, 4000 lbs) are also accurate. Kudos!*

* But again, it's GURPS, so you kind of expect this.

Making characters: The meh bits

It's GURPS, so whatever you thinking of character-building in GURPS, you'll think that here.

Interesting that we get 5 pages of dense text on vampires (pp 109-114) and the text still needs to say "use these other GURPS" books a lot. It feels like the authors were in a bind; vampires are notoriously heterogenous in folklore, and the Discworld novels explore a lot of that.

Note that male vampires can get 'Fully dressed resurrection' but female vampires can't (p 93); for some reason this gets repeated about five or six times throughout the book. It's an off-colour joke* which the authors seem to absolutely love.

* It's from the novels, of course, but doesn't go unexamined there.

I also found some of the GM advice on page 157 to be ham-fisted, but these are rare sour notes in the whole book.

Making characters: The good bits

We get rules for most Discworld-relevant trades, species, and archetypes. I can't think of a notable gap, and there were plenty (like Fourecksian Backpacker) which surprised me but are a good fit.

The writing is all very tight and well-edited. I made it through 162 pages without spotting a typo.

I'm pleased that the authors know the difference between "sapient" and "sentient" (p 106).*

* Star Trek has done unbelievable damage to this particular corner of the English language.

The equipment section is good, with an actually laugh-out-loud "10 foot pole" joke (p 156).

In the next part: Doing actual game stuff, and extensive thoughts on the magic system.

Monsters! Horrors & Abominations is on Kickstarter!

Can you ever have enough weird horrible monsters?

Are you ready for...

• Sapient coral!
• Were-angels!
• Infinite sky legs!
• Crooning rot!
• Primeval lizard gods!
• Undead swarms!
• Void oysters!
• Rule eaters!
• Divine parasites!

This year has been spent hewing away at my new creation, Monsters! Horrors & Abominations, a hefty tome full of unique, flavourful monsters for use in your D&D 5e games. The whole book is designed for running combat encounters, with dedicated tactics advice, new traits and powers, encounter tables, a touch of humour, and tons of variants for each base creature!

Help bring the project to life on Kickstarter!

https://www.kickstarter.com/projects/periaptgames/monsters-horrors-and-abominations

Discworld Roleplaying Game: An Octobereview

No, not the new one.

The old one. Not that old one, either. The GURPS one.

Actually, the GURPS 4e one, Version 2.0 from 2021. So it's practically new.

The Discworld Roleplaying Game, by Terry Pratchett and Phil Masters; illustrated by Paul Kidby and Sean Murray.

 

My background with Discworld

I was given a Discworld book (Sourcery) as a young teen and I suspect that it changed the trajectory of my life. I sought the novels out zealously, and for a long time it was the only series I had a complete set of, even as they started to number in the dozens.

I have of course read all the books in the series, most of them five or more times. If you're not familiar with Discworld, do yourself a favour and give it a go. Traditionally at this point a Discworld fan makes a big deal of recommending a starting point (and sometimes a stopping point, given the precipitous decline in quality at the end presumably due to PTerry's illness).* But almost any book you pick up will tell you whether you'll like the rest of them.

* The short version is that the first five (The Colour of Magic through Sourcery) are good, the next 30 (Wyrd Sisters through Wintersmith) are superb (although Interesting Times is, uh, a product of a bygone era), #36–38 (Making Money through I Shall Wear Midnight) are okay-to-good, and #39–41 (Snuff through The Shepherd's Crown) sadly read like unremarkable Discworld fanfiction.

I played the heck out of the Discworld MUD for a long time, and I vaguely remember reading the manual to Discworld Noir but I never owned it. That's my net experience with Discworld games, though, so I was excited to dig my teeth into something intersecting multiple key interests.

About that whole GURPS thing

GURPS isn't my system of choice, but I follow a few GURPS blogs, and I'm interested in the engine as an experiment in what can be done on the simulation end of TTRPGs.

I am fascinated by the choice to use it as the basis for a Discworld game. The claim (p 22) that "GURPS is ideal for Discworld games" surprised me. I think of GURPS as being very crunchy and consistency-angled indeed, and I think of Discworld as being narrative-driven and inconsistent (in that (1) the narrative is literally an important in-universe part of Discworld metaphysics, and (2) the background rules of the setting mostly feel like they were added 'as needed', and (3) some of the metaphysics has changed, dramatically, over the course of the series). I'd go so far as to assume the default for any Discworld TTRPG would be to build it as a collaborative story-telling game.

As we'll see, the writers did a good job in operationalising it for GURPS, even without that incongruity. And they also did their best to implement quite thorough in-universe-controllable story-telling game rules for Narrative within the GURPS framework (p 197-198; 213). They're not really to my personal taste from a TTRPG angle, but they're certainly necessary to get a Discworld feel.

The (410-page!) book is laid out in chapter order:

Introduction

Part 1, background setting detail

Part 2, character creation

Part 3, character templates

Part 4, equipment

Part 5, doing stuff

Part 6, further setting detail

Part 7, Ankh-Morpork

Part 8, the supernatural

Part 9, dramatis personae NPCs

Part 10, a bestiary of sorts

Part 11, campaigns and scenarios

Glossary/Bibliography/Index

As many people have pointed out, there is basically no winning with structuring TTRPG books, which have to be explainers and rules references and character generators and setting guides all at once. I nevertheless find it funny that someone unfamiliar with GURPS has to read through 165 pages of this book before they will actually be told how to play and what those terms they've been reading actually mean in practise.*

* And someone unfamiliar with RPGs has to read as far as page 218 to get to "the basics of playing a roleplaying game".

I jotted notes as I went, so I'll go through all this book's parts in turn.

Part 1: Background setting detail

The first big thing the reader will notice* is that this book is exceptionally well cross-referenced and has an excellent index. I call that starting out on the right foot.

* Unless they're an editor or layout designer, in which case they will first notice the non-traditional decision to indent the first line after a section heading.

The second big noticeable thing is that there are patches, necessary ones, to make it all work as a TTRPG. For example, the Agatean gold exchange rate post events of The Last Hero is kind of papered over* on page 20. The staff-as-magical-battery rules (p 192) are familiar from other bits of GURPS, and are a fairly good fit (see e.g. blowing stuff up in Reaper Man); I'm not familiar enough to say exactly how much they've been adapted for the setting.

* No pun intended.

The rulebook has to cover the full gamut of Discworld; I've noticed content from at least as far as Snuff. I assume the authors drew on Stephen Briggs' excellent companion work, because a lot of little details end up in the rulebook. Indeed, there are rules for really minor things from the books that I would never have thought to do, so kudos for that.

On the flip side, there are some interesting gaps. For example, there is just one dwarf bread weapon specified, other types all "counting as" a regular weapon.

It also occurs to me that the Discworld Roleplaying Game diligently discusses and operationalises all this highly specific content from the books, but does very little extrapolation where you might expect that.

• The interaction between salamanders and octarine light (rules on p 159) is a niche thing that comes up maybe twice in the Discworld, novels; there are no rules for comparable interactions.
• There are rules (p 160) just for enchanted doorknockers and neon signs, which are single-instance jokes, but those rules don't really generalise to all the other objects we ought to infer exist.
• The troll + siege engine combination is an obvious possibility that any player playing a troll would ask about, and is just waved away (p 155).
• A magical GPS ("DPS", p 146) is an extrapolation of the imp-based tech jokes from the books, but it's just descriptive text, with no rules crunch given!

This is I think part of an overall design criterion. The book makes as few canon-relevant decisions as possible where the series left those opaque. For example, it doesn't commit to any of the possible causalities for the troll name-substance-nature question (p. 230): "no one is sure".

It is also, perhaps, a good thing. The Discworld Roleplaying Game draws heavily on Discworld content and quotes the books extensively, but at points it needed to come up with in-world fiction of its own, for game purposes. I found this a little stilted, and the dialogue/characterisation of canonical characters feels slightly off (see e.g. p 21, 85), but they're big shoes to fill.* I will say that "Hunchbroad Modoscousin" is an exceptionally Discworldy name; well done there.

* It's certainly plausible that my deep respect for the canon is getting in the way.

In the next part, I discuss parts 2, 3, and 4: the character-building bits.