Showing posts with label Warlord. Show all posts
Showing posts with label Warlord. Show all posts

Thursday, November 30, 2023

Class Showcase: Spellbinder & Warlord (2023)

Oddly enough, it was around this season way back in 2016 when I did a post about these same two classes, for the Beta 4 version of the rules. It's interesting to compare and contrast where the designs have changed over the years.


Working on the other "Disciple" classes (Druid and Occultist) helped to kind of lay the groundwork for how the Warlord would take shape, in this iteration. Essentially, there's one universal Warlord feature, one feature unique to each of the two subclasses, and one feature for each of the three combat roles -- similar to the other Disciples. I had been meaning to take the idea of the old-school Fighter getting an army of followers, and impliment some form of that into TNP for a while now; in pre-3.5 D&D (so, before my time in the gaming space -- apologies if I get any of this 2nd-hand information slightly wrong) Fighters got this perk when they received the title of "Lord." To me, it seemed obvious to fit this feature in with the Warlord class, just based on the naming convention alone. With the other Disciple classes having summoner-type "controller" abilities to work off of, the groundwork for the "Lord of War" was already laid, and this feature actually came together quite quickly.

As I had teased in earlier posts, the Spellbinder didn't need a lot of changes from the 2019-ish iteration, since it didn't require a class die makeover. I was kind of fiddling with the "Blademaster" specializations for this class right up until the last minute, so don't be terribly surprised if they get tinkered with a bit in the future. I've always sort of liked the idea of Spellbinder as the over-class for Swordmage and Hexblade; the name originally was meant to incorporate "the other, other Warlock subclass" from 4th Edition -- the Binder. But, when looking up the meanings of words to see if they really fit (something I agonized over a lot on the debilities, for example -- and also why the Mystic eventually became the Occultist) I found that the word 'spellbinding' means to captivate or even hypnotize; this helped to add another dimension to the class, and helped me build out some of its magical abilities. Sort of like the Acrobat and the Adventurer (to varying degrees) the Spellbinder kind of took on a life of its own with TNP, and became its own "thing."


...

This post marks the end of this season, for the blog. Typically the first post of the new year will come out on January 11th, so I would check back then for any updates.
If you look back on the posts throughout this year, you'll know that there's still a lot of work to be done, in order to finalize the designs. I'll try and squeeze in some writing over the next month, to get some of the "SRD" ironed out; some other goals would be to get an updated "monster math" document (with at least some example monsters) as well as finalizing the campaign-building mechanics.

Monday, August 21, 2023

Class Updates: August 21st (2023)

Quick overview:

  • Cleric: I would consider to be updated
  • Druid: stable, but not complete
  • Occultist: work in progress
  • Warlord: preliminary work started
  • Spellbinder: not started

As mentioned before, figuring out the Disciple class category (Druid, Warlord, Occultist) is going to be a big piece to completing this puzzle. My general intention with the category is to possibly have their "unique thing" be that they can switch their subclass -- possibly requiring a long rest, or spending a reserve, or similar. We'll see if the finalized designs (for the Occultist in particular) make this workable.

Looking back on previous drafts, both the Druid and the Occultist had the option to gain training with either "Influence" (now "Communication") or Subtlety, as a "category upgrade"; this is going to at least be kept as a placeholder form of category upgrade, particularly since the Warlord previously had the option to gain training with one Attribute or one Skillset (abeit as a "class upgrade"). This may ultimately be revised down to a skill rank, rather than skill training.
The other placeholder category upgrade will be the ability to gain an additional power source; currently this can be any power source, but may ultimately be scaled back to "any power source from your class list."

The final (obvious) category upgrade option is to gain additional roles; this is pretty straightforward for the Warlord, and will probably be kept as access to the different animal forms for the Druid, but for the Occultist it will likely require a major class rework. As it stands right now, the structure of the Occultist is effectively a "roles, but no subclasses" setup, which needs to be expanded to include both roles and subclasses. Essentially, the Necromancer and Warlock "roles" will become subclasses, and new role mechanics will need to be layered on in addition.


