10 Favorite Nuggets From Monte Cook’s Your Best Game Ever

Roleplaying games have benefited from decades of advice for players and game masters. Every year, several new books offering help to roleplaying gamers reach print. Meanwhile, bloggers like me and countless others post advice and hope someone finds it useful.

With all this coaching, who needs more? For my part, I look for topics that haven’t gained much discussion and gather the best suggestions.

Monte Cook brings credentials earned through a long career in roleplaying games. In 1988, Cook started working for Iron Crown Enterprises on their Rolemaster and Champions games. By 1992, he started working for TSR where he penned Dead Gods, one of the greatest D&D adventures since 1985. He served as a lead designer on D&D’s third edition. For his Monte Cook Games, he designed roleplaying games such as Numenera, Invisible Sun, and The Strange. Among living RPG designers, Monte surely rates as the most famous and acclaimed.

This year, Monte published Your Best Game Ever, “A tool book, not a rulebook—for everyone who plays or runs roleplaying games.” When this book of advice reached Kickstarter, it rated as a must for me.

The finished book brought a couple of surprises. First, the campaign touted a long list of contributes from roleplaying game pioneers like Jennell Jaquays to famous voices like Matthew Mercer. I expected a compilation of advice from the contributors. Instead Monte stands as the book’s primary author, with the contributors seasoning the book with short sidebars. This makes a happy surprise because Monte brings a singular voice of 30-some years experience, which gives the book a clear, consistent feel. Second, outside of starter sets, few books of roleplaying advice aim to help beginners. Your Best Game Ever starts as a primer for new players, and then builds to help veteran gamers. This old enthusiast kept noting favorite quotes and even pages.

I chose ten passages from a 240 page book to give a taste of the content inside. But as I read and scribbled notes, I kept thinking that Your Best Game Ever rates as a book I want to come back to again and again. Highly recommended.

1. Lean Into Failure (Occasionally) (p.58)

You play games to win, and you win an RPG by succeeding at your goals (defeat the villain, get the gold, get more powerful, and the like). But if you’re a player focused on story, you need to look at things a little differently sometimes, because to win an RPG from this perspective is to tell a great story. And sometimes the best stories arise out of failure or defeat.

2. Anticipating Where the PCs Will Go (p.99)

A good GM knows where the PCs will go and what they’ll do before they do. However, the GM doesn’t force them to go anywhere or do anything. How on earth do you accomplish that?

Players have their PCs go where things sound most appealing, interesting, or fulfilling of their goals (wealth, power, information, the recovery of the kidnapped duke, or whatever). And you are the one who controls the places and things that fit that description.

Sometimes, you can subtly encourage the PCs to go in a certain direction or do a certain thing (because you’ve got stuff prepared for that choice). You do this by observing and learning what the players are likely to do. Once you figure things like that out, you can guide the players and they won’t even know you’re doing it.

3. Leading Questions (p.128)

GMs should be very aware of when they ask leading questions. Now, my point here isn’t to encourage you to avoid them—just to be aware of them. Sometimes, leading questions are valuable tools. But most players will read into a leading question, so don’t use them unless you want a player to read into them. This leading question is probably the most powerful in the arsenal: Are you sure you want to do that?

4. Speaking for the Group (p.129)

Sometimes one player will attempt to speak for the group, saying something like “We turn on our flashlights and go inside the warehouse.” If that happens, just go with it. If the other players don’t object, it makes things a little easier and moves them along a little faster. You don’t have to get confirmation from all the other players. It’s their duty to pay attention and interject with “Wait, I don’t want to go into the warehouse,” or “I’ll stay outside while everyone else goes in” if that’s how they feel.

5. Answering Questions (p.129)

Sometimes a player will ask a question that they shouldn’t have the answer to. Questions like “Are the police in this town corrupt?” or “Where do criminals fence their stolen goods around here?” Rather than saying, “You don’t know,” try instead asking the player “How will you go about finding the answer to that question?” Doing that turns their question into a forward-moving action. It becomes something to do, and doing things is more interesting than asking the GM questions.

6. Pacing Within a Session—Important Moments (p.132)

Sometimes, though, it’s worth taking a bit of time with an important moment. An audience with the queen, the appearance of an elder god, or flying a spaceship into a black hole are all scenes where it might be okay to take your time. In fact, the change of pacing will highlight the importance of the moment and can, all by itself, convey the gravity you want. But here’s the thing about slower pacing—you have to fill up the gaps with something. In other words, it’s okay to slow things down, but if you do, you need more evocative description, more intriguing NPCs, or more exciting action.

7. Pacing Within a Session—Unimportant Moments (p.132)

A GM who is adept at pacing will take this a step further, to the point of perhaps surprising the players, at least at first. If there are a couple of rather low-powered guards at the entrance to a high-tech complex and the players announce their intention to take them out quickly, the GM might just say, “Okay, you knock out the guards. What do you do with their unconscious bodies?” No die rolls, no game mechanics.

That will catch the players off guard at first, but it’s going to tell them about the difficulty of the challenge and the importance of the encounter. In an instance like this, the GM knows that PC victory is a foregone conclusion, and rather than taking ten minutes to resolve the rather meaningless encounter, they simply get to the heart of the matter, which is what the PCs do immediately after the fight—do they try to hide their infiltration or charge right in? Because the GM knows that decision will affect the rest of the session far more than how much damage they can inflict on a low-powered foe. Plus, it saves session time for the challenging encounters to come.

8. Enduring Player Agency (p.136) If you put a PC in a situation where their abilities don’t work, you’re taking away their agency. Rather than negate their abilities, require them. If a character can phase through walls, don’t set up the villain’s fortress so that the walls prevent phasing. Instead, make it so that phasing is literally the only way the PCs can get in. By requiring that ability, you’ve rewarded the player for selecting it.

9. Even a Simple Game Is Fun (p.142)

The events that occur because of ideas generated by the players rather than the GM, and events that come about because of the inherent randomness of the game, are far more likely to make or break a session than the ideas the GM provides.

My point here isn’t to contend that the GM doesn’t matter. As someone who loves running RPGs more than almost any other activity, I’d never say that. What I’m saying is don’t put too much pressure on yourself as you’re getting ready to run a session, particularly if you’re a new GM. I’ve made this point many times, but I’ll make it again: RPGs are about group storytelling. It’s not all on you. It’s on the group as a whole.

10. Character Death (p.230)

Sometimes in RPGs we gloss over the effects of death in the story, but that’s not entirely believable and means missing out on great narrative opportunities. If a character dies, talk about how that impacts the survivors. Have a funeral in the story. Track down their next of kin. Build a memorial. Do something to recognize that the characters in the group are very likely close friends and would react as people who have lost someone significant in their lives.

Leave a Reply