The Alexandrian

Ptolus - In the Shadow of the Spire

IN THE SHADOW OF THE SPIRE

SESSION 15B: THE GHOSTLY MINSTREL PLAYS

January 12th, 2008
The 5th Day of Kadal in the 790th Year of the Seyrunian Dynasty

THE BEJEWELLED SCARABS

They returned to the door at the base of the stairs. Tee was able to easily pick the lock and then swing it open.

The walls of the thirty-foot long chamber beyond the doors gently curved out and then curved back to a narrow open doorway. Everywhere Tee looked, the walls and floor of the chamber glittered brightly in their torchlight. It took a moment for her to realize that they were completely covered in the gleaming carapaces of large scarab beetles… and that each carapace appeared to be studded with large gemstones.

However, none of them were moving. It appeared that all of the scarabs were dead.

Unfortunately, appearances could be deceiving: As Tee crossed the threshold of the room, a metallic skittering filled the room and the layers of bejeweled scarabs began shifting.

One of them scurried out into the center of the room, stopped, and turned towards to Tee. Before she could react, one of the diamonds studded upon the scarab’s back flared with a blinding brightness.

Tee stumbled back, her eyes overwhelmed by the flash. Several of the others who had also been standing in the doorway were blinded, too.

Agnarr barged his way into the room and Tor followed, but the tight quarters made it difficult for them to find or hit the scarabs. Indeed, not all of the scarabs  in the room were moving – only some of them. But these were now spitting painful acid and emitting blasts of impossibly cold air which withered the skin where they touched.

After several minutes of complete disarray, it seemed as if they were beginning to get the upper hand. Several of the scarabs had been smashed, and the frequency of their attacks – and the blinding flashes of light – were decreasing as their numbers were thinned.

Shardsoul Slayer - Monster Manual VUnfortunately, the sounds of their struggle had attracted the attention of something else: A mechanical creature – lithe and angular with a body of smooth blue-gray metal – rounded the far corner. Vicious tines protruded from the joints along its arms, legs, and curved spine.

They were out of position and taken by surprise. Worse yet, the scarabs had not yet been vanquished – the diamond scarabs continued to emit their blinding flashes of light, leaving them painfully vulnerable to the construct’s slashing tines, crushing blows, and serrated fangs.

Agnarr and Tor tried to move into a defensive front – blocking the powerful construct from their more vulnerable comrades. Unfortunately, this proved disastrous. Every few moments the construct’s single eye – a malevolent green orb – would pulse brightly, and in that instant powerful telepathic waves filled with hate and rage would wash over those nearest to it.

Agnarr almost immediately succumbed to the telepathic assault, and immediately turned on Dominic – who was standing directly behind him. Tor shouted a warning, but before anyone could react, Agnarr’s greatsword had smote Dominic to the floor. The powerful blow dropped the priest to his knees, blood gushing from his chest. Read more »

In Arneson’s Blackmoor, as described in the First Fantasy Campaign from Judges Guild, there are “fighting machines”, “water machines”, “flying machines”, and “teleportation machines”.

First Fantasy Campaign - Dave Arneson (Judges Guild)For those unfamiliar with the First Fantasy Campaign, it is largely comprised of the raw notes Arneson was using to run his campaign. Very little effort is made in the way of explanation, and the notes are also frequently (and frustratingly!) incomplete. Or confusingly combine notes from different, incompatible eras of the campaign. No explanation is given for what any of these “machines” do (although PCs are able to build flying machines and there’s also an “ancient war machine” in a Dark Lord’s throne room which he uses to communicate with his subjects).

Everyone basically assumes that they know what the “teleportation machine” and “flying machine” are. (Although that’s an assumption that you might want to challenge: It is very easy to casually interpret these early documents through the lens of what we know Dungeons & Dragons would become, while forgetting that D&D didn’t actually exist yet when these documents were written.) “Water machine” and “fighting machine”, in any case, have proven more elusive.

Some have postulated that the “water machine” is a boat. That its entry on Arneson’s treasure tables is identical with his description of this magical item:

Skimmer: Can cross stretches of water at great speed, 50 mph and greater, as well as marsh and short (10 yards) stretches of low unobstructed land. Hitting a snag will wreck the Skimmer and cause the occupants one Hit Die in damage per 5 mph of speed. Chance of hitting a snag is about 1% per 100 miles of water, 5% in marsh, and 5% every time any land is crossed. All encounter chances can be ignored due to its speed.

