Sunday, 13 May 2018

The Awesome Pain in the Ass That Was DragonQuest

Continuing my trio of bargain-bin rescues from Glasgow (actually a gift from Paolo, in lieu of buying an adventure from the system) I present to you DragonQuest, 2nd edition!

Why does this RPG system set my teeth on edge? My nostalgia should be all for SPI and the days of punching out wargame counters, all for Deathmaze and Citadel of Blood and War of the Ring and Sword and Sorcery. But good boardgaming chops do not guarantee a good roleplaying game.

Let's judge a book by its cover. Sorry guys, RPG players are not just dreaming of being Conan. D&D art got that right more often than not. They are in a fantasy-hero world, but team players; just like they're in a horror world, but not doomed, and in a science fantasy world, but stone cold medieval. The Frazetta muscleman hoisting up the results of his DragonQuest like a trophy bass is someone else's idea of "sword and sorcery".

The writing style of the game is a 180 degree reaction against the fast, loose but evocative D&D writing of the time. No gaps and confusing terminology here! DQ is buckled and strapped into the case law structure of an SPI wargame's rules (see 3.7.5.1 and apply the Rules Writing Procedure). If the GM has leeway, we'll tell you exactly where that leeway is. It's meant to be clear, but it's mechanizing and alienating on the page. The wargame influence also shows in the tight regulation of combat on a hex grid.

Maybe case-law would work if the mechanics were more elegant, as in Metagaming's contemporary offering The Fantasy Trip. But they're standard Rolemaster-type fare, a percentile skill system with "RPG 2.0" features like separate fatigue and physical damage, damage-reducing armor, critical hits, background packages, custom advancement ... Determining target numbers might have you multiplying 39 by 2.5. Damage involves frequent table lookups to see if a crit and physical damage happen. God forbid you should have a d6 laying around the house, here, roll one of your d10's and take half for a d5 instead. And roll four of those d5s to determine your character's stats.

What's a Satanic panic?
But it's funny how often interesting magic systems come attached to clunky base mechanics, while elegant systems like TFT or RuneQuest have difficult or prosaic approaches to magic. Certainly, something was possessing SPI around the turn of the 80's. They had a boardgame about the demons from the Lesser Key of Solomon, and worked some of those names into their Citadel of Blood adventure game. And yes, there's a whole school of DQ demon summoning that ramps up to 16 pages of fully powered Goetic infernal royalty. That menu is clearly where all the love lies, and the other magic schools suffer collectively by comparison. Some are solid, some near-unplayable like the Water Magic school with its Aquaman-style restriction.

By the way, there is a lot of cribbing from D&D, especially in the monster list. And in the kind of rules that compel game balance. Wizards can't cast near cold iron or while being distracted by damage. Player characters who poison their weapons might nick themselves. This points at the heart of the problem, that Dragonquest isn't built around a compelling setting (implicitly, as in D&D, or explicitly, as in Runequest). So much of it is generic that the special stuff fails to stick.

For example, instead of alignment, your characters get a quasi-astrological Aspect which gives them bonuses and penalties for very short periods of the day or year, or around a birth or death. Sounds cool, but it doesn't really resonate with any other social or magical structure, mostly boiling down to an optimum time and place to do housebound skill tests. Only the death aspect has any impact on the typical adventurer, with a +10% bonus just after a mammal dies near you.

At least the 2nd edition book concludes creditably, with a tight little sample adventure in a bandit oasis. It maybe shows, though, that DQ doesn't really know what kind of fantasy game it is. The journey to the camp is described last of all, oh yeah, you might encounter a sand golem. The real detail is put into the characters at the camp, their secrets and intrigues. It's not really necessary that one is a halfling and another is a hobgoblin. The magic, too, is subtle, pulp-story stuff. There are other consequences of aping the pulp era (the camp is run by one "Alla Akabar," and roles for NPC women comprise jealous wife and sex victim). Perhaps the game is more suited for would-be Conans after all?

