Building out Class Features (2025)

At the risk of throwing out the baby with the bathwater, I think the solution to the "cantrip problem" is to pivot the design space off of attribute mechanics. I started to think about it more as, "I use a spell, therefore I add 1d6 to the pool, for this attack." Now, as has been stated clearly before, not all classes/subclasses will get access to cantrips -- so what if we make having that specific class feature be the source of the 1d6 that we add to the pool? This lets us more easily differentiate Clerics from Paladins, and Druids from Rangers. (Another big distinction between spellcasters in 5e is ritual casting; this class feature is what I would argue is the main thing separating Sorcerers and Warlocks from being as high on my list as Druids or Wizards, in particular.)

Now that we've established what attributes won't do, we need to figure out what they will do, with regards to cantrips. If two-handed weapons are assumed to be getting a +8 damage mod, and two-weapon fighting will get +3 damage to each attack (assuming our standard array of +4/+3/+2/+1/+0) then we probably need to figure out something comparable to that, for cantrip attacks.

Would a single-target attack simply add both mental stats, as damage? Is there an easy way to balance out a "number of attacks" stat with the assumption that a "cantrip damage" stat will now likely be your highest stat? The problem is that if the only thing that "cantrip casters" care about is their mental stats, then suddenly everyone's got a +4 in one and a +3 in the other, and there's no variety. Maybe we still need to encourage spellcasters to have a +2 finger-waggling stat, after all. Do we simply treat (ranged) cantrip attacks the same way as (melee) two-handed weapon attacks, and add double the damage mod? How many attacks does an archer need to make, in order to be able to compete with that? This will take a bit more thought in order to flesh out, it seems. 

The other aspect of class features that I wanted to bring to the fore was the idea of "exceptions-based design." I touched on it a little bit (albeit ham-fistedly) in a recent post, where there are general rules, but then there are exceptions made to those rules. One example with the sequel mechanics is that the general rule (so far) is that we assume TWF will use the lower damage mod between STR and DEX. This would encourage a class like a Fighter to put high stats into both, in order to be good at TWF; it would also make it more expensive for spellcasting classes (who rely more on investment in mental stats) to also be good at TWF.

However, as an exception, we might allow the Ranger subclass to simply always use the higher of these two stats, meaning they don't have to invest in both -- or to simply override this rule and use a different stat, such as AGIL. If the assumption within the "lore" of the Ranger is that they are always scouting ahead and need to be able to react quickly, then incentivizing them to have a higher AGIL would reflect that in the mechanics, via having a higher initiative score. AGIL also being tied to stealth would likewise tie in to the presumption of Rangers as hunters and ambushers, stalking their prey from the shadows.

This also makes me ask, how should the Monk/Rogue class be designed? If the starting point is that Monks will probably get an INT bonus to their AC, my immediate thought actually isn't to slant Rogues towards CHA. Monk generally lends itself to being the multi-attack class, whereas Rogue is more of an "alpha strike" class, using sneak attack. If the general rule is that DEX (or AGIL?) is the "number of ranged weapon attacks" stat, the obvious exception to build in for Monks would be to allow them to also use this number for melee attacks (perhaps using their lowest physical stat as the damage modifier?) Or maybe it makes more sense to go with "highest physical stat" as number of attacks and "lowest physical stat" as their melee damage mod.

Likewise, if the Rogue's preferred damage mod stat is DEX, would it make more sense for their dice pool stat to also be DEX, or should it be AGIL? We definitely want Rogues to be the best at things like lockpicking, so leaning more towards DEX seems like the obvious move... but it really is a question of how to balance the two. Much like in 5e, this gives the Rogue the versatility to put any remaining stat points into whichever mental stat they choose, making it more of a decision around which skills to focus on, than purely a combat consideration.

Dovetailing into the Rogue idea, the mechanic of "finesse" weapons from 5e is something that I think could make an appearance, allowing either STR or DEX to be used for damage, when attacking with a one-handed weapon (and not doing TWF). To tie this back into the conceit of class features, perhaps the "one-handed weapon stat" could be a function of classes, rather than having a general rule. Or, say, the general rule is that STR is the default, but characters with "finesse weapon proficiency" can instead use DEX. So we would expect classes like Rogues or maybe Rangers to have this proficiency, but Barbarians likely would not. Maybe a benefit of being a Barbarian is that you could always use STR, when doing two-weapon fighting.

---

Slightly off topic, but bringing things back to Eldritch Horror... One of my complaints with the game is how some characters are more about their items than their intrinsic abilities. While this is also a complaint I've had about D&D, it's significantly worse in a game where world-events regularly cause you to lose possessions at random. I do appreciate the conceit of reusing existing in-game items as a way to equip the starting class features for characters, but this style of game in particularly causes the weakness of item-dependent characters to be laid bare. The classic D&D comparable is when the party is captured and stripped of their belongings, imprisoned, etc. This is why TNP and the sequel generally focus on treating everything as a class feature -- even things that could reasonably be represented as items. In this way, they are part of the character at all times, and not something that can be taken away from them; they are just always assumed to be part of what the characters can do.

...

This post is a little bit ahead of schedule (or "on time," as far as our most optimistic forecasting is concerned...) Next post will likely be up by November 19th, at the latest -- but possibly even by the end of next week, depending on how things go.

Powers vs. Power Strike: Fishing for Crits (2025)

I'm sure I've mentioned it before but let's examine the difference in ethos between 4e and Essentials a little bit.

With an attack power in 4e, generally you declare that you're using it, then the button gets pushed, and you roll dice to determine if you hit. This means that (hit or miss) the power is expended, assuming it is a Daily or Encounter power. In Essentials, the Fighter class instead functioned off of confirming a hit with a melee basic attack; after the hit was confirmed, they would then push the Power Strike button (an encounter power) to deal additional damage. (The Paladin in Essentials got a similar mechanic, and the Scout subclass for Ranger also got access to Power Strike.)

What this meant was that you never had to "waste" your encounter powers, on a miss. It also meant that you could choose to use it only when you scored a critical hit, thus maximizing the damage effectiveness even further. It's also worth mentioning that since attacks like Charge or opportunity attacks also functioned off of melee basic attacks in 4e, buffing such attacks with Power Strike was also possible. In the 2014 version of 5e, this is also true of the Paladin's Divine Smite ability, because it is cued off of scoring a hit with a melee weapon -- so this could be done with each attack made on your turn, in addition to opportunity attacks (as long as you have the spell slots to burn.) Similarly, the Battle Master in 5e keys its maneuvers off of scoring a hit first, and then expending superiority dice after.

So, how will this work for the TNP sequel mechanics?

Well, the ethos of "2d6 + pool" implies that all of the dice will be in the pool, before the roll is made. This means that we're going to be declaring which power we're using, first -- much like in 4e. However, since adding dice to the pool increases our chances of hitting (while also increasing damage) we end up getting a benefit similar to the "Power Strike"-style of mechanic, but without the two-stage confirmation system being applied to the roll.

This begs the question of whether there should be a mechanic for critical hits, in the sequel. If we take 1/20 as our baseline (5%), then saying "11 or 12 on 2d6" would give us a 2/36 (or 1/18) crit rate, which is pretty comparable. However, we need to keep in mind that the assumption is that the attacker will always be rolling at least 3 dice; scoring at least an 11 on "highest 2 of 3d6" already boosts that to almost 1/5 -- whereas a 12 is only 7.41%

