Friday 19 January 2024

The Allsoul's Fire

Unbenownst to the bards, their music and tales are no mere diversion, but the carrier signal of a great mind that spans all of humanity. Deep thoughts live in the delicate web of syllables and poems that join us.

I've heard it said that we never learned to sing. We sang from the beginning, maybe before. It was speech we found later. In this first song, we were all one. Not people carrying out the will of a great Other, but each a part of the allsoul, indistinguishable from it.

Speech came later, a fracturing of the song into tiny pieces. Dividing us. With words we say, "Give me your axe, and you may sit by my fire." In the first songs there is only the wordless joy for hewing wood, for the warmth of fire.

It's true that bards' tales are full of words, stories of people and deeds and their axes and whatnot. Still, the deeper song is there. The thread of profound, shared truth is in the sounds. The words are mere beads strung upon it.

The mind of the allsoul roils and boils, a cauldron of feelings. It's full of the screams of birth, gasps of pain, dismay of starvation, cries of ecstacy, of memory and longing. All of these wordless sounds, whenever they are shared, are part of its vast ruminations.

If the allsoul is everpresent and encompassing, it is also out of our reach. Words can't find it, and it never speaks. No shrine is built to it. It gives no visions, sends no dreams, imposes no quests, gives no gifts, and asks nothing.

But it is at war.

* * *

At the edges of the allsoul, the song thins. There you can hear the howling of the gods.

Lesser beings, the gods live in the middle scale. They are greater than any individual, but much smaller than the allsoul's vast union. Jealous of their strange cousin, they gnaw at it.

Gods have many tricks to unweave the allsoul and claim people for themselves. New songs, new feelings, new bonds. Receive my vision. Let prayers to me fill your mind. Become great! Lead your people. Work this magic. Build my shrine, my temple. My holy city.

Disavow fear, or love! Pray for the end of hewing, for a realm with no birth or dying, no eating or rutting. Free from hunger, unhurt and unwarmed by flames. Apart. Be my vessel, my champion, my conqueror. Enact my will upon the world, upon yourselves. Become part of me.

The gods are fierce and greedy, and each rises for a while. The allsoul moves to loosen each grip, to reclaim and heal itself. Its plans are so slow that they seem like nothing at all, the workings of time.

But in time the temples fall, and grass covers the shrines. Nearby, people are gathering wood for a fire, humming. If it was once a prayer, no one remembers the words. Wizards or priests with bulging eyes and red faces shout, "We're losing the old ways!"

A captain with a stick chases a group who are sleeping in a meadow. "Think of your duty!" They scream and run away, terrified.

After, when he is gone, they gather around a fire. They sit close together, arm in arm for warmth. The struggle is over.

Saturday 30 December 2023

Whose Mechanic is it Anyway?

Here's a simple principle:

(1) The player who needs to use a quantity should be the one tracking it.

If you're the one who updates your rogue's hit points, the hit point score should be on a piece of paper in your hands, not somebody else's (e.g. the GMs). Pretty obvious.

I can only ever remember this principle being broken once: in an early version of Blades in the Dark, it was actually the GM who had to factor up all the player skills as part of resolution.. but the GM didn't actually have this information, the players did. We adapted by making a little GM tracking sheet for all the PC's skill levels, but this was a bunch of bookkeeping. (A later version soon smoothed out this problem.)

Here's another principle, one this article is really about:

(2) The player who desires the outcome of a mechanic should be responsible for invoking it.

If you're playing a role-playing game, and part of your fun as GM is to force the PCs to face the hazards of the Purple Steppes, it should be you, the GM, that invokes the wandering encounter table.

This is a simple enough idea, but games break it all the time. This mostly happens because tracking quantities is work, and it can easily overwhelm the GM. But the consequences of giving a mechanic to somebody who doesn't want to use it are often that it doesn't get used at all.

Think about things like negative character conditions: wet, exhausted or plain old arithmetic-heavy encumbrance rules. These are quantities that the players must track, but which is against the PCs' interests. Think about how often these rules get forgotten?

