Status Report (2018)

Just a short post to round out the month of May:

In TNP, there are effectively only a handful of debilities/status effects, which can potentially be used as riders for monster attacks:

• Push
• Prone
• Weakened
• Immobilized
• Grappled
• Incapacitated

My early intention is to class these based on how debilitating they are; the more debilitating, the less the damage of the attack would be, and vice-versa. I would categorize them as such:

• High damage: push, prone, weaken
• Medium damage: immobilize, grapple
• Low/no damage: incapacitate

So, using the established mechanics for stepping-down monster damage, (Advantage, Trained, Untrained, and Disadvantage) this should give us a framework for building status effects onto monster attacks, by using their baseline damage expression and reducing it down depending on the effect being added.

Since the default assumption for Standard Monsters is that they deal "Untrained" damage, this limits how far their damage can be stepped down; by extension, this means they should not have access to the strongest debilities, and that these effects should be limited to stronger monsters, exclusively.

Now, that being said, this is essentially all "theorycraft" since it is hard to give a firm numerical value for these effects, which could be directly equated to an amount of damage. Nevertheless, I feel this gives a solid base from which to conduct playtesting, and then begin to troubleshoot the design.

...

Next post should be up on June 6th, so check back then!

Design Origins -- Part 3: The Monster Roll

May is Monster Month! (...I've decided, retroactively.)

Today I'm going to do an "origins" post, talking about where the Monster Roll came from; if you're not familiar with this mechanic, it's in the new Monster Workshop doc which was featured in the previous blog post.


Reverse Engineering
Back in about... some time prior to 2013, I briefly took over DM duties for the 4th Edition group I had been playing with. I kind of liked homebrewing monsters (once I had gotten into it) with the help of the guiding formula provided by Blog of Holding, known as "Monster Manual 3 on a Business Card."

The core component of the monster math for 4e, as broken down in their post, was this:

• Attack roll: d20+5+level
• Average damage: 8+level

I decided pretty early on that I wanted to make a universal dice expression to represent this math, so that I could use it for any monsters that I was controlling as the DM (instead of having to refer to a half-dozen different stat blocks, for weapon damage.)

What I came up with was this:

• Attack roll: d20+d8+level
• Average damage: 1d6+1d10+level

To further streamline, I integrated "recharge" and "when first bloodied" mechanics into the d8 roll (using roughly appropriate percentages from the source material, for this conversion) as well as using it for situational +4/+5 bonuses; the most common example I can refer to would be instances of bonus damage for being hidden, or bonuses to AC against opportunity attacks while charging.

The damage would be scaled up, per tier -- adding an additional 1d6+1d10 in place of every 10 levels of flat damage bonus.

Making it Your Own

Around the same time, I would be working on my previously mentioned Unnamed RPG, which was essentially a change from my earlier tabletop designs (more rooted in "Diablo 2"-style skill trees and classes) to something that was a bit more "lego-bricking" in character-creation -- but with 4th Edition as its basis for things like movement, area, and powers. Those who have read about this RPG before, will know that it used 1d6+1d10 for its resolution mechanic, as well as using only d6 and d10 for its damage rolls.

After a few iterations, some critical analysis from the outside, and an abortive playtest, I decided to abandon this project and move onto the next. It was around this time that 5th Edition D&D had come out, and so the designs therein had started to shade and shape what I wanted to include in this game.

Whose Roll is it, Anyway?

In the early playtesting for TNP, the PCs had one die worth of HP; this meant that monster damage had to be relatively low. In order for it to be balanced across the classes, I kept it to 1 point per "hit" (or maybe 2, for stronger/solo monsters.)

Now, this is where I should mention how 5th Edition (along with my own DM experience) were influences on the design. The DM has a lot to do, so I wanted (as much as possible) to download some of the mechanical "heavy lifting" onto the PCs. This idea was meant not only to ease the workload of the DM, but to also keep players engaged during their off-turns. 

So I looked at 5th Edition's design: some attacks are rolled, but others call for a "save." (In 4th Edition, the rule is "attacker always rolls.") I realized that a way I could achieve my goal was to simply make all monster attacks trigger a "save" -- this would be called the "Defense roll" in TNP. Conversely, when the PCs attack, they make an attack roll.

What we end up with is a consistent rule, albeit one different from 4th Edition:
"PCs always roll"

This goes against the convention in D&D (generally) of monsters and PCs being built the same way, and using the same mechanical framework. The problem that then presented itself, was that if monsters were to use skills, they still needed to make a roll (since the core mechanic for skills is the flat "DC10" rule, and because generally skill checks are not made in opposition to each other.)

The Witch's Hammer

So as the design evolved, it was decided that PCs should be given more HP. The natural progression of that line of thinking, was that monster damage needed to be increased, too.

This is when monsters started to move away from 1 or 2 points of damage, and minions took up that design space. I had always liked using homebrewed "2-hit minions" in 4th Edition, so the opportunity to build them into the design from the ground, up (rather than have them as a work-around) was an exciting prospect --  a chance to put more tools in the DM's hands.

Somewhere along the way, the idea of taking the "universal roll" (used in both the Unnamed RPG and my own 4e monster homebrews) and applying it to the monster math just sort of came together. It was probably around the time I was making the first monster math posts, and I realized I needed to put pen to paper on how I wanted things to run, and what the mechanics should look like.

With the 1d6+1d10 mechanic, I had a damage expression I could build around, as well as a resolution mechanic for skills -- which worked within the existing framework. It was a unified mechanic, in the sense that regardless of which action the monster took, the dice that the DM needed to roll for them remained the same; if the PC's Defense roll was successful, the result of the monster roll would simply be moot. It also opened up a new design space for monsters: the potential for deciding their action after making the roll.

A roll of 10 or higher would mean a significant amount of damage... but only if the Defense roll failed. However, if used to make a skill check, that result would be a guaranteed success. This makes for some interesting choices to be had. It also lets the monster's actions be a little more scripted, in the case of lower rolls; a roll that has no chance to succeed as a skill check will invariably be used as a damage roll. The hope with this is that it can speed up turn-taking for the DM; a big complaint about 4th Edition was the length of combat, and since the DM operates the largest number of combatants, I figured it was the side of the table where the most headway could be made, in that regard.

In Conclusion...

So now you know the "how" and "why" of the Monster Roll. Since I'm currently focusing my efforts mainly on monster-building tools for TNP (at least when I'm not playing D&D, or making new characters) I'm hoping that all the aspects mentioned in this posts will continue to be further refined and sharpened, in the very near future.

