Monday, October 30, 2023

Class Showcase: Cleric & Occultist (2023)

Given that it's nearly Halloween, it seemed like Occultist was an obvious choice for today's post. And since D&D's cleric class famously was based off of the vampire-hunter Van Helsing, that seemed like another solid candidate.


Like many classes, the Cleric breaks down into essentially a melee subclass (Battle Priest) and a ranged subclass (Invoker). In the 4e paradigm where [role + power source = class], it makes sense to split Invoker off from Cleric; in a paradigm closer to 5e, Invoker just seems like a specialized cleric, with particular spells picked. I chose to give the Cleric class a d10, so that the Invoker could have a few extra reserves to burn for powering their abilities (rather than putting debuffs on themself to power them, as in 4e) -- this is also why the Invoker is one of the first real instances where the newly-defined debilities make an appearance, within a class' features.

Beyond that, I felt like a "healing word"-esque spell and a buff like Bless sort of neatly encapsulates the basic Cleric's toolkit in 5e -- barring specific flavours from domains beyond the obvious divine-ish types.


The Occultist was a class I actually took a long time to settle on a name for. I eventually picked this one after it came up as a class in Darkest Dungeon. In earlier iterations, I had the Animate Dead ability as exclusive to the Necromancer, and the Eldritch Blast ability as exclusive to the Warlock. In the previous iteration, I decided to make both of these abilities available to all Occultists (mainly because they both required a standard action to use) and treated Necromancer and Warlock more as 'roles' rather than distinct subclasses. This lastest version kind of splits the difference; the two aforementioned abilities remain universal, but the curses remain specific to each subclass. The Banishment ability was changed to a controller ability from a Necromancer ability, the Hellish Rebuke ability was changed from a Warlock ability to a striker ability, and Vampiric Touch was added as a support ability.


Generally the ethos in TNP has been to try (as much as possible) to fit the abilities of each class into 3 features, which are sometimes bundles of smaller features -- almost akin to how feats work in 5th Edition D&D. There is some bending of this rule; a class might have one feature and each subclass might have 3 of their own features, in addition to that (such as the Cleric... sort of.) The Occultist essentially has 4 features (one of which has 2 different subsets, depending on subclass) and 3 possible role features, on top of that. In the earliest versions of TNP, the idea was that ALL classes should be able to fit onto one sheet of paper; now, it's usually 3, but some of the simpler classes make in at 2 (with the 1st page essentially being the key, basic statistics for each class loadout.) Hopefully this allows the game to overall strike the right balance between complexity as well as range of character options.


...

Check back for the next post on November 10th!

Friday, October 20, 2023

The Conundrum of Class Dice Bonuses

Since the summer break, I've been trying to figure out a solution to the problem with the d12 bonus. What it comes down to is that because d12 is such a large damage bonus, it has to be a relatively small attack bonus, in order for the DPR to be balanced against the other (smaller) dice bonuses -- to wit, in the current iterations, the d12 does not provide an attack bonus at all. This creates a problem, because it does not bestow the multiplicative effect to "extra damage" that dice bonuses with an attack bonus offer. I came up with a fix, but in the process I realized I should also clean up some of the nomenclature a bit.


Class dice bonuses are bonuses to attacks, which use class dice; they can be bonuses to attack rolls and/or to damage rolls. When used as a bonus to an attack roll, the class dice bonus is referred to as an attack bonus, and when used as a bonus to a damage (i.e. base damage) roll, the class dice bonus is referred to as a damage bonus (or bonus damage, depending on grammatical considerations.) Extra damage is something entirely separate from bonus damage; extra damage is only ever represented by d6s and/or d10s, can only be used for damage (not for attack bonus), and is in addition to both base damage and bonus damage.

Now, it's important to remember that while all 5 of the class dice bonuses may be applied to a given attack, only one may be used as an attack bonus -- and you can choose which one to use, after rolling all bonuses. Some of the class dice bonuses have special functions that work "as an attack bonus," meaning that in order to benefit from said bonus, no other attack bonus may be applied. Specifically, the d8 bonus when it ties the attack roll (d20), or using the d10 roll in place of the d20 (i.e. a 10 on the d10 being used to make a hit.) Remember this for later.