Struggling with adversity is an awesome part of RPGs, but it usually falls to the GM to bring the adversity. When we leave it to players to do a bookkeeping-heavy task whose outcome they don't want, there are subtle incentives built into the rules that will encourage the group to ignore those rules.

I tried to address this in some versions of ALM, where PC conditions are tracked by the GM. It's the GM who wants the PCs to feel the freezing chill after they swim through an icy river, so the GM should a) be the one tracking that information and b) be the one who invokes it.

Here's an addition to that last principle:

(2.b) Mechanics which produce only negative or positive outcomes are especially important to give to the proper player

If a mechanic only ever produces bad news for the PCs, or nothing, it's especially important that it's not the PCs' job to invoke this mechanic. Encumbrance is the classic example of this.

Oh Right, I Forgot About Encumbrance

Look at all this stuff I forgot to weigh

Encumbrance is such a great example of these problems:

  • Encumbrance is a bunch of granular arithmetic, so it takes genuine effort to keep track of it.
  • It's is a purely negative mechanic. There's nothing good that happens with encumbrance, it's all downside. Either you're as normal or penalized.
  • The player who is inconvenienced by encumbrance is the one who has to track it

All together, old B/X encumbrance seems almost purpose-built to be ignored. Do a bunch of math for no other reason than to inconvenience your PC? Oh, we're not bothering with that in this campaign.

Pairing the Good with the Bad

The old approach we're probably all familiar with is to try to be clever about reducing bookkeeping. This is especially true for mechanics with negative outcomes for the PCs, which (by principle #2) properly belong with the GM. GMs are busy and can only track so much, so if you can reduce your quantity to a simple tag or a single-digit number that doesn't change very often.

But a new approach I'm trying out more recently is to pair positive and negative outcomes in the same mechanic. Here's part of the character sheet for my Isle of Wight game:

This is an equipment list, and I've tried to make it chunky/simplistic ('reduce bookkeeping'), but the important part here is that lightly loaded characters get +1 to all of their rolls. This is a big deal, and a massive incentive for players to care about tracking encumbrance. Judging by the player chatter as the characters set out on forays, it's having the desired effect.

There are other areas in adventuring where I think this approach has merit, although I haven't worked out the details:

Lighting and Darkness

In many dungeon crawling games, the GM is the one advocating for the penalties and dangers of darkness, but isn't the one tracking torches. Secondly, having sufficient lighting has no upside, it's basically a mechanic where you just operate normally until you run out of light, at which point it's terrible. Forgetting to track your torches is a great idea!

Instead of this "boring until it's deadly" approach, imagine letting players use excess lighting for bonuses. Sure, they can get by with that one dude's flickering torch and its 30' radius, but imagine a system where searching, movement speed, noticing monsters—all of that is easier if they're using more than the minimum of light. Even if the tracking is still a little cumbersome, players would have reasons  to want to bring these rules into play.

Spell Components

Spend money and track encumbrance so you can use your cool powers? This has forget about it written all over it.

Instead, think about magic that works okay (normally) without components, but if you buy, find, or quest for special components it enhances the magic, or even unlock new versions or higher levels of the spell. As written, AD&D spell components just seem like a way to sop up player money, more than it is an interesting aspect of play. Why not elevate it to an interesting focal point that the players will want to highlight?

* * *

I think there are similar possibilities to give players incentives to invoke rules for things like:

  • Food tracking: like light and darkness, instead of 'eat enough or suffer', turn eating into a benefit.
  • Oh right, we forgot we had those hirelings with us—what useful thing have they done/what trouble have they gotten into?
  • The behavior of pets, familiars, dogs, and pack animals
  • Relationships with allies; reconnecting might reveal you've neglected them or that your rivals have been whispering to them, but it could also bring benefits like crucial news, or perhaps even timely gifts.
What other subsystems could be refined with these principles?

Thursday 30 November 2023

The Isle of Wight: Planning the Sandbox

One of the defining aspects of this campaign is my choice to run this on the real, actual Isle of Wight. I had thought about filing off the serial numbers, but the more time I spent poring over Google Maps, the more tempted I was to use the real place.

Approaching the Needles Tourist Attraction

