In recent games I've been trying to run things a little more sandbox-style, going off-the cuff moreso than relying on pre-planned adventures. It's resulted in some more dynamic and surprising games, and also in some that have kind of petered out without much of a sense of a climax, but I'm liking the results so far. Events in the game are flowing more organically and naturally, based much more on what the PCs want and how the various NPCs are reacting to their actions.
That said, I am a planner by nature (not so much in real life, but definitely where D&D is concerned). I like to plan ahead, especially if I know where the game is likely to go in the next session. One of my recent games involved a week-long wilderness journey where the PCs had to take the inert body of my setting's god of light to a rendezvous point, and hand it over for safekeeping. They had members of the local resistance movement with them to act as guides, so I was about as certain as a DM can ever be about where the game was going.
With that knowledge, I set about figuring out what would happen along the journey. Normally I'd have placed set encounters that fit the adventure and tried to lead it along a certain plot path, but right now I'm trying to take the "plot" out of D&D as much as I can while still planning ahead. So rather than pick the encounters myself, I decided to do the whole thing using random charts. Below I'll detail how I put the adventure together, and how I also drew quite a bit of setting inspiration from the results I rolled up randomly.
The first step was to work out how long the journey would take at the party's optimal speed. They were travelling light (aside from the big old crystalline god torso they're lugging about), and the journey to the rendezvous point and back to the city of Port Bracken came to about five days.
Next, I started rolling for random encounters using the tables I'd made when I drafted up my maps. (I really should put up an image of the wilderness region, but I only have it as a hand-drawn map. I need to scan it at some point.) The 3rd edition rules call for a random encounter check for every hour of travel, but that's way too often. I can't be rolling twenty-four dice per game day, especially on the fly. Instead, I've split the day into four time periods: morning (6am to 12pm), afternoon (12pm to 6pm), early night (6pm to 12am) and late night (12am to 6am). I make one check for each of those periods, then roll a d6 to determine the hour in which the encounter happens.
Another wrinkle I've added to random encounters is the idea that sometimes you'll see signs of a creature rather than the creature itself (the howling of wolves, an old campsite, an animal that's been killed by the creature, etc.). Whenever an encounter is indicated, I give it a 1-in-4 chance that the encounter will be signs of a creature. The next time an encounter comes up, there's a 3-in-4 chance that the encounter will be with the creature indicated. This allows a little more foreshadowing to be added to random encounters, and gives the PCs more of a chance to plan ahead.
For the journey I rolled the following:
- Seven dwarves around midday on the first day
- Signs of wights at the end of the second day
- A wight encounter on the morning of the fourth day
- An encounter with bombardier beetles around midnight of the fourth day
- An encounter with an escaped refugee on the final day
- A mixed encounter a few hours later, with Priests of Malak (the god of darkness) and hippogriffs
The dwarf encounter was easy to figure out (although I had to resist the urge to do a Snow White riff). The timing had it happening at a bridge, so I set them up as cutthroat bandits making travellers pay them to use the crossing. I threw in a little bit of background about them being a troupe of jesters who've had trouble finding work, and also made a note that they'd be extra-curious about the body of the light god if they caught a glimpse of it.
For the wights, I figured a destroyed camp would be the best way to foreshadow them; I didn't want anything too immediate, because there was going to be a pretty big gap between the sign and the encounter. So I placed a camp with some abandoned tents and bedrolls, along with the corpses of some dogs that had suffered an energy draining.
The wight encounter I just placed as a simple ambush/attack, noting that the head wight was being served by lesser wights who were the former inhabitants of the ruined camp.
The encounter with the beetles was a trickier one, as I was struggling with ways to make it interesting. It was set to happen around midnight, and I find encounters can be a little trickier to realistically set up when the PCs are camped, especially when the monsters aren't all that intelligent or mobile. I resigned myself to making it a straight-up predatory ambush, but I was saved when I got around to rolling for random weather. A thunderstorm came up at pretty much the exact time the PCs were set to encounter the beetles, so what was going to be a boring slugfest became much more potentially interesting, as the beetles would be stirred out of their nest by the lightning and thunder and stampede into the PC camp. (Well, I thought it was going to be awesome, but the PCs ran away from the wights and turned that encounter into an overland chase. They ended up a few miles away from where the beetle encounter was set to happen, and I didn't want to railroad them back into it, so I shrugged my shoulders and let it go. I still think it would have ruled, though.)
The refugee encounter and the one with the priests of Malak and the hippogriffs were set to happen within an hour of each other, so it made sense to connect them. After all, the priests are pretty much in charge of Port Bracken, and they're definitely the sort of folks that someone would be trying to escape from. So I made this refugee a member of the Resistance, and gave him a minor connection to one of the NPCs the party was travelling with. (As an added call-back, I made him a member of the Hucrele family from The Sunless Citadel, which I'd run very early on in this campaign.) The priests of Malak would be in pursuit, and would no doubt stop to question the PCs, who would have to decide whether to risk their necks for someone they hardly knew.
That just left the question of the hippogriffs. One thing I've done to spice up my random encounter tables is include a result that calls for rolling on the table twice, with both groups being encountered simultaneously. The idea was that it would be up to me to make sense of the combination, and that the results would make for some more dynamic encounters. The evil priests of Malak being combined with generally good or neutral hippogriffs seemed on the face of it like the PCs should stumble into a fight between the two groups, but with this encounter being so close to Port Bracken it didn't feel quite right. Hippogriffs are often used as mounts, and with the priests being a hunting party it made sense to go that way. I tweaked it a little by making the hippogriffs into zombies, as use of undead slaves is a big part of how the priests of Malak operate. Yeah, I'm not sure zombie hippogriffs would be able to fly either, but the 3rd edition rules say they can, so I went with it.
That final encounter added a lot of detail to my setting: a new NPC, more information about the Resistance and the NPCs travelling with the party, a mention of the "labyrinth cells" below the Temple of Malak, and the idea that the temple's hunting parties use zombie hippogriffs as steeds. None of this existed before I rolled on the random tables.
Because I had some extra time to plan, I decided to roll up a different set of random encounters just in case the PCs happened to make the journey while slowed due to encumbrance. I don't remember the results as well, because they weren't used in the game, but what was effectively pointless busywork still gave me some setting details. After the thunderstorm (because I was still using the same weather results), I rolled for an encounter with giant centipedes. Then, I rolled for an encounter with dire wolves and giant centipedes together. Then, I rolled for an encounter with ogres and dire wolves together.
The giant centipedes coming out after the storm was a really nice bit of serendipity that mimics how certain creepy-crawlies pop out after the rain in the real world. The dire wolf/centipede combination was an odd one, but the subsequent ogres/dire wolves combo made sense of it all. Obviously, these ogres prize like to eat giant centipedes, and they're out hunting after the thunderstorm using their pet dire wolves to track them. This is the kind of thing I'd probably never come up with on my own, but came to me almost right away when I was forced to make sense of the whole thing.
So at the moment I'm enjoying this way of creating adventures, with my own design biases being guided by random tables moreso than by my own whims. It's forcing me to think outside of my usual box, and I'm liking the results. No doubt it will be harder to do effectively when I have to roll these things on the fly, but hell, everything in D&D is harder when you have to do it on the fly. Practice will hopefully make these things come more naturally.
No comments:
Post a Comment