The general rule is that a class dice bonus can be used for an attack bonus OR a damage bonus, but not both -- however, there are exceptions (which is partly why to simplify things, one of the reworks I was considering was to just allow all dice to be used for attack bonus AND damage bonus.)


As I had said from the top, the d12 bonus:
a) does not have an attack bonus component, and;
b) does not properly scale with extra damage dice

So how do we fix this? Well, what I've come up with is this:
"As an attack bonus, the d12 bonus allows all extra damage dice to be treated as having rolled their maximum value."

Essentially what this does, is take the base hit chance (50%) and crit chance (5%) without an attack bonus (or, when applying the d12 bonus, which has no attack bonus component) and instead of multiplying those chances by the random roll of the extra damage dice, you're multiplying them by the maximum value of the extra damage dice. The result is that the extra damage scales up, more in line with the other class dice bonuses.

As mentioned in a previous post, since each class dice bonus (with a base damage of 1d8) produces a DPR of about 7.3 we then need the extra damage dice to work out to at least another 16.7 DPR, in order to hit our "1 KPR" number of 24 DPR. By using the d12 bonus this way, we're multiplying the maximum value of 5d6 or 3d10 by 50% (hit) and taking double that amount, multplied by 5% (crit):

(30 * 50% = 15) + (60 * 5% = 3) = 18


So this means that with the d12 bonus in play, the DPR from extra damage can be increased to 18, finally putting it just about on par with the other bonuses.


Now, this may seem a bit unintuitive and weird, since objectively the roll of the d12 is doing nothing to provide the actual attack bonus. But we do need to treat it as an attack bonus, to keep other attack bonuses from being applied in addition to this one. Since the ~7.3 DPR from the d12 bonus comes entirely from damage, this also means that the rule for the d12 bonus must be that it can be used for attack AND damage, in order for this math to work out.

