Go to Part 1

Everything we’ve been discussing here are basic, systematic designs. But there’s no reason you need to be symmetrical. Maybe node A has two clues pointing to node B while node C is clue-happy for node A.

On a larger scale, you’ll probably find yourself mashing together lop-sided conglomerations of disparate structures.

For example, a good-sized chunk of my current campaign is based around a general layer cake approach: An interconnected web of criminal organizations allow the PCs to generally make their way up the “chain of command”. But this layer cake naturally funnels towards various sub-conclusions, and I’ve also included loops designed to carry the PCs back to points prior to the various funnels.

That approach may seem jargon-filled, but it’s really just a matter of embracing the fundamentally flexible principles of node-based design, strewing clues liberally, and spot-checking to avoid problem areas.

Looking over my notes for this campaign, I’ve come to think of this as the “cloud”: Dozens of nodes all containing clues and linked to by clues. Even if we discount all the different ways in which the PCs can approach each of these nodes, the complex relationships which emerge from the node structure make literally hundreds of potential outcomes possible.

But I didn’t have to think about that emergent complexity as I was designing the campaign-scale scenario: All I needed to do was design the criminal organization, break it into node-sized chunks, and then lay down the clues necessary to navigate to and from each node.

As I write this, my players are about mid-way through this section of the campaign. It’s been filled with countless surprises for all of us, and these surprises lead me to a final point regarding the strengths of node-based design: It’s flexible in play.

Because each node is, effectively, a modular chunk of material, it becomes very easy to rearrange the nodes on-the-fly. For example, when the PCs raided an enemy compound and wiped out half of their personnel before being forced to pull back, it was very easy for me to look around, grab a different node full of bad guys, and plug them in as reinforcements.

In other words, it was as easy for me to call in the reinforcements as it was for the NPCs to pick up the phone. Node-based design gives you, by default, the scenario-based toolkit I talked about in “Don’t Prep Plots”. And the underlying structural function of that node hadn’t changed: The NPCs still had the same clues to provide that they’d been designed to provide at their previous location.

Go to Part 9: Types of Nodes

It took about forty years before Frank Miller rationalized Batman wearing a huge target on his chest. (He can’t armor his head.) But as I was watching the first episode of Naruto today, I was struck by how quickly they demonstrated the silliness of ninjas wearing big, round bullseyes in the centers of their backs.

(Particularly in a universe where shurikens are apparently the size of small Japanese cars.)

But when I stopped to think about it, I realized (in my own little Milleresque fashion), that it might not be a mistake after all: These are members of a fierce, warrior-centric culture. They’re supposed to stand bravely in the face of danger. And what’s the quickest way to make sure your soldiers never turn and run?

Put a huge target on their back.

…

What? You were expecting something profound?

Fine.

(1) When creating a fictional world, what can you include that seems deliberately odd by our modern and cultural understanding of the world? The oddity will draw the attention of your players/readers/viewers, allowing you to reveal some deeper truth about the setting. And once it has been explained, the oddity will (by its very nature) stick in the memory (along with its associated truth).

(2) I may be underestimating Masashi Kishimoto, but I’m guessing he didn’t give any more thought to the placement of that logo/bullseye than “that looks cool”. But that doesn’t mean that there isn’t value to be found in my explanation of it. Attempting to rationalize the incoherent can give rise to fresh and creative ideas.

When I’m using published modules I am almost always forced to adapt them to the cosmology of my own campaign world. For example, in my primary D&D campaign setting there is only one pantheon of gods. Trying to adapt adventures designed for the typical multi-pantheism of D&D can pose some unique challenges. But I welcome the challenge because the effort of rationalizing the incoherency between world and adventure results in a richer and deeper understanding of the world. It’s given rise to saint cults, lineages of holy artifacts, regional factionalism, heresy rituals, and more — and rather than defracting or detracting from the world, all of these elements instead become refined and concentrated.

(And this can flow both ways: For example, the conflict between the Imperial Church and the Reformist Churches in my campaign world frequently allow me to re-purpose church-vs-church material from published scenarios. But this will also frequently enrich individual adventures by introducing avenues of friction and tension which would otherwise be atypical.)

The real world is made up of diverse and often contradictory viewpoints, cultural traditions, and personal opinions. By injecting and adapting material created by others, some degree of that balance between the coherent and the incoherent which can be found in the real world is brought into the game world.

Go to Part 1

LARGE LAYERS

In case it hasn’t been clear, I’ve been using three-node layers in these examples because it’s a convenient number for showing structure. But there’s nothing magical about the number. Each “layer” in the previous examples constitutes an interlinked environment (either literal or metaphorical) for exploration or investigation, and you can make these environments as large as you’d like.

