Tag Archives: Arduin

How D&D’s Rules Changed To Encourage More Varied Groups of Heroes Than Those in the Pulp Fantasy That Inspired the Game.

14 Replies

Today’s Dungeons & Dragons focuses on letting players build custom characters to suit their taste, but for half of the game’s 50-year history, the rules emphasized rolling a character and playing the numbers the dice gave. Especially at first, gamers demonstrated their play skill by making the most of some random combination of scores. Original D&D paired non-humans with particular character classes, so dwarves could only become fighting men. Every elf, dwarf, and (until 1977) hobbit fit their race’s archetype. Mainly though, gamers loyal to the game rules played humans, because the rules limited the number of levels non-humans could gain. For example, a dwarf could only reach level 6. Largely human parties suited the taste of D&D co-creator Gary Gygax. Ability scores hardly mattered, and with limited character options, characters became distinctive as they adventured and won magical gear. Those magic trophies served as mementos and made one elf play differently from all the others.

Today’s game looks very different. If a party contains a single human, the group rates as unusual. Player’s typically want characters who feel extraordinary from level 1. Often, that means playing the best ale-loving, hammer-smacking, dwarf who ever craved gold. Sometimes that means playing a dwarf wizard who happens to love gardening. The countless tiny, fairy barbarians that have joined my tables show that players relish a chance to play a character who defies type and at least seems one of a kind. Non-human characters only match a racial archetype when a player chooses it. To most players, the old rules that made races fit a stereotype now feel confining. Sometimes, those old rules even feel like a troubling reminder of outdated attitudes.

This evolution took all of D&D’s 50 years. This post tells the story of the change.

“In the old days, elves and dwarves and some of the other playable options were very much the product of folklore, and in folklore, elves and dwarves were embodied metaphor,” says D&D’s lead rules designer Jeremy Crawford. “They were metaphors for different aspects of the human psyche. So, elves were often associated with more elevated lofty aspects of the human psyche. Dwarves were often associated with the industriousness that some people manifest.” In fairy tales, these metaphors became talking creatures. “You can meet a demon that’s embodied evil. You can meet an angel that’s embodied good. You can meet a dwarf that’s the embodiment of industriousness and hardiness.”

Early D&D included rules that made characters fit the archetype of their chosen race. The game restricted non-humans to particular classes and blocked their advancement to higher levels. Later, the game added racial ability score modifiers that encouraged characters to fit certain archetypes, so half-orcs gained strength and constitution, but lacked charisma. Originally, half-orcs only excelled as assassins.

Gary Gygax favored the sort of human-dominated fantasy that appeared in the fiction that inspired him. To Gary, non-human level limits explained why humans dominated D&D worlds despite the extraordinary talents and longevity of elves and dwarves. Gary wrote, “If demi-humans, already given some advantages, were as able as humans, the world would be dominated by them, and there goes the whole of having a relatively familiar world setting in regard to what cultures and societies one will find in control. So, a demi-human is unlimited in thief level only, as that this a class not destined to control the fate of major groups or states.

“Why are humans more able to rise to higher levels than demi-humans?“ Gygax wrote in a internet discussion. ”Because the gods say so, and don’t like pointy eared types with curly-toed shoes, squat miners with big beards, hairy-footed midgets, etc.” Gygax intended the comment as harmless fun at the expense of make-believe creatures, and in 2005 most readers read it that way. But now the comment reads in a way Gygax surely didn’t consider. In our history, people have justified inflicting countless horrors on other humans by claiming that God disapproved of some group. Talking about even fictional half-humans like this raises uncomfortable echoes.

Arduin adventure party

This adventuring party was pictured in Arduin Grimoire III

Even in D&D’s first years, not every player shared Gygax’s taste for games where most characters resembled the human heroes of Poul Anderson, Fritz Leiber, and Robert E. Howard. When J. Eric Holmes wrote the 1977 D&D Basic Set, his draft explained, “An expedition might include, in addition to the seven basic classes, an African witch doctor/magic-user, a centaur, an Amerindian medicine man/cleric, a lawful werebear, a Japanese samurai fighting man and a half-human, half-serpent naga”. The published book cut most of those options, leaving only “a centaur, a lawful werebear, and a Japanese samurai fighting man.” In Dragon 53, Holmes wrote about the set’s limited character options. “I am personally sorry to see the range of possibilities so restricted. The original rules (the three little brown books) specifically stated that a player could be a dragon if he wanted to be. I enjoyed having dragons, centaurs, samurai and witch doctors in the game. My own most successful player character was a Dreenoi, an insectoid creature borrowed from McEwan’s Starguard.” Meanwhile, Arduin Grimoire III (1978), an unofficial supplement to D&D, included pictures of an exotic adventuring parties that scarcely resembled a typical group. Author Dave Hargrave wrote, “The fact is that most players want individuality in their characters.”

When Wizards of the Coast purchased TSR, new CEO Peter Adkison steered D&D to more flexible character options. “My biggest beef with the older rules were the consistent limitations on what characters could become,” Adkison wrote. “Why couldn’t dwarves be clerics. Why could wizards of some classes only advance to some pre-determined level limit? Why couldn’t intelligent monster races like orcs and ogres pick up character classes? In my mind these restrictions had no place in a rules set but should be restrictions established (if at all) at the campaign-setting level.” The 2000 edition scrapped non-human level limits and rules that limited each race to particular classes.

Still, ability score modifiers remained in the game, and they stayed in the 2014 Player’s Handbook. Lead rules designer Jeremy Crawford said the modifiers “are specifically there just to reinforce the traditional D&D archetypes for dwarf adventurers, elf adventurers, halfling adventurers, and so on.” The modifiers meant a player who wanted to play something like a dwarf wizard had to settle for a less efficient character.

Experienced players rarely settled, so the ability score modifiers felt like as much of a restriction as the old rule that limited dwarves to playing fighting men. As for new players, the ability score modifiers became a trap. A player who fancied playing a halfling barbarian would later learn their character suffered a permanent limitation. Restrictions that force players to make interesting choices can make better games. Much of the fun of character building comes from choosing among enticing options, but for players set on a class, the choice between one race and a plainly weaker option adds nothing. “All games are about making choices and making meaningful choices,” Crawford said. “But we want the choices to be between things that are all fun and interesting. Like a great example is making the choice between the classes where it’s an open-ended field and you get to just choose the one that sing to you. What we don’t want is choice where just hiding inside it is some kind of trap. And that’s what the traditional ability score bonuses often feel like to people.”

Aside from adding a trap—and not the fun kind—ability score modifiers raise troubling reminders of how real ethnic groups can suffer from racist stereotypes that paint people as lacking certain aptitudes. D&D’s unfortunate use of the word “race” makes those reminders far more powerful. When D&D creators Dave Arneson and Gary Gygax adopted the word race for the playable species in D&D, they used the term in the same sense as the human race. More commonly, “race” refers to human groups who share superficial traits common to their ancestry, and that use recalls a long history of people using ancestry and appearance to justify mistreating and exploiting people.

