Friday, March 23, 2018

Design Origins -- Part 2: Class Dice

Continuing on from where "Part 1" left off, today I'm going to talk about something I consider to be the defining characteristic of The Next Project: Class Dice.


The Previous Project
As I touched on last time, to a greater or lesser extent, TNP evolved out of the previous RPG that I had written. That system was defined by using only the d6 and d10, for all of its mechanics. In discussion and in playtesting, people found it unintuitive; it essentially functioned as a d20-style system, but with 1d6+1d10 as your "action" die. The main "selling point" of this particular dice gimmick simply wasn't compelling enough.

The game also suffered from being more of a "point-buy" style of character assembly, with only the thinnest of fantasy trappings applied. Players sort of had to take the jumble of mechanics and create their own "skin" for what sort of character their "class" was supposed to be. The game just failed to click with people, on an emotional or psychological level.


Paradigm Shift
So for my next project, I knew that I wanted to do something more recognizable -- something class-based. I had also basically settled on using the d20 for the "action" die; whenever you make an attack or a skill check, just roll the d20. You may need to modify it, after making the roll (i.e. by adding static modifiers or additional dice to the roll, or rerolling using Advantage/Disadvantage) but I knew I wanted something straightforward, and easier to tinker with than 1d6+1d10 had been.

However, I still wanted to retain some of the sense of "these two dice are all you need" that the previous game had brought to the table. Somewhere in an internet discussion about purchasing extra dice, it was pointed out that buying the sets of polyhedral dice (with 1d4, 1d6, 1d8, the "percentile" dice, and 1d12) was sort of a waste, since the d4 and d12 are so rarely used, particularly prior to 5th Edition coming out (which was when this discussion took place.)

That was where my mind sort of made a connection.

Instead of having the entire system function around the same two dice, use the d20 for the core mechanics, and the other die-shapes for the class mechanics.

This was something I really liked, from a tactile perspective: a table of players with just one or two sets of polyhedral dice could/should be able to play an entire party of characters. The idea of using dice rolls for bonuses was also something I liked from 5th Edition, as I wanted to remove any redundant or fiddly modifiers.


Credit where credit is due
Games such as Dungeon World and 13th Age sort of influenced this design ethos, with the former using damage dice as a class-based mechanic, and the latter having the combination of class and weapon "group" determine the damage die to use -- Rogues do better damage with daggers and shortswords, whereas Fighters get the most out of a greatsword or greataxe.

The idea, then, was to figure out which classes each of the dice would represent.


The Original Slate
As mentioned in the last post, from the outset, the first slate of 5 classes was probably going to include some combination of these classes:

  • Bard
  • Rogue
  • Barbarian
  • Ranger
  • Fighter
  • Monk
  • Paladin

In 4th Edition D&D, the numerical stats for classes are generally just reverse-engineered from the baselines established within the mathematical framework -- there's nothing really flavourful about them. So I went back to D&D 3.5 for inspiration.

If you think of a Wizard in 3.5, they have a d4 for their hit die, they generally will have a dagger or darts for their backup weapons (using d4 for damage) and one of their iconic spells is Magic Missile (also using d4 for damage.)

Similarly, when you think back to Rogues, one of their iconic abilities is the stacking of d6s for sneak attack damage -- conveniently, they also used d6 for their hit die, in 3.5! The same kind of thinking went into the Ranger (d8 hit die, d8 weapons such as longswords and longbows) as well as the Paladin (d10) and the Barbarian (d12)

I wanted this first slate to be as quintessential as possible, which is why I went with the 5 classes I did: Mage, Rogue, Ranger, Paladin, Barbarian.


Growing the Roster
A similar process was undertaken when designing additional classes, in order to expand to a 2nd and 3rd slate. In some cases d4 and d6 were used to mimic the d8 and d12, giving those dice some additional design space to muddle in:
 - Monk was designed as a "1d4" class, with the Archer as a "2d4" class (and later the two would start to blend together, in the Acrobat.)
 - As a class that would gain HP by shapeshifting, it made sense to slot Druid in at a d4, adding one extra die to its HP in "cat" form, and double that for "bear" form.
 - When the Fighter finally became a d6 class, it was so that it could simulate both dual wielding (shortswords,) archery (shortbow,) or two-handed weapons (greatsword,) to showcase it as the "weapon master" style of class. Doubling the d6 for their HP helps to slot them into the frontline "warrior" space.

Having a Warlock (with a d10 Eldritch Blast as its iconic ability) also helped push me towards mixing things up a bit, instead of having every d10 class be melee-focused. Conversely, the need for a "heavy mage" made d12 the obvious slot for the Spellbinder.


From there, most other classes just sort of fell into place, to flesh out the three slates:
  • Warlord as the "heavy martial" made for a nice d12 class, for the 2nd slate
  • a fireballing Sorcerer for d6 -- almost a no-brainer
  • Bard and Cleric at d8 (as the support classes) seemed the right fit for dabbling in both melee and ranged combat, without being the strongest at either.
  • Adventurer as a two-weapon, melee fighter made sense for d10
  • Guardian with a "2d6" melee subclass (Warden) and a "1d6" caster subclass (Shaman) seemed the right fit


-----

Next Post
Check back April 4th for the next update; hopefully by then, I will have at least a playtest-ready version of the rules document compiled, to share.

No comments:

Post a Comment