Saturday, 28 April 2018

One Page Dungeon 2018: Beneath the Nameless Towers of the Kremlin

This year I thought I would do something gonzo and topical about all the rumors, disinformation, and horrible truths surrounding the Russia of the Czars, the Soviets, and Putin. There is a wealth of material, some of it verified, some of it shadowy, some of it obvious bullshit, and some of it (like Mushroom Lenin) a purposeful hoax. Any adventurers from any world using time or dimensional travel might find themselves summoned to the mad science labs under Moscow, embroiled in a Kremlinological intrigue.



Linked pdf version with sources for all the history and mythology.
 

Wednesday, 25 April 2018

Why the City?

File:Dommersen Gothic cathedral in a medieval city.jpg
"All I wanted was a repeating hand crossbow!"


Continuing the discussion about urban supplements and adventures ...

Cities and towns are ambiguous places in fantasy adventure roleplaying games.


They are safe places where parties can expect to rest, refit, do business, and train in a predictable way.
They are boring places where the above activities take place, between real adventures, with little fuss or muss.

BUT

They are dangerous places of adventure, crime, fights, intrigues, in the tradition of Fafhrd and Grey Mouser and dozens of other fantasy sources.
They are interesting places full of local color and characteristics.

Because of this dual role, and other characteristics such as their non-linear, fractal organization, cities are easy to get wrong in play. Players just want to trade and heal up, but the GM comes barging in with plots and names and scenery and thieves and murderers. Players want to get involved in the city, but the GM doesn't have details, or has so many details that there's no place to start. The encyclopedic organization of nearly every city book ever produced, including the one we looked at last time, doesn't help with this at all.

If you want the city to be safe and boring, in fact, there's no need for any special material about the city, other than a name, location, and approximate size to gauge the availability of goods and services.

Otherwise, it's useful to think about four kinds of "actions" in urban play.

Player-to-GM, mandatory. Players expect they can do a number of things in a decent city or town. Find an inn to rest, a temple to heal, various shops to buy equipment and sell loot, places to train. An urbanity without any of these features is damaged and in need of explanation, as when you buy a sword that is prone to break at the first blow.

Player-to-GM, optional. A lot of urban play revolves around players asking for goods and services that are not standard or listed in the rules. "Can I buy a repeating crossbow? Can I commission one? Can I find an arena fight? Is there a wizard who wants to trade spells with me?" The GM can agree, flatly refuse, or put some kind of test or adventure in the way.

GM-to-player, optional. GMs can also insert clues or hooks to tempt the players into adventure as they go about their mundane business; strange buildings, odd happenings in the street, the old man in the corner of the inn. Or, the players can just get things done and move on to the next dungeon.

GM-to-player, mandatory. This is when characters, plots and situations force themselves on the players. Guards barge in, thieves sneak in, wizards demand their time, the neighborhood is on fire; a thousand ways for the city to compel adventure.

Now, this scheme can help coordinate GM and player expectations about what they think is fun about cities, with players being able to talk about their need for more or less GM involvement at any point in the campaign. But it also suggests a better way to organize books about cities.
  • You start, literally, with the party at the city gates, describing what they see and what they have to do to get in.
  • You list the most common targets of Player-GM Mandatory play -- inns, shops, temples -- how to find them, and any "color" peculiarities about them (the temple has a dragon's skull for a dome! the inn has a goblin barkeep!) The players can stick to that shallow level of interaction, or dive in deeper.
  • You then describe ways to satisfy a number of Player-GM Optional requests, including things they may not have thought of themselves. The unusual goods and services in the town, and what they have to do to access them.
  • You give hooks and encounters that are GM-Player Optional, things they may see in the street. This is how you introduce factions: start with visible signs in society, later the full story of who is involved, and how these interact behind the scenes.
  • Finally, some strong moves that are GM-Player Mandatory. These can proceed logically from the party's other business (they see something they shouldn't have seen, so assassins are sent after them; a messenger from the Red Wizard Guild tries to talk them out of further business at the Blue Wizard Guild store). They can introduce contingencies, countermoves, campaigns.