Our characters in roleplaying games represent us in the game’s imaginary world. They might be just-pretend types like dragons, vampires, and robots—sometimes pronounced warforged—but we identify with them because our game world stand-ins think and feel mostly like us as people. Our characters represent people, and if they’re people, we can imagine them enjoying the same versatility and potential as real-world people.

To “pave the way for truly unique characters,” Tasha’s Cauldron of Everything (2020) stopped linking ability modifiers to race. Now, players could create a dwarf wizard with a green thumb without settling for a less efficient build than a similar character who happened to be an elf. “It is not our assumption and never has been in fifth edition that those bonuses in the players racial traits are true of every member of the race,” said Crawford. “As the game continues to evolve, and also as the different types of character people make proliferates and becomes wonderfully diverse as people create types of characters that many of us would never imagine. It’s time for a bit more of those old assumption to, if not pass away, to be something that a person can set aside if it’s not of interest for them and their character. It’s with that in mind that we created this system to be true to our philosophy. We sometimes talk about when we give DMing advice to whenever possible say yes. This is a system about saying yes to players. That yes, you can play the dwarf you want to play. You can play the elf you want to play. You can play the halfling you want to play.” In D&D, player characters stopped serving as metaphors.

The Arduin Grimoire: The “Coolest RPG Book Ever,” also the Book Gygax Mocked As Costing Readers 1 Int and 2 Wis

5 Replies

When creators dream up imaginary worlds, they can go in two directions. They can build their world from a curated set of ideas, and then fit these pieces together into a logical and consistent manner. In a fantasy gaming, these creators worry about how magic affects society and culture, and then wind up with worlds like Glorantha or Tekumel.

The Arduin TrilogyDave Hargrave’s campaign world of Arduin was not built; it was piled. To create Arduin, Hargrave took every fantastic element he dreamed up or fancied and piled them into one work of love. If Tekumal is a museum, with treasures for contemplation, then Arduin is a dragon’s horde, with everything shiny heaped to the walls.

Dave Hargrave pictured in his adventure collection, “Vaults of the Weaver”

Inspired by the Greyhawk and Blackmoor supplements, Hargrave printed his house rules, lore, and advice in a little, brown book named after his world, The Arduin Grimoire. In 1977, his unofficial supplement to Dungeons & Dragons debuted at California’s DunDraCon II convention. The book’s success led to the sequels Welcome to Skull Tower (1978) and The Runes of Doom (1978).

In a look back on the trilogy, Ryk Spoor called Arduin “one of the most absolutely concentrated essences of the fun of roleplaying games ever made.” Jonathan Tweet, the lead designer of third-edition D&D, called Arduin the “the coolest RPG book ever.”

Sometime in 1979, I found the series on the shelves of The Hobby Chest in Skokie, Illinois. The pages teemed with fresh ideas. The author suggested strange pairings of science and fantasy. He tore up the D&D rules and offered wild changes. It all seemed a little subversive. I became enchanted. I haven’t found a game book that proved as enjoyable to read. At first I thumbed through the books at random, discovering gems, then I turned to page one and read. (Due to the books’ random organization, both reading orders felt the same.) As Hargrave wandered through Arduin lore and free-associated roleplaying game wisdom, I learned three lessons.

Arduin advertisement from The Dragon issue 6, April 1977

Arduin advertisement from The Dragon issue 6, April 1977

Fantasy gives freedom to imagination.

As D&D’s audience exploded, in the days before Appendix N, most new players’ experience with fantasy started with Tolkien and ended with a few imitators. The sort of science-fantasy found in say, Jack Vance, seemed wrong. To us, Hargrave preached bigger imaginary playgrounds. “The very essence of fantasy gaming is its total lack of limitation on the scope of play, both in its content and in its appeal to people of all ages, races, occupations or whatever,” Hargrave wrote. “So don’t limit the game by excluding aliens or any other type of character or monster. If they don’t fit what you feel is what the game is all about, don’t just say ‘NO!,’ whittle on them a bit until they do fit.” (Vol. II, p.99)

Evidence of his creative abandon appears everywhere, from the “Multiversal Trading Company” to descriptions of the world’s 21 hells. For instance, the 17th plane of hell features blasted futuristic cities and space ports under a blue-black, moonless sky. Most vegetation is petrified. This hell’s most common inhabitant is The Black Wind, a fog of shifting shadows, lit by crackling, blue lighting bolts. The wind envelops and attacks psychically, taking over the body, and “forever making it alien.”

Hargrave welcomes a variety of character types. “Do not be a small player in a small world, embrace the whole Alternity and give different types a chance. I think you will find that the world your game is in will become a lot more fun if you do.” (Twenty years later, Dave Hargrave’s portmanteau “Alternity,” from alternate eternities, would become the name of a Wizards of the Coast RPG.)

‘Alliance’ from Arduin volume 3 and an advertisement in Dragon issue 30

Gary Gygax favored D&D parties where humans outnumbered the elves, dwarves, and other non-humans. Such groups matched the mostly human characters in the fantasy tales that inspired D&D.

Today’s D&D groups resemble the Star Wars cantina scene, where exotic species outnumber the odd human. Hargave encouraged similar, strange mixes. An advertisement for Arduin shows an adventuring party consisting of 4 unlikely companions:

  • a phraint, emotionless humanoid insects
  • a deodanth, undead elves from eons in the future, now lost in their past
  • a saurig, dinosaur-men from the distant past bred as killing machines
  • a masked, human samurai somehow somehow fighting alongside these gonzo creatures

Even now, this assembly seems stranger than the typical Adventurers League mix of, say, a tiefling, a tortle, someone with fire for hair, and a goblin named Percy.

The rules belong to players.

Jonathan Tweet noted the weakness of the Hargrave’s rules. “The Arduin system is usually unbalanced and often unbelievably complicated.” Still, some mechanics would fit a modern game. For example, he offers rules for touch attacks and a hit point system that resembles fourth edition’s. But the specific rules hardly mattered. Hargrave encourages players to own the rules and their games, to tinker, to playtest. On presenting his magic system, Hargrave advises readers to “take whatever I have that you like, use the old established fantasy gaming systems…and put together whatever you like in a magic system. Who knows, it may end up with such a good system that people will want to publish your fantasy world.” (Vol. I, p.30)

Detail makes game worlds come to life.

In an era when state-of-the-art setting design consisted of the Wilderness Survival map and some encounter tables, Hargrave opened a world with detail that rivaled any setting that came later. According to Ryk Spoor, “One of the strongest and most powerfully attractive parts of the Arduin series was that, within and around the game mechanics, the statistics for demons and items and spells, Dave Hargrave wove tales and hints of his campaign world, giving us a look at the life of a world that didn’t exist, but…perhaps… could, elsewhere.”

Arduin Now and Then

To gamers today, Arduin’s three lessons may seem obvious. New games seek freshness by colliding genres, so cowboys meet the undead, magic meets cyberpunk, and so on. Endless setting books lend detail to world building. When the fifth-edition designers explain their hesitancy to tweak the published rules, they say the rules belong to the players now. Arduin’s phraints seem to have become Dark Sun’s Thri-Kreen.