An interesting quirk of the pool system is that damage potential also increases hit potential. This also means that as your crit chance goes up, your crit damage is going up; rolling 5d6 gives almost a 1/5 chance of scoring a 12 on the attack roll, but having 3 dice of crit damage is also going to do a lot more than only having 1 die (particularly if crits are handled by say, using the rolled damage but also adding the dice's maximum value, as in TNP.)

A third thing I've been thinking about is whether there should be a flat number of "daily" power uses, or whether this should be tied to attributes in some way. In previous RPG designs that I've done, I had encounter and daily resources keyed off of stats, so the idea of doing it that way is not completely foreign to me. I was thinking of it in terms of utilization, with my classic example being the Paladin. You're going to want STR for damage, and CHA as your pool stat... but then what? We've got at least 3 other attributes to account for, and we don't want to end up with the default "dump everything into AGIL because it's initiative."

So do we make something like INT the "per day" stat (for Paladin, at least?) that governs the number of uses of your "dice pool" stat? This would necessitate your INT and CHA stats both always being at least a +1, which ties into the idea I had presented previously that your class might prescribe which of your attributes has to be a +0. This also (aside from the obvious) highlights that a "flat 10" number of points to be spread across 5 attributes would probably be a little high, if the assumption was that the Paladin only really needs meaningful numbers in 2 of those stats... particularly if the max in any stat is expected to be +3 and not +4. I do like the idea of a +4/+3/+2/+1/+0 as the "standard array" for a loadout with 5 attributes, so maybe that just solidifies it.

Now, what this does is create some interesting choices. Do you want to "pool" harder, but less often? Do you want to do it weaker, but more often? Do you want to just swing your sword harder (knowing that you're getting double your stat as damage, on a two-handed weapon) and let the pool just be a nice cherry on top, once or twice a day? Naturally, there will be ways to optimize it, but then we also have to think of how our attribute choices impact skills, and not just combat -- which I think would tend towards a heavier focus on CHA, for our Paladin. From a design perspective, we also should give some consideration to, "if our pool button can only get pushed X times per day, then how should that number line up with our crit math?" while keeping in mind the fact that pushing the button is also what increases those odds.

...

Bit of a broad discussion in today's post, but hopefully the ideas flow together well enough for the readers out there.

November's scheduling is a little bit in flux, but I would expect the next post to be up by November 13th, so check back then!

General vs. Specific (2025)

At the risk of harping on attributes a few too many times, I think it's worth discussing whether the sequel designs should use "general" rules, and whether there can be exceptions to those.

The best examples of "specific beats general" that I can think of are both from 4e D&D. The general rule was that you could shift one square, as a Move action; the mechanic specific to kobolds was that they could instead do this as a Minor action. Likewise, using your 2nd Wind was generally a Standard action, but dwarves could use theirs as a Minor action.

Also worth mentioning in this discussion is how 4e handled class-specific combat mechanics (i.e. powers.) Most classes fell into one of two paradigms: you had one attribute which determined your attack (hit chance) and damage modifier, and had 2 you could pick from for your "effect" riders, or; you had 2 attributes used for attack and damage (depending on the power), with one obvious attribute for riders. Generally, these were referred to as "A-shaped" and "V-shaped" builds, respectively (some people would instead refer to V-shaped as "Y-shaped.")

So far in the sequel mechanics, we have a few general assumptions:

• TWF will use the lower of STR or DEX for damage mod
• cantrips will use the lower of INT or CHA for dice pool bonus
• AGIL mod will be the number of ranged weapon attacks, per round

The question I found myself asking initially is whether the AGIL stat should serve the same function for spells as it does for weapons, thus negating the temptation to add a 3rd mental stat. And then I started thinking, "well if DEX is the finger-waggling stat, that seems like it could be used for doing somatic components for spellcasting..." This ties back into what I was saying about 4e, where Sorcerers sort of had STR crowbar'd in as their 3rd (2nd?) stat; this kind of setup was particularly important, given that 4e had your defenses use the higher of two paired stats, so every class needed to emphasize one of STR/CON, INT/DEX, and WIS/CHA.

I think part of the problem is that having the dice pool stat be the higher of the spellcasting/mental stats is unintuitive to most people; the obvious thing to do is to put your big numbers in the thing you're using all of the time (i.e. your cantrip stat), but the restriction requiring the numbers to balance off of each other throws a wrench into all of that. However, if we allow for a 3rd stat to give additional attacks, that might make it easier to balance, while giving a bit more variety.

Specifically, you might be balancing a +2 cantrip stat against the ability to only attack once with it vs. a +1 cantrip stat but the ability to attack twice with it. The question then is, do we apply a "general" rule for the "cantrip attacks per round" stat, or do we make that a "specific" rule, based on class or subclass? The latter seems to be preferable, because then we can also use that to reinforce which skills (if any) we would prefer those subclasses to be good at. For example, if Intimidation is a STR skill, we might actually want that to be "attacks per round" stat for Sorcerers; if the expectation is that Wizards are better at opening doors, that might point to DEX (i.e. lockpicking) as their stat.

I had previously mentioned in the Discord that a standard array might consist of something like +4/+3/+2/+1/+0 (and for the record, a +4 two-hander stat still balances fairly well vs. a +3 TWF stat, in case anyone was wondering.) This gives us a total of +10, which is nice; I had intended that perhaps a floating +1 from class/subclass might be in addition to that. However, it seems like a pool of +10 (with a subclass-specific "locked in" bonus being deducted from that that total, rather than added to it) is more likely to produce the sort of balanced array that we're angling for. In this way, I think a simple rule such as, "you cannot have more than a single +0 attribute," or "all attributes must be at least +1" will be sufficient to keep people from min-maxing their stats, without having to put an actual ceiling value on stats. It might even be the case that your +0 stat is a sort of "specific" rule, for each class/subclass.

The other exception that has been hinted at before is that the Warlock subclass might not have a dice pool stat per se, but that they can use CHA as their cantrip stat -- even if it were to be their highest mental stat, thus giving them more potent cantrips than what other classes could achieve. I think this is fairly in line with the general 3.5/5e mechanics of Warlocks. Likewise, we could have the Necromancer subclass use INT as "number of summons" that they can have under their control at any time, rather than give them a "cantrip stat" at all.

The other thing to remember is that classes like Paladin and Ranger will no doubt use "spellcasting" stats for dice pools and/or other functions, but they won't have a cantrip stat to balance off against. It stands to reason that if STR is the Paladin's "weapon stat" of choice, and CHA is their "dice pool stat" the obvious 3rd choice would be to bump AGIL (the initiative stat) -- but what if a wrinkle of the system would be that Paladins are required to use a +0 AGIL stat? That might be punishing, but it also makes things interesting by eliminating the "obvious" answer from the equation. You could even incentivize this, for example by granting a bonus to AC for doing so; this is reminiscent of how Monks are given certain unique abilities when not wearing armor in 5e, or similar restrictions that Barbarians have while raging.

...

I'm running a bit behind on posting this month, but hopefully we can get back on track now.
One more post before October is out, so check back on (or just after) the 31st; the plan for November would be to post on the 10th/20th/30th to round out the year.

Standard Array (2025)

So, what should the attribute numbers look like, in the sequel?

I've been working from the assumption that the ceiling would be +3, but the paradigm has shifted so many times, it's probably worth reexamining. In a previous post, we've established that the baseline hit chance for weapon attacks is expected to be 72.42% -- so with a two-handed attack adding double STR (+3 * 2 = +6) mod, the [lowest 1 of 3d6] roll (2.04) computed through the hit chance produces a 5.822568 DPR result. Now, if we take the same roll and hit chance values but use only a +2 mod, we get 2.925768 -- which when doubled results in 5.851536, representing a two-weapon fighting routine. This is a great starting point, as these values are very close to one another.

So if the desire is to get the "TWF stat" to always be a +2, it probably stands to reason that it should be something like "lower of STR or DEX" allowing those stats to be either +3/+2 or +2/+2. The other way to do it might be "middle of STR/DEX/AGIL" which also has implications for spellcasting.

If the idea is to balance 3 stats against one another, that likely indicates that the idea is to make the lowest stat a +1, rather than a +2/+2/+3 array. This would be necessary for spellcasting, if the idea is that the "cantrip stat" should always be a +1, for example. This means that the overall array would consist of a single +3, a single +2, and then +1s for the remaining four attributes -- because this assumes 3 spellcasting attributes, and thus 6 attributes in total. We've mentioned before that maybe having +2 be the "minimum" spellcasting stat could be an acceptable quirk of the system, if the alternative is to crowbar in an entire 6th attribute.

Should we complicate the matter by having separate pools of attribute points for physical stats and for spellcasting stats? This actually seems like it would work better for producing the desired results, while allowing for more than just a single +3 and/or +2 stat. Something like a floating +1 based on class/subclass would be a mechanic that works well, for this conceit. If we go with these ideas, it seems like you'd have 3 points to split between 2 spellcasting stats, and 5 points to split between 3 physical stats -- in addition to that floating +1.

If spellcasting is to function off of the lower/higher of two mental stats, the class bonus would help to differentiate builds a little bit, i.e. if a Sorcerer is assumed to get a +1 CHA while a Wizard gets a +1 INT. Similarly, if a Paladin's "dice pool stat" is CHA, they might get a bonus to that stat, requiring them to focus their physical stats more on one mode of combat; by contrast, a Fighter might get a boost to STR or DEX, allowing them to be equally at home with two-handed weapons or TWF.

Is there room for a +0 stat, in the array? Well, if there is, it seems like it would only fit into the physical stat side of things (regardless of how many mental stats there ends up being.) Much like how attributes contribute to skills in TNP, it might be easiest to assume that everything starts at "rank 1" and then increases from there. So far, I haven't come across anything to suggest that the cap needs to be higher than +3... 

Really, the question then becomes whether the dice pools will consist of 1 stat or 2; some of the earliest theorycrafting for "d6 pool" suggested a normal melee attack would add +STR number of dice to the pool, and a Paladin's Smite ability would also add +CHA number of dice to the pool. With the designs migrating to "2d6 + pool" I feel like the necessity for double-stat pools has gone away. Worth mentioning here, I've also floated the idea that "daily" powers might allow all dice in the pool to contribute towards damage; this means you could put your highest 2 dice towards the attack roll (ensuring the best chance of hitting) without missing out on those dice, for their damage potential. This is something that harkens back to the "class dice bonuses" in TNP, most of which can be used for attack or damage, but some of which can also be used for both.

...

I should have a bit more free time coming up later in the month, so expect the next post to be out by October 21st at the latest. A third post will also be out before the end of this month.

Weapons & Armor (2025)

Carrying on with the sequel mechanics discussion, there are a few things that the previous post made me think about, that I'll talk about today.

When trying to balance out spells vs. weapon attacks, if there are to be only two spellcasting stats, it might be harder to make the "cantrip dice pool" stat be any lower than +2; to balance this out vs. weapon attacks, I had talked about spells not adding a modifier to damage. In this specific paradigm, it means cantrip spells would have a better chance to hit (with a pool of 4 dice rather than 3) but the damage would be more random (2d6 as compared to 1d6+mod, usually a +3).

That might be workable enough, especially considering that the alternative is bolting an entire 6th attribute onto the system...

In the previous post, I hinted at the idea of "proficient" weapons applying a 1d6 bonus to your pool. There might also be other benefits we could apply. For example, as an alternative to using 2d6 for two-handed weapons, I had suggested that instead the system could use 1d6, but you might be able to add double your STR modifier to the damage roll; this could be a benefit you only gain from using a two-handed weapon with which you have proficiency. Likewise, the attempts at balancing out two-weapon fighting vis-a-vis two-handed weapons has so far been assumed to revolve around using a lower stat for the damage modifier; this could similarly be made contingent upon whether or not you are proficient with suitable weapons for two-weapon fighting.

This is sort of a milieu that I had used in one of my previous attempts at RPG design, whereby the math was derived from 3 unnamed stats, but certain qualifiers would specify whether a particular mechanic would use the highest, middle, or lowest of your 3 stats. Most of the feats that were purely math boosts were typically, "use your highest stat for this mechanic [instead of your lowest or middle stat.]" Assuming there is a cap on the possible values that your stats can be, this likewise places a ceiling on how high your modifiers for any mechanic can go; it helps create a framework for contextualizing all of the other math and mechanics in the system.

Bringing this back to our example, an "untrained" character doing TWF probably would add no modifier to their damage rolls, whereas a "proficient" character might add the 'middle' modifier, between STR, DEX, or AGIL. Similarly, we need to think about what the upshot to doing a single, one-handed weapon attack would be (if the ethos is basically, "well, anyone can attempt to do TWF," such as is the case in 5th Edition D&D.) The obvious thing that comes to mind is that such an attack would almost certainly have to use your highest stat, but also that your loadout could then include a shield. With the defensive bonuses meant to be fairly few and far between, my first assumption would be that shields are a flat +1 to "AC" (per se) for a proficient character, and provide no benefit if not proficient.

At some point I'll have to really drill into the math, and determine what the "correct" numbers are for AC bonuses -- particularly if we're assuming that "Monks add WIS to AC" will be a mechanic in the game (putting aside for the moment, whether or not WIS will be in the designs). It also begs the question of whether "flat modifiers only, for defense rolls" really makes sense for player-characters. This gets back into what I said about Eldritch Horror, and keeping the mechanics simple and unified... But, perhaps things like a Shield spell or a Rogue's evasion ability make more sense as "dice pool bonuses" to defense, or as rerolls. If such mechanics are meant to be in the game, it makes little sense to have them function as a +1 bonus; if we know the attack and defense results, then we'll know whether a +1 will make a difference, often leading to such abilities not being useful. Off the top of my head, I think this is why Bless in 5e is +1d4 instead of +1 (as in 3.5 D&D.)

Somewhat related to this topic (if I've mentioned it before, I'll say it again, but...) my intention is that there will be no "AC stat" the way that (by and large) DEX is the AC stat in 3.x and 5e D&D. My feeling is that this only serves to arbitrarily raise the floor on all of the math, and I don't think it needs to be there in order to make the stats useful. AGIL probably tracks closer to something resembling an AC stat in the TNP ethos, and the intent so far is that this would instead be used for initiative -- something I feel is impactful enough, on its own. I've also hinted that AGIL might be the "number of attacks"-stat for ranged weapon attacks in particular, if indeed this is needed as a balancing mechanic (i.e. sacrificing "+mod to damage" in exchange for hitting more targets.)

Part of figuring out how the pieces come together is a question that was brought up in Discord, as to whether the assumption of "1 weapon = 1 attack" for melee really makes sense, or if a better assumption would be that, say, a large weapon can attack in a sweep, or that a lighter weapon can attack fast enough to hit multiple targets in a comparable time frame. I don't generally work from a paradigm of "TTRPGs should have weapon-speed mechanics," but it's not as if this is an unknown concept in the RPG space -- indeed, the entire conceit of "DPS" tracks back to the need to make an apples-to-apples comparison between weapons of varying attack speeds, a concept that I think most people of my vintage would attribute to being pioneered by World of Warcraft. It might be the case that in a design ethos like the TNP sequel (where the expectation is that there will be push-button, dice pool bonus, massive "finishing move"-type powers) it makes sense to have the "at-will" combat abilities be a little more flashy and showy than just "1 weapon = 1 attack."

...

Alright, that wraps up posting for this month. Expect the next post to be up on October 10th.

Building out "2d6 + pool" and other Sequel stuff (2025)

Let's talk sequel mechanics.

Say you're making an unarmed strike. The basic idea would be that you would roll 2d6 vs. the defender also rolling 2d6. On a success, you would deal damage equal to your STR "modifier" -- so, if that number is +1, it would be 1 damage, or 3 damage if the modifier is +3. Now, add onto that, using a proper/proficient weapon for your character would add 1d6 to the pool for this attack; what this means is that you would instead roll 3d6, selecting 2 dice for the attack result and 1 die for the damage result (to be added to the STR mod.) The defender would then roll their 2d6, after attack dice have been assigned; if you're having flashbacks to the RISK episode of Undergrads, you're not alone.

Now, I received some specific advice (from the people who brought you Strike!) that, "a 2/3rds accuracy [means] If you attack 4 times, you'll miss 3 or 4 of them 1/9th of the time." In other words, without constant luck-mitigation mechanics, 66(ish)% hit rate means that someone will have a very boring time in combat, for 1 out of every 9 combats. As such, I've decided to tune the hit chance for the TNP sequel slightly up, from this number. By setting a baseline of 3d6 vs. 2d6 (and where attacker succeeds on a tie) we achieve a 72.42% hit rate, if the calculation is assuming that the attacker simply takes the 2 highest dice every time (which is about the easiest way I know how to calculate it, in anydice.) Now, that's not to say that we couldn't tinker with this, by adding modifiers to the defense; I just felt it would be easiest on the DM to not have to assume they will always be adding something to the defense roll, which they would need to look up or otherwise memorize.

The other thing we need to assume is that the attacker will regularly be adding dice to the pool, either via encounter/daily type powers or "teamwork bonuses" (as I tend to refer to them) such as flanking, Bless spells, debuffs to enemies, etc. As such, the DM doesn't necessarily have to feel bad if they do beef up enemies defenses a little bit, since the party should have tools to overcome them mathematically.

The other side of the coin is, if enemies are assumed to not have access to the attack-buffing utility that the players have, to what extent should the players' "armor class" get buffed beyond a simple 2d6 roll? At first glance (with flat bonuses being such a potentially big shift in the math) it seems like only the heaviest armored PCs would get even a +1 bonus... possibly a +2? But then this bends back around to the question of, "if a Monk doesn't cast spells, do we let them use their WIS stat as a bonus to AC?" Would that potentially make them the hardest character class to hit? The knock-on problem with that is the presupposition that in the sequel, ALL characters have 10 HP (maybe letting them add their STR, since there are no plans for a Constitution attribute.) I can say with a high degree of certainty, that a character with 2d6+3 AC and only 10 HP is a lot more unkillable than one with 2d6+1 AC and 13 HP.

Now, bringing things back to the example from the start of this post, the conundrum I run into is, "well if adding a die to a melee attack is dependent upon using a weapon," then how do we make this math work, with spells? The example keeps breaking down for "basic attacks" whenever I come back around to applying these mechanics to spells. Do we just say, "actually, screw it, spells are just a 3d6 pool by default, for no reason" or should this be keyed to something like lowest mental stat? It almost feels like (particularly assuming 2 mental stats, and not 3) that we'll end up with the lower stat applying to basic attacks, and the higher stat effectively being the "dice pool stat" for encounter/daily powers.

If the intention is that the plinking stat always needs to be a +1, that further inclines the designs towards having 3 mental stats rather than just 2 -- otherwise you'd naturally expect all spellcasters to put a +2 in one spellcasting stat, and a +3 in the other. This might be workable, after all, so maybe you just say "spellcasters have a dice pool advantage over martials, but they don't get to add their modifier to damage rolls," or something. This has a very 5e vibe to it, where spells generally only deal dice damage, with no modifiers. Also, having to rig the math so that "basic spell attack bonus" is always your +1 stat, and can never be higher...? It ends up feeling gamey and arbitrary -- one of those moments when you can look at the game and all you see is the design spreadsheet, instead of the immersion you should feel, when playing.

The problem with saying "X mental stat does at-will damage, Y mental stat does encounter/daily damage" is you end up with the problem of every spellcaster putting a +2 in X and a +3 in Y -- assuming they all get at-will spells... This would mean things potentially get to be very "paint by numbers." This creates a potentially interesting design space, though. To wit, in 2014 D&D (5e), the "half-caster" classes expressly don't get cantrips (i.e. at-will spells) so it's not as if the idea of siloing off these sorts of mechanics is particularly new. There's also the possibility of say, having the Cleric/Paladin type class use only weapons for attacks, and their spells are only used to heal rather than do damage. This would beg the question of, "OK, so is every Cleric and every Paladin just going to max STR, and then one puts WIS as their 2nd stat but the other makes it CHA" and there's no real difference? Or do you let the Cleric have cantrips, so that they at least put a +2 in both/all mental stats? Ultimately part of the question is how much utility there is to be gained, by hanging the mechanics for both classes off of one chassis in the first place. (TNP succeeds at this by using class dice; regardless of subclass, you're using the same dice, so the mechanics will at least have that much in common.) Maybe the distinction can be as simple as all Cleric healing can be done at range while all Paladin healing must be done from melee/touch distances. 

It seems more and more obvious that the applications of mental stats in spellcasting will be class and/or subclass specific; if there is to be a difference between a Wizard and a Sorcerer, the obvious one would be that the offensive punch would come from INT and CHA, respectively, for those classes. Likewise, it might be the case that a Warlock uses CHA offensively but a Paladin uses CHA defensively. You can also build in some exceptions-based design, like maybe "Warlocks always use CHA for offensive spellcasting [even if it isn't their lowest mental stat, i.e. for at-will spells]" with the tradeoff being that they don't get per-day spells, as such -- again, this is sort of the conceit of the Warlock in any D&D edition besides 4th, but it carries a decidedly more 5e vibe to it.

...

Harkening back to the Eldritch Horror boardgame, one of the things that I dislike about it mechanically is that it is such a mishmash of mechanics. Normally you succeed on a 5 or 6, but Bless increases that to succeeding on a 4, whereas Bane reduces that to only succeeding on a 6. The game also has mechanics that let you reroll one of the dice in your pool, but also to add dice to the pool after the fact. In my opinion, it could benefit from picking one of these mechanics and sticking to it -- as you might guess, my preference would be to just expand the dice pool. A similar train of thought came up with regards to the sequel mechanics; if a mechanic allows for a bigger pool of dice for the damage... should we simply say, "You can also use the attack roll dice as damage roll dice [as is possible with some of the class dice bonuses, in TNP]"? Or should the attack dice always be excluded from the damage roll, but the dice pool should be made even bigger?

If the attack dice are allowed to be used as damage, this would incentivize putting the highest possible rolls towards the attack -- which removes some of the gambling aspects of using an "average" attack roll, to try and boost the damage roll higher. That is to say, it essentially works against the spirit of what the dice pool mechanic is trying to do, so my instinct would be to simply expand the pool instead. This kind of tilted me towards using the "attack as damage" mechanic sparingly, if at all -- such as, maybe only having it apply to daily powers. This mechanic would, however, interact in interesting ways with a "power attack" mechanic, which might stipulate having to use your lowest die from the pool as one of your attack dice, in exchange for adding 1 die (or more) to the pool; it sort of brings that gambling aspect back to the table.

---

A fairly long post today, albeit mostly speculative. Hopefully this will bring some results in the near future, and I can start to narrow down the designs and bring things into sharper focus.
Next post is planned for September 30th, so check back then!

Leveraging Synergies (2025)

A recent topic of discussion on the TNP Discord was how D&D 2024 compares to TNP, in terms of what it's doing with skills.

In 5e, you have a proficiency bonus that scales up as you level (starting at +2) and generally speaking, you get proficiency with 4 skills -- 2 from your class, and 2 from your background. Certain features (such as Jack of All Trades, for the Bard class) let you add half of this bonus to your skill checks; other features allow you to add double this bonus, a mechanic which is typically referred to as "expertise." Barring these outliers, your proficiency bonus will scale up to +6 and your ability mods will cap out at +5; a +11 modifier effectively means a 10% success rate against a DC30 (i.e. only a d20 roll of 19 or 20 would succeed.) Most DCs in 5th Edition are done in increments of 5, with each increment representing a 25% swing in difficulty; with advantage, a d20 roll with no modifiers vs. a DC10 is equivalent to about a +5 bonus, or about 25% (coincidentally).

As you can probably guess, this leaves 5e with a fairly narrow band of DCs it can meaningfully use. So with the 2024 rules, they've tried to crowbar in advantage, if/when you can reasonably argue to the DM that proficiency bonuses from a skill/tool/etc. would overlap for a given action; instead of stacking/doubling these proficiency bonuses, the DM is instead encouraged to grant advantage on the check. The problem is that not all skills have a tool which makes an obvious pairing with them, causing a difference in effective DC of potentially 25% (the difference between advantage vs. a straight roll.) In short, this is an afterthought, and that's why it's mechanically/mathematically unsound.

If we go back to 3.5, there was a system for "skill synergies" whereby 5 ranks in a given skill granted a +2 bonus to a related skill. Even this was a very "pick & choose" kind of affair, where it was not universally applied. By contrast to what 3.5/5e D&D are trying to do, both TNP systems have skill synergies built into their baseline assumptions. Every "core" skill falls under an Attribute and a Skillset; what this means is that adding bonuses to a skill always increases the bonuses to the other skills that are related to it.

For example, in 3.5 having 5 ranks in Bluff gives you a +2 to Diplomacy and Sleight of Hand checks. In TNP, if you increase your Subtlety skillset, that would increase both your Bluff and Sleight of Hand skills; likewise, increasing your CHA attribute would increase both your Bluff and Persuasion skills. Because all core skills fit somewhere on the grid, this built-in system for synergy works across all core skills; the skillsets effectively serve as another vector (in addition to attributes) by which thematically-linked skills are able to be synergized. In TNP, you can gain training and/or a bonus rank in either the attribute or the skillset for a given skill; instances of overlapping training do not stack, but they do provide the "mastery" bonus to such skills. In the sequel, each bonus to a given skill's attribute or skillset would add an additional d6 to the pool for that type of skill check.

Now, admittedly, where this idea falls short in the TNP systems is with knowledge skills; although they are grouped by power source (and only half are unique to a given power source) power sources are not given a "score" nor do knowledge skills have "skillsets" or any other such 2nd vector to group them together. In TNP this is somewhat remedied by additional ranks (beyond 3rd) being more readily available, for knowledge skills. As for the sequel mechanics, those details are still being worked out.

I think a strength of the 2d6 ethos for the sequel is that every die you add into the pool has the potential to matter. One complaint I've heard about older versions of the World of Darkness system is that it's still all down to random chance; you roll X number of d10s, and need a 10 to show up, in order to succeed. Likewise, when I play Call of Cthulhu-based boardgames, you end up needing a 5 or a 6 on a d6 in order to succeed; if you fail, you spend a token and gamble again. In both cases, your previous failures don't get you any closer to success. (Worth mentioning here, most newer versions of Axis & Allies, including some 3rd-party off-shoots, allow for previously-failed technology rolls or "tech tokens" to accrue towards eventual success at such research.) With the sequel mechanics, the fact that you are always adding 2 dice together, means that you avoid the pitfalls of the WoD and CoC systems, because low rolls are still potentially useful and therefore worth something. The other thing is that having 2d6 as the DC provides some variability in which results will succeed, as well; obviously, high rolls always have a better chance at success, but nothing is out of the realm of possibility in an "opposed roll" paradigm.

---

Running a few hours behind schedule, but managed to stay caught up for August.
Look for the next post around September 10th.

Conventional Wisdom -- Part 2: Class Breakdown (2025)

Just to give some context, I feel it's helpful to recap what the projected class list for the TNP sequel is shaping up to be:

1. Cleric/Paladin thing
2. Sorcerer/Wizard thing
3. Druid/Ranger thing
4. Monk/Rogue thing
5. Barbarian/Fighter thing
6. Necromancer/Warlock thing
7. Bard/Warlord thing

So, specifically, how does this relate to our question of "WIS stat: yes or no?"

The first thing I think of is, if we're structuring mental stats sort of like the physical stats, then it might be the case that there's one stat for offensive spells, one for healing spells, and one for determining the number of targets of your spells. If class #1 and class #7 are meant to be healing classes, then the obvious solution is for them to use CHA as their healing spell stat, since that stat would be somewhat ubiquitous to those archetypes. Ok, so what about class #3? You could possibly make an argument for INT being their healing stat, but WIS is clearly the more obvious choice.

This is where we get into the problem of, "the Wizard is the best at Religion, because the Wizard is the best at INT." How do we solve for this? Do we make the spell functions of the attributes be class-specific? Do we make the knowledge skills for each class function off of their key mental stat? Do we do both? Really, when trying to make attributes work properly, we need to use them in ways that work mechanically, but also reinforce the expectations that the lore and the archetypes impose on the game. And it must be said, that in a non-multiclassing paradigm, it is much easier to fiddle with these levers.

As a bit of a sidebar, this also brings up the lack of utilization of the INT stat, in modern D&D. Without going into detail, this stat has lost features from 3.5 to 4e, and from 4e to 5e. It's only used as the spellcasting stat for Wizards (and later, Artificers) as well as Eldritch Knight (the Wizard version of Fighter) and Arcane Trickster (the Wizard version of Rogue.) So is this something we should try and "balance out?" It seems that the Necromancer half of class #6 could possibly focus on INT; Druid and Ranger could utilize it more, and maybe Cleric, too? What about for class #7? It feels like you could almost do something with keying certain class features of theirs to the INT stat, but not outright spellcasting. How does class #4 fit in? Is Rogue the INT version and is Monk the WIS version?

The other question to consider is if certain spellcasting classes are meant to be completely shut out of healing, then does it really make sense to have 3 (potential) spellcasting stats? Does it make sense to split offensive and defensive spellcasting across 2 stats, to begin with? 5e D&D doesn't do this; each class uses one stat for all of their spellcasting (and often use the same stat for their class features, too.) So should the point of differentiating a Cleric as a WIS caster and a Paladin as a CHA caster lean more into differentiating their skills? In that case, it seems that the implication is that the spellcasting stat (if indeed there is to be only one) for each given class, should be the stat that most closely aligns with the expected skillset of that class.

Again though, this butts up against the problem of who's the odd man out, when it comes to skills like Religion: if you make it a WIS skill, Paladins become bad at it, and Rangers become good at it; if you make it a CHA skill, Bard/Warlord characters are suddenly good at it, but Druids are suddenly worse at it. I feel like the way to avoid this while keeping 3 mental stats, is to make each "class skill" from the knowledge skills just use your highest mental stat. The alternative is to see if we can pare the stats back down, and somehow rework the "power source" framework to be functional with the new implied math.

The other vector to approach it from (particularly if your "good skills" are supposed to use your highest mental stat) would be to ask, what are your "good saves" supposed to be? This harkens back to the previous post, where essentially we have to ask, "What does each save do?" If Paladins, Bards, and Warlords are meant to be good at CHA saves, does that mean their minds are hard to dominate -- or is that meant to be represented by characters with high INT? Or high WIS? The other question is, what else is a non-spellcaster (such as a Monk) getting out of picking one mental stat over the other? The classic answer would seem to be something like "add your WIS to your Armor Class," and particularly in a non-multiclassing system, that seems highly workable.

(I also find it slightly telling, that out of 7 classes, there are only 2 you could reasonably classify as purely martial; I feel like this is reflected in the class utilization of 2014 D&D as well as the reworks in 2024 -- which expands spellcasting for most classes that have it. Unlike 4e, where all classes have powers, 5e really is a return to all powers being spells, and so only spellcasters have real powers -- thus necessitating the overabundance of spellcasting classes.)

...

We'll look to do one more post, by August 31st -- otherwise the intended 4th post for this month might have to be punted to later in the year.

Conventional Wisdom (2025)

I had mentioned in a previous post that I'd like the sequel to TNP to have a Wisdom attribute. So far, that hasn't managed to work itself into the designs, but maybe it should.

As far as the physical stats go, it's seeming like STR will be the two-hander damage stat; I'm moving off of the idea of adding dice for two-handed weapons, and instead leaning towards adding twice your STR mod to the damage roll. This would make it a little easier to balance against TWF, where maybe the damage mod would be the lower of DEX and STR (or you use STR for the mainhand, DEX for the off-hand?) The thing then is how to operate ranged weapons in this paradigm. The idea to this point is that they would have a low (or no) mod, but you could attack multiple times (likely a max of 3.) The idea being that this number of attacks would likely be based off of your stats -- either DEX or AGIL.

Where I've hit a snag is when trying to figure out how this translates to spells. Is there a "number of attacks" stat, or a "number of damage dice" stat? Should there be a stat that's only used for healing, rather than damage? Probably it would make sense for the stats to work differently for each of the spellcasting classes, so there would be no "hard and fast" rule for how the stats work, the way that there could be with plain old weapon attacks.

It almost seems like rather than just being a straight repurposing of TNP's 5 attributes, the sequel mechanics demand there be another mental stat. The case for this is also helped by the fact that "power sources" as a mechanic don't... quite function as intended; does each class have a 'score' with 2 different power sources, and that's how your knowledge bonuses are divvied up? The problem with that is it's effectively duplicating the mechanic of attributes, without the corresponding skillset mechanic to back it up.

So perhaps it makes more sense to reinvent the wheel, and slot the knowledge skills under attributes again, adding Wisdom back in as one of them. Then essentially what you end up doing is going, "well if X is the Cleric/Paladin spellcasting stat, then Religion should use X stat." The problem is that you end up with the Venn diagram where druids are probably supposed to be good at Religion, but also good at "nature" skills -- so do those skills all use the same stat?

I've always thought (particularly in a non-multiclassing system) that it'd make sense to just let each class use their highest mental stat for any knowledge skills on their "class skill list," so to speak. Is that a better way to handle knowledge skills, vis-a-vis attributes? Since there are only 10 knowledge skills, I think you could easily cover them between the 3 mental stats, without too much trouble; the outlier would be something like Animal Handling, which is meant to sub in for riding/using mounts -- something that maps more to Agility than to a mental stat.

The other thing that this gets into is whether the sequel will have traditional saving throws, or not. From the 3.x perspective, INT or CHA saves seem to make no sense -- so why does 5e have them? I agree that they're poorly defined. I also would take it a step further and say that I personally don't understand how WIS became the default mind-affecting/mind-controlling/Vicious Mockery-ing save. WIS being related to "will power" or a WILL save seems to have more to do with alliteration and inertia than anything else; CHA being an option for your WILL stat (in 4e) vibes with "force of will" or "force of personality" (if not outright "will power" -- the difference seeming academic) being tied to Charisma moreso than to Wisdom.

If INT is the go-to "big brain" stat, you could win me over with an argument that INT is the save used vs. mind control. Really, I find myself asking, "Why isn't everything an INT save or CHA save, instead of leaning so heavily on WIS?" If you start from the assumption that mind-affecting spells should either be INT or CHA, what does a WIS save even get used for? It's particularly hard to imagine any of the mental stats really being used for "saves as opposed checks" where you're not really saving out of a combat effect... but that begs the question of "isn't that just a skill check?"

Maybe if WIS is tied more to senses/perception, then WIS saves become more about saving against things like stunned/blinded/deafened; having WIS back in the lineup means skills like Perception and Insight don't necessarily have to be shoved under INT and CHA (respectively) either.

I'll have to sit down and really hammer out the details more. But overall, I feel like this would be one of those rare cases of "addition by addition." Hopefully working WIS into the mechanics solves more problems than it creates. In particular, I think it'll be interesting to iron out how having 3 mental stats will work, with regards to spell mechanics.

...

It's always rough coming back from a break, especially in summer when the weather is nicer -- hence the delay.
Next post should be between the 21st and 25th, with a 4th post before the end of the month. Stay tuned!

Sequel Mechanics: Initiative (2025)

I know I had said previously that I would be interested in trying to make initiative checks back into a form of skill check, but I've since realized that's a bad idea.

The whole point with a d20 initiative roll is to actually provide some dispersion of the numbers, so there's less worrying about tie-breaking, or everyone's numbers being bunched up together. If you're doing a d6 pool and taking the highest 2, you're actually getting the opposite effect; similarly, this is why TNP still uses a d20 initiative roll, rather than a d10+d6 skill check.

Since the default mechanic for most rolls in the sequel will be some variation on 2d6, my first intuition is to have it so that initiative checks start with 2d6, and then add 1d6 "per plus" of Agility, to the pool. So a character with a +3 Agility would roll 5 dice, and the total of all of those 5 dice would be their initiative count. I feel like this would be a good compromise, providing the desired variance while also giving a tangible benefit to having a higher attribute.

The interesting thing with that idea, is you could then use the attribute as a tie-breaker if needed. For example, if someone with a +1 Agility rolls 18 on 3d6, and someone with a +3 Agility rolls 18 on 5d6, then the person with the +3 would win on the tie-breaker. It also makes my brain tingle a little bit, because instead of everyone randomly rolling a number between 1-20 and slapping a modifier on it, your attribute effectively determines the ceiling for how well you could possibly roll; a +0 would cap out at 12, while a +3 would cap out at 30.

Initiative sort of naturally avoids the pitfalls of needing a "release valve" for excessive dice, since the number can basically go infinitely higher. This makes it easy to have any initiative bonuses just add dice to the pool, rather than use something like advantage on a d20 roll, for example. Likewise, with 2d6 as the minimum roll, it's easy enough to have a -1 dice pool penalty as a baseline mechanic.

---

Another relatively short post for today, since it's a pretty quick topic.
In the background, I'm still working out ways to get the other mechanics ironed out w/r/t weapon dice and spells and attributes and such.

Next post will hopefully be on or before June 17th, with one more post before the July break.

Balancing Act: Combat Attributes (2025)

I mentioned previously that the relationship between the d6 pool and "weapon dice" could be one where 2-handed melee weapons add 2d6 whereas 1-handed melee weapons or ranged weapons only add 1d6. The question is how to balance out the utility of these different loadouts. Obviously, there are a few assumptions we need to start from, in order to lay the groundwork; probably there will only be one of your five attributes going as high as +3 (with likely a single +2, and either two +1s or two +0s to round things out.) The other thing is that the baseline assumption of the math is that you will always use your two highest dice for your attack roll; this means that your damage roll will consist of the remaining (i.e. lowest) dice in the pool.

Without accounting for hit chance, the lowest 2 of 4d6 (i.e. two-hander) averages to 4.66
Similarly, if we take two swings with a one-hander (i.e. two-weapon fighting, lowest 1 of 3d6) the average is 4.08

However, when we account for the dice pool attack vs. a 2d6 defense roll, the two-hander is actually going to hit about 10% more often -- meaning the damage modifier needs to bring the TWF routine up to a damage number that's about 10% higher, in order to be comparable in utility. When we factor in a +2 damage modifier for both attacks, the damage is still behind the two-hander (assuming it's at a +3 damage modifier) -- 8.08 vs. 7.66, without factoring in hit-chance. So, that might need some more fine-tuning.

The initial idea I had for balancing out ranged attacks was to use the lower modifier (between STR and DEX) for damage, but allow a number of shots based on Agility mod. The question really then becomes, how do spells even work? Is it just INT mod for number of attacks, and CHA for damage? Is it class/subclass dependent? Is one stat used for damage and one for healing?

This is actually a thing I had narrowed down (somewhat) in my previous RPG designs; basically, weapon-users could attack twice, and magic-users could target one square and all adjacent squares to it. Maybe that'd have to be sort of a class-level of feature, since not all casters are "blasters" per se. The other thing was that I had weapons be sort of an extension of spells, so if you used a dagger or wand, it'd be 1d6 and greater targeting capacity, but if you used a full length staff, it'd be 2d6 with more of a one-target aim. Maybe the baseline for spells in the TNP sequel need to start from something similar?

...

Bit of a shorter post today, as things are a little busy lately.
Hopefully June will be a bit closer to the planned blogging dates; check back on the 5th or 6th.

Power Sources: The 6th Attribute?

I've been giving some thought to how TNP compares to D&D, as it pertains to skills.

If you think about how skills work in 3.x, 4e, or 5e D&D (the versions I'm personally familiar with) there are two main components: ability score modifiers, and skill points/skill training/skill proficiency, respectively. In TNP, skills are linked thematically along two vectors (Attributes, and Skillsets) whereas in D&D skills only share ability modifiers in common, and the remaining skill math varies completely independently; the exception to this would be skill synergies in 3.x, where 5 points in [skill X] provides a +2 bonus to [skill Y].

That all being said, where TNP veers off from this structure is with Knowledge skills. Where D&D uses INT (and sometimes WIS) for its knowledge skills, TNP instead keys them to Power Sources: Arcane, Divine, Martial, Primal, and Shadow. But with TNP having only 5 attributes instead of 6, I've been starting to wonder (particularly in the context of the sequel mechanics) could power sources be treated as a "6th attribute" for your character? (i.e. 5 universal stats and 1 variable one, rather than 6 that are universal.)

The quirk with knowledge skills in TNP is that they are grouped together, like a skillset (sort of) but they lack that 2nd vector linking them to anything else... aside from other power sources; each power source consists of one unique skill, and 2 other skills that are each shared with different power sources. Coming back to sequel mechanics in particular, with the core skills having both an attribute bonus and a skillset bonus to their dice pool, how would you do something similar with knowledge skills? My first thought was that since in TNP, all classes basically have 2 power sources, you could just... do that again. The problem is not all power sources overlap with each other, and unique knowledge skills don't overlap at all; in short, the extra math has to come from somewhere.

So should power sources be linked to skillsets? There's some synergy between the two in TNP, so maybe power source and skillset could be the two vectors linking knowledge skills together. For example, with Infiltration linked to the Shadow power source, a +2 Infiltration skillset bonus could be applied to Streetwise, Dungeoneering, and Local knowledge skill checks. Because of unique skills being their own thing, it seems that power sources would need their own bonus -- but then you end up with all skills in that "set" having the same bonus. However, if it is assumed that all characters have two power sources (say, one with a +2 and one with a +1 bonus) that could at least give the shared knowledge skills some variance. The issue with that being, now we're talking about a "7th attribute" and not just a 6th.

I came into this talking point from a place of trying to cram knowledge skills back into an "ability score" framework, after TNP successfully extracted them from that. And I feel like I'm not any closer to solving that puzzle. It doesn't make sense to give all knowledge skills a flat bonus, but it also doesn't seem to make sense giving all knowledge skills within one power source the same bonus; it seems like the more "a la carte" approach of TNP is all that works. We'll have to see how thing go, as the design process carries on.

...

I've got one more post planned for May, so check back by the end of the month for that.

Death of the DC10 -- Part 2: Rise of 2d6 (2025)

Slowly but surely, the sequel mechanics seem to be rounding into form. The initial conceptualization of something focusing on a "d6 pool" engine seems to now be pivoting into a 2d6 engine, with d6 pool features. So let me unpack all of that, a bit.

In a previous post, I touched on the fact that TNP has 5 basic types of rolls: attacks, saves, skill checks, initiative checks, and base damage rolls. With the 2d6/d6 pool mechanics, the sequel is moving more towards combining attack rolls and damage rolls together; the quintessential idea is that you will pick 2 dice from the pool to use as your attack roll, with any remaining dice being used for damage. There might be a power attack mechanic that (for example) allows you to add dice to the pool, but requires you to use the lowest die from the pool as one of the attack dice; there might also be mechanics ("Daily" powers, as a potential example) which allow the attack dice to be counted in the damage pool as well as the attack roll -- not unlike how some of the class dice bonuses function, in TNP.

(Similarly to 5e, my intention with the sequel is to turn initiative checks into just another type of "ability check"; in the TNP ethos, it makes sense to use Agility for this purpose for a couple reasons, not the least of which being that STR and DEX are assumed to be the weapon attack attributes, while INT and CHA would of course be the spell attack attributes. This change would further simplify the number of basic roll types.)

Now, the idea has come about to replace the DC10, and it's looking like the replacement will be 2d6+mods. For one, this effectively lowers the DC to 7+mods; as mentioned in the last post on this topic, having an attack roll of 2d6+2 vs. DC10 is functionally the same as 2d6+0 vs. DC8. By transitioning the DC to 2d6, this acknowledges the realities that the attack rolls were facing, while also allowing us to remove "ability score modifier" math from the baseline assumptions. For skills, the variability in the DC also means that we remove the issue of "only 5s and 6s matter"; this makes the 2d6/d6 pool mechanic way more viable for skills, without having to incorporate something like the two-stage roll that was proposed before.

By de-coupling ability score math from attack math, we can actually look at expanding the range of modifiers again. I think probably what will evolve as the basic structure of the classes is that one attribute will be your damage modifier stat, and another attribute will be your "dice pool stat." So, for example, as a paladin you could have a +2 STR that adds to every melee damage roll you make, and a +3 CHA which adds dice to every Divine Smite spell/attack that you use -- or you could flip the two, if you want to trade higher burst-damage for more reliability. This has come as something of a revelation recently, and I think it'll open up the designs a lot more; ironically, by going back to the TNP ethos of not having attribute math contribute to attack math, we're actually able to do more with attribute math, and not less.

Since the baseline assumption is that an attacker will be rolling at least 3 dice, I'm leaning towards the idea of one-handed melee weapons and ranged weapons representing the 3rd dice of the attack; two-handed melee weapons would be 2d6, essentially adding a 4th die to the pool. There might be some tinkering around the edges, as to how this works; my first intuition is that two-handed weapons and unarmed attacks (i.e. straight 2d6 roll) would gain a +STR mod to damage, while one-handed/"two-weapon fighting"-type attacks could have the option to add STR or DEX -- or maybe one for the 1st attack and the other for the 2nd? (Ranged weapons might add no mod, or the lower of the 2 mods, but that might be unnecessarily fiddly.) This would still need to be balanced out against spellcasting; it might be the case that spell mods (such as INT and CHA) would simply add dice to the pool, but not damage modifiers. But that also begs the question of, which attribute modifier would spellcasters use, for push-button "Daily" powers, or similar effects?

I've floated a few ideas as to how defenses/"saves" might work, but so far I think the most compelling idea is having saves tied to effects, rather than saves tied to attributes. I think there will likely be an "Armor Class"-equivalent that is tied to class bonuses/features; having Agility tied to both AC and initiative seems overbalanced, so I'm probably going to try and avoid that. In general though, the DM can use 2d6 in a pinch to determine success or failure; skill check DCs can be nudged up or down using small modifiers, but I think the general assumption for monster "save" DCs should be an unmodified roll.

The other interesting quirk about a 2d6 baseline assumption is that it also still allows room for mechanics based around rolling "doubles" or "ties." And since 2d6 is the backbone of each type of roll (attacks, saves, checks, and opposed checks) you can have classes or other features apply different bonuses on doubles, to each type of roll -- almost akin to how 'mastery' in TNP works as sort of a universal dice modifier.

All of these things have made me very positive about the direction that things are going, with the sequel development. I think the current implementation of the d6 pool mechanic now does an adequate job of filling the design space left behind by 'class dice'. I also like that despite axing the d20, DC10, and other things from TNP designs, the ACIDS "skill grid" and the Knowledge skill/Power Source paradigm have been able to remain intact, giving a strong foundation to build upon.

...

Apologies for the delay in posting; I'm hoping to cram 3 posts into what remains of May, so that we can keep on track. Check back around this time, next week!

The Death of the DC10? (2025)

Without completely rehashing the conversations that came to light on Discord, I'll summarize some of the key points.

Essentially, the DC10 is one of those elements that the current sequel design retains from TNP; an argument could be made that it's vestigial, or that it's one of those "ship of Theseus" situations -- but on the other hand, you have to start somewhere. Where it seems to be at loggerheads is in the particularly sequel-ish notion of adding flat modifiers into the mix. To wit (and, in short) if the assumption is that your combat rolls will always add your highest stat (i.e. a +2) then the DC isn't really 10, it's more like it's actually an 8.

So, one direction in which that conversation forks off is, how do we incentivize variety in combat modifiers? Well, essentially you would have to structure a class' basic features such that the +2 was always (or at least, often) adding dice to the pool. The math tells us that a +1 increase in attack is about equal to adding one more d6 to the pool, so the bigger incentive is going to be adding the die, because it also adds a d6 of damage (and not just +1 damage.) Alright, but since our acceptable range of modifiers is already so limited (+0/+1/+2) how do you iterate that idea over, say, 6 different classes? This idea also solidifies the notion that the attribute array would have to be limited to a single +2 -- otherwise, you'd put a +2 into your attack stat, and a +2 into your "dice pool" stat, because that's a no-brainer.

Now, this sounds like a nitpick, but part of the reason I chose DC10 in the first place is because of the ergonomics of it; 10 is the first double-digit number, it's also ingrained in 10-fingered humans (which is likely the reason the base-10 number system exists.) But as I've said before on the blog, where it really came from was if you strip away your +3 attribute and +2 proficiency when trying to hit an AC15, the math of +0 vs. AC10 is exactly the same. But that's talking about d20 math, and the sequel isn't in that paradigm at all, anymore.

So the first idea that occurred to me was to strip out the modifiers; to keep the math the same, we'd have to arrive at a DC8 -- at least for a basic combat roll involving 3d6. Well, 5 is a nice starting point (for the reasons mentioned previously) and adding the number of dice to that gives you 8. So maybe the DC is "5 + [number of dice]" instead of just a flat 8. What I quickly found with that is the DC escalates slightly, for almost no meaningful change in hit-chance; this felt like it was adding overhead to the mechanics with no subsequent added functionality.

Building off of that, the next idea that popped into my head was, "what if the DC was [number of dice] * 2?"

What this would functionally do is lower the DC of the 'basic attack' down to 6, giving a much higher hit chance and reliable damage output; it also creates a cap where having 6 dice in the pool bestows steep diminishing returns, and 7 pushes the DC into impossible territory (i.e. 2d6 cannot equal more than 12, and 7 dice would create a DC of 14.)

With a little help from the people who brought you Strike! RPG, I was able to get a very precise calculation as to what the math would look like on this (rather that just ball-parking it, with my limited mathematical knowledge.) Using the two lowest possible dice (which still produce a hit) for the attack roll, and the remaining dice for damage, we get:

3d6 DPR = 3.58
4d6 DPR = 5.40
5d6 DPR = 5.93
6d6 DPR = 3.21

The question then is, does this give us enough flexibility to build out the mechanics? Clearly, the answer is "not quite" since this would effectively cap the number of additional dice you could add to the pool at 2 or 3; the only way you could get around that is to cap the DC at something like 10 -- go figure.

The other thing we have to remind ourselves is that without using modifiers, "only 5s and 6s matter" starts to creep back in. (It genuinely makes me wonder if the Arkham Horror-type games are built around the assumption of 5s and 6s being successes, for this same kind of reason -- or it could just be a coincidence.)

And that's pretty much where I sit, at the moment -- stuck between a rock and a hard place. It seems silly to have flat modifiers that don't matter, but it seems nearly impossible to diversify those numbers, either. On the other hand, if you go back to the paradigm of "attributes only matter for skills" then we've just reinvented d20 TNP (seemingly right down to the DC10, even) -- almost like building that ship of Theseus I mentioned at the start.

...

April should be a lot better for sticking to the planned schedule of 5th/15th/25th, so check back on those dates, for more!

Double or Nothing (2025)

I was giving some consideration to the skill mechanic proposed in the previous post; to wit, a baseline +0 mod would result in a straight 2d6 vs. DC10 roll. This has pretty low odds of success (1/6th) compared to the d20 baseline of 1d20-1 being about 45%

So what if we do something with rolling doubles? 5+5 and 6+6 would already make a success, but the other 4 combinations (out of the 36 possible, with 2d6) makes for an 11.11...% outcome; if you add this to the 1/6th chance, it becomes 27.77...%

Now, clearly, based on the numbers in that previous post, we probably wouldn't want to shift all of the other odds up ~11% so probably this mechanic would be limited to when you're only rolling 2d6 on a skill check.

But maybe there's something we could do, using the doubles with attack dice.

If the baseline roll is 3d6 (2 used for attack, 1 used for damage) there are 216 combinations that can result; matching pairs would exist in 36 of those (including triples) 24 of which would be combinations other than [5,5,X] or [6,6,X] ...which again results in 11.11...%

If we go back to another previous post, we laid out the attack math, where a +2 mod resulted in a 68.06% hit chance, and a +1 mod resulted in 52.31%; increasing either of these numbers by ~11% keeps us still well within acceptable hit-chance ranges, which is pretty interesting! The question would be, how do we apply this sort of bonus? A boost of this size actually pretty closely mirrors the usage of "Combat Mastery" in TNP, so it stands to reason that this bonus could apply in similar situations. (The other bonus mechanic in TNP being class dice bonuses, which the sequel mechanics would mirror/mimic by using the d6 pool mechanic.) Also worth mentioning: off the top of my head, it wouldn't change damage-roll outputs very much; only a combination like [4,4,6] would actually produce a meaningful damage boost (by allowing the 6 to be used for damage instead of attack, while still producing a hit.)

I think if the general ethos of the game's mechanics is to roll a pool of multiple dice but ultimately only use 2 of those dice to determine the result, then including something like doubles adds a fun layer to it. Obviously, once we go beyond 3d6 and start to account for a bigger dice pool, the math would get more complicated.

It also recently occurred to me that the previous post basically took the 3d6 math, and put a new slant on it. As mentioned before (when looking to other possible dice mechanics) the ranges for flat modifiers on 3d6 vs. DC10 are extremely narrow; basically only +1/+0/-1. What the previous post did instead, was basically turn the flat modifier into a die pool, using the 3rd die (i.e. 2d6+[highest 1d6, of the pool] instead of "3d6+X"). Having a two-stage skill check roll is still a little bit janky, but I think something like that was sort of inevitable, in a "d6 does everything" mechanical paradigm.

However, by adding doubles to the success pool, we actually decrease the necessity of rolling the dice pool, albeit only by that ~11%. It speeds things up a little, because results like 2+2, 3+3, and 4+4 (which would still mathematically have a chance to succeed, with a 3rd die added to them) are instead just fast-tracked to being successes, bypassing the need for that 2nd-stage of the check.

...

One more post is scheduled before the end of March; to try and keep things on track, it'll likely be out by March 28th at the latest.

Reverse Engineering (2025)

I've been thinking on how to handle the skill check mechanics for the sequel, and I realized the original idea had gotten away from me, somewhat.

In TNP, the skill "check" die is a d10, and the bonus die is a d6; to mimic this in a d6 system, the obvious thing to do would seem to be replacing the d10 with 2d6. But somehow I'd gotten to a place where it had morphed into some variation on "d6 pool for everything, all the time," and it still seemed to miss the mark. Without beating a dead horse, the effective mod range is a bit limited, and the dice rolls that matter are likewise pretty limited. So I went back to the fundamental 1d10+1d6 idea.

Ok, let's say the "check" die is 2d6; anytime you make a check, you roll 2d6. Against a DC10, this gives you only a 1/6 chance of success -- so some more dice and/or mods are clearly needed. The average on 3d6 is 10.5, meaning that 3d6 vs. a DC10 is basically a coin flip. What TNP does is essentially increase the number of "bonus" dice you can roll, thus increasing the odds of rolling a high bonus/modifier to your check. We could apply this same logic to a 2d6 system; the base check is 2d6, and the bonus is the highest d6 out of a pool. If we're using the current baselines, this would be a maximum of +2 from Attributes, and probably the same for Skillsets (maybe +3?)

Using anydice, we can figure out the odds for how this works vs. a DC10:

• 2d6+1d6 = 62.50%
• 2d6+[highest 1 of 2d6] = 75.23%
• 2d6+[highest 1 of 3d6] = 81.13%
• 2d6+[highest 1 of 4d6] = 84.37%
• 2d6+[highest 1 of 5d6] = 86.35%

This actually looks really promising, because as the chance of failure drops towards that 15% threshold, the diminishing returns on further boosting a skill start to kick in. Adding the implicit assumption of a 3rd die (except in the case of a +0 mod) also gets around the problem of "only 5s and 6s matter." The problem is that this breaks the check into 2 distinct rolls, which is a bit inelegant; the base 2d6 clearly can succeed, but is unlikely to do so -- but pooling them all together completely changes the math. If the 2d6 is a 3 or less, then the bonus dice become irrelevant (because the check has no chance of success) but a result between 4 and 8 means that success is still possible -- unlike with the "dice pool only" model, where it's just... 2 out of X dice have to equal 10, so if you roll all 4s and 3s (or lower) you're just screwed.

So now that we've established that this works, the immediate question is, can we further reverse-engineer this into a combat system? As I've often said, you should either have a unified system (that usually works great for one subsystem and badly for another) or you have distinct subsystems, but both serve their purposely excellently. The conundrum of an "all d6 system" is that it's not very unified if there are still distinct mechanics for combat vs. for skill checks -- despite everything using the "same" dice. 

The current combat mechanics are based around the supposition of 3d6+mod, where 2 dice (plus a flat mod) are used for the attack roll, with the remaining die (plus the same mod, probably) being used as the damage roll. To make this work anything like the check dice... basically it would mean a significant boost to hit-chance, assuming we're sticking with a cap of +2/+2d6 modifiers (which, you can't really meaningfully go lower than that, so...)

As mentioned in the previous post, the fact of attack rolls having damage as a "release valve" for unused dice means that the attack mechanics will likely/necessarily have to be different than the skill check mechanics. The other consideration is that the "acceptable ranges" for both types of rolls are different; skills should mostly fall in the 45% (i.e. a -1 mod, in D&D terms) to 85% range, whereas attacks probably need to have 55% or 60% as a baseline, and increase to 90% or possibly 95% with teamwork and other bonuses. This all makes it hard to unify mechanics, since unified mechanics should (presumably) produces unified outcome ranges -- so if that isn't the goal, then unified mechanics likewise shouldn't be the goal. This new idea now gives us mechanics that hit both of our prescribed benchmarks; the question next is can we do anything to further simplify and/or unify these two systems, and still produce comparable outcomes?

...

Next post is due on (or about) March 15th, so check back then for more!

Stream of Consciousness [2025-02-13]

I've been out of pocket for most of the intervening time since the last post, so I haven't had much opportunity to sit down and focus on TNP or sequel stuff. (Other non-TNP stuff has caught my attention recently, though.)

Carrying on from the previous post, one question that came to mind was how to handle the Attribute mods, with regards to skill usage. For example, just because a "+2" Attribute is used as a flat modifier for combat, does that mean it has to be used as a flat modifier for skills, too? Or could that +2 mean "add 2 dice to the pool" instead? It's a little bit unintuitive and inelegant to do it that way, but in the earlier sequel designs, it was intended that the math would function in a similar fashion; specifically, attributes would be flat modifiers for combat but provide "skill rank bonuses" (i.e. add d6s to the pool) when it came to non-combat. (By extension, it was supposed that Skillsets would use a binary trained/untrained convention, for bestowing advantage on the d10 component of skill checks.)

So what would be the value in doing that? Well, basically if you have bonuses to Skillsets that don't interact with combat in any way, you can hypothetically have a bit more variance in those bonuses. In reality though, our acceptable ranges for skill checks is something like (best 2 of) 3d6+0 through 5d6+2 -- effectively meaning a maximum of a +2 Attribute modifier and a +2 Skillset bonus. If our Attributes are capped at only one being a +2, then that would mean more Skillsets could have a +2 bonus (since they'd be paired with +1 or +0 bonuses, from Attributes.) Part of the issue is that for the most part, there isn't a significant difference in the boost from going to an additional +1 flat modifier vs. an additional +1d6 into the dice pool; for skills, where the math tends to remain relatively static and not impacted by situational bonuses, this causes a bit of a lack in variety.

Does the skill check mechanic need to be kicked down to 2d6? The problem is that 2d6+2 is still a <50% success rate, so you'd probably be adding a 3rd die to the pool most of the time anyway... which feels kind of like reinventing the wheel. On the other hand, it'd potentially let Skillset modifiers go as high as +3, without breaking anything.

Honestly, if all of this navel-gazing has taught me anything, it's that using both Attributes and Skillsets for dice pool bonuses is beginning to seem like a more appealing option as time goes on. Having to work around the flat modifiers is too much of a straight-jacket, particularly if you know you're going to layer something else onto it, in addition; having both of them simply add to the pool eliminates this problem entirely. It would also open up the possibility of having a less tightly-banded range for Attribute modifiers, i.e. opening it up to having more than one +2, if nothing else.

...

We've got one more post scheduled for this month, so in order to keep roughly on schedule, that should be out by February 24th at the absolute latest. Check back then!

Sequel Musings -- Part 2: A New Paradigm (2025)

In the short intervening period since the previous post, a lot of spitballing and discussion has gone on, in the TNP Discord. Without belabouring the point too much, the combat mechanics have essentially been narrowed down to "keep 2d6," with the baseline assumption starting at rolling 3 dice; any two can be used as the attack roll (scoring a hit on a 10+) with the remaining dice used for damage.

So how does that hit-chance look, when a modifier is applied to it? (Calculated by using the highest 2 of 3d6):

• +0 = 35.65%
• +1 = 52.31%
• +2 = 68.06%
• +3 = 80.56%

From that, I would argue that we can eliminate +3 as an option for the combat math; the percentage is already too high, and the system needs to account for other bonuses. The basic idea would be that bonuses granted from class features, teamwork, etc. would add more d6s to the pool; much like TNP, extra dice not used for the attack roll would be used for extra damage -- and the attack roll would never exceed 2d6+mod.

For combat math, I think it's safe to assume that your highest modifier would always apply. It also means that on a "basic attack" the average damage roll (on a hit) would be the remainder of [2d6+2 - DC10]; if the average of 3d6 is 10.5, and at least an 8 needs to be added to the +2 in order to score a hit, that remainder ends up being 2.5 -- in which case, I would argue that it probably makes sense to also add this +2 modifier to the damage roll.

Now, moving away from combat, to the skills side of things...

If we use the TNP "skill grid" as our basis, we can rank skills by assigning a value to them, based on both their Attribute and their Skillset. If our assumption is that combat math is fueled by Attribute mods (which range from +0 to +2) then we have to shape our Skillset bonuses around that. That all being said, we don't need to give as much consideration to outside modifiers, the way that we would do with combat.

My first intuition was "Skillsets add ranks, and Attributes also add ranks," or in other words, neither adds a flat modifier, but both could add to the "d6 pool." The problem with this (as was brought to light in discussion) is that it amounts entirely to randomness, whereby you're just rolling more and more dice and hoping for some combination of 5s and 6s on two of those dice (or a 4 and a 6, obviously.) The upside is that even at "highest 2 of 6d6" the success rate is only just approaching 75% which also means that even by adding 4 additional dice to the baseline 3d6 roll, the math only then breaks the 80% mark. If the +3 modifier math was deemed too high for combat (because it reaches this 80% mark) then it stands to reason that a +2 cap for Attributes means a +1 cap for Skillsets, if these modifiers are meant to be potentially combined together. By letting one of these numbers be dice instead of a flat modifier, it gives us a bit more wiggle room for some variety. A +2 modifier added to "highest 2 of 5d6" (i.e. +2 dice to the pool) would cap out at just over 90% success rate -- which is basically the absolute ceiling of what I think would work, for skills. 

This also begs the question of, in a spread of 5 Attributes, how many +2s, +1s, and +0s should a character have? If you're able to overlap two +2 Attributes with a +2d6 bonus on two Skillsets, suddenly you're at that mathematical ceiling, for something like 1/3rd of the skills in the game. If skillfulness is meant to be spread across a party of 4 or 5, then this wouldn't make any sense. It probably stands to reason that a well-rounded party would have one character with a +2 for each of the 5 Attributes -- meaning an Attribute spread of something like +2/+1/+1/+0/+0 as the default. By extension, this would allow bonus dice from Skillsets to have a bit more flexibility, since we only need to worry about one Attribute's worth of skills ever approaching that 90% (and of those, probably/maybe only one out of 3-4 applicable, overlapping Skillsets.)

Anyway, that's a lot of talk about dice probabilities and math. The challenge once you find a dice engine that hums, is how to convert that into something that feels like the type of game you want to be playing. In essence, you back-port the mechanics onto the character classes as best you can, rather than starting from the character concept, and trying to make up mechanics that fit and work.

...

As the blog schedule goes, the next post should be up on or about February 12th, so make sure to check back then!

Sequel Musings (2025)

Perhaps it shines through in some of the posts I've made about the TNP sequel before, but the designs (such as they are, thus far) don't really have me as excited as some of the breakthroughs I experienced when working on TNP. For example, I don't like how the 'first attempt' mechanics boil down to "sometimes you use this mod, sometimes that mod, and other times no mod." Broadly speaking, I think the weapon damage die mechanics don't carry the same pop that 'class dice' do in TNP (because these mechanics don't stack, unlike TNP) even though they're meant to behave similarly. The weapon damage dice feel like a compromise, particularly when the attack math is laid bare, and there ends up being no variance in the crit bonuses.

So I'm beginning to lean in a new(ish?) direction.

I've made a post in the past, offering and evaluating some alternative "DC10" mechanics. The suggestion that made the most sense (in the paradigm of the attribute ranges extrapolated from TNP / projected into the sequel design ideas) was basically 2d6+mod, where 'advantage' would be "3d6, keep the 2 highest" and 'disadvantage' would likewise be "3d6, keep the 2 lowest."

In addition to that, I've also teased other concepts I've had in mind, for other RPGs I might want to design -- with this one in particular jumping to mind:

an ultra-lite mechanical system, that fires off of d6s only (and maybe a standard deck of 52 cards) that can easily be played on a bus, or out on a camping trip

So why do I bring this up?
I'm sure I've posited this before, but if you're going to push forward with "d6 pool" as your 'unique selling proposition' (particularly if the decision is made to shed the 'weapon damage dice' mechanics) then the next question invariably is, why keep the d20?

I keep finding myself answering that question with a question: What do you replace the d20 with?

One of the mechanics that I had used in previous RPG designs was sort of... mixing and matching attack dice and damage dice, to create "power attack" or "precise attack" mechanics. So for example, if the attack roll was 1d10 and 1d6, and the damage roll was 2d6, a "precise attack" would let you use the two highest dice out of all 4 -- ensuring you a better chance to hit, at the cost of lowering your overall/average/maximum damage. Perhaps the d6 pool could be modified to perform this sort of function, as well?

Just spit-balling here, but lets say your default mechanic is to roll 5d6, and you can use up to 2 of them as your attack roll (probably adding an attribute modifier, or similar) with any remaining d6s used as your damage roll. In a way, this sort of brings back the tradeoffs that class dice bonuses have, where you're often using a die to score a hit (or a crit) at the expense of using that die for damage. To wit, you would be trying to compile the two lowest d6 rolls possible to hit that "DC10" mark, so that your higher rolls could be preserved for damage.

This ultimately begs the question of how the d6 pool is to be bounded. If at its core, the system is relying on "2d6+mod" in order for DC10 to be at all viable, then it stands to reason that the design might have to hand-hold players towards ensuring their main attack stat is at least a +2 (assuming that such stats are used for both number of dice in the pool, and for attack modifiers... which might be messy.) Then, situational and/or "power" bonuses can ping either flat numbers or secondary stats, in order to add more dice to the pool. And, if the assumption is that the d6 pool is both your attack and your base damage (because we're not using weapon damage dice) then your floor actually needs to be +3 / 3d6 in order for this to work. That all being said, a straight 2d6+3 vs. a DC10 isn't significantly better odds than 1d20 vs. DC10 -- with the added downside that +3 is already near the ceiling of where TNP designs would imply that attribute modifiers ought to be.

Maybe you just say "screw it" and make it so that the default roll is 3d6, with any modifiers being over and above that? In that paradigm, a +2 mod might give you 5 dice total, with your attack roll being (effectively) 2d6+2, with 3d6 remaining for damage. Something about that feels "off" though, to me. Heck, maybe the attack roll needs be changed to 1d6 and the DC changed from 10 down to 5?

Anyways, I think there's something to this, but I haven't quite hit the nail on the head just yet. I already feel as though marrying the 2d6+mod ethos to the "d6 pool" idea has more going for it than... "weapon damage dice, but also d6 pool, but also d20." I'll have to give it some more thought to try and clean this up (and admittedly, I don't really know how to calculate for this type of dice-rolling, since it isn't a simple "keep the highest" or "keep the lowest" sort of rule -- so I'll have to dig deeper into that, too.)

...

Hopefully that was an enlightening post, for everyone.
Next entry is due up on January 31st, so check back then!

Having Reservations (2024)

Let's talk a bit about reserves!

I'll start by saying that the baseline assumption I'm working from for the sequel designs, is that all characters just have 10 HP and 10 reserves; 10 is a nice round number, and 10 is the default target-number or "DC" in TNP anyway. But there are other sources to consider.

One of the games that I've played with a D&D group that I'm a part of is the Warhammer Quest: Cursed City board game. This game effectively has a "wounds" system, whereby being hit twice removes one of your four action dice; for all intents and purposes, this means that the player-characters each possess 8 HP. There is no consideration given to a Constitution score or racial/background bonuses. Early drafts of TNP had all monsters function almost as minions, dealing a fixed amount of damage (usually 1 point) which is similar to how monsters in Cursed City tend to work; this allows HP to be relatively low, compared to the 30ish you would start with in modern TNP (or 4th Edition D&D) for example.

Since in TNP, "everything is derived from the dice," earlier drafts had HP as a function of a rolled class die; this was pretty quickly revised to "maximum value of your class die" (producing a range from 4 to 12) but the obvious imbalance this created led to (effectively) a flat 20 HP being added to these numbers, to even things out a bit more. Naturally, monster math and mechanics had to be completely reworked to accommodate this.

However, since the sequel is expressly not built off of class dice, we can use something like a flat 10 HP to avoid all of the complexity that got built onto the original, simple TNP framework. Likewise, rather than needing to have reserves be "maximum of 2d4/2d6/1d8/1d10/1d12" so that all classes are more or less balanced, we can just give everyone 10 reserves and be done with it.

Now, a topic that I brought up in the Discord is the idea of a "TNP version 1.1" which would fall outside of the sequel designs, and be more of "the same" game, as TNP. In particular, one thing I brought up was the (often blogged-about) idea of per-day and per-encounter abilities. So let me break this idea down a bit -- hopefully without re-treading too much ground.

Basically, if the assumption is that "one reserve = one full heal-up" then the idea becomes something like, "if you have [a maximum of] 7 combats per day, you need 7 reserves for healing," meaning any extra reserves can be used to fuel your other class features. The basic idea is that TNP 1.1 would focus around properly implementing this idea.

To wit, a class with 8 reserves (i.e. 2d4 or 1d8 as their reserve calculation) would have 1 extra reserve not needed for healing, each adventuring day; the assumption would be that these classes would have a "once per day" reserve-burning ability. Likewise, a class with 12 reserves (2d6 or 1d12 calculation) might have a "once per encounter" reserve-burning ability.

So maybe the hierarchy ends up looking something like this:

• 8 reserves: 7 for healing + 1 per-day ability
• 10 reserves: 7 for healing + 3 extra healing
• 12 reserves: 7 for healing + 1 per-day ability + 4 extra healing -OR- 7 for healing + 5 for per-encounter abilities

In this case, extra healing might be for the character to top themselves up (if they are a tanky class that is expected to eat more damage than average, and therefore needs more healing) or to spend their own reserves to provide healing for allies -- such as in those situations where monster damage outpaces expectations. I'd like to have a cleaner method, such that the "10 reserve" builds could have more flexibility, but in a "dice determine everything"-paradigm like TNP, I'd rather be limiting these kinds of things to 1/day or 1/encounter, rather than have to somehow use the dice to justify a different limit.

To take things kind of full-circle, this brings into question the "sequel logic" of just having a flat 10 reserves for everyone; as with a few things already so far in these designs, the space for building mechanics around spending reserves for stuff other than healing is effectively lost by going to a flat math model. However, it's important to remember that the TNP "reserve-burning" mechanics are actually an attempt to unify 4th Edition's healing surge resource with (if not its per-encounter resources) its per-day resources. With that in mind, perhaps the solution as it pertains to the sequel designs is to re-adopt something akin to the 4e power progression, whereby (for example) per-encounter powers are gained at odd-numbered levels, and these are what essentially fuel your "d6 pool" features. So, reserves and "reserve-burning" abilities are no longer fueled by a unified mechanic -- but the upshot is that the numbers become easier to flatten out and balance.

...

Alright! So with today's post being on-schedule, the final post of the year should be on December 10th or 12th, as previously planned. Check back then!