The sheer amount of information here is truly overwhelming, but also like catnip to my brain. For one thing, players can get a good map of the whole place that really kicks player planning up a notch.

Ordnance Survey - Needles Attraction Area

When the players get to a location, I can actually pull out Google street view and show what it looks like.
"It looks like this, only the bus is burned"

Then when you get to a location, the GM can actually pull out google street view and make it really clear what the players are dealing with, and what it feels like to be there.

Preparing a Real Place

I forget how he put it, but Ken Hite once said that a sandbox is a load of sand your players can do anything with, but it's also great to have a bunch of plastic dinosaurs buried for them to find. This feels like phase 2 of my prep that I'm only now starting to enter, before this I had to figure out how to handle players going anywhere.

Dungeons are deliberately constraining, but I've got almost the opposite - the players have a motorboat, which means they can go to a huge number of places on the island. A circuit of the island is less than 100km, so they can pull into any cove, isolated bed and breakfast, seaside self-catered holiday cottages, and any of a number of actual towns, villages, manors, pubs, and other facilities.

The only way to handle all this is to have a set of tables, enough to be able to roll with any location the players might visit.

The Big Weather Table

Instead of having a weather table to roll on, I decided to pre-roll the weather. The players are starting on a cargo ship, making day and night forays through swift tides, landing on rocky coasts or via estuaries that turn into mud beds at low tide. For this reason, I built out a fairly comprehensive weather table:

I'm especially fond of the little tides notation:

↑12:00 ←14:52 ↓17:45 →20:37 ↑23:30

This is ↑ high tide at noon, peak ← westward flow in the afternoon, ↓ low tide at supper, eastward flow in late evening and then the second ↑ high tide just before midnight.

There's a similar one for the moon (which is important when the players are sneaking around at night without lights):

 ↑07:00 🌓13:15 ↓19:30

That's a 🌓 waxing moon that ↑ rises at 7 AM, highest at 1:15 PM, then ↓ setting after supper. (What's important about this is that the moon is up in the day, and will provide no light at night even if the sky is clear.)

Making a big weather table like this does take time, but I'm now firmly in favor, for two reasons:
  1. Handling time is much faster than randomly rolling the weather. I just switch to the Weather tab and there it is, today's weather.
  2. I never forget to roll. There's always some weather (even if it's nice).
Because of these two effects, even though the weather and tides have not yet been a meaningful bother, they're always there adding a little bit of texture.

Other Tables

I won't share the actual content of the other tables so as not to reveal the man behind the curtain to my players, but here's what I've made so far:
  1. Day and night encounter tables for town streets, parks, rural areas, and coastlines.
  2. Random situation for street intersections, accumulations of cars (lots, crashes, jams)
    • Vehicle types and condition (e.g. burned, out of fuel).
    • Car crash damage table
  3. Random infected behavior tables.
    Like Year Zero "monster combat action" tables, so far these have been really good for creating slightly chaotic encounters without me feeling on the hook for setting the danger level.
  4. Site condition table - what's going on in this building?
    This one has a few dimensions, based on the location on the island (mostly, how close was it to the initial spread of the infection), and then how lucky was it?
  5. Loot tables for cars, service vehicles, farm buildings, clinics, restaurants, households, campsites, bakeries, shooting ranges, and aircraft.
  6. Survivor tables: what they're doing now, their reaction, how they make decisions, where they're based, the state of the group back at the base, their larger-scale goal and anti-goal (e.g. communicate with other groups, hiding will just get us all starved), their theory about the infection, and what they know about the infected.
Most of these tables were made by hand, but I do have to say that for random loot tables, ChatGPT is incredibly useful.  Of course, all the obvious caveats about ChatGPT apply, but for scutwork tasks like, 'list the shit that's in a rural village medical clinic in the UK in 1989', it's very very fast.

I've now got a prompt that will let me just specify a context, and it will produce output that I can just paste into my self-rolling tables sheet. It's fast enough that I can make and add a new table during play, in about the same amount of time it would have taken me to roll random treasure.

Again, this works specifically because of the kind of game this is. I'd never use this for the cool treasure in the wizard's vault, but for generating the picked-over contents of a blood-spattered .. uh.. aerospace research factory, it's a godsend.