True, but in 1978, Arduin’s lessons demolished barriers that would never stand again.

Gary Gygax versus The Arduin Grimoire

In the 70s, Gary Gygax resented products that rode his and D&D’s coattails. The man had 6 children to feed! Arduin aped the little, brown books and tore down D&D’s rules, so the grimoires earned particular ire. In the Dungeon Master’s Guide (1979), Gary added the Vacuous Grimoire (p.155) as a dig at The Arduin Grimoire. Read it and lose 1 intelligence and 2 wisdom. In the pages of The Dragon, Gary attacked spell points, critical hits, and other rules that Hargrave offered as improvements.

TSR issued a cease and desist letter to Hargrave, who responded by blanking references to D&D. My printing splices in mentions of “other popular systems” and “old established fantasy gaming systems” where D&D was mentioned. Hargrave took to calling Arduin a completely different game, although it skipped essential rules that readers must find elsewhere (in D&D). Rules sections are labeled as changes or revisions to an unnamed game (still D&D).

Over the years, Hargrave created the missing rules needed to make a stand-alone game. But no one cared about his rules. Dave Hargrave never realized that his rules hardly mattered.

His feverish invention mattered. Arduin’s lessons mattered—and they changed role-playing.

Emperors Choice Games offers Arduin products for sale. The original trilogy now appears in a single volume.

XP Started as One of D&D’s Breakthrough Ideas. Now the Designers Don’t See the Point

18 Replies

When Dave Arneson ran a session of his Blackmoor dungeon for his Dungeons & Dragons co-creator, Gary Gygax’s biggest impression came from two innovations: (1) the dungeon expedition and (2) how characters improved with experience. In Playing at the World, author Jon Peterson describes reactions to the revolutionary game and shows new players and reviewers always touting the experience system. The steady reward of experience and levels forged an obsession for many players. I shared their fervor. In my junior high cafeteria, when I overheard some kids talking about a strange game where you could kill an orc, gain experience points, and get better at fighting, that single notion hooked me.

Early in Dave’s Blackmoor campaign, characters earned one experience point for each hit point of the monsters they killed. Players rarely saw the details. Blackmoor player Greg Svenson recalls, “We didn’t track our experience points as is done now. Dave simply told us when we had transitioned from one level to another.” Dave liked to shield players from his game’s numbers, partly for mystery, partly so he could change rules whenever he thought of something better.

His method for awarding experience certainly evolved. In a 1978 interview, Dave Arneson recalled awarding experience for characters who used skills associated with their class. “Each player increases in ability in a given area by engaging in an activity in that area. For a fighter this meant by killing opponents (normal types of monster), their ability to strike an opponent and avoid the latter’s blows was increased.”

While realistic, awarding experience points (XP) for different activities could have split groups to work their separate professions. If characters gained, say, spellcasting ability through endless hours of practice and study, players would face choosing between the fun of exploring dungeons and the drudgery of practice. “While it is more ‘realistic’ for clerics to study holy writings, pray, chant, practice self-discipline, etc. to gain experience, it would not make a playable game,” Gary wrote in the Advanced Dungeons & Dragons Dungeon Master’s Guide. “Magic users should be deciphering old scrolls, searching tomes, experimenting alchemically, and so forth, while thieves should spend their off-hours honing their skills, casing various buildings, watching potential victims, and carefully planning their next job. All very realistic, but conducive to boredom.”

In the pursuit of realism, Chivalry & Sorcery (1977) took study so seriously that the authors argue that magic users shouldn’t leave their labs at all. “What real ‘experience’ is to be had in a dark, damp dungeon?”

Gary saw dungeon expeditions as the second compelling innovation in Dave’s game. To succeed, the budding D&D game needed a way to lure every character into the dungeon, and then to reward their risk taking. Players loved seeing their characters gain power, so Gary motivated them to explore dungeons by stocking the underworld with treasure and by awarding characters experience for winning gold. The rogue might want wealth, and the paladin might want to smite monsters and to give to the church, but they could both win experience in the dungeon. Plus, the hunt for treasure resonated with players. Gary wrote, “If you, the real you, were an adventurer, what would motivate you more that the lure of riches?”

In addition to rewarding players for seeking fun, the XP-for-gold system offered another benefit: It created a simple way to award experience points for succeeding at non-combat challenges. As a new PC in the original game, potentially with 1 hit point, you had little chance of leveling through combat. Players joke that D&D is about killing things and taking their stuff, but in the original game, you were better off using your wits to take stuff. So long as your cunning led to gold, you got experience.

In the original game, characters earned much more experience for gold than for monster slaying. This rewarded players for engaging in exactly the dungeon exploration that made the game so much fun.

Once treasure led characters to the dungeon, Gary harnessed the system to tempt players to higher risks. In the early D&D game, players chose the amount of difficulty they wanted. Every level of the dungeon corresponded to a level of character, so the first level offered challenges suitable for first-level characters. Players could seek greater challenges—and greater rewards—as they went deeper.

When Gary created this aspect of the game, he needed to find ways to entice players deeper into the dungeon. If a cautious party could gain nearly as much loot on an easy dungeon level as on a deeper one, why go down? Gaining experience could become a safe—and dull—grind.

To draw characters to danger, Gary doubled the number of experience points needed to advance to each level, then matched the increase with similar increases in treasure. To rise in level at a tolerable rate, players needed to delve as far down as they dared.

Doubling both experience requirements and rewards offered a second benefit: Low-level characters could join a higher-level party and catch up quickly. This gave newer characters a boost and so made dead characters easier to replace. Also, the quicker advancement made monsters that drained characters of levels a bit less punishing.

In the decade after D&D’s introduction, a mania for creating realistic alternatives to D&D dominated the hobby. Every D&D player who ever wielded a foam sword cooked up a more realistic alternative to the D&D combat system.

The XP-for-gold system struck players everywhere as unrealistic. In the original Arduin Grimoire (1977), Dave Hargrave wrote that in his game, “[Experience] points are given for many reasons, but NOT for gold or other treasure. After all, it is the act of robbery, not the amount stolen, that gives the thief his experience.” In 1989, with the second edition, D&D would follow suit. The game would never award XP for gold again.

Without XP for gold, only killing monsters earned specific experience awards. Players liked to say the D&D only awarded XP for killing things, but that has never been true. While second edition stopped granting experience for gold, “a character can earn experience points for successfully completing an adventure or achieving a goal the DM has set.” But neither dungeon masters nor published adventures tended to follow the advice. Everyone, professionals included, tended to ignore improvised awards for experience in favor of the set numbers printed for each monster.

In the countless video games that adopted experience points, the mechanic proved its psychological draw. With every battlefield victory, gamers saw their score rise, leading to higher levels and greater power. This feedback of rewards kept gamers hooked. Electronic games brought advantages to an XP system. The computer freed players from working the math, and CPUs patiently served an endless stream of foes to characters who needed to grind their way to the next level. Still, grinding hardly sounds fun.