As long as each node has a minimum of three clues in it and a minimum of three clues pointing to it, the Three Clue Rule and its inversion will be naturally satisfied and guarantee you a sufficiently robust flow through the layer. But as you increase the number of nodes, you also open the possibility for varying clue density: Particularly dense clue locations could have six or ten clues all pointing in different directions.

Obviously, however, the larger each layer is, the more prep work it requires.

DEAD ENDS

Dead ends in a plotted mystery structure are generally disasters. They mean that the PCs have taken a wrong-turn or failed to draw the right conclusions and now the train is going to crash into a wall: There should be a clue here for them to follow, but they’re not seeing it, so there’s nowhere to go, and the whole adventure is going to fall apart.

But handled properly in a node-based structure, dead ends aren’t a problem: This lead may not have panned out, but the PCs will still have other clues to follow.

In this example, node E is a dead end. Clues at nodes B and C suggest that it should be checked out, but there’s nothing to be found there. Maybe the clues were just wrong; or the bad guys have already cleared out; or it looked like a good idea but it didn’t pan out into usable information; or it’s a trap deliberately laid to catch the PCs off-guard. The possibilities are pretty much limitless.

The trick to implementing a dead end is to think of clues pointing to the dead end as “bonus clues”. They don’t count towards the maxim that each node needs to include three different clues. (Otherwise you risk creating paths through the scenario that could result in the PCs being left with less than three clues. Which may not be disastrous, but, according to the Inverse Three Clue Rule, might be.)

On the other hand, as you can see, you also don’t need to include three clues leading to a dead end: It’s a dead end, so if the PCs don’t see it there’s nothing to worry about.

Of course, if you include less than three clues pointing to the dead end then you’re increasing the chances that you’re prepping content that will never be seen. But this also means that the discovery of the dead end might constitute a special reward: Extra treasure or lost lore or a special weapon attuned to their enemy.

Which leads to a broader point: Dead ends may be logistical blind alleys, but that doesn’t mean they should be boring or meaningless. Quite the opposite, in fact.

In the same vein as dead ends, you can also use “clue light” locations. (In other words, locations with less than three clues in them.) Structurally such locations generally work like dead ends, by which I mean that clues pointing to clue light locations need to be “bonus clues” to make sure that the structure remains robust.

The exception to this guideline is that you can generally have a number of two-clue locations equal to the number of clues accessible in a starting node. (For example, in the layer cake structure diagram you have three nodes in the bottom layer with only two clues each because the starting node contains three clues. If there wasn’t a starting node with three clues in it, the same structure would have potential problems.)

LOOPS

In this simple loop structure all four nodes contain three clues pointing to the other three nodes. The advantage of this simple structure is that the PCs can enter the scenario at any point and navigate it completely.

Obviously, this is only useful if the PCs have multiple ways to engage the material. In a published product this might be a matter of giving the GM several adventure hooks which can be used (each giving a unique approach to the adventure). In a personal campaign, clues for nodes A, B, C, and D might be scattered around a hexcrawl: Whatever clues the PCs find or pursue first will still lead them into this chunk of content and allow them to explore it completely.

Go to Part 8: Freeform Design in the Cloud

A couple days ago I talked about the Long Con of DRM and the inherent ethical and cultural problems with embracing (or even accepting) DRM systems.

When this topic comes up, people often mention Valve’s Steam as a counter-example of how to “do it right”.

They’re half right. Steam has taken the onerous nature of DRM and turned it into a feature by allowing you to access your Steam account and play your games from any computer in the world. The system also, obviously, allows you to buy games online and have them instantly delivered.

In other words, people don’t (generally) complain about Steam because the platform gives you the ability to do something that you otherwise wouldn’t be able to do. I can understand (and share) the appreciation of that added value.

On the other hand, all of these features could be offered without DRM which requires the copy I currently have downloaded to my computer to be periodically re-validated. (DrivethruRPG does it.) And any game that you buy in a box at your local store and then need to validate through Steam’s servers before playing is every bit as bad as every other online activation schema in terms of its long-term impact on consumer rights.

Make no mistake: The Half-Life 2 box I have on the shelf contains nothing but a worthless coaster on the day that Valve goes out of business or migrates to Steam 2.0. And the Orange Box I purchased through Steam directly will become nothing more than wasted hard drive space only a few days later.

The features Steam offers to the consumer are the reason I’m willing to occasionally buy games through the service. But the unethical DRM that they’ve made part of their service is the reason that I rarely do so. And if there is any other method of purchase available, I’ll avail myself of it.

Unfortunately, the PC gaming industry’s increasing reliance on draconian DRM is the reason that all my game purchases in the past 3 years have either been indie games or console games.