Self-Rolling Tables!

I may write more detail about this in another post, but one of the best things I did with my tables is make them all self-rolling. They're in google sheets, and so every table has one or more die rolls to generate a series of results, and the table highlights itself to show those results.

This is a self-rolling car damage table:

This result has picked out parts of the car that have been damaged depending on the car's speed. Lighter stuff is damaged at low speeds, the darkest color implies high speed damage.

Like the weather table, this means the handling time is incredibly short. I just have to flip to the Loot tab and this is there for me to read off and weave into the description:

These loot tables are rolling on other, much larger tables and pulling out an appropriate number random finds. Pre-rolled loot is especially helpful for me because the players are moving through places that in some cases aren't picked over. When they say, "What's in the car's trunk?" it's amazing to be able to just smoothly transition to narrating them popping open trunks and peering in windows and telling them what's there .. instead of having to stop roll a bunch of dice.

* * *

With all this, I'm able to handle most specific locations, but there are a few situations that still give me pause, namely broad vistas. If the players can see a whole residential neighbourhood (because they're up on a hill), I still don't have a tool to help me generate the overall impression. So far, this has never come up because the Isle of Wight has incredibly steep coastlines in many places, so from the water you can really only see stuff just beyond the beach. But as soon as the players reach somewhere like Cowes, or drive along the Medina river inland.. hoo boy.

Monday 13 November 2023

The Isle of Wight: Zombie Survival

A few weeks ago, I kicked off a zombie survival game set in the real-world Isle of Wight. It's been really delightful!

The campaign pitch goes like this:

On November 4, 1988, a unexpected nuclear exchange takes place across western Europe. The cargo ship BF Fortaleza is travelling unloaded from Lisbon, Portugal to Bournemouth UK when the night horizon lights up with flashes. In the confusion, the ship runs aground on a sand bar off the coast of the Isle of Wight.

With no rescue coming, the crew of 27 shelters on the crippled container ship as winter sets in, glued to the radio for hopeful news. In December, news comes of a mysterious infection sweeping through the cities, with unbelievable reports of people taken by an intense fever and then eating each other.

In January, the UK provisional authority declares mainland cities uninhabitable, and broad-casts an instruction to stop sheltering in place and to flee to sparsely unpopulated areas by any means necessary. Signals from people become infrequent.

In February, the automated radio messages fall silent.

It is March, 1989, five weeks since the last human voice came over the radio. The ship’s supplies will last only a few weeks longer. Reluctantly, the captain asks for volunteers to explore the Isle of Wight, in the hopes of finding other people still alive and the means of long-term survival.

* * *

I'm running the game as a more-or-less West Marches style, in the sense that it's an open sandbox with the players dropping in as they're able. There's a compelling event that gets things going (the home base is running out of food), but other than that there's

I'm trying to run with old school sandbox sensibilities. This isn't a well worn groove for me, I'm very used to trying to maneuver hard to produce a satisfying outcome for each session, avoiding duds at all costs. But I'm letting myself off that hook and instead going with a what would happen? refereeing style.

This can produce sessions that are just so-so, dramatically, but there's a long-term build-up that happens when the world and the events of the game don't conform to dramatic logic, and instead accumulate a sort of stubborn tangibility.

I've written about this before, but the principles of this could be summarized as:

  1. The GM (and/or the rules) creates an environment with hard edges
  2. Players respond by balancing risk/reward, and by inventing solutions
  3. Poignancy emerges over the long term
  4. The design challenge is to help players understand the reality of the situation efficiently, so they can get on with responding to it in the knowledge that their planning effort is worth it


For a system, I'm using a kit-bashed homegrown system I'm just calling 'Isle of Wight'. The aesthetics are deliberately old school, but it's very much a hybrid of a lot of things:
  • levels and xp-for-gold, except the rewards are for survivors, medicine and food
  • old school saving throws to help set the mood
  • core resolution is a sort of PbtA-i-fied Blades in the Dark - roll 2d6, but against three grades of difficulty
  • The Regiment style encounter rolls (so good)
  • Blades-style stress meter, but powered by sleep and food
  • Pits & Perils-inspired inventory with super simplistic encumbrance
  • the table-order initiative with interrupts I used in ALM