When second edition stopped awarding XP for gold, D&D superficially became more of a game of killing than ever. Except D&D matured anyway. Adventures started spinning stories deeper than that one time we killed a minotaur for gold. Originally, every character chased treasure; now, characters pursue adventure for justice or for honor or for countless other reasons, including treasure. And that worked so long as when players joined a game, they joined an unspoken pact to find reason for their character to accompany the other characters in following the plot.

In the newer, story-driven play style, some players stopped seeing the point of counting experience. Those players included current D&D head, Mike Mearls. “Tracking experience points and using them to award levels makes a lot of sense in open-ended games, where the players can go where they wish, tackle the specific challenges that appeal to them, and create their own goals as a campaign progresses. In this type of game, when the players decide to assault the lair of a blue dragon, their primary goal is most often the treasure and XP they’ll gain for defeating it,” Mike wrote.

“In a more story-driven campaign, however, that lair assault could have a more complex purpose. Defeating the dragon removes a threat to the realm and creates a key event in the campaign’s story arc. In this type of campaign, treasure and XP take second place in the characters’ goals, behind the dragon’s importance in the narrative. The reward lies in making the kingdom safe and completing the mission, not necessarily in collecting loot. Leveling up might feel like the best way to mark that campaign milestone, even if the XP earned by slaying the dragon doesn’t quite cover it.”

In addition to faulting XP for failing to serve narrative campaigns, D&D’s designers disliked the bookkeeping behind XP. Jonathan Tweet and Rob Heinsoo, the designers behind D&D’s 3rd and 4th editions wrote, “We think that XP systems are better left to computer games.

Even today, players still mischaracterize D&D as a game that only awards experience for slaying, mainly because every monster lists an XP number, while diplomatic and other challenges lack them.

Meanwhile, the game’s designers abandoned experience points in favor of milestones—leveling after story-driven accomplishments. Mearls wrote, “In the past, we’ve always defaulted to using experience point rewards for everything. However, for narrative-driven adventures like adventure paths, that approach can prove troublesome. Designers have to jam in the ‘correct’ number of combat encounters to make sure the PCs level up at the right pace. Adventure design thus becomes a process of matching up the right flow of XP to the correct tempo of the plot. Otherwise, if characters don’t level up at the expected rate, subsequent chapters in an adventure path become too difficult or too easy.”

When Mike complains about jamming in combat encounters, he reinforces the canard that the D&D rules only allow XP for killing monsters. Even a long-time designer never considers other XP awards. To be fair, story awards that help characters meet the level requirements of an adventure yield the same result as a DM announcing that everyone gains a level. Milestones lose the math, but they also lose the hook of small XP rewards for successes, seeing progress, and then earning levels.

The fifth-edition hardcover adventures lack enough monster-slaying XP to keep characters on pace with the adventure’s target levels. The designers could have added XP awards for other accomplishments, but they show little interest in supporting XP. This disinterest posed a problem for those of us who ran the hardcover adventures for the Adventurers League through the first 7 seasons. The league used experience then, and if the characters had only earned XP for slaying, they would never reach the levels targeted by the adventure. I may have violated the letter of League rules by awarding extra XP for overcoming non-combat challenges. I may be good, but I’m not completely lawful. Don’t tell the administrators.

Now, the League follows the D&D designers by dropping XP in favor of granting players the option to advance after an adventure, chapter, or other milestone.

Next: XP versus milestone advancement—at least we can all agree that awarding XP just for combat is terrible.

My Two Most Controversial Posts Prompt a Trip Into the Comment Section

9 Replies

The last two months included the two most discussed posts in the 7-year history of DM David, which calls for another trip into the comment section.

In Should a Dungeon Master Invite Players to Help Create the D&D World Beyond Their Characters? I considered the pros and cons of asking players to share a role that usually falls to the dungeon master.

Ilbranteloth suggested turning potentially dead characters into an invitation to let players imagine a different twist. “On potentially deadly hits against the PCs, they decide if they are killed, or something more dramatic (and often worse) happens.” Perhaps the character loses a leg and a bit of speed. Or perhaps the player trades death for some dramatic complication. Players focused on story understand that character arcs benefit from setbacks and might be eager to revive a dead character in exchange for a complication that makes a richer story.

After I created a Dungeons & Dragons Summoning Spell Reference, Teos “alphasream” Abadia shared some concerns raised by summoning.

“I’m not generally a fan of the summoning spells. They can be too strong (they can be like a fireball of damage every round, round after round, for the casting of one spell), they tie up the terrain impeding movement (especially by locking down melee fighters, preventing a dynamic combat), and they make combat a slog (in almost any combat, the monsters lack the damage to kill more than a couple of the summoned monsters).

“That last bit is what kills it for me. At the meta level, the monsters should ignore the summoned creatures, because killing them is basically impossible unless they’re a horde of low CR creatures and the monsters have area attacks. So, the easy move is to target the summoner and break their concentration, but that takes away from what the player who did the summoning wants. I haven’t found a happy medium.”

Summoning spells typically offer a choice between lots of weaker monsters and fewer, stronger monsters. When the designers set choices that made summoning crowds far more efficient, they made the spells more likely to turn fights into slogs.

When I play foes with an 8 or higher intelligence who see ongoing spell effects, I start making spellcasters preferred targets. After all, characters with an 8 Intelligence practice even more savvy tactics. When players think their DM unreasonably targets them with attacks, players can get salty, but when concentrating spellcasters become targets, their players know it’s coming.

Two readers added to The True Story of the Cthulhu and Elric Sections Removed from Deities & Demigods.

Alphastream wrote, “Some readers may not appreciate how, back then, books hung around for a long time. We had decades with the same books on the shelves. Not as old stock in a corner, but as an active part of what gamers would buy and use. As an example, check out this Shannon Appelcline article where he shares White Wolf Magazine’s list of top-selling RPGs for 1992. At number 9 is the 1981 Fiend Folio!

“Books like Deities & Demigods were a presence for decades, which helped keep this bit of controversy prominent across many years.”

The long sales life of books from this era also led to a 2nd edition that remained broadly compatible with AD&D. The designers wanted to make big improvements, but TSR management wanted books like that old Fiend Folio to continue generating sales.

Zenopus Archives wrote, “There’s a whole earlier chapter to this story. The Mythos write-up in Deities & Demigods is derivative of the original write-up ‘The Lovecraftian Mythos in Dungeons & Dragons’ by J. Eric Holmes and Rob Kuntz that was published in Dragon magazine 12 in 1978. The bulk of this article was written by Holmes, and the Deities & Demigods write-up has the same entries, except for one. To me, Deities & Demigods clearly used the original article as a starting point. Read more at Dr. Holmes and the Cthulhu Mythos.”

In Bring the Thrill of Finding Treasure Back to the Adventurers League, I wrote about how D&D traditionally motivates both characters and players to seek gold. This tempts players to take the risks that help make D&D fun.