Go to Part 1

On the other hand, there is something to be said for the Big Conclusion. There are plenty of scenarios that don’t lend themselves to a shuffling between nodes of equal importance: Sometimes Dr. No’s laboratory is intrinsically more important than Strangeways’ library. And the Architect’s inner sanctum requires the Keymaker.

So let’s talk about some alternative node structures.

CONCLUSIONS

In this design, each node in the second layer contains a third clue that points to the concluding node D. The function should be fairly self-explanatory: The PCs can chart their own course through nodes A, B, and C while being gently funneled towards the big conclusion located at node D.

(Note: They aren’t being railroaded to D. Rather, D is the place they want to be and the other nodes allow them to figure out how to get there.)

One potential “problem” with this structure is that it allows the PCs to potentially bypass content: They could easily go to node A, find the clue for node D, and finish the adventure without ever visiting nodes B or C.

Although this reintroduces the possibility for creating unused content, I put the word “problem” in quotes here because in many ways this is actually desireable: When the PCs make the choice to avoid something (either because they don’t want to face it or because they don’t want to invest the resources) and figure out a way to bypass it or make do without it, that’s almost always the fodder for an interesting moment at the gaming table in my experience. Nor is that content “wasted” — it is still serving a purpose (although its role in the game may now be out of proportion with the amount of work you spent prepping it).

Therefore, it can also be valuable to incentivize the funneling nodes in order to encourage the PCs to explore them. In designing these incentives you can use a mixture of carrots and sticks: For example, the clue in node A might be a map of node D (useful for planning tactical assaults). The clue in node B might be a snitch who can tell them about a secret entrance that doesn’t appear on the map (another carrot). And node C might include a squad of goons who will reinforce node D if they aren’t mopped up ahead of time (a stick).

(That last example also shows how you can create multi-purpose content. It now becomes a question of how you use the goon squad content you prepped rather than whether you’ll use it.)

FUNNELS

The basic structuring principles of the conclusion can be expanded into the general purpose utility of funneling:

Each layer in this design (A, B, C and E, F, G) constitutes a free-form environment for investigation or exploration which gradually leads towards the funnel point (D or H) which contains the seeds leading them to the next free-form environment.

I generally find this structure useful for campaigns where an escalation of stakes or opposition is desirable. For example, the PCs might start out investigating local drug dealers (A, B, C) in an effort to find out who’s supplying drugs to the neighborhood. When they identify the local distributor (D), his contacts lead them into a wider investigation of city-wide gangs (E, F, G). Investigating the gangs takes them to the Tyrell crime family (H), and mopping up the crime family gets them tapped for a national Mafia task force (another layer of free-form investigation), culminating in the discovery that the Mafia are actually being secretly run by the Illuminati (another funnel point).

(The Illuminati, of course, are being run by alien reptoids. The reptoids by Celestials. And the Celestials by the sentient network of blackholes at the center of our galaxy. The blackhole consciousness, meanwhile, has suffered a schizoid bifurcation due to an incursion by the Andromedan Alliance…. wait, where was I?)

In particular, I find this structure well-suited for D&D campaigns. You don’t want 1st-level characters suddenly “skipping ahead” to the mind flayers, so you can use the “chokepoints” or “gateways” of the funnel structure to move them from one power level to the next. And if they hit a gateway that’s too tough for them right now, that’s OK: They’ll simply be forced to back off, gather their resources (level up), and come back when they’re ready.

Another advantage of the funnel structure is that, in terms of prep, it gives you manageable chunks to work on: Since the PCs can’t proceed to the next layer until they reach the funnel point, you only need to prep the current “layer” of the campaign.

LAYER CAKES

A layer cake design achieves the same general sense of progression that a funnel design gives you, but allows you to use a lighter and looser touch in structuring the scenario.

The most basic structure of the layer cake is that each node in a particular “layer” gives you clues that lead to other nodes on the same layer, but also gives you one clue pointing to a node on the second layer. Although a full exploration of the first layer won’t give the PCs three clues to any single node on the second layer, they will have access to three clues pointing to a node on the second level. Therefore, the Inverted Three Clue Rule means that the players will probably get to at least one node on the second layer. And from there they can begin collecting additional second layer clues.

Whereas PCs in a funnel design are unlikely to backup past the last funnel point (once they reach node E they generally won’t go back to node C since it has nothing to offer them), in a layer cake design such inter-layer movement is common.

Layer cakes have a slightly larger design profile than funnels, but allow the GM to clearly curtail the scope of their prep work (you only need to prep through the next layer) while allowing the PCs to move through a more realistic environment. You’ll often find the underlying structure of the layer cake arising naturally out of the game world.

Go to Part 7: More Alternative Node Designs