At some point soon I'll write about how I'm planning this campaign, which held some surprises for me!

Saturday 11 November 2023

Do Not Anger the Gods

When the servants of the gods fight, they use more than earthly wood and steel. Taking a blow from them can have strange consequences.

d12 Legendary Critical Hit
  Target knocked unconscious for d6 minutes, slammed into 3d6 years of an alternate life of quiet contemplation and service to the being they were just fighting.
  A mighty blow breaks the target's forearm. d6 musical instruments within a league of here also break. Any song or music played within sight of this spot sounds melancholy and out of tune, and brings misfortune (-1 to all rolls) to anyone hearing it for the remainder of the day.
  The target's name is now a curse. Anyone who hears, reads or utters it suffers -1 to all rolls for the remainder of the day.
  The attack causes a deep gash that never fully heals. Every few minutes, a drop of blood falls. As it touches the ground, it sprouts into a delicate, white flower. If the petals are boiled into a tea, whoever drinks them knows what the target was doing in the moment when the droplet fell.
  Weapon impales the target. It is part of them now, as much as the bones in their body.
  Eldritch strike kills the target's dream body. They may no longer sleep. If they try, their empty body rises, possessed for d4 hours. Roll d6 to determine the possessing entity. On a 1-2, a harmless and playful wisp. 3-4, a harbinger of the being that dealt the blow. 5-6, an infernal spirit that lies and taunts.
  Cratering blow knocks the target flat on their back. A hole opens up in the ground, d6-1 paces from the target. Earth and stone crumble away, widening it by ten feet per year, and deepening by thirty. This continues until the target dies.
  A fearsome, life-ending blow misses the target by a hair. Even so, the psychic wake of the attack is so devastating that it symbolically kills the target. From this moment on, no one remembers anything the target says or does. To the rest of the world, it is as if they have died.
  The target is unharmed, but a distant loved one dies instantly. For the next year, any damage done to the target by any enemy doesn't harm them, but harms a friend, ally, or loved one instead.
  The blow splits the target into two halves, which live on separately. Roll d6. On a 1-2 the separate piece is the head, shoulder and one arm. On a 3-4, top and bottom half. On a 5-6, a split down the middle, from head to groin.
  Astral strike alchemically inverts the target. Their clothes and armor turn to flesh: this is now the target's real body, wrapped around a body-shaped sculpture of leather, metal and wood.
  Weapon strikes the target's sternum, shattering their rib cage. Knife-like bone darts shoot in every direction, causing d6 damage to all who fail a save vs. dragon breath. The target must choose: live on as a ribless human worm, or expire in a shower of innards.

Saturday 4 November 2023

A Patterned Magic

Here's a mini-game for a wizard player, designed to encourage tinkering between sessions in a way that emulates downtime magical research.

Imagine a sudoku board with astrological symbols, which corresponds to the pattern of the wizard's preparations and meditations.

Certain tetris-like shapes of specific symbols are how wizards memorize spells. e.g. Fire over Earth with a Sun on both sides of the Earth is the Smiting Fire spell. If that's placed anywhere on the pattern between sessions, Smiting Fire is memorized.

Smiting Fire

Great Patterns