Eric Bohm wrote, “Taking the treasure out of the game seriously undermines an important component of the D&D formula. The heroic component remains mostly intact. If your character is motivated to help people for the sake of helping them, with only an abstract unquantifiable reward, everything works. Other kinds of characters are less well supported, while truly mercenary character concepts become basically unplayable.

“What about the lovable scamp who is in it for the gold? Or the many redemptive arcs of those get roped in for the base rewards and are swept up in higher motivations? How can a malefactor tempt a hero away from the path of virtue?

“The only character who grabbed any money from the hoard in Waterdeep: Dragon Heist when I ran it was an NPC. The players weren’t tempted; therefore they did not feel like it was worth roleplaying their characters being at all tempted. It just wasn’t interesting for them to play into it. Let me state that again. Players with characters standing in a vault full of gold felt that it was pointless for them to even pick up a single bag of gold. Where is the fun in that?”

Obviously, players can still create characters motivated by greed, but without the incentive of gold, taking risks for treasure seems like a sucker’s bet.

At the start of season 8, I wondered with James Introcaso why the Adventurers League would introduce rules that blocked characters from keeping gold in the season that featured Waterdeep: Dragon Heist. The adventure hooks characters with a chance to win a fortune in gold. James speculated that perhaps the potential windfall triggered the need for the rules change.

In How Years of Trying to Fix Obnoxious People Shrank D&D’s Appeal, I talked about how relying on a DM’s judgement rather than on extensive rules may have helped fifth edition’s popularity.

Alphastream agreed but saw areas where fourth edition succeeded in making D&D easier to run. For instance, fourth edition’s in-store play program D&D Encounters drew tons of players. “DMs loved being able to run an hour of play with 1-2 pages of very simple (and yet engaging) adventure text. Spells turned into far simpler powers meant DMs could jump in with less experience. True story: Despite playing and DMing D&D for 17 years, when 3E came out, I waited 9 months before DMing my first organized play game because I felt I didn’t know 3E spells well enough to run a game. We’ve taken a step backwards here, in that many DMs again feel they can’t DM (especially at high levels) because of the complexity of spells.

“So, I think there is a balance to be struck between these design goals of keeping the game engaging and keeping it easy to learn and simple.”

“I would also say that while 3E really built up the game and added a lot, 4E in many ways was working to fix problems—the length of an adventuring day, the need for someone to ‘have’ to play the cleric, how many magic items a character had, and even how much experience a DM needed to feel confident. It really took the laundry list of issues, including ‘bad DMs’ and tried to fix them. The legacy of those fixes is excellent. We can see many of those improvements carried on into 5E.”

In How D&D Shed the Troubling Implications of Half -Orcs, I wrote about how D&D struggled to erase the implication that half orcs came from rape. The entry became this blog’s most read and discussed post until another post topped it.

Wil cifer argued that the original implications of half orcs fit history. “Rape was a commonplace occurrence during war in medieval times. Why would a barbaric race even in a fantasy setting be kinder and gentler? Rewriting the tone of a historical time the game is based on is stupid.”

But D&D is a game that gleefully tosses aside historical accuracy and realism in favor of fun. The game features magic and dragons. To unravel any D&D world, just pull any of countless threads and check it for historical accuracy or check how it stands in the face of magic.

Other readers argued that making half orcs the product of sexual violence turns orcs into stronger villains. Andrew wrote, “I have been playing D&D since 1981, and I have no problem with half-orcs being the result of an orc raping a human female. Orcs are monsters, created by an evil deity, Gruumsh. Taking the monster out of the monster has very little appeal to me. Can and should there be points of moral ambiguity in a D&D game? Without doubt. There should be. But monsters do monstrous things, including rape.”

To players like Andrew, crushing evil and righting wrongs feels more satisfying when the campaign shows evil and the suffering it creates. Purely evil creatures make uncomplicated foes that justify killing.

David Streever wrote, “D&D is a fantasy game that is sold to everyone from small children to adults; you can feature as much rape as you like in your version, but I’m glad it’s not in the core books, and I’ll stay away from your table.”

In your D&D game, if all the players welcome a darker tone, you can explore any origin you like for half orcs. But for a broader audience, the game benefits when it avoids saddling every half orc with a vile background.

In response to Running Group Roleplaying Scenes—How Permission From an RPG Legend Made Me Stop Talking to Myself, simontnm gave a suggestion. “If I have multiple NPCs talking I tend to use minis, and put my finger on the mini of the NPC actually talking.

“‘Don’t have NPCs talk to each other’ is good advice, but it’s occasionally necessary to deliver an NPC to NPC one liner. Keep it short and sweet.”

The History of Traps In Dungeons & Dragons prompted Ty to point out the difference between good, real traps and quality traps in D&D. “From a game play standpoint, traps are just a terrible idea all around. Conceptually, in order for a trap to be a ‘good’ trap, it needs to be massively unfair. It needs to kill outright or seriously maim. One minute you’re alive, and then boom, you’re dead. No saving throws, no noticing something off at the last minute, no jumping out of the way.”

Ken W replied, “You need to take the edge off your realism. A trap shouldn’t be ‘instantly lethal’ in game terms any more than a strike with a sword or great axe. In real terms, if you get hit by a swinging claymore, you are likely suffering a severe wound. But the abstraction of D&D combat and hit points means that each hit represents a depletion of stamina, not a mortal wound. Only when you reach 0 hit points does it really represent that fountaining arterial spray we would otherwise expect.

“Traps operate in the same space as combat weapons in this regard. The only difference between a trap and an enemy combatant that gets a turn while the PC is surprised is…well—nothing. Except the trap essentially ‘dies’ after its turn is over.”

Good traps in the real world make lousy traps in D&D. The best traps in D&D are in places where everyone expects a trap or that show obvious signs of their presence.

Alphastream wrote, “A trap can be a lot of fun when found, if it requires engagement to disarm. As a DM or author, I try to think through the point of the trap—not just for whatever creatures put it there—but for the game experience. The trap can be hard to find and that’s fun, or it can be easy to find and be fun as well. Think of ‘only the penitent man shall pass’ in Indiana Jones and the Last Crusade. That’s fun because you know it is there and need to figure out a way past it. Similarly, traps can be found and that can be the beginning of the engagement.”

Beoric wrote, “Perfectly good traps can be suspected because the nature of the trap is not entirely concealable. Raiders of the Lost Ark-style traps can be suspected because the tiles on the floor have no grout because they are pressure plates, or there are holes in the wall from which darts shoot.

“The trap may also be old, and detectable by signs of wear, like a layer of powdered stone on the floor or vertical gouges on the wall for a falling block trap, or soot on the walls or floor with a fire trap, or spent missiles on the floor with a dart or arrow trap.

“Also consider that some traps can be very well concealed if they are not being looked for, but still be detectable if actively searched for. A standard old-school pit trap was pretty much undetectable visually and could only be detected by tapping it.”

“None of those are actually bad traps. They just have limitations because of their nature.”