Essentially, I think of attack bonus and damage bonus more and more like two separate buckets, that can each be filled in specific, different ways. Attack bonus is more like a "typed" bonus, in the sense that, for example, a "feat bonus" to attack can be stacked with a "power bonus" to attack, and a "circumstance bonus" to attack... but not with another "feat bonus" to attack; if every class dice bonus to attack is considered a "feat bonus", then only the highest/best would apply. Bonus damage is more like an untyped bonus; all of them can be stacked (unless they specifically don't apply, such as when using one for an attack bonus prohibits using it as a damage bonus.)

...

Anyway, hopefully that doesn't muddy the waters too much; it was the simplest fix to the class dice problem, short of reworking the whole scheme from scratch.

Next post should be up on October 30th, so check back then!

Tuesday, October 10, 2023

Class Showcase: Fighter, Paladin, Ranger (2023)

 So for today's 3 classes, we have the (mostly) martial bunch:


If we look at 5th Edition D&D, these classes are sort of grouped together, with "fighting styles" being their common mechanic; the fighter gets access to all, ranger leans towards two-weapon fighting or archery, and paladin can basically get any of the others.

It seems clear that there was a deliberate attempt to make Fighters in 5e that could be built for more than just melee, and I felt that was valuable to keep in TNP. However, I didn't want the fighting styles to be something you were pigeon-holed into, so I added the mechanic of each additional style giving you extra damage. The TNP version of the Fighter is actually an outgrowth of the original "Warrior" class, which was a much more barbarian-ish, d12 class; as the Fighter-y bits got added more and more into the Warrior, the d12 made less and less sense. When I started working on the 3rd slate of classes, I decided to make the Fighter as a separate, d6 class, and later with the two-dice revision, d6/d12 seemed the obvious choice.

The Paladin in TNP, on the other hand, was one of the original 5 character classes... sort of -- having evolved out of the d10 "Fighter" class to include some more holy/healing abilities, which the slate was otherwise completely lacking. There are some subtle influences from Diablo 2, as the Paladin in that game was probably my favourite class. I liked the idea of either taking a Cleric domain or a Fighter role (or possibly fighting style) with the Paladin, so I sort of massaged that into the class specialization options; the Fighter and Paladin sharing the d6 class die made role the easier fighter option to share. In much the same way as in 5e, the Paladin isn't mean to be a "pure" healer or "main" healer, but they're a frontliner who can dish out some healing as they fight. I can honestly say I had fun playing a Blackguard in 4e, and so including a dark Paladin with some of the thievery-type skills had always been on my radar.

The Ranger has always been a d8 class, but honestly, stapling an "extra damage die" such as the d10 onto the class just worked flawlessly. The scout subclass bounced around between Ranger and Rogue for a bit, before finally settling in as part of the Adventurer class; I wanted to keep classes to only 2 subclasses, and that sort of necessitated this. Probably the two-weapon fighting and the archery Rangers are the most iconic, particularly coming out of 4th Edition; TNP's Ranger is more akin to the Essentials' Hunter ranger, stapled onto the beastmaster archetype of the Martial Power book. I feel the latter playstyle became popularized for a lot of people (myself included) with the World of Warcraft hunter class, and I think using the beast for 4e's iconic "twin strike" manages to work out ok.


...

So, the remaining "completed" class is the Rogue, with 5 others still needing to be polished up and finalized; I might squeeze in a post on another topic, rather than continue with the class showcases, for the next one.

Check back on October 20th!

Saturday, September 30, 2023

Class Showcase: Acrobat, Bard, Sage (2023)

For today's post, we're going to look at 3 classes that have sort of been tangled and disentangled from each other, at various points in the development.


When I had first set about making a d4 Monk class (at the start of doing the 2nd full slate of classes, if memory serves) there was essentially a "mundane monk" subclass (the Martial Artist) and a "magical monk" subclass (the Ki Master). Later on, when I got around to doing a 3rd slate of classes, one of the ideas I started off with was to add an archer, as a "2d4" class. Eventually, the archer and the "mundane monk" got stapled together to form the Acrobat. Although not mechanically inspired by the Avenger or the Executioner from 4th Edition, the idea is that with different power sources (such as Divine or Shadow, respectively) the Acrobat can be used to approximate the flavour of such classes.

Likewise, the Sage started off as the d4 Mage class. In early iterations, the "INT Mage" was the wizard subclass, with the "CHA Mage" being the bard subclass. Later, that would change to Wizard and Swordmage being the Mage subclasses (with Bard and Sorcerer being subclasses for the "Trickster" -- kind of a de facto "CHA Mage" class.) With the big remix that came out of the 3rd slate, the "magical monk" got stapled onto the wizard subclass, to create the Sage class. As such, the Wizard is kind of the "mental Sage" whereas the Monk is the "physical Sage" in terms of their skills.

By recombining the subclasses this way, both the Acrobat and the Sage end up with a melee subclass and a ranged subclass. The Bard would eventually get spun off into its own class, as would the Swordmage (expanding to include the Hexblade subclass, under the banner of the "Spellbinder" class.)


As a side note, the general realignment that came with the expansion to a 3rd slate of classes was meant to organize the slates more around power sources.

If you look at the 4th Edition books...
  • Martial characters were in PHB1, and Heroes of the Fallen Lands
  • Divine characters (specifically Cleric and Paladin) were in PHB1, Heroes of Shadow, Heroes of the Fallen Lands, and Heroes of the Forgotten Kingdoms
  • Arcane characters were in PHB1 (Wizard, Warlock), and PHB2 (Bard, Sorcerer), with variants and subclasses for those spread across all of the Essentials books
  • Primal characters were in PHB2, PHB3 (Seeker), Heroes of the Forgotten Kingdoms (Sentinel Druid, Hunter and Scout Rangers), and Heroes of the Feywild (Berserker Barbarian, Protector Druid)

The original slate in TNP was meant as more of a classic/"greatest hits" compilation (Mage, Rogue, Ranger, Paladin, Barbarian[-ish]) but when the roster expanded to 3 slates, it became more of an exercise in answering the question, "How would the 4e classes have been grouped, if we started with all of them and worked backwards [rather than start with the 8 classes from PHB1, and expand outwards]?"

With the Ranger class moving from "Martial" in PHB1 to "Martial and Primal" in Heroes of the Forgotten Kingdoms, and Rogue being a good candidate for the underdeveloped Shadow power source, this left the Martial roster for TNP a little thin; the obvious way to fill it out was to combine Martial and Divine into one slate, consisting of the Acrobat, Fighter, Cleric, Paladin, and Warlord classes.

An "arcane and shadow" slate drawing from the Wizard, the "magical monk", the Rogue, the Sorcerer, the Bard, the Swordmage, the Hexblade, the Warlock, and the Necromancer would have more than enough material to flesh it out. Likewise, a combined "primal, or primal & martial" slate including all forms of Ranger, Druid, and Barbarian, as well as 4e-specific classes like Warden, Shaman, and Skald seemed to cover enough ground as well.

To sum up, the idea was that each TNP "book" (i.e. slate) would revolve around one or two power sources, and have all of the classes (and other materials) related to those power sources included. It's meant as sort of a refinement of the 4e ethos, where each "PHB" seems to have a primary power source (but also secondary and tertiary ones) as well as each power source having one or more "players' option" splat-books... to say nothing of the Essentials or post-Essentials books.


...

Anyway, that's all for this month.
Check back on October 10th for the next post!

Wednesday, September 20, 2023

Class Showcase: Adventurer, Barbarian, Guardian (2023)

I've been a little bit overly scrambly lately, so I'm going to use this post to release some of the updated classes. Hopefully this will produce some conversation and feedback, on the chance that any changes or tweaks need to be made. I decided to go with these 3 classes in particular, because the Barbarian borrows its class specialization options from the other two.


If you click into the links, you'll see that these are the "2021" versions of these classes. Most classes that have been completed since the 2018 version are referred to this way; the classes which are still being worked on will be referred to as "2023" versions.

The Adventurer arguably has changed the most, going from previously using a d10; for a two-weapon fighting class, d8 weapons seem like a better fit, and d6 for an extra damage die seems more appropriate for a subclass (Scout) that often lends itself to being more like a rogue.

The Guardian split into the Warden (defender) and Shaman (support) subclasses, borrowing from the 4e classes of the same names. The Guardian class essentially uses animal spirits to bestow supernatural powers; the Warden bestows those powers on themself, whereas the Shaman causes these spirits to possess an ally. The idea is that the Shaman is a support class more in the vein of a Warlord or Bard in 4e, using their allies as a conduit for attacks and such.

The Barbarian is meant to be more akin to the Berserker class from 4e -- but not entirely mechanically similar. The general idea being that rage is effectively "striker mode" while not raging is closer to "defender mode." As a d12 class, the Barbarian is focused on melee combat, while as a d10 class they're also potentially a very heavy hitter.

...

Anyways, that's all for today. If I stick with the format of releasing 3 classes at a time, that would mean 5 posts like this in total, taking us to the end of October. If I have the handful of remaining classes finished by then, we'll be in good shape.

Check back September 30th for the next post!

Sunday, September 10, 2023

Are Old Mechanics the Next Mechanics?

As things crystalize and start to be narrowed down, I'm beginning to think back on some of the dice mechanics that have been shed from TNP (that, and the possible rework to class dice bonuses, that I mentioned in my previous post.) Specific to that, I'm wondering if the "d6 and d10 as extra damage, only" (mixed with beefed up bonuses for the other dice) could constitute the basis for a different game.

All in all, it sort of got me thinking back to some mechanics that have come and gone. At one point, there were no "opportunity attacks" just "opportunity damage" -- no attack roll needed; I wonder if, within the paradigm of two class dice, this is still necessary. Similarly, there used to be a "reliable" property, whereby if a basic attack missed, it would deal damage equal to the missed attack roll (i.e. a number between 1 and 9.) This didn't make a lot of sense, in a paradigm where the base damage of a successful attack might be 1d4 or 1d6, so it only ended up being used on classes which would use bigger dice for damage -- effectively creating a "rich get richer" kind of situation, leading it to eventually be scrapped. I've never liked using half-damage (or half-anything, for that matter) in my designs, so this was my attempt at a simple, streamlined "damage on a miss"-mechanic. If there's anything to be learned from this experiment, it's that damage on a miss should only ever be 1d4, or maybe 1d6?

Another big mechanic that has disappeared is stuff happening when you roll doubles; for advantage and disadvantage on d20s in particular, this was meant to remove the frustration of rolling twice but only getting one result. When it comes to damage dice "treat 1 die as having rolled its maximum" on a tie is sorta just like, "expertise, again" albeit less useful the higher the tie is. It's another way to boost damage, but it's not particularly... slick, really. It's also a bit trickier to calculate the math for "roll two and take the highest, but also" than it is to just do without that extra wrinkle.

Basically, the alternate class dice mechanics I was testing boiled down to this:
  • add the d4 to the attack
  • add the d8 to a miss
  • use the d12 in place of the attack roll

Now, to boost up the damage output, I revised the basic concept of these bonus dice from "attack OR damage" to "attack AND damage." The other universal (sort of) perk, was how a tie between these bonus dice and the attack roll (d20) interacted. In short, when you roll a d20 with any other, smaller die (or along with another d20) the chance of a tie is 5% -- this mechanic is used on the existing d8 mechanic, to produce additional crits. The idea here was that this would also be bolted onto the d4 mechanic (as well as treating that die as max value, for the damage component only.) The idea with the d12 would be that (at least) if the result was a tie and both values would be considered a hit, the attack would be treated as a crit, and (possibly) that any other ties would be treated as a hit.

Overall, I think "use the d12 roll in place of the d20 roll" is a really slick mechanic within a DC10 paradigm, assuming you don't have to bog it down with a bunch of other baggage. I'd really like to use that somewhere, and in fact it'll probably appear on one or more of the d12 classes. I also think it might be interesting if these stripped down d4/d8/d12 mechanics could be used for saving throws (instead of d6 bonuses.)

One underused mechanic that I brought up ages ago is using things like "surge value" or "current number of reserves" as hard-number modifiers for class mechanics. In particular, one thing I thought of lately was using the max value of 1d8 or 2d4 (such as from its use as a surge value) as a replacement target number. Changing the DC from 10 to 8 would effectively boost the hit chance on an unmodified d20 by 10% -- and would also provide some neat interactions with the tying mechanic of the d8 bonus, since that die could effectively cover the entire "miss" range that way. I haven't incorporated this in any classes previously, but there may be some implementation of it for the unfinished classes -- I may even go back and relook at some of the others, particularly in cases where 1d8/2d4 is paired with one of the 'striker dice' (d6 or d10.)

One of the main mechanics in earlier drafts was "trade-offs" which... apparently some people thought was a misnomer? Essentially, it was a double roll, whereby you'd use one roll as a bonus and the other as a penalty; apparently, this does not describe a trade-off, but whatever. This worked a lot better in the paradigm of a single class die; nowadays when it is used in the text, which die to use for the double roll has to be specified every time, rather than just saying "using your class die." It's a bit tedious.

As I've said before, I really like the "percentile as adv/disadv" for its ergonomic qualities; it's also handy because a tie on 2d10 ends up being a 10% possibility. I've combined this mechanic with a d6 roll for both the (post-d20) skill mechanics in TNP, as well as the monster roll mechanic. The other thing with d10s is that expertise increases the chance of a 10 (i.e. succeeding at a DC10) by 10% as well. Hopefully, this kind of illustrates why I think this mechanic has some potential, if there is to be a "next next project."


---

Check back for the next post on September 20th!

Thursday, August 31, 2023

Damage Per Round vs. Monster HP (2023)

As was established in a previous post, the baseline of 1d8 + any one of the 5 class dice bonuses produces about 7.3 damage per round (DPR). Now, the d12 bonus is the outlier in that it does not produce any additional hit or crit chance; this became a concern of mine when I started to look into the interaction of hit and crit chance, with the stacking of extra damage dice. We'll set that aside for now, but I'll come back to that at the end of this post.

Now, coming back to our monster math expressions, we know that standard monsters should have about as much HP as a PC, and that our encounter budget allows for 2 standard monsters per 1 PC. So what does all of this actually mean?

Let's start with the HP: how much HP do PCs have? Since we now calculate HP as "the maximum possible result of your initiative roll [including initiative bonus]" this gives us a range between 24 and 32. This is the same range as in previous iterations, the difference being that we're using initiative roll instead of "basic roll" (i.e. 1d20 + class die, which became muddled once the change to two class dice was made.) Initiative rolls use a d20 + a bonus based on one of your class dice: 1d4, 2d4, 1d6, 2d6, 1d8, 1d10, or 1d12.

What this means is that a team of 4 PCs should deal something like 192-256 damage per encounter, in order to kill off the 8 standard monsters (having between 24 and 32 HP each.) Following the ethos of 4th Edition D&D, ideally combat should be somewhere around 3 or 4 rounds of combat. If we average out this total over 4 rounds, this results in 48-64 damage per round, as a team of 4 PCs.

Now, let's assume that each 'striker' in the party is expected to produce 1 kill per round (KPR). This translates to 24-32 damage per round. Assuming our baseline of 7.3 damage (as mentioned at the start) this means that the striker needs to produce an additional 16.7-24.7 DPR to hit this benchmark. Since the party needs to achieve 48-64 DPR, and if 1 KPR = 24-32 DPR, this means that the remaining 3 party members only need to account for half of the remaining DPR requirement. If we take 24 HP and split it 3 ways, we come up with 8 -- not far off of our benchmark of 7.3; once we add in things like combat mastery from status effects or tactical considerations, this should be easily doable.

So how do we get strikers up by that additional 16.7-24.7 DPR?
Let's look at the proposed baselines we're dealing with, in terms of "extra damage dice." First, it's important to remember that a change was recently made whereby these dice always have mastery applied to them; this increases the average of each d6 to 4.33 and each d10 to 6.4

Now, if we calculate out 5d6 and 3d10, we get averages of 21.65 and 19.2 respectively.
At this point, we have to stop and remind ourselves that this is damage, and NOT DPR -- and we MUST calculate the DPR in this instance. The baseline hit chance in TNP is 50% (a 10-19 on the d20) with a 5% crit chance (natural 20.) So, we'll do 55% of this damage, per round -- plus the maximum damage of these dice (30, in either case) an additional 5% of the time, since crits deal the rolled damage plus the maximum value of the damage dice.

(21.65 * 0.55) + (30 * 0.05) = 13.4075

(19.2 * 0.55) + (30 *0.05) =  12.06


As you can see, when added to the baseline DPR, this still leaves us far short of the damage necessary for 1 KPR. For the sake of argument, let's increase the hit chance and crit chance, by applying the d4 class dice bonus to it; this bonus increases the crit chance to 17.5%, which changes the calculation as follows:

(21.65 * 0.675) + (30 * 0.175) = 19.86375

(19.2 * 0.675) + (30 * 0.175) =  18.21


Now when we add in the baseline DPR of about 7.3, these numbers only just barely break the minimum threshold of doing the 24 damage needed to achieve 1 KPR. Now, imagine if this example were using the d12 bonus (where there is no increase in hit chance or crit chance) rather than the d4 bonus, and you can see where the problem arises. This is why I recently gave some consideration to boosting all of the dice bonuses; I've been prototyping some changes to the d4, d8, and d12 which would increase the baseline DPR to about 8.8 and crucially would add an increase in hit chance for the d12 bonus. The problem is that it's still significantly smaller than the d4 or d8 bonus, meaning it still doesn't scale well w/r/t extra damage dice -- unless the baseline DPR with the d12 bonus is increased to something closer to 9.3

The other question then becomes, do we simply dispense with d6 and d10 bonuses, and only use those dice for extra damage? I've contemplated it, but it really does leave the Paladin (d6, d10), Rogue (d6), and Occultist (d10) classes in a lurch -- unless you compensate them with some unique +hit mechanics, or just boost their extra damage dice beyond the cap, high enough to outpace their lack of a hit booster.


Now, one thing I've discovered in going over all this, is that most classes (in fact) aren't attacking only once per round. At a bare minimum (depending on things like subclass) everyone will at least be doing some kind of two-weapon fighting routine, if not a flatout AoE against an entire maelstrom, or some other form of multi-attack. As such, I think I'm just going to power through, with the bonuses from the most recent draft of the rules intact; it's far too late in the game (no pun intended) to really consider a major overhaul to the base mechanics.


...

As with things like the decision to axe advantage on base damage, the new class dice mechanics I was tinkering with will basically be filed (at least mentally) in my "list of things for the NEXT next project."

Hopefully this deep dive into the math was illuminating for those of you reading out there.

Check back for the next post on September 10th!