The first two of these are kind of what I was getting at in the Street Guide Without Streets years ago. It's also a similar structure to the functional method of room description in adventures. With a little thought about what's useful, writers can satisfy both the GM's need for accessible information, and the player's variable needs for involvement with the goings-on in a city.

Monday, 23 April 2018

Can We Do Better than the Tyrant's Demesne?

So. I'm back.

Visiting Paolo up in the northern lands, we went to the excellent game shop Static on King Street and browsed its second-hand trove. I came away with two third-party products from the glory days of my first encounters with D&D, the early 80's days of electric-typewriter-and-Letraset layout, amateur art, and occasional gemstones of creativity amid the dross of naive simulationism. Paolo added thereto a third item from his collection. In the next few posts, I'll now review and muse upon these items in ascending order of interest value.

First up: WITHIN THE TYRANT'S DEMESNE, "a complete campaign module set in the world of Haven." The stats are from the "Thieves' Guild" game but very similar to the levels and abilities of D&D or its then-numerous improved systems. The authors don't get cover billing, but it's a collaboration among four names, chiefly Walter Hunt and Richard Meyer. The artists include -- is that Jeff Dee? no, the similarly cartoon-deco-styled V. M. Wyman (are those sci-fi lady initials?), and some other less talented names.

Overall: A standard fantasy city where the intrigues are predictable.

Cons: The kind of gazetteer-style design Zak's Vornheim reacted against. We start with a regional map and history, call out the factions and describe in detail each of their characters, go for a "tour" around the city neighborhoods, involving more building, shop and character descriptions, and finally -- in a 48-page book -- get down to six pages of plots and encounters that deploy what we've seen.

There's very little bizarre about the place, even in its weirdness. There's a tyrant, who keeps power through his brutal guards, the unfortunately named Redshirts, and also through a coopted thieves' guild. There's a merchant society, a bunch of wizard guilds. Reading about the other characters, it doesn't feel much like a tyranny is going on. Political allegiances of most shopkeepers are down to a random table. Explicit descriptions of oppression, resistance, toadying, plotting, and cowardice are few and far between. Probably the most memorable encounter hook is a bunch of blobby chaos creatures who bring back human meat for a butcher, Sweeney Todd style.

Awful wordplay abounds, like the gang modeled after The Who with a "Dr. Jimmy," a "Quiet One," etc.; the potion seller Plazebo; throwing in some obscure US labor movement references, a wizard called Ilgwu who is involved in a plot with the resistance leader Johill. But ...

Pro 1: In a fantasy world filled with Butars, Adars, Radmars, Bonams, Corams, and the occasional Lobar (all from the Tyrant's Demesne, mind you), it can be hard to get names straight. Yes, awful puns can help the DM remember who's who.

BUT, the players must get the puns only too late, or never. So Plazebo is too obvious; the Who goons could be just under the radar. Likewise the most clever name in the module, a lockpicker named Kasserine Khyber, after two famous mountain passes from military history. I once had a party do a whole campaign where Rick, son of Nick lived in a millhouse with a water gate near the Ford of Jerrold and was being investigated by the Wood Warden Burnsteen from the rangers' Post... Thankfully, they never got it until I revealed the scheme.

Pro 2: The intrigues, when actually described, are decent spots of mystery. There's a fairly linear plot to follow and discover a traitor to the Tyrant; a more multi-threaded plot involving apparitions of the apparently dead Johill, with a Scooby Doo-type explanation; and a number of short encounters that highlight some of the other secrets of the town. They're just hiding behind long stretches of description that follow neither the logical order of player engagement with the setting, nor the order of GM preparation to run any given adventure. The helpful table of NPC stats in the back can't mitigate this.

To do better in a modern-day roleplaying work, we have to realize what the city is, functionally, for the players and their characters. And that's the next post.