In case I've forgotten to mention it previously, there was a late substitution on the 3rd slate, whereby the Druid was changed to a d4/d12 class and the Guardian was changed to d4/d6. This worked out a lot better since the Druid was originally built off a d4, and Guardian was built off a d6; essentially, Guardian utilized stacking d6s of extra damage, so converting it to a d12 was actually a bad fit. Conversely, the Druid wasn't built to utilize such a mechanic, so the change to a d12 is a better fit -- if anything, it's somewhat under utilized for the class.

There were some similarities I found while working on the Cleric (d4/d10) and Druid (d4/d12) since their dice are so similar. Mechanics such as the "Druidic Focus" (which previously called for a double roll of "your class die") have mostly been changed to instead roll both class dice; I consider this to be only a "placeholder change," since testing is obviously going to be needed. Another thing is that the Cleric in particular had a lot of utilization of "advantage on base damage" -- a mechanic which was only very recently axed from the designs, precipitating several reworks. So, porting the class from a d8 to d4/d10 (in addition to those reworks) has likewise created a lot of "placeholder changes."


I think I'm going to have a fairly easy time with the Spellbinder, because the basic structure is already in place. Blademasters' unique thing is that they can gain certain features from other classes, and the Sage Domains are already essentially built to be used by multiple classes in the slate; the subclasses for Spellbinder are already formalized, so most of the work will be in format updating, and potentially adding Occultist roles to the list of features that can be borrowed. Being a 2nd slate class, Spellbinder remains using the same, single class die -- so almost nothing should need to change mechanically.

Wednesday, January 10, 2018

What to expect from 2018

Happy new year, everyone!
For those keeping score, the blog had just over 1000 views a year ago, and now it's at just under 3000.

Today I'm going to try and touch on as many thing as I can, pertaining to what I plan to write about on the blog this year, as well as the sorts of innovations and changes that will appear in the game design itself. But before getting into any of that, I'm happy to announce that the first draft of the "starter slate" classes is all ready to go:


I should point out that these classes have been written with much of the new framework in mind; it shouldn't be difficult to have the rest of the classes match up to that. Notably, since there are no "archetype-only" classes in this slate, it'll be important to make sure that those classes have enough customization options, once they are re-written.

In terms of the blog itself, of course I will be including information on changes to the designs, as they come up. In addition to that, I would also like to go back and discuss how some of the existing ideas came to be, and why those decisions were made; for example, I'd like to write about the original slate of 5 classes, the use of Class Dice, and the skill setup. In terms of scheduling, I'm hoping to stick to the plan laid out here, adhering to my "every 10th day"-ish routine, with breaks in July and December.

As I touched on in my previous post, in terms of development, I want to essentially update the classes to the 2018 Edition aesthetic, one slate at a time -- rather than doing all classes in concert with one another. What this means is that (once the core rules are likewise updated) I intend to do some playtesting with the starter set, then adjust those classes (and the core rules) as needed, then work to release another slate of classes, playtest them, and so forth in that fashion.

...

For some mechanical changes (in addition to those already announced) I'm going to work at streamlining and fixing a few things:

Opportunity Attacks: Though I like the conceit of just doing auto-damage with these actions, it's not a good fit for TNP. With some classes getting "double roll and stack" on this damage, it clashes with the positional mechanics that can impose disadvantage on OAs, requiring a specific rules-exception that I don't like. Also, not having an attack roll makes it sort of a misnomer, and I haven't found an alternate piece of jargon that's to my liking. As such, OAs will now use a traditional attack roll. One potential benefit of this is that it will allow for classes to have both a basic attack and an Opportunity Attack "loadout" which may open up new design space.

Trade-offs/Double Rolls: The mechanic of Trade-offs is one that has often been classed as a misnomer, by some of the readers. As the designs have evolved, the specific use of Trade-offs has not been applied uniformly enough, in my estimation. Since things like Counter-attack and Power Attack already have design changes planned (to make them operate without using Trade-offs) I'm going to remove this piece of jargon from the rules, completely. This means that some class abilities will have to be (or have already been) completely changed or replaced. For other instances, the "double roll" terminology will be used instead. Since double rolls that are not just advantage or disadvantage are generally limited to using Class Dice (rather than d20s) you can expect to see that spelled out more explicitly, in the next draft of the rules.

