I haven't posted that much about my Tomb of the Iron God campaign - though I did share one memorable mini-game event. I have been reluctant because a) I'm not sure people want to read play reports, honestly and b) it's so tied into the Tomb that I really wanted to wait to the end to do a report.
That report is coming, but it will be more a review of the module and description of how I altered the Tomb for my playing style, than what the players did therein. And to get into that I need to talk about the three things I find useful in an adventure key, without the cliched and restricting terms "crunch" and "fluff".
Finch's Primer. This can also extend to psychological descriptions of NPCs and their motivations.
"This room is a small domed natural cavern 10' high at its apex. Its walls are moist and caked with formations of off-white and beige limestone, while a layer of fine sand covers the floor. A crude gate of half-rotted oak logs lashed together with rope stands at the north exit, held closed by a twine latch on the inside. A patrol of 6 kobolds armed with clubs and throwing stones is resting here and telling stories. The troops are wary but led by a hothead, Kzitch."
Digital stats: Numbers and classifications in game terms, on which game procedures and rules can be based.
"The north door can be easily opened from the south side, but takes a door opening roll at -1 from the north side. There are 6 kobolds - a leader with 4 hp and five with 3,3,2,1 and 1 hp. Kobold: AC 13, +0 to hit, damage = club 1d6 or thrown rock 1d3 with 30' range, move 9, morale +2 if leader alive and present, -2 otherwise."
"In this room are 6 kobolds including a leader. If they detect the party first, the leader will take 1 combat round to rally his wary troops, and then charge headlong. If surprised by the party, they will rush behind the gate and attempt to hold it against the party. If the gate is pushed by those on one side it will start to topple forward to crush those on the other side, possibly creating a shoving contest."
So, at one end of the descriptiveness scale is the minimalist kind of description found in the Stonehell or Castle of the Mad Archmage megadungeons. Statblocks are often dispensed with, you are lucky if you get hit points for the creatures, and the DM is usually left to provide details about the physical surroundings and play out the logic of the encounter.
At the other end is the maximal style of, say, Ruins of Undermountain, where everything and every contingency is described along all three dimensions in great detail, you get to know every hobgoblin's government name (I'm hardly exaggerating) and one room description takes up half a page to two pages.
I actually find all three of these elements useful, in the appropriate doses. It's good not to have to flip through a rulebook to find an armor class, and good to have some idea of the monster strategy. But there has to be some compromise, because I want the written material to be manageable and not stretch over multiple pages. Of these three, the one I can most easily come up with myself on the fly is the procedural, and the one thing I would most like to see is the analog.
You see, in Old School play ... fluff is crunch. The sandy floor,
moist walls made of soft stone, composition of the gate, and
disposition of the kobolds all can feed into the players' improvised
plans and the DM's improvised rulings. Critics of "fluff" in adventure writing, already prejudiced by that term, call it unnecessary. Indeed, the prose need not be purple. But basic material facts about the structure of things are something I'd rather not have to improvise, even though I have done so many times running both Tomb of the Iron God and Castle of the Mad Archmage.
Saturday, 14 April 2012
Analog, Digital, Procedural
Subscribe to: Post Comments (Atom)
This is the most important post written so far this year.ReplyDelete
Good post. Every new game master needs to read this. Hell, it will help me a lot.ReplyDelete
I'll agree with -C and raise:ReplyDelete
"You see, in Old School play ... fluff is crunch."
This is the most important sentence in the most important post written so far this year.
For DM's like myself who have difficulty conveying imagery analog details are a life saver. I'd certainly like to see more adventures written in the same vein.ReplyDelete
This comment has been removed by the author.ReplyDelete
There are some tersely-written OSR dungeons that would greatly benefit from the occassional zero-ing in on the procedural, particularly those with multi-room encounters.ReplyDelete
Too many stick to the one style throughout - it's lazy and saying 'tradition, less is more, blah' doesn't justify incompetancy.
I agree, though the traditional mode is not actually "less is more." Many of the classic modules are actually quite verbose. The super concise style actually seems to be a relatively recent thing.Delete
Yeah, having to improvise material details too much also has the danger of potentially forgetting those details later. For modules, I think the most important distinction to keep in mind is a separation of knowledge intended for players and knowledge intended for the referee because all that text is not literature to be read but rather a tool that the ref uses to answer certain questions. What should I describe to the players? What monsters are present and what are their stats? What triggers any traps? What things are hidden and how? If these things are mixed, the tool is hard to use (and most modules mix them).ReplyDelete
I have always hated the terms crunch and fluff. This post explains nicely why. So thanks for that.
Absolutely! Well put. I've been running Barrowmaze and loving it, but the first session didn't go all that well for this reason. It had been a while since I had run a large dungeon of any kind, and I ended up going through the whole thing with a pencil and adding descriptive details to each room. Not to write dramatically, but to give the players details to hang their hats on.ReplyDelete
I read this for Blogs On Tape! http://blogsontape.paperspencils.com/2019/12/12/episode-73-analog-digital-procedural-by-roger-g-s/ReplyDelete