Session 18C: The Smoke of the Foundry

Sun Tzu said:

If large numbers of trees move, they are approaching. If there are many [visible] obstacles in the heavy grass, it is to make us suspicious. If the birds take flight, there is an ambush. If the animals are afraid, [enemy] forces are mounting a sudden attack.

Back in Session 13 I discussed the value of having a toolkit of basic tactical techniques in your back pocket as a Game Master. The headline for that essay was “Simple Simulatonist Tactics,” and the reason I did that is because I believe that the Game Master’s tactical acumen is not necessarily limited to the diegetic tactics of their NPCs.

In other words, the tactical techniques you use as a GM don’t always map to what would purely constitute tactics in the real world. You can think of tactics as being the techniques by which you achieve your desired effect upon the battlefield: In the real world / simulationist play, the desired effect is usually victory. (Often the method used is to manipulate your opponents’ thoughts and their decisions – see the Battles of Trebia and Cannae, for example – but ultimately you goal is victory.)

In dramatist and gamist play, however, your tactical choices as the GM may be made to achieve ends other than victory. Instead, you use tactics to achieve either dramatic effects or to create interesting challenges.

For example, the combat system in D&D 4th Edition is heavily designed to create My Perfect Encounters™. These encounters are balanced on a razor’s edge in order to create a gamist tactical challenge, and in order for the game to work properly the GM needs to make tactical choices appropriate to that paradigm.

When I was playing the D&D Gamma World version of this ruleset, for example, I once forgot what system I was using and had the bad guys perform a tactical retreat from a combat they were losing and seek reinforcements: This completely unbalanced the precarious encounter balance of 4th Edition and resulted in a near-TPK. (You can read a fully playtest report here.)

Even when a system isn’t mechanically tying your hands like this, though, you can still make decisions like this: It would be more interesting, from a gamist perspective, to fight the Big Bad Guy in his stronghold, so he won’t come charging out from his sanctum to save his minions. It’s dramatically more interesting to fight a sequence of elementally-themed bad guys, even if it would make more sense for the bad guys to form mixed-force tactical groups. And so forth.

HEAR THE REINFORCEMENTS

Here’s a simple dramatist tactical technique your can add to your toolkit: Letting the PCs hear the reinforcements coming.

(To be clear: This is certainly something that can arise naturally out of simulationist play – as the result of opposed Listen and Stealth checks, for example – but if the GM is specifically choosing to let the PCs hear the reinforcements coming order to create effect, that’s a dramatist decision.)

This is a great technique because it gives the players a space in which to make decisions that aren’t possible when the reinforcements just burst into the middle of the encounter: How can they prepare for what’s coming? Is there a way that they can delay the arrival of the reinforcements? Do they take the opportunity to withdraw before the reinforcements arrive? Do they pull out some heavy guns to clear their current opponents? And so forth.

One of the Shuul who had been in the front hall, satisfied that Tor and Dominic were pacified, turned and headed back through the hall and into the materials storehouse. Two more turned and headed into the second foundry, directly below Tee’s feet. In the sudden silence pervading the Foundry, Tee could hear their footsteps echoing ominously below her…

You don’t really get the Platonic ideal of, “Oh shit! There are more goblins coming!” in this multi-faceted conflict between the PCs, Shilukar, and the Shuul, but there are numerous examples of how auditory cues of what’s happening elsewhere can affect the immediate battlefield.

In this case, the basic technique of hearing the reinforcements coming is being complicated through the more advanced techniques of crossovers. In practice, this single battle is being treated as several different encounters, with things happening in one battle crossing over (often through those auditory cues) into the other encounters. (The proximity of those encounters also means that characters – particularly the NPCs – are often rushing between one encounter and another.)

Session 18B: Missed Opportunities

“The Crimson Coil?” Elestra said. “I think I’ve heard something about them. Random acts of violence. Vandalism. That kind of thing. I got the impression they hadn’t been around for years, though.”

“That’s right,” Tee said. “I was still living here. The cult members wore blood-red robes and hoods. They’d spontaneously appear in huge gatherings to wreak random chaos. Then, about two or three years ago, the Knights of the Pale tracked them to their stronghold – I think it was called Pythoness House. Reportedly the whole cult was wiped out.

Last year I wrote Rulings in Practice: Gather Information, which discussed how to handle information-gathering tasks like canvassing and research.

The 3^rd Edition of D&D, however, features a very interesting and fairly clear-cut distinction between “information you gather” (in the form of a Gather Information check) and “information you just know” (in the form of a Knowledge (local) check). Given that the information in question was often the exact same information, I found it necessary to really figure out exactly what the relationship was between these skills and how they should be handled in play. It’s a distinction that I think remains valuable in subsequent editions of D&D, including Pathfinder (which has the exact same distinction) and even 5^th Edition (which lacks the specific skills but nevertheless will run into similar issues of adjudication).

The short version:

Knowledge (local) gets you the same information, but at +5 DC.

Knowing something off the top of your head is simply more difficult than going to look it up. From a balance standpoint, the +5 DC is also the cost you pay for not needing to spend 1d4+1 hours (in the case of 3^rd Edition) looking for the information.

This same basic principle can be applied widely, even in systems that don’t mechanically distinguish between different forms of knowledge acquisition: In some cases, depending on the exact mechanics involved, you might test to see if they know something off the top of their head and then, if they spend the time necessary to actively look for that information, you can apply a bonus to their check.

(If you wanted to focus even more attention on this aspect of game play, you could even vary the size of that bonus based on how they actively look: Better libraries give better research bonuses, for example.)

In practice, there are some forms of information that very specifically require canvassing and, therefore, Knowledge (local) simply isn’t applicable for. (Did anyone see Bob Anonymous in the silver light district on Friday night? You need to actually go down there and ask around.) In practice, though, I recommend generally being pretty liberal in what you allow people to now.

ACCLIMATION

The other issue raised by Knowledge (local) was exactly what “local” consists of and also what happens with the skill when you leave one “local” and go to a different “local.”

As a loose guideline, I would apply a -4 penalty to Knowledge (local) checks on a scale from whatever your “local” was: Different city in the same area. Different region in the same kingdom. Different kingdom. Different continent (or similar divide). Different plane.

(So the penalty would be -8 if you were from the boondocks and went to the capital.)

This penalty could be quickly abrogated by a character who became acclimated to a new locale. At various times I would use a period of a fortnight or a month, but at the end of each period the size of the penalty would be reduced by -1. (That reduction was against the base -4, not the total penalty.)

The logic was that part of your Knowledge (local) skill is, in fact, the knack for picking up local knowledge.

On one occasion a player wanted to speed this process up, so I allowed them to make Gather Information checks once per day (and with the normal time required) vs. DC 15. Each success reduced the number of days required by the margin of success on the check.

This never really came up in the Ptolus campaign, of course, because it’s all set in one city. But in other campaigns I found it was a nice balance between making the Knowledge (local) skill useful for globetrotting characters and also allowing characters to enter strange places f without instantly being experts on their minutia.