Advantage/Disadvantage: I am considering a few changes to these mechanics:
1) a return to "if you have both advantage and disadvantage, roll 3 dice and use the middle result" (which appeared in earlier drafts.) I might want to have this in place, so that the design space of using both the highest roll and the lowest roll remains viable, in instances where both advantage and disadvantage would apply.
2) re-rolling the dice, in the case of disadvantage resulting in a tie; overall, I don't like to have re-rolls (particularly for play-by-post purposes.) However, the general rule of "treat one result as its maximum value on a tied double roll" functionally does nothing, with disadvantage -- I may want to change that.
Neither of these are set in stone yet, but they are both on my radar.

...

That's about all for today; check back next weekend for another post!

Tuesday, November 21, 2017

Back to Basics -- Part 2: Numbers & Nomenclature

Everything old is new again, as today's post is a sort of follow up to a post I made just over a year ago.

There are a few things I want to touch on in specific, but overall this post is going to be about some changes I want to make, in order for the game to be simpler and more accessible.


Expertise

When I sat down to write the actual text for Beta 4, I had decided that I wanted to make Basic Attacks somehow distinct from Iconic Attacks. What I mean by this, is that generally they use the same dice rolls, so I wanted to add something a little extra to Basic Attacks, to make them distinct. My initial thought was to use the "roll and compare" mechanism: "when you make a Basic Attack and the attack and damage rolls are equal, treat the attack as a critical success."

This effectively increases your "critical threat range" by one number (i.e. 5%) regardless of the class die being used for the damage roll. The problem is that Basic Attacks are given so many modifiers by class features, that it becomes clunky and untenable. So, I decided to give all Basic Attacks the Expertise property; this gives the same increase to crits, but also a little boost to damage as well.

Through the process of working out "bonus math" and subsequently trying to integrate those mechanics when crunching damage output for various attack routines, I came to realize that "always-on" Expertise needed to go. Particularly with so many d4 and d6 classes being able to use the "double roll and stack" rule for their damage, layering Expertise on top of that just had the effect of further narrowing the possible range of results -- or, as I put it, making it closer to flat damage, with none of the elegance of flat damage (because it still required rolling.)

(An interesting note, worth making mention of here, is that the average result of "double roll and stack d4" is the same as "d8 with Expertise"; the same is true for d6 and d12, respectively.)

The result of all of this, is that it frees up the design space of Expertise, to be used more meaningfully. In the earliest drafts of the game, characters gained Advantage on their attack rolls for doing things that were iconic to their class: Rogues benefited from attacking "flanked" enemies, and Barbarians got the benefit when they were raging, for example. The problem is that Advantage ends up being a huge bonus, and eventually most instances of Advantage were ripped out or dialed back. However, this is where a smaller bonus like Expertise can (I hope) step in to fill the gap.


Advantage

Following from this "dialing back" of Advantage, gaining it as a bonus to attack rolls changed in the rules to being almost exclusively the purview of positional considerations -- High Ground, Prone, etc.

The intent, then, was to start using the aforementioned "bonus math" to give classes their boosts gained from fighting "in-character," so to speak. Two main problems arose with this: first, no matter how streamlined the mechanisms for the bonuses got, they always tended to be unintuitive, and to have the potential to slow down gameplay; secondly, when crunching out damage for actual attack routines, Advantage always made it a lot easier to hit the benchmarks, because it tends to be such a huge boon, mathematically.

All this being said, I think that bonuses using class dice will be limited to "support" abilities, which will allow them to layer onto other bonuses, such as Advantage and/or Expertise. As such, Advantage will start to make a return to the designs of some classes, but Expertise will be used in instances where it is more appropriate.

Bottom line: the math has to work, but the gameplay has to be smooth.


Damage on a Miss

The mechanic used for this in TNP (known as the "Reliable" property) has always been "deal damage equal to the unsuccessful attack roll." I've always preferred this over alternatives of "half damage" or "minimum damage" (in the case of their being multiple damage dice stacked onto one attack) just because it is a little quicker to adjudicate.