“There is a great discussion of this at the Hack and Slash Trick and Trap Index.”

Alphastream expanded on how traps worked in play across editions.

“In fifth edition, it’s still not entirely clear nor standard whether Investigation or Perception is most commonly used for finding a trap. I have my thoughts, which I think are right, but I see it run many different ways. In general, I think that if a trap is one that could be seen with the naked eye, then Perception would work. For example, a pressure plate that has slightly discolored stone, or which is slightly sunken. Otherwise, and in my game this is most of the time, the trap is not obvious and needs Investigation to be found. A well-crafted pressure plate is like any other stone. The only way to find it is to tap at it or otherwise determine what it is, which uses Investigation.”

“Fourth edition’s concept of ‘trap as monster’ failed due to the underlying math, which assumed a check per round and 4 checks to disable the trap, which was supposed to equate how monsters were envisioned as taking 4 rounds to defeat. The problem is that this cold math doesn’t understand how that 4 round concept wasn’t very accurate—players focused fire on important targets and might take them down in 1 round, while ignoring others.”

Players tended to focus fire on traps and break them more quickly than a rogue could disable them. Or players ignored traps in favor of the monsters, and then stepped around the traps.

“I like to think 4E’s trap concept is still really cool, but it takes clever authoring to communicate to the players how to engage with it. It is awesome if the cleric immediately realizes that this trap is empowered by a rival deity and they can shut it down and greatly help the party by doing so. That feels really heroic. It’s awesome if the rogue can tell the party that interacting with the trap for two rounds will move the rays of lightning to the area where the enemy archers are standing. These are great cinematic concepts if you set them up right.

