Scenes and nuggets - the DGP way

Anyone remember the DGP "nuggets" system? It was back when GDW had handed over most of the development of their Traveller game to Joe Fugate and crew of DGP. They had been thinking on adventure design a bit. The result was that they designed adventures in the format of "nuggest", which were self contained scenes. I wrote about them once before in relation to campaign play of Battletech. Now I'm thinking of them again, for organizing your scenario in a more general sense.

Each nugget had some thing that would happen, some NPC you could talk to and a place to visit. The new thing was that DGP had sorted these in order, and told you which nugget had to go after the other. It was kind of like the solos, where you had forks in the road where you had to choose were to take the plot. I always thought these nuggets were a sweet idea, but I also never felt they worked as promised.

In Trail of Cthulhu the authors write about how to structure your adventure along a "spine" and then have branches off that tree. Core clues, those that are crucial for the mystery, are forming the spine of the adventure. I have not yet played much ToC, so I have no  solid opinion on how well that works. It doesn't read like it would work that well, but maybe it just puts into words what we have been doing all along. The thing is, this is what the nuggets DGP used reminds me of. I guess nobody is surprised that this idea was old.


Now I feel like pulling out some of those old Traveller books and taking a look at them with ToC in the back of my mind. For those who are interested in adventure design, it might be something worth studying. Identifying where you have choke points is very crucial if you want to make sure you don't limit your players, and maybe structuring your scenario in nuggets like that is a good way to find out the logical structure of your design? If you do that, you can then design where to break up the rails, and where to leave them in. I for one am going to take a look at those old nuggets again.

How to write adventures - stringing scenes together

I've posted before on my thoughts about scenes as the currency of gaming. This post is about how to use them to best effect. I'm not claiming to tell how it is, this are my thought right now, and will probably change.

Having scenes thought out, I think it's quite tempting to decide from the start which of your darlings you want to use, and what's going to happen. Especially the latter is tempting. If you "figure out" that they players will do B after doing A, you can be pretty sure that they will want to do C instead and will violently protest about that B you dangle in front of them. Don't do that. I at way to got at doing just that. So, how do you do?

I've tested out a few ways myself, and read about what others have done. I think that there are a few way to do scene based design without laying down the tracks. I think the best way is to have one opening scene, one scene with some kind of conclusion to the main conflict and in between you have the other scenes. If you introduce a threat in scene one, and put in some things that leads up to the conclusion or what brings the conflict to a head you can kind of have your cake, and eat it too. Say you have a bad guy planning to do a bad thing at a specific place at a specific time. Then it's fairly obvious which the concluding scene will be, and if the first scene is designed to involve the players you probably have your adventure right there. You could probably run that after just thinking about the supporting cast and some key locations, and after putting some stats to that you could improvise the rest.

My latest game, which we cancelled due to scheduling problems, was supposed to be some attempt in this vein. I had a starting scene introducing the action, and when a key event happened a NPC would show up, kill another NPC and then I'd let the law descend and see which way the player character jumped based on whom they had befriended before the murder. That way I hoped to tell a story, while giving the players the ability to steer most of the action. Key for me here would be that even if the players did nothing, I could make sure something happened, and if they did take the plot and run with it, I could just throw in that smoking gun and go along with the ride.

Wish me luck herding the cats back together and we might see if it worked!

How to write adventures - some attempts at consolidating ideas

I've listened to quite a few podcasts  where the topic have been how to write convention scenarios. That combined with my experiences running Savage Worlds and my post apocalyptic game have resulted in some conclusions. At least I think it's conclusions. But, naturally, I will probably keep thinking on the topic, and probably keep posting new ideas. Now I felt like summarizing somewhat.

I think I've found two ways to write adventures. There might be more ways, but these two have worked for me, and I felt like taking some note of what parts were needed for the machine to work.

First off, Location Based Design.

For this to work, you need two things.

1. A map
2. Threats

The first thing can be a dungeon map, or a map of a city, spaceport or whatnot. It should provide things to investigate, and things to uncover. The second thing can be monsters, traps and NPCs with nefarious plans.

The Location Based Design I think work best when the reason for being there is not based on the location. It should be something that the PCs take with them, a mission or a rumour. For the longevity of this type of design I think that is a key thing.

Secondly, Scene Based Design.

For this design to work, you need three things.

1. Where the scene is set.
2. Those who are present stated up, with intentions and motivations.
3. What just happened, the "bang".

In this case I think the reason for being there is different. Now it should be part of the location. Either it is the place, or the people there, that compels one or more characters to be there.

Naturally, to have more than a very short scenario you will need multiple scenes. The way you string them together can probably be a topic in of itself. I'll get back to it.

I will try to dive a bit deeper into how these two crystallized in my next post, and bring some examples. Anyone having experiences with those two sets of design frames are welcome to chime in. I hope I will better understand my own thinking, and know I have more to learn on the topic.