This gives us a range of miss damage from 1-9 (or 2-9, with Expertise) for an average of 5 damage (or 5.5 with Expertise.) The problem with this expression comes when applied to attacks that normally could not reach the high end of that range, i.e. 1d4, 2d4, 1d6, and 1d8.

As such, "Damage on a Miss" will only be used as a tool for boosting DPR on attacks that could deal more than a maximum of 8 damage, on a 'hit'. Probably attacks that would result in a single d10 of damage will also be excluded, so mainly this would be utilized on attacks where d6s, d8s, or d10s are being "stacked" -- or where a d12 is being used. So while classes making attacks below this range would not natively be given the "Reliable" property, it could still be given to them by a bonus "support" mechanic, as it currently exists for the Warlord.


Basic Attacks, Power Attack, and Counter-attack

With the Expertise mechanic no longer being a defining characteristic of Basic Attacks, a few properties remain unique to them: Reach, Reliable, and the ability to Power Attack with them.

My intention with Power Attack is to change it from this:
Before you make a basic attack as a Standard Action, you can choose to make a Trade-off using your class die; apply the lower roll as a penalty to the attack roll, and apply the higher roll as a bonus to the damage roll.
To this:
Before making a Basic Attack, you can impose Disadvantage on the attack roll; if you do so, you can treat a successful attack as a critical success.
What this would do, is make access to Advantage more clearly beneficial when using Power Attack. It also removes the disparity between the penalties involved (a d4 being a much smaller one than a d12, for example.) Counter-attack could use a similar rule, granting an Opportunity Attack if the triggering Defense roll is successful.


Basic Abilities and Iconic Abilities

The initial structure of classes was such that you had Iconic Abilities, which gave you suites of benefits. Generally speaking, every class also had an Iconic Attack, which differed from Basic Attacks, as has been explained above. However, some Iconic Abilities simply offered benefits that modified Basic Attacks; there was confusion over whether this was meant to be considered an Iconic Attack (for the purposes of whether Expertise/Reach/Reliable properties applied, or if Power Attack could be used) which it was not.

Going forward, the phrase "Iconic Ability" will not be used. Instead, these will be labeled as either Class Feature, Subclass Feature, Archetype Feature, or Role Feature, as appropriate. Features that grant a modification to a type of Basic Attack, or that grant an Iconic Attack will subsequently be more clearly defined, with each having its own entries under that Feature's heading.

Related to this, Basic Abilities (STR, AGIL, DEX, CHA, INT, WIS) were named as such, since they were not ability "scores" in the traditional sense, and were more fundamental and simple than the Iconic Abilities. The temptation has lingered around to simply lump these in as "Skillsets" but I think there is still use within the design in having the two be separate; some classes have the option to gain training in one "Skillset" of their choice, for example, and it is not intended for them to be able to pick a "Basic Ability" set for that option.

With "Iconic Ability" terminology going away, now is a good time for a change here, too. I've decided that Basic Abilities will be re-titled as simply "Attributes." This terminology is fairly common in the RPG space, and is probably more accurately descriptive for its utilization within TNP.


Blogging/Scheduling

I'm planning to get out one more post before the end of the month, so check back for that on November 30th.
I will also do another post before the middle of December -- likely a year-in-review sort of deal, tying up any loose ends.
Then, I will be on break for about a month, during which time I will start work in earnest on the new draft of TNP, which I am tentatively referring to as the "2018 Edition."

Friday, November 10, 2017

Know Your Role (Beta 4)

In one of my recent posts, I talked a bit about how subtypes will be changing in the next iteration of the rules; the two forms of "combat subtypes" (those that can be chosen/changed at the start of combat) will be unified under the "Role" banner.

The plan is that there will be 3 classes with both Roles and Archetypes (Fighter, Bard, Adventurer) and 3 classes with Roles only (Warlord, Mystic, and Druid.)

In past iterations, the Warlord's roles appeared as "Commander" and "Protector" archetypes. What will now be "Roles" for the Mystic could easily have been strict Paths, but I felt "Necromancer" and "Warlock" were close enough in feel, that allowing more customization was the side to err on. Similarly, as the design progressed, the Druid's subtypes felt less and less like the building blocks of two distinct classes, and more like two sides of the same coin.