Check back May 25th for the next post!

Monster Math (2018)

New content is now live!

That's right! The guidelines for monster stats are now available (in early-draft form) and a link has been added to the end of the Playtest document (linked on the sidebar.)


Square Peg, Round Hole
Since I wanted monsters to have a universal dice-rolling mechanic (1d6+1d10) I had to round off a few edges, in terms of bonuses and penalties. As you'll see in the document, Advantage and Disadvantage are adjudicated a little differently than how they operate for PCs.

Essentially, how it works is like this:

• Advantage: on a tie, maximize both dice
• Disadvantage: cancels out Advantage, or uses the lowest roll

I had tinkered with having Advantage work similarly to the "double roll and stack" rule, potentially maximizing one die or the other. In short, I found it both a little clunky and not a big enough bonus, so I went with maxing both dice, instead.

The Mother of Invention

It should also be pointed out that the previous post (Monster Math -- Part 3: Standards & Elites) contained a mechanical error, which has been corrected in this draft: Standard monsters will use the universal monster roll for damage, but only use the highest die, rather than adding them together. I had figured this out before, but it sort of got lost in the shuffle; when it came time to make the post, my brain reverted back to an older loadout.

However, when double-checking the math this time around (and coming across this snag) I came up with another lever that can be used to differentiate monsters a bit, and at the same time allow them to mesh with some of the existing mechanics.

When a monster is able to stack their roll, the roll is described as "Trained" whereas using only the higher result means the roll is "Untrained." So monsters that specialize in melee might only have this bonus to their melee attacks, whereas "artillery" types might have it only on their ranged attacks. It's worth noting that Expertise can be seamlessly applied to monster rolls, as a straightforward damage boost.

Rogues' Gallery

In addition to Standard and Elite monsters, Minions and Swarms were also established in an earlier post. This new draft rounds out the list of antagonists, with the addition of Solo monsters and Archenemies.

Solo monsters are what I envision as "Colossus" fights -- an enemy that has to be brought down in stages -- whereas Archenemies are the final boss of a shorter or longer story arc; they are exceptionally strong and resilient, a single combatant who is a suitable challenge for an entire party.

Moving Forward

I still have intentions of updating a few more classes, but monster math has taken my attention, for the time being. I have some ideas for implementing area attacks, as well as attacks that impose debilities (I just need to try and square the math); basically, the idea will be to use Trained/Untrained/Disadvantage as a means of "stepping down" damage, in order to leverage such powers. In addition to that, I will want to come up with some sample/example monsters -- in particular, conversions of popular or iconic enemies.

Check back May 15th!