[CONAN] Full-Time GM, Part-Time Prep

[Supplement Four]

I had nothing to do with what follows except to recognize it as an exceptional post that should be posted here for Conan GMs.

I've never taken someone's post from another forum and transplanted it before, but if anything deserves that effort, it's the work this guy put into this piece.

Happy reading.

S4


(The next dozen plus posts are the transplanted post and not my words.)

 

[Supplement Four]

Lesson 1: Be organized.

There are a few lessons that I consider fundamental to this style of DMing; without them, you will find yourself doing preparation that does not need to be done, or even redoing preparation that you have already done. In order to cut your prep, you need to streamline as much of your process as possible, and that starts with organization.

This may seem pretty obvious, but, if you intend to run a lengthy campaign, you should keep it all together, in one place. This is particularly important for the DM who has little prep-time, because such a DM is most likely to work on bits of the campaign in a piecemeal fashion, particularly if inspiration strikes unexpectedly. This is all well and good, but do yourself a huge favor and keep it all in one place! Commit to this before you even begin the campaign, and you will save yourself a lot of headache (and extra work) in the long run.

 

[Supplement Four]

Lesson 2: Know the rules.

Maybe your players all want to play a light-hearted game and specific knowledge of the intricacies of the rules-set is not that important, because it just won't come up. That's great. However, all it takes is one rules-savvy player and your lack of knowledge is exposed. Does it matter? That depends on the player. The player might act as a repository of said knowledge in the game; if this is so, take advantage of this resource!

If, on the other hand, the player is the type to look for any advantage he can get, your lack of knowledge has given him a pretty big one. In such a case, it is particularly important that you educate yourself.

But it's important anyway. Why? Because the better you understand the rules, the more consistent you will be as the game rolls along and, believe me, if you are trying to streamline, consistency is your friend.

If you don't like a rule, fine—don't use it. If you don't know every arcane minutia of the rules, that's okay, you can rule on the fly, and look something up later. But, the more solid your grasp on the basics (and the commonly used not-so-basics), the better equipped you will be to tinker with the rules, and to make consistent adjudications in play.

 

[Supplement Four]

Lesson 3: Reduce the bookkeeping.

The last lesson kind of leads into this one. Take a look at the rules. There are probably several things that jump out as tedious and time-consuming. Can you ditch them? Do they need to be replaced with something? How can you reduce the bookkeeping load both for you and your players?

Right off the bat, I'm going to throw a proposal out here. Ditch the Experience Point system. It is cumbersome and, frankly, encourages a style of play (that is, combat-driven) that will make your life more difficult.

Some DMs simply advance PCs whenever it feels appropriate. If you would prefer a little more structure, however, I recommend advancing the PCs in level as they accomplish quests (say, 2 major quests, with 3 minor quests counting as a major). There is some degree of tweaking that you can do here, as well. For instance, if you want earlier levels to come quicker than later levels, you could add 1 major quest to the total needed every time a level is achieved.

With this simple substitution, we eliminate the need to figure out how much XP a party earns, how to divvy it up, how many combats you need to plan for so the party can level, and how to advance the PCs if they take an approach that isn't combat. These things may not seem significant, but they add up, and they eat away your prep—and playing—time.

 

[Supplement Four]

Lesson 4: Get your players to do the work.

Now that you've got an idea what kind of mechanics you're going to support your campaign with, it is time to start in on the setting. And, you know what? Your players can—and should—help with that. What you need to do is provide incentive to do so.

This is how I do it: Whenever a player takes it upon himself to do something outside of the game that could potentially enrich the play experience (make a map, NPC, prop, or whatnot), I award a point that the player may use with any PC in any game I run to alter fate in some way--turn a hit into a miss or vice versa, turn a hit into a crit, throw in a plot-twist. This awards the players according to their initiative (as opposed to the PCs' initiative ) and has the added bonus of helping the entire party be more survivable (which, in turn, makes my job easier--it's like rewarding myself for getting them to do prep for me!).

It comes down to this: The more minds that are excited about the campaign setting and actively working to embellish it, the richer it will be—and the less work you have to do to get it there, the better off you will be.

 

[Supplement Four]

Lesson 5: Every element is an NPC.

Everything. That abandoned village the PCs just came across? NPC. The pile of loot they've been after? NPC. That forest fire bearing down on them? NPC.

What does all of this mean? It means that a little personality will go a long way. The better your players remember things, the more sparse your notes can be.

More importantly, if you are going to do as little preparation as possible, you will not have detailed notes on many of the elements in the game. Therefore, you need to make what notes you do have count. Think about these elements as characters and it will be much easier to bring them to life. As with any NPC, you should be thinking, “How will the PCs interaction with this character matter?” When you get down to it, that's all that ever matters.

 

[Supplement Four]

Lesson 6: Don't plot. Hook!