The challenge with integrating these three classes into the Role framework comes out of ironing out what their subtypes actually do. The Warlord is pretty straightforward, in this regard: while the class chassis contains the "healer" mechanics, the Commander is the part that contains the "enabling" mechanics -- so I'd say this makes it the "Support" role; the Protector maps pretty clearly to the "Defender" role.

This gets a little messier once we start to look at the Mystic and the Druid, however. The Warlock is a straightforward "blaster" sort of character (i.e. the "Striker" role); the Necromancer is a "Summoner" (as is the Druid's Summoner subtype, obviously) but unfortunately, "Summoner" isn't a pre-existing Role. The Shapeshifter doesn't fit neatly into the framework, either; it's intended to be able to use its forms to serve different roles -- a kind of "6th man" character class, so to speak.

However, with the "4.1 version" of the Druid, the class chassis was given a "healer" mechanic -- in a way, making it very similar to how the Warlord is built. So while the Shapeshifter subclass isn't specifically about "enabling" allies, it is intended to use its utility to "support" the party -- by being whatever they need in a particular combat encounter (or perhaps to round out an undersized group.) Although I've waffled on whether or not to simply rename the "Support" role to "Utility" across the board, I can say that I have decided to put the Shapeshifter under this heading -- whatever it ends up being called, in the end.

Now, the Druid and Mystic being related by a summoning mechanic, harkens back to an earlier draft (Beta 2, maybe?) where the Summoner class came in "Beastlord" and "Necromancer" flavours. It still makes sense that they should share a Role, now -- but I wasn't sure if having a "Summoner" role that applied to only two classes was the way to do it.

The solution came in looking at the existing Roles, and how they are doled out so far. Controller is currently only found on the Bard and Adventurer classes; while those roles are more about controlling enemies, it's not much of a leap to then apply that convention to the role of controlling summoned creatures. What helps make the case, is the fact that the controller role (as it exists in 4th Edition) can be a bit broad and nebulous, but also that some of the controller classes in that system gained summoning options, at different points in its lifespan.


So, for classes with roles, we end up with this setup:
  • Fighter: Defender, Striker
  • Warlord: Defender, Support
  • Bard: Controller, Support
  • Mystic: Controller, Striker
  • Druid: Controller, Support
  • Adventurer: Controller, Defender, Striker

It has long been my intention that Power Source would be the lynch-pin by which you could re-spec your classes; since The Next Project has traditionally been less about leveling up, I wanted to provide some lateral flexibility for character "growth." Power Source makes sense, for keeping the flavour of your character consistent (while allowing you to change its mechanics) but it's clear now that Role will also be something which players can pivot their character class upon. Probably all classes with access to Roles will begin with one, and be able to "purchase" additional Roles as they level -- which would then carry over, if a character changed to a class that also utilized the same role, or roles.

Wednesday, April 26, 2017

Change Log [2017/04/26] (Beta 4)

Playtesting is ongoing, but here are some changes that have been added in the past month; expect more in the coming updates.

  • [Core Rules] Capped the number of enemies you can create a maelstrom with using the "Engage" action (Move) at "maximum value of your class die"
  • [Core Rules] "Shift" action (Move) can now engage one unengaged enemy
  • [Core Rules] Subclasses changed so that they must be selected when entering initiative (instead of at char-gen)
  • [Core Rules] Paths added to the character customization options
  • Changed Cleric, Sage, and Rogue subclasses to "Paths"
  • Changed Warlord archetypes to "Roles" and renamed them accordingly
  • Changed Warlord's options for Performance skills to include Expertise or Training, instead of just training
  • Sage's power sources expanded to 3, but narrowed down a bit
  • Bard's power sources changed to "arcane, plus one of Divine/Martial" instead of "any two"
  • Mystic's power sources changed to "two of Arcane/Primal/Shadow" instead of "Arcane + Shadow"
  • Guardian's power sources changed to accommodate the new Subclass mechanics
  • Adventurer's power sources changed; Scout only gains two of Martial/Primal/Shadow instead of all three; Skald now gains two of Arcane/Martial/Primal instead of Primal and one other
  • Swordmage's Shielding Sigil changed so that opportunity attacks can negate enemy actions; Beguiling Blade changed to grant advantage on defense when counter-attacking an enemy with your sigil
  • Bard now has the option to take an archetype from other classes within their slate (i.e. Sage schools, Hexblade, Swordmage)
  • Bard's Arcane Luck ability now has the [Concentration] tag added
  • Sage's Eldritch Enchantment changed to grant advantage on attack rolls, and to use your class die for bonus damage.
  • Spellbinder's skills adjusted again; Hexblade back to only 2 core Trained skills; split skill selection into 2 toggles instead of 1 toggle and 1 solely for Hexblade.
  • Cleric's Divine Smite using the Life Domain now restores HP equal to the rolled damage (instead of using a separate roll)

Tuesday, December 20, 2016

Heavy Metal Thunder -- The Warlord and The Spellbinder (Beta 4)

Today's post features two classes based off the the d12 class die:

Warlord was one of the first few "expansion" classes that I wanted to add, after the first slate was finished (as has been mentioned here previously.)

I personally never quite got the allure of the "lazylord" style of gameplay, but I included it nonetheless, with a few twists of my own; making the Warlord a d12 class was mainly done for two reasons:
  • a distinct lack of d12 classes to take inspiration from, in pre-existing d20 systems
  • the desire to make attacking a powerful option for the class, rather than always opting to make someone else attack instead
This also meant that Warlord would be a melee-focused class, as per the role of the d12 within the system. It's a class that is more effects-based than damaged-based, in some ways similar to the Ranger.

The Commander archetype can direct allies as either a Standard Action, or when they make an unsuccessful attack. This is intended to allow players to be conservative and just trade their action to their teammates, but to also not punish them for being aggressive and choosing to attack.

The Protector archetype is meant to be a strong battlefield controller, wading into the thick of things to defend allies and punish enemies. 


With the Warlord polished up for Beta 4, their slate is now complete!

Heroes of Martial Might & Divine Power



...

Spellbinder began its life as the Swordmage archetype for the Mage (d4) class. Originally, Mage was the only class that had any sort of teleportation abilities, so it was logical that Swordmage would fit under that umbrella. When I settled on writing 3 slates (and on what shape those would take) the Mage became the Sage, with Wizard and Monk as its archetypes; it made sense to shift an archetype like Swordmage up to a "heavier" slot, like the d12.

As for another archetype to go with the Swordmage, probably one of the first names to come to mind was the Hexblade. In a slate of classes built around arcane magic and shadowy power, it made for a class with an interesting dichotomy to reflect that.

Though not as fiddly as the Essentials version of the class, the Hexblade as presented here takes inspiration from the Fey pact, with its focus on teleporting; this also serves to make this archetype a good fit for the umbrella class. The Hexblade also works well with the d12; it's basically a melee-focused version of the warlock, a class that naturally lends itself to the mechanic of burning reserves (of which d12 classes get the highest number) for powerful effects.

The name "Spellbinder" doesn't seem a great fit at first glance, but I think the archetype names themselves compliment one another. However, the definition of the word "spellbound" references distracting, fascinating, or holding someone's attention (either with the spoken word, or outright magic.) This seemed perfect for a class with one archetype that focuses on distracting enemies to protect their allies (Swordmage) and another that gains their attention in order to punish them even harder (Hexblade.)

I also had intentions of incorporating ideas from the "Binder" (warlock subclass in 4e) just to wrap the name up neatly, but a quick glance at that class showed it to be mostly a ranged version of the Hexblade, and so it was not really suited to a d12 class.


The Spellbinder caps off another slate!

Heroes of Magic & Shadow


---

All of the classes are now set! That means it's time to move on to other aspects of the game's design. Going forward, posts will likely focus on the "GM side" of the system, although player options may see some further tweaks and refinement.

TNP Design will be taking a short break for the holidays, but expect a new post on January 5th.
See you in 2017!