The Alexandrian

Go to Part 1

Of course, it’s all well and good to say, “Prep Situations.” But one of the reasons people prefer the plotted approach is that it provides a meaningful structure: It tells you where you’re going and it gives you a way to get there.

Without that kind of structure, it’s really easy for a gaming session to derail. It’s certainly not impossible to simply turn the PCs loose, roll with the punches, and end up somewhere interesting. Similarly, it’s quite possible to jump in a car, drive aimlessly for a few hours, and have a really exciting time of it.

But it’s often useful to have a map of the territory.

This line of thought, however, often leads to a false dilemma. The logic goes something like this:

(1) I want my players to have meaningful choice.
(2) I need to have a structure for my adventure.
(3) Therefore, I need to prepare for each choice the players might make.

And the result is an exponentially expanding adventure path:

Node-Based Scenario Design - Exponentiall Expanding Adventure Path

The problem with this design should be self-evident: You’re preparing 5 times as much material to supply the same amount of playing time. And most of the material you’re preparing will never be seen by the players.

In some ways, of course, this is an extreme example. You could simplify your task by collapsing some of these forks into each other:

Node-Based Scenario Design - Collapsed Forks

But even here you’re designing eight steps worth of material in order to provide three steps of actual play. You’re still specifically designing material that you know will never be used.

And in other ways it’s actually not that extreme at all: The original example assumes that there are only two potential choices at any given point on the path. In reality, it’s quite possible for there to be three or four or even more – and each additional choice adds a whole new series of contingencies that you need to account for.

Ultimately, this sort of “Choose Your Own Adventure” prep is a dead end: No matter how much you try to predict ahead of time, your players will still find options you never considered — forcing you back into the position of artificially constraining their choices to keep your prep intact and leaving you with the exact same problem you were trying to solve in the first place. And even if that wasn’t true, you’re still burdening yourself with an overwrought preparation process filled with unnecessary work.

The solution to this problem is node-based scenario design. And the root of that solution lies in the inversion of the Three Clue Rule.

Go to Part 3: Inverting the Three Clue Rule

Share on TumblrTweet about this on TwitterShare on StumbleUponShare on FacebookShare on RedditShare on Google+Digg this

One Response to “Node-Based Scenario Design – Part 2: Choose Your Own Adventure”

  1. Michael Taylor says:

    I question the “You’re still specifically designing material that you know will never be used.”. If you create material for a specific game world, you might not use it now, but you can also use it later – in another adventure, in another situation. I’ve always found that the ideas gotten from creating these ‘side-paths’ are often very useful in fleshing out the game world.

    Of course I don’t have time to game anymore because of this approach! ;)

Leave a Reply

Archives

Twitter

Recent Posts


Recent Comments