Seriously. The more detailed your plans, the more clever your schemes, the more dastardly your designs, the more time you have wasted! Your NPCs should most definitely have diverse motivations and (sometimes) complex objectives, but you, the DM, should not! The players will subvert, dash, and render obsolete any such attempts.

Instead, throw out lots and lots and lots of hooks. Write these hooks down (on separate index cards, for instance). Keep them all with your campaign stuff (a box is good). If the PCs don't bite on the hook, make a note on the card, stick it back in the box, and pull it out to complicate their lives later.

This is the core philosophy that drives this DMing style, so I will reiterate: Every hook that the PCs ignore is a potential complication down the road. Create plentiful hooks; they will not be wasted.

 

[Supplement Four]

Lesson 7: Never stat what you don't need.

But, how will you know what you need to stat? Chances are, you have a pretty good idea, already, but if you are in doubt, you do not need to stat it! Even when you do need to stat something, you only need to stat what you need! It sounds so intuitive, but, seriously, if you let yourself, you could easily sink more time into creating stat-blocks that will never get used than into any other aspect of campaign-prep.

But, what if you need combat stats for some NPC you didn't bother to stat out? Fake it. There are a few different ways to do this effectively. Two of them will be described in the next lesson, but there is one thing you can and should do before you ever begin playing.

Create or acquire some generic templates of creatures/NPCs that you can quickly adjust to fit your needs on the fly as the need arises in play. These should not be detailed; just enough to get by with.

This is a minimal amount of prep that you should do before you start the campaign and again when the PCs level. The small amount of prep can—and will—save the day at some point.

With this as a fallback, you should have no reservations about giving as few things as few stats as possible.

 

[Supplement Four]

Lesson 8: Re-fluff and recycle.

Two other things you can do to help you put together an unexpected combat are also useful tools all-around, so they get their own lesson. Take a monster out of the monster manual. Great. Now you have stats, but how does it fit in? You could just drop it in, but if you use it a lot, things could get old. But, re-fluff that monster over and over again, maybe make a minor mechanical adjustment, and you've got a different experience, every time.

What about that NPC that you actually did have to stat out. Now that he's dead, you're done with it, right? Not so! Keep those stats handy; they, too, can be re-fluffed.

The more time you save with these creative adjustments, the less time you waste reinventing the wheel.

 

[Supplement Four]

Lesson 9: Keep notes during play.

This is going to seem obvious, but it is really important for a consistent, long-running campaign—especially one light on preparation. When you make up something (like an NPC's name) or something happened that you need to remember, write it down! Don't write down everything—just the important things. Make sure you keep these notes organized with the rest of your campaign after the game is over.

The time you save not having to remember things could astound you.

 

[Supplement Four]

Lesson 10: Don't use weird names.

That last lesson leads into this one. Don't use weird names. Just, don't. Seriously, how are you going to remember Xian'thrak'halitosis when you need to without looking it up? That's just wasted time. Bob's no good either, because it tends to break player immersion, but at least you can remember it.

Try simpler (even, occasionally, real) names and, especially, titles. Not lame titles. Evocative ones. What's the difference? Well, that's just something you'll have to figure out for yourself.

 

[Supplement Four]

Lesson 11: Most battles should be skirmishes.

If your players want to grind out combat after combat, you should seriously consider letting one of them DM, or pick up a published adventure, because combat prep requires time and lots of combat prep requires lots of time.

Therefore, battles should fall into two categories: minor and significant. Minor battles should never be long, overly complex, or unavoidable. Use weak enemies, sparse (but interesting) terrain features, and multiple ways to succeed or to bypass the conflict.

Significant battles, on the other hand, should be significant. Use difficult enemies, complex terrain features, and awesome imagery. Give these combats the love they deserve; they should be the focal point of the session, after all.

The minor skirmishes leading up to such a battle should be easily forgettable, but should serve an important function—they highlight just how epic the major battle is and help it be all the more memorable.

 

[Supplement Four]

Lesson 12: Listen to the players.

I don't just mean listen when they're talking to you (although, obviously, you should). Listen when they're talking among themselves.

Listen to their conjecture. Incorporate it into the story (with some twists, of course). This will give the players a sense of satisfaction for being right, and gives you access to a valuable resource: other people's ideas.

Listen to their plans (when they discuss them openly). This will give you an idea what you need to prepare for in the near future. Don't use this information against them (much), or they'll just stop talking in front of you.

Listen to their conversations. This will give you a better understanding of what the PCs want out of the game, and what the players want. This, in turn, will help you focus on what preparation you ought to be doing and what isn't so important.

 

[Supplement Four]

Lesson 13: If the question is, “Can I do [something that's cool],” the answer is “Yes!”

Simple, right? But it is the most important lesson. You've got enough work to do, let the players bring the Cool. They'll be energized and excited about the game, and all you have to do is let it happen.

If it's cool, find a way to let it happen.

 

[Supplement Four]

End Quoting The Excellent Posts.