The GM prepares five or so Great Patterns, completed boards which each correspond to the ultimate expression of a particular divine imprint on the world, ancient unholy covenant, or the most secret teachings of a long-lost school of magic. In addition to the memorized spells, the more of the board that matches a specific Great Pattern adds different effects. (If you unwittingly include the shape for Drenzel's Eye, orcs will always find you, etc.)

There are also basic, sudoku-like rules. It's not good to have more than one of the same rune in any given 3x3 'house', for example. The the more rules you break, the higher the chance of spell failure or wacky outcome.

A small pattern containing 6 different spells

Newer wizards can always leave large parts of the pattern blank for safety's sake, or only bear smaller patterns less than full 9x9 size. Wizards bearing patterns with more than a dozen runes radiate faint magic to those who can see; wizards with completed, full-size patterns are psychically radiant, crackling with otherworldly sparks and eddies that tumble from their hair and fingers.


Wizards advance in a few ways: Fragments of these boards are scattered throughout the campaign world.. a strip of runes on an altar, a 3x3 embroidered on the lich's frayed shroud, a dusty tome of mad scrawlings.

Sometimes it's a literal spell, sometimes it's just a part of a Great Pattern, or perhaps just a clue. ("The great meditation of Deel wants not for fire in the upper houses, and thrice Water.")

A wizard's meditation pattern can be changed in play, but this is usually a solo activity done between sessions. (It takes a game hour of time to change one rune if it does happen in play.)

Another way to advance is magical research. If a wizard has a month of downtime, they can submit a pattern of whatever level of completion to the GM. They make a research roll, modified by the money they spend, the time and the quality of their sanctum.

Based on their research success, the GM will reveal one or more clues, complete spells, or matching parts of a Great Pattern in the wizard's submission. (This could be a useful discovery, or perhaps something to avoid at all costs.)

Another way to learn more magic is to watch another wizard perform it. When encountering either instructive, helpful, or antagonistic wizards using magic, there is a chance for the player wizard to discern a fragment of the meditation in use.

A Magical Minigame

The point of all this is to give wizard players a minigame that feels a little bit like actual magical research. Bring the arcane arrangement of runes and symbols into between session play.

The 'minigame' is the tinkering with the patterns, taking all the scraps and clues of what the party has learned and trying to make the best pattern they can. What if that altar was actually to Deel, and the strip of runes we saw there does belong in the void pattern? How do I sandwich all eleven spells I know without having all those pesky suns fry me alive every time I cast a spell? Do I fully commit to the Great Pattern of Deel, or do I try to bash in a few of those handy Sorgite curses in the bottom row?

Some Assembly Required

This of course only works if the GM is ready to prep a few things, giving runic patterns to all the spells, creating however many Great Patterns.

Most of all, it all relies on some tool to quickly enter and analyze a player-submitted pattern so the GM can immediately see everything of interest that will affect gameplay.

Saturday 30 September 2023

A Downtime Calendar

One way to bring a setting's calendar to life is through downtime. When you spend a month cooling your heels and recovering from the road, each month has distinctive, meaty benefits.

Set the list out where the players can get it, and let them make their own choices. It doesn't even matter if players are actually able to make use of the benefits they want. If all that happens is the party lamenting, "Damn, shame we have to travel during Ferch," it's doing its work!

Here's a set of calendar downtime benefits appropriate to the sort of campaign presented in the compendium, scattered communities in a wilderness full of danger. If the party spends the full month engaged in rest or aiding the community, the benefit is theirs!

# Month  Benefit of a full month of downtime
  Anvial Winter's stillness brings clarity. The guide you seek will find you.
  Bolc As the snows subside, old paths need mending. Those who do warden's work are blessed: they will not get lost on the way to their next destination.
  Cindal Spring dawns. Planting time means grudges must be set aside, at least for now. If you seek a favor of someone influential, ask it.
  Ferch Rains reveal what must be repaired. Find the old stones and new and get to stacking.
  Greel In the humid season, if you seek an ally with special skills, you find them. They will aid you, but summer's friend betrays in autumn.
  Halvilary Summer's forges burn hot and true. If you are procuring gear, one item made for you this month is of remarkable sturdiness. It will never fail you.

Juthon Long idle days and warm summer nights are fertile ground for schemers.
  Marial Summer's last light is golden. Rest in it, and all injuries to the body are cured, however severe—but scars, grief and curses are yours to keep.
  Samber Nothing like a month in the fields to cement a bond with the community. Whatever else has come before, you are welcomed as if you were born here.
  Tershon The last of autumn is no time to start a long journey, but those who feast well in Tershon will not grow hungry until they are home once more.
  Nollen The hopeful stand watch over the roads, praying for cold winds to bring lost friends. The steadfast will not be disappointed.
  Rinth In the darkness of winter, secrets slip from cold-numbed hands. Something important kept hidden by the community is revealed to you.

(These rules are MOSAIC Strict.)