This, however, appears doubtful to my eyes. To explain why, let’s talk a little bit about where these “machines” appear in Arneson’s notes. The Water Machine appears in two different treasure tables, one for Loch Gloomen (where it’s on the “Information” sub-table):

Crystal Ball 9, Teleportation Machine 4, Flying Machine 3, Fighting Machine 10, Water Machine 11, Special Devices 12 + 2, Ancient Books and Manuscripts 8 + 5, Stores of Normal Weapons 7, Clothes 6, etc.

And the other for Bleakwood (where it’s on the Equipment sub-table):

Crystal Ball 1-5, Illusion Projector 6-10, Teleporter 11-12, Flyer 13-17, Skimmer 18-20, Water 21-30, Dimensional Transporter 31-32, Time 33, Transporter 34-39, Borer 40-44, Screener 45-46, Communicator 47-51, Tricorder 52-56, Battery Power 57-66, Medical Unit 67-72, Entertainer 73-82, Generator 83-87, Educator 88-92, Robots 93-98, Controllers 99-00

Note that “Teleportation Machine, Flying Machine, Fighting Machine, Water Machine” has become “Teleporter, Flyer, Skimmer, Water” on the latter list. It’s possible that Water Machine does mean Skimmer, and Arneson simply repeated the same entry twice in a row on the table, but that seems unlikely.

On the other hand, this isn’t the only seeming repetition on the table: Note that “Teleporter” (i.e., Teleportation Machine) and “Transporter”, which one might immediately assume to be the same thing, are listed separately. I, however, suspect that these are not the same thing, that the “Transporter” is based more literally on Star Trek and is a large facility which you can use to beam yourself to other locations (but not take the equipment with you).

And, similarly, I think that the Skimmer and the Water Machine are two different things (albeit perhaps grossly similar in function).

One option for the Water Machine would be a submarine.

Another option I’ve considered is that these “Machine” entries are actually triggers for sub-tables that no longer exist. (This wouldn’t be the only example of missing sub-tables in the First Fantasy Campaign.) Looking at Supplement II: Blackmoor, we find a number of water-related magical items: Ring of Movement (Swimming), Manta Ray Cloak, Necklace of Water Breathing, Helm of Underwater Vision. These could easily be re-characterized as “Water Machines”, perhaps suggesting that the other Machine types are also sub-categories. One could imagine similar sub-tables for other Machine categories.

Something else to note, however, is that you’re more likely to get a result of “Water [Machine]” on the Bleakwood table than literally any other type of treasure except the “Battery Power”. The function of Battery Power is also unexplained, but it seems quite likely to be way of recharging Arneson’s science fantasy “magic” items. Is it possible that the Skimmer is the Water Machine of the Loch Gloomen table and the “Water” entry is some similar resource that could be used in conjunction with the other items? Could it actually be some form of liquid fuel that could be used to power vehicles like the Skimmer?

While potentially cool, there’s no question that it’s a fairly large reach. Supplement II also includes another water-themed item which purifies 10 square feet of seawater. If that’s all that a Water Machine does, it could explain why they were so ubiquitous.

BY WAY OF FIGHTING MACHINES

Let’s leave the Water Machines aside for a moment and talk about the other enigma here, the Fighting Machines. One suspicion is that these are, in fact, robots. (Note that there is no “Fighting Machine” entry on the Bleakwood treasure table, but an entry for “Robots” has been added.)

Here, however, is what the phrase “fighting machine” would have almost certainly conjured up in an SF pulp afficionado’s mind in the early 1970s:

War of the Worlds - illus. Henrique Alvim Corréa

The fighting-machines of H.G. Wells’ War of the Worlds are, of course, vehicles. But they also have a robotic aspect to them.

I’m actually drawn to the idea that all of the Machines are autonomous robots – some of which might also function as vehicles – specializing in the listed functionality. Thus:

  • Fighting-Machines are Wellsian tripods (with some perhaps at a smaller scale, and the larger suitable for giving their controllers a huge advantage in Blackmoor-style war games).
  • Teleportation Machines as robotic entities who, upon request, will teleport you to a location of your desire. (Or use the same function as a devastating offensive capability or means of flight.)
  • Flying Machines as UFO-like objects guided by sentient intelligence. (I’m anachronistically thinking of the ship from Flight of the Navigator; although, again, at various scales.)
  • Water Machines as submersibles? Perhaps.. Or perhaps simply water-proofed robots.

This also suggests the possibility that the “ancient war machine” is, in fact, a robot through which the Dark Lord speaks.