“I tried my own hand at it with Dungeon of Doom. Nate and I designed a large variety of 5E traps in that adventure, and they provide a diversity of experiences. (You can get the adventure free and also see people play through them, all at https://dwarvenforge.com/descent/.) Thank you for putting up with the shameless plug, but it’s hopefully useful for people given this article.”

For Ability Checks—From the Worst Mechanic in Role-Playing Game History to a Foundation Of D&D, Daniel Boggs contributed fascinating D&D history that I didn’t know.

“It is a quirky history, given that a primary reason ability scores were created in the first place was as a means to make ability checks—to put it in contemporary parlance. The D&D ability scores and saving throws arise as a distillation of the concept of personality traits and character skills created by Dave Arneson for Blackmoor. In pre-D&D Blackmoor, players would roll against a trait, Strength for example, or Looks, or Throwing, to see if they were successful at the attempt. When D&D came along, Arneson & co. continued to use ability checks in their games. You can see an example of a Dexterity check in Arneson’s First Fantasy Campaign (1977) where a character must save versus Dexterity to remove their armor in time to avoid drowning in Blackmoor Bay. And of course ability checks are also very prominent in Arneson and Richard Sniders’ Adventures in Fantasy game (1978). In writing D&D, Gary Gygax failed to mention this purpose of the ability scores as he apparently preferred to create an arbitrary percent chance and have the players roll percentiles instead. So, you did have some early players who figured it out on their own or who learned it in some way from Arneson, most D&D players didn’t grok the intention behind the scores and thus you got that rather odd system proposed by Ives in Dragon #1. You can see some original Blackmoor characters here.”

My post 6 Popular Things in D&D That I Fail to Appreciate sparked such a furor that I posted a follow up. Many commenters took the challenge of changing my mind.

I’ve already recanted my dislike for game worlds that unnecessarily make adventuring a common profession.

Alphastream argues that monsters that bounce from table to table at multi-table events can work, but he sees room for innovation. “I’ve written these, though they aren’t my favorite device for the reasons you mentioned. I think they work best when they are in small pods. The blue dragon in Confrontation at Candlekeep works well because it makes sense (you have 4-6 towers and parties at each tower, the dragon flying in between), it is announced dramatically (so everyone gets the concept from the start), it is central to the action (no one is forgetting about the dragon), and it lets players interact with it once it leaves their table (they can jump on it or fire at it, at the risk of failing at their table). With the second Open I tried to create a different experience, one that still made sense and which provided a combination of combat, skill, and risk-reward. I would tweak it further if given the chance. All of that is to say that I think these can be done well. I think DM David is exactly the kind of person who could come up with a cool version and submit it to an Epic author.”

I’ve grown to accept that adventures with carnival games work well as an introduction to the game. Alphastream touts another benefit. “I think carnival games can offer a lot of activity in a short time and offer something to every player. Very few things can do that.”

As for the way that using miniatures for the wrong monster sometimes confuses me, Creeper Jr wrote, “I don’t need minis to match exactly, but I find it incredibly helpful if there is some sort of rhyme and reason to it. My portable mini kit includes: 4 goblins, 4 guards, 4 archers, 2 mages, 2 knights/fighters, 2 rogues, 2 large green slaad, 2 giant spiders. Each mini has a color-coded base accent. This doesn’t take up too much room, is relatively cheap to put together, and allows us to quickly identify enemies with sort-of-thematic minis.”

Alphastream supports budding mini collectors eager to put minis on the table. “Sometimes a DM wants to buy a box of minis or two and try to use that purchase for their efforts. I get that. I still think it beats Starburst, but maybe that’s because I don’t super love Starburst. If the monsters are Belgian truffles, or Ferrero Rocher, sign me up! Here again, we can imagine we are witnessing the beautiful creation of a nascent miniature collector. They will go from this table to assemble an army of awesome minis on a bed of Dwarven Forge. It’s like seeing the future unfold before us!”

Josh rose to defend the dragon-slayer pose on page 7 of the second-edition Player’s Handbook. “I’m one of the ones who love the picture. The adventurers seem like real people, each different and interesting in his own way. The mage isn’t old. Nobody’s half dressed. The dragon’s of a size that would pose a threat to normal people and level 1’s. It’s a good level 1 accomplishment. And as for the pose, I assume there are a lot of unlisted utility spells, including one that takes the image in a caster’s mind and transfers it to paper. It’s a level 2 spell. Colored prints are level 4.”

Commenters replying to How Well Do You Understand Invisibility in Dungeons & Dragons? considered a couple of odd corners of the rules for invisibility.

Dave Barton summarized one aspect. “In essence, two foes who can’t see each other have an equal chance of hitting as if they could see each other. Think about that for a minute.”

This rule especially defies common sense because it grants ranged attackers just as good a chance of hitting when they can’t see their target. Sometimes D&D trades plausibility for simplicity.

Aside from the ability to hide anywhere, invisible creatures don’t get advantage to hide or any other increase to their chance of success.

Pewels asks “How would you handle light sources on a PC going invisible?”

Saphhire Crook answered, “The issue of invisible light sources crosses into that dangerous territory of ‘invisible eyeballs’, which is where invisible people cannot see because their eyes cannot receive light since it passes through them.”

“In 3.5, light sources continue to exist, but their origin becomes invisible, implying that the target simply reflects no visible light (or all light hitting or reflecting off them is magically duplicated and filtered).”

Every so often, someone leaves a comment that delights me. My post on Dave Hargrave, Once subversive, the Arduin Grimoire’s influence reaches today’s games, inspired such a comment from Old School, New.

“As a former associate of Hargrave, I’ve been around awhile and have seen innumerable articles written on the worlds of Arduin and its foothills. Many are bad, many are way too ‘fannish,’ and a lot of them are simply misinformed and/or myopically aligned with other gaming systems, to the point of zero objectivity.

“This article, however, rates as the finest piece on the subject of Arduin/DH, ever. Nothing else comes close. Incredibly well written, fair, meticulous, and factual.

“And you actually dug-up a pic from Different Worlds. Haha! Among other things.

“Yes, Arduin wasn’t perfect. Not hardly. But it was grand, visionary, insane, stupid, ham-handed, and utterly magnificent. Kinda like its creator, right?

“Anyway, massive cheers for a spectacular blog entry. I should think it’s the all-time definitive description of Arduin and its master—warts and all.

“Seriously, Mr. Hartlage, you’ve created something beautiful here.”

Thanks! I feed proud to garner such kind words.

Dungeons & Dragons and the Dream of the Grand Campaign

18 Replies

The original Advanced Dungeons & Dragons Dungeon Master’s Guide included an instruction that seemed pointless to most readers, even though Gary Gygax shouted it in caps. In AD&D, he explained, “YOU CAN NOT HAVE A MEANINGFUL CAMPAIGN IF STRICT TIME RECORDS ARE NOT KEPT.” DMs needed to work with players to record every character’s use of campaign time.

Few dungeon masters bothered with such bookkeeping. The 2nd edition explains the reason. “Time passed in previous adventures has little of no effect on the current session. Next game session, the DM announces, ‘A week or so has passed since you last went out.’ An entire campaign can be played this way.”

When I first read Gygax’s declaration, no one I knew tracked campaign time. Still, thanks to the The Arduin Grimoire, I aspired run a campaign that marked time. In a trilogy of little, brown books, Dave Hargrave explored his Arduin campaign’s lore and house rules. See Once subversive, the Arduin Grimoire’s influence reaches today’s games. For me, the most inspiring passage revealed the scope Dave’s game.

“The Arduinian Campaign has been running about as long as D&D and related role-playing games have existed. Game time has been more than 11 years (of 453 days each). Over 480 player characters have been permanently killed in that time, and many more have had to retire due to wounds or afflictions acquired in campaigning. On the other hand, two characters have become Dukes of the realm and half a dozen are Barons (three landed and collecting taxes. raising troops, etc.). One even managed to woo the youngest daughter of the king and just this ‘end year’ all Arduin celebrated their nuptials. So, even though it is a hard and dangerous world, the rewards are usually more than a bold player can ever expect.”

Unlike Arduin, my campaign featured a mere series of adventures for a single party. To most gamers now, that’s a campaign. But Hargrave, Gygax, and D&D co-creator Dave Arneson ran grand campaigns on a scale I dreamed to achieve. Someday, maybe.

When Arneson and Gygax made the original game, they ran campaigns for player communities who floated in and out of frequent game sessions. The original rules suggested one DM and “from four to fifty players” in a single, fantastical campaign. “The referee to player ratio should be about 1:20.” Gygax’s Greyhawk campaign hosted weekend sessions for up to 20 players, but most parties included fewer players. During the week, Gygax let players drop in for spontaneous sessions. Often, he ran D&D for a single player.

The megadungeons under Castle Greyhawk and Blackmoor helped make those campaigns work. Every game session mounted a new expedition into the dungeon, so the particular cast of characters never mattered. See When megadungeons ruled Dungeons & Dragons.

Once character’s left the dungeon, they needed to heal at a rate of just one hit point per day. “The stricture of time is what makes recovery of hit points meaningful.” Recovery aside, characters involved themselves in projects like castle building, magical studies, and training. “All of these demands upon game time will force choices upon player characters, and likewise number their days of game life.” Campaign strategy involved spending your characters’ time.

Much of this resembles modern D&D’s downtime system, but with the time spent matched to days on the campaign calendar. A character could not leave for a month of training, and also join tomorrow’s dungeon crawl. The campaign calendar forced regular players to keep a variety of characters. TSR’s first employee, Tim Kask, explains, “If my currently-favorite Fighting Man was laid up recuperating, but word had just come at the tavern that a new menace was in the offing with a promise of loot, I played my next-best-for-the-situation character.”

Time in these campaigns advanced in step with real-world time, keeping all the campaigners on the same schedule. “The recommend time period for individual adventure campaigns is roughly on a one to four basis, with one real week equal to one Game Month.”

Arneson and Gygax’s players mostly stuck to dungeon and wilderness adventures, but other early games imply a bigger canvas. The scope of what players achieved in Dave Hargrave’s Arduin campaign awed me.

In the ideal grand campaign, a bunch of individuals and groups don’t just play in parallel—their actions affect all the other players. Groups change over time. As parties form and reform, characters share information. Rumors from the local inn tell the news of the day. Some players develop rivalries. For instance, Ernie Gygax and Rob Kuntz raced to be the first to retrieve the Magic User’s Crown from under Castle Greyhawk. Sometimes players unite against common threats.

To describe Arduin, Hargrave seemed to channel Stan Lee. “The Arduinian multiverse has been rocked to its very cosmic core by revolutions, wars, assassinations, royal marriages, and the nearly complete and utter entropic destruction of the entirety of it all in one cataclysmic confrontation between utter evil and everyone/thing else that wanted to survive!”

Actually, Stan Lee may inspire more than just Hargrave’s bombast. Much of the secret sauce that made Marvel comics so successful was that events could ripple between comic book titles. In the corner of panels, little notes from the editor revealed the connections. In the early days, Lee would even coordinate each hero’s schedule between books. By those early standards, if Captain America traveled to Europe, he couldn’t spend the same month with Iron Man in New York.

The title “grand campaign” comes from the first page of Chivalry & Sorcery (1978), a game that aimed to beat D&D by supporting a grand style. Designers Ed Simbalist and Wilf Backhaus wrote that C&S emerged when “a degree of dissatisfaction emerged over the limited goals that were available to our [D&D] characters. The solution was to develop an all encompassing campaign game in which dungeons and wilderness adventures were just a small part of the action.”

In 1978, C&S boasted the “most complete rules ever published.” The game covered everything from mass combat, to tournaments, to courtly love—everything that fit in 128 pages of 6-point text.

In the grand campaigns suggested by C&S and Arduin, every player controlled a cadre of characters, including dungeon crawlers, but perhaps also nobles, traders, courtiers on so on. All gain space to follow their goals, and some will reach them. In response to all their actions, the campaign world changes and develops.

In my post on C&S, I had some fun at the game’s expense. Unlike D&D, where players join in parties to adventure, C&S and the grand campaign offers fewer reasons to gather at a table and play together. This limits the style’s practical appeal.

But the biggest limit to the grand campaign comes from the DM’s time. DMs hosting grand campaigns must run a few group sessions a week, plus 1-on-1 sessions for the exploits of nobles, soldiers, and thieves. Then add time for preparation. Who needs sleep?

I do. I have regular games to play and another post to write. Still, the dream of the grand campaign feels as compelling as ever.

Once subversive, the Arduin Grimoire’s influence reaches today’s games

20 Replies

When creators dream up imaginary worlds, they can go in two directions. They can build their world from a curated set of ideas, and then fit these pieces together into a logical and consistent manner. In a fantasy gaming, these creators worry about how magic affects society and culture, and then wind up with worlds like Glorantha or Tekumel.

Dave Hargrave’s campaign world of Arduin was not built; it was piled. To create Arduin, Hargrave took every fantastic element he dreamed up or fancied and piled them into one work of love. If Tekumal is a museum, with treasures for contemplation, then Arduin is a dragon’s horde, with everything shiny heaped to the walls.

Dave Hargrave pictured in Different Worlds issue 31

Dave Hargrave pictured in Different Worlds issue 31

Inspired by the Greyhawk and Blackmoor supplements, Hargrave printed his house rules, lore, and advice in a little, brown book named after his world, The Arduin Grimoire. In 1977, his unofficial supplement to Dungeons & Dragons debuted at California’s DunDraCon II convention. The book’s success led to the sequels Welcome to Skull Tower (1978) and The Runes of Doom (1978).

In a look back on the trilogy, Ryk Spoor called Arduin “one of the most absolutely concentrated essences of the fun of roleplaying games ever made.” Jonathan Tweet, the lead designer of third-edition D&D, called Arduin the “the coolest RPG book ever.”

The Arduin TrilogySometime in 1979, I found the series on the shelves of The Hobby Chest in Skokie, Illinois. The pages teemed with fresh ideas. The author suggested strange pairings of science and fantasy. He tore up the D&D rules and offered wild changes. It all seemed a little subversive. I became enchanted. I haven’t found a game book that proved as enjoyable to read. At first I thumbed through the books at random, discovering gems, then I turned to page one and read. (Due to the books’ random organization, both reading orders felt the same.) As Hargrave wandered through Arduin lore and free-associated RPG wisdom, I learned three lessons.

Fantasy gives freedom to imagination.

Arduin advertisement from The Dragon issue 6, April 1977

Arduin advertisement from The Dragon issue 6, April 1977

As D&D’s audience exploded, in the days before Appendix N, most new players’ experience with fantasy started with Tolkien and ended with a few imitators. The sort of science-fantasy found in say, Jack Vance, seemed wrong. To us, Hargrave preached bigger imaginary playgrounds. “The very essence of fantasy gaming is its total lack of limitation on the scope of play, both in its content and in its appeal to people of all ages, races, occupations or whatever,” Hargrave wrote. “So don’t limit the game by excluding aliens or any other type of character or monster. If they don’t fit what you feel is what the game is all about, don’t just say ‘NO!,’ whittle on them a bit until they do fit.” (Vol. II, p.99)

Evidence of his creative abandon appears everywhere, from the “Multiversal Trading Company” to descriptions of the world’s 21 hells. For instance, the 17th plane of hell features blasted futuristic cities and space ports under a blue-black, moonless sky. Most vegetation is petrified. This hell’s most common inhabitant is The Black Wind, a fog of shifting shadows, lit by crackling, blue lighting bolts. The wind envelops and attacks psychically, taking over the body, and “forever making it alien.”

Hargrave welcomes a variety of character types. “Do not be a small player in a small world, embrace the whole Alternity and give different types a chance. I think you will find that the world your game is in will become a lot more fun if you do.” (Twenty years later, Dave Hargrave’s portmanteau “Alternity,” from alternate eternities, would become the name of a Wizards of the Coast RPG.)

The rules belong to players.

Jonathan Tweet noted the weakness of the Hargrave’s rules. “The Arduin system is usually unbalanced and often unbelievably complicated.” Still, some mechanics would fit a modern game. For example, he offers rules for touch attacks and a hit point system that resembles fourth edition’s. But the specific rules hardly mattered. Hargrave encourages players to own the rules and their games, to tinker, to playtest. On presenting his magic system, Hargrave advises readers to “take whatever I have that you like, use the old established fantasy gaming systems…and put together whatever you like in a magic system. Who knows, it may end up with such a good system that people will want to publish your fantasy world.” (Vol. I, p.30)

Detail makes game worlds come to life.

In an era when state-of-the-art setting design consisted of the Wilderness Survival map and some encounter tables, Hargrave opened a world with detail that rivaled any setting that came later. According to Ryk Spoor, “One of the strongest and most powerfully attractive parts of the Arduin series was that, within and around the game mechanics, the statistics for demons and items and spells, Dave Hargrave wove tales and hints of his campaign world, giving us a look at the life of a world that didn’t exist, but … perhaps… could, elsewhere.”

The impact of Arduin

To gamers today, Arduin’s three lessons seem banal. New games seek freshness by colliding genres, so cowboys meet the undead, magic meets cyberpunk, and so on. Endless setting books lend detail to world building. When the fifth-edition designers explain their hesitancy to tweak the published rules, they say the rules belong to the players now. Arduin’s Phraints seem to have become Dark Sun’s Thri-Kreen.

After reading the books in 2008, James Maliszewski mused that most of Arduin “generated a resounding ‘meh’ for me,” mostly because its better ideas “were readily accepted and incorporated into gaming.” He concludes, “It’s nearly impossible to read the Arduin Trilogy now and see any of its ideas as original as they once were.” True, but in 1978, Arduin’s lessons demolished barriers that would never stand again.

Gary Gygax versus The Arduin Grimoire

In the 70s, Gary Gygax resented products that rode his and D&D’s coattails. The man had 6 children to feed! Arduin aped the little, brown books and tore down D&D’s rules, so the grimoires earned particular ire. In the Dungeon Master’s Guide (1979), Gary added the Vacuous Grimoire (p.155) as a dig at The Arduin Grimoire. Read it and lose 1 intelligence and 2 wisdom. In the pages of The Dragon, Gary attacked spell points, critical hits, and other rules that Hargrave offered as improvements.

TSR issued a cease and desist letter to Hargrave, who responded by blanking references to D&D. My printing splices in mentions of “other popular systems” and “old established fantasy gaming systems” where D&D was mentioned. Hargrave took to calling Arduin a completely different game, although it skipped essential rules that readers must find elsewhere (in D&D). Rules sections are labeled as changes or revisions to an unnamed game (still D&D).

Over the years, Hargrave created the missing rules needed to make a stand-alone game. But no one cared about his rules. Dave Hargrave never realized that his rules hardly mattered.

His feverish invention mattered. Arduin’s lessons mattered—and they changed role-playing.

Related: For an affectionate and funny tour of the first Arduin Grimoire, read “Arduin Grimoire cover to cover” from the first post at the bottom of the page.

Emperors Choice Games offers Arduin products for sale. The original trilogy now appears in a single volume, although the price seems high for anyone but a passionate student of RPG history.