Looking again at seemingly duplicated entries on the treasure tables, I’ll note that teleport-type objects actually show up three times: Once as a Teleportation Machine, once as a Transporter, and once as a Teleportation amulet. If the Teleportation Machine is just a magic device allowing for teleportation, than its utilitarian function is basically identical to that the of the Teleportation amulet. But if the amulet is an item you can carry, the Transporter is a largely immovable facility, and the Machine is an autonomous robot/tripod… Well, you can see how these all become distinct items.

Weighing against this interpretation is the fact that you’d expect some of Arneson’s original players to have recounted running into Martian tripods or teleporting robots. On the other hand, there are truthfully very few accounts of those early adventures, and those accounts have very rarely (if ever) included mention of any robots. Or tricorders. And those are right there in black and white.

With that being said, I’m not claiming to have definitively revealed holy writ here. There’s simply not enough information preserved for us to ever recover definitive answers. But this is one of the cool things about exploring these ur-texts of the hobby: That first generation of GMs may have collectively never figured out how to effectively transmit what they were doing in writing, but in puzzling our way through the fragments they did leave behind, I find there’s an amazing alchemy of closure that takes place, prompting creative insights that would never occur in simply reading a more authoritative text.

Back to Reactions to OD&D

Go to Running Castle Blackmoor

IN THE SHADOW OF THE SPIRE

Session 15A: The Labyrinth’s Machines

…and then arcs of purplish electricity began to leap between the bulb-tipped rods protruding from the machinery in the center chamber and the rods in the coffin chambers. From there, the arcs converged on the coffins themselves. The electrical bolts danced with a horrible beauty, filling the three chambers with harsh light that seemed barely dimmed by the smoky glass.

Since writing the Three Clue Rule, I’ve spent just over a decade preaching the methods you can use to design robust mystery scenarios for RPGs that can be reliably solved by your players.

Chaositech - Malhavoc PressNow, let me toss all of that out the door and talk about the mysteries that your players don’t solve. And that, in fact, you’re okay with them not solving!

Note that I did not say “that you WANT them not to solve.” And there’s an important distinction there: If there’s a mystery you don’t want the PCs to solve (for whatever reason), then you simply don’t include the clues necessary for them to solve it. That’s not what we’re talking about here: These are mysteries that the PCs can solve. They just don’t.

And that’s OK.

In fact, it can greatly enhance your campaign.

You can see examples of this in the current campaign journal with the strange machinery the PCs investigate and are, ultimately, unable to fathom.

“So what did it do?” Elestra wondered.

“Without occupants for the coffins, most likely nothing,” Ranthir said.

First, why is this OK?

Because the mystery is structurally nonessential. There is something to learn here, but the failure to learn it does not prevent the scenario from continuing.

When we, as game masters, create something cool for our campaigns, there is a natural yearning for the players to learn it or experience it. But that’s a yearning which, in my opinion, we have to learn how to resist. If we force these discoveries, then we systemically drain the sense of accomplishment from our games. Knowledge is a form of reward, and for rewards to be meaningful they must be earned.

Second, why can this be awesome?

The technique I’m suggesting is that your scenarios can be studded with literally dozens of these nonessential mysteries. At that point, it becomes an actuarial game. When including a bunch of these in a dungeon, for example, it becomes statistically quite likely that the PCs won’t solve all of them. (They might, but they probably won’t.) And the ones they don’t are going to create enigma; they’re going to create a sense of insoluble depths. Of a murky and mysterious reality that cannot be fully comprehended.

And that’s going to make your campaign world come alive. It’s going to draw them in and keep them engaged. It will frustrate them, but it will also tantalize them and motivate them.

It should be noted that one of the things that I think makes this work is that these mysteries are, in fact, soluble. I think that, on at least some level, the players recognize that. And the fact that there is, in fact, a solution has a meaningful impact on how you design and develop your campaign world.

(There’s also a place for the truly inexplicable. My 101 Curious Items is an example of that. But it’s a different technique and its effect is distinct.)

In the end, that’s really all there is to it, though: Spice your scenarios with cool, fragile mysteries that will reward the clever and the inquisitive, while forever shutting their secrets away from the bumbling or unobservant. When the PCs solve them, share in their excitement. When the PCs fail to solve them, school yourself to sit back and let the mystery taunt them.

If you’re wondering what one of these little mysteries looks like when the PCs solve it, check out Session 10 when they’re confronted with the gory remnants of an ancient tragedy:

When they approached the corpses they discovered that they were just two among many: Rounding the corner into the larger room they saw more than a dozen humanoid corpses strewn around the room. In the center of these corpses a massive, wolf-like corpse lay – it, too, had been horribly burned until its remains were nothing more than charcoal which had endured the ages.

Investigating the other chamber flanking the door of glass and bronze revealed an even stranger sight: Shards of iron had been driven with seemingly random abandon into the walls of the room. They recognized this iron: It was of the same type used in the cages they had seen before.

“Did something cause one of the cages to explode?” Elestra said.

“Or explode out of it?” Ranthir hypothesized.

“Like that creature in the other room?” Elestra said.

In this case, you can see how the PCs apply information they’ve gained from other encounters within the Labyrinth to shed light on the current forensic analysis. I hadn’t really planned that, per se. I just knew what the story was behind this room and how that story tied in with the rest of the complex. So when the players started asking questions about the metal fragments in the walls, I knew they were related to the cages they’d already encountered.

Note that this specifically works because these aren’t purely random bits of dungeon dressing. These nonessential mysteries aren’t just unrelated puzzles: They’re all part of the scenario, which inherently means that they’re also related to each other. Thus, as the PCs solve some of them and fail to solve others, what they’re left with is an evolving puzzle with some of it pieces missing. Trying to make that puzzle come together and glean some meaning from it despite the missing pieces becomes a challenge and a reward in itself.

This advice doesn’t just apply to dungeon scenarios, either. Any scenario can have these nonessential background mysteries woven around its essential structure: What’s the true story of how the Twelve Vampires came to rule Jerusalem? How did the Spear of Destiny end up in that vault in Argentina? What exactly was Ingen doing on Isla Nublar in Jurassic Park III? Who left these cryptic clues painted on the walls of the Facility?

In general, though, don’t think of this as something “extra” that you’re adding to the scenario. This stuff will usually arise organically out of the scenario as you’re designing it: You need to figure out what happened to the Isla Nublar facility, for example, to build your dinosaur island hexcrawl around its ruins.

This technique, therefore, can also help you avoid one of my pet peeves in scenario design: The incredibly awesome background story that the players have no way of ever learning about. Look at the background you’ve developed for the scenario: If there are big chunks of it which are not expressed in a way which will allow the players to organically learn about it, figure out how the elements of that background can be made manifest in the form of nonessential mysteries.

In the case of the Laboratory of the Beast, I knew that this section of Ghul’s Labyrinth had been used to work on several distinct research projects. Every lab, therefore, could be a separate little mini-mystery revealing exactly what Ghul’s arcanists had been working on down here and, thus, collectively also tell the story of these laboratories.

Ptolus - In the Shadow of the Spire

IN THE SHADOW OF THE SPIRE

SESSION 15A: THE LABYRINTH’S MACHINES

January 12th, 2008
The 5th Day of Kadal in the 790th Year of the Seyrunian Dynasty

Taking another turn down a hallway led them to a complex of three large chambers. In the center chamber, a massive apparatus of machinery had been built up in the middle of the room. Nearly ten feet across, it extended from the floor to the ceiling.

The far wall of this chamber was inset with a large, ten-foot wide sheet of smoky, opaque glass flanked by two doors.

To the left and the right, the other two chambers of the complex lay down short halls. In each of these rooms, short flights of stairs led up to large, coffin-like boxes of metal lying on the floor. To either side of these boxes were thick, metallic rods thrusting up from the floor with large, bulbous ends.

For now, Tee skirted around the machinery and checked out the doors. They were unlocked, leading to a small side chamber from which one could look through the smoky glass and observe the outer chamber. The northern all of the side chamber was covered in a morass of machinery – wires, glass tubes partially filled with liquid, convoluted gearworks, and the like.

Ranthir was fascinated. He had never seen anything like it before. It quickly became apparent that both the equipment in the side chamber and the main chamber was actually sunk into the floor, and probably connected to each other.

Tee moved to the coffin-like metal boxes. She discovered that their lids could be rotated to one side, revealing an interior surface coated with twisting tubes of glass. These formed coccoon-like depressions – one apparently shaped for a humanoid; the other for a large dog or wolf. Both were outfitted with manacles.

Ranthir, meanwhile, believed he had puzzled out the strange activation method used by the equipment: Several metallic spheres would need to be “spun up” by hand and then, while those were still in motion, three levers would need be flipped, and, at last, a button pushed.

“Should we try it?” Elestra asked. Read more »

Nefarious noble scheming has long been a staple of fantasy fiction, and it quite often makes the leap to space operas and the like, too. (Herbert’s Dune, for example.) Figuring out what the local nobility is up to in your campaign, therefore, can be an endless font of drama, intrigue, and scenario hooks.

A great deal of effort can be spent trying to get it “right”, but this is often an illusory goal. If you’re running a specifically historical campaign, then there will be a “true” version of how nobility worked for your chosen place and time period. But beyond that point, the historical norms of noble titles are so utterly varied by region, country, and time period that anyone insisting that there is, for example, one “correct” relationship between Dukes is, at best, deceiving themselves.

For example, depending on where and when you’re standing in history, a marquis could be:

  • A nobleman who controls an Imperial territory
  • A ruler of a border area (originally because those were the ones under Imperial control; but later simply because they were border territories)
  • A noble more powerful than a count and less powerful than a duke
  • A noble more powerful than a count and less powerful than a duke, but specifically because in this country dukes have to be members of the royal family
  • A synonym for “count” because the distinction between “count” and “marquis” has been bureaucratically blurred out over the past several centuries
  • A noble subservient to the king, but whom counts consider their liege
  • A courtesy title, often assumed by the cadet lines of noble familes
  • Any number of completely unrelated things in Asian cultures for which the term was used in translation

Once you realize that there is not, in fact, an ultimate truth to be found here, you’re freed up to make up you own noble traditions and relationships that are peculiar to the fantasy realms you choose to create.

This can often include making up entirely new titles. For example, in my D&D campaign world, the title of Syr dates back to a pre-historical empire. In addition to being a noble title (usually of regional leadership), it’s also the faux-etymology behind a male knight being referred to as “Sir” and female knights being referred to as “Sera”.

(And if you’re thinking, “Wait… aren’t female knights referred to as Dames?” That’s right. You’re starting to get it.)

A TANGLE OF TITLES

We have a tendency, when creating fictional worlds, to create things which are altogether too tidy. In the real world, things get messy: The Gregorian calendar, for example, is a hodgepodge of historical kludges and political compromises piled one atop another.

To make your world feel real — to make it feel like a place where people actually live — you’re going to muck it up a little bit.

For noble titles, you can achieve this with a three-step process:

1. Create a system which makes perfect logical sense.

For example, there’s the King. They’ve got a bunch of powerful Dukes who have sworn allegiance to them, and each Duke has either Counts (who rule inherited lands in the interior of the country) or Marquises (who rule over inherited lands on the border of the country) who have sworn allegiance to them.

2. Create just two exceptions: One grandfathered in from some other system. Another that’s newfangled and recent.

For example, in addition to the Counts and Marquises, there are also the Atabeks, druidic lords who swear fealty directly to the king, but who rule over nomadic tribes rather than specific pieces of land. More recently, Harald IV disbanded the duchies of Baudore, Hensfelle, and Ramsey fifty years ago because their dukes were possessed by demons. The Counts and Marquises who once swore fealty to those dukes now swear their oaths directly to the king, with no intermediary.

At this point, you’re done for now. Put your noble titles aside and either continue worldbuilding or get back to playing.

The goal here is to introduce a few cracks into your perfect system. Marring the perfection from the beginning is important because you’ll tend to want to preserve something that’s unbroken and “makes sense”. Once you’ve broken it a little bit, though, you’ll find yourself more open to the next step…

3. Whenever the current system doesn’t quite work right for your current adventure… add an exception.

For example, maybe you discover that the Free Cities were founded by Atabek-led tribes who settled into an urban life, resulting in some Atabeks functionally being mayors. (Because the PCs went to a Free City and you needed to figure out how their government fit into the existing system.) Or you discover that some counts are actually religious men who act as liaisons between religious land-holdings and the royal government, and that these noblemen are given the title of Vicomte. (Because you thought the imagery of an evil religious nobleman who rules out of a gothic cathedral was cool.) Or maybe it turns out that the marquises weren’t always inherited titles and, technically, the king can still create non-hereditary marquises, and will do so sometimes as a way of elevating knights who have proven worthy of greater reward. (Because you wanted a foppish city-born noble to act as a foil for the PCs… and then later realized that a title of Marquis would be a cool reward for the PCs to receive after saving the kingdom.)

In other words, don’t try to lay down all the messy complexities of life in one fell swoop. Layer it in as necessity requires.

That’s the way it happened in the real world, after all.

Archives

Recent Posts

Recent Comments

Copyright © The Alexandrian. All rights reserved.