- Archer can now Counter-attack against ranged; same Hunter ability re-worded
- Acrobat using d20 to Power Attack removed; specialty basic attacks are now Reliable; Martial Artist's prone ability now works on unsuccessful attacks; Archer's reroll ability now works on any ranged attack (not just ranged basic)
- Wizard's Magic Missile basic attack is now Reliable; Veritable Vision now grants Expertise to damage rolls
- Assassin now gets training in either AGIL or Infiltration, instead of defaulting to AGIL
- Rogue Tactics given archetype-specific effects; clarified how Disengaging works via Cloak & Dagger
- "Warrior" class renamed to "Adventurer"
- Adventurer's Defender ability changed to "1d10[exp] or 1d20[exp] for defense rolls"
- swapped some aspects of the Fighter and Adventurer TWF abilities
- Soldier archetype's power attack ability limited to attacks made as a standard action; Weapon Training's miss roll is now likewise limited; Weapon Training can no longer turn misses into crits
- Fighter's Protection style changed to "allies in your maelstrom" instead of "Nearby ally"
- changed some Guardian totem perks to require spirit manifestation; Blood Totem now does extra damage when you are bloodied
- Cleric regains some HP when spending reserves in combat
- Ranger mark damage changed to "advantage; stack if you already had advantage"
- Bard can now Power Attack using a basic roll
- Bard's "Leader" role renamed to "Support"
- Necromancer's Animate Dead changed to allow for multi-HD minions
- Warlock's minor action attack removed; Eldritch Blast iconic attack now targets a number of enemies based on the roll, rather than making a number of attacks based on the roll
- Mystic's trained skills corrected to fit current format (oops)
- Paladin's Holy Aura reworded, now grants defense bonus only on unsuccessful rolls
- Paladin now gets training in either STR or Influence skills, instead of both (still gets additional skill training from their Archetypes)
- Swordmage now gets training in both STR and Influence skills, instead of one or the other
- Hexblade's Beguiling Blade changed to "roll class die in place of d20 roll" rather than "double roll and stack in place of an unsuccessful attack roll"
- Changed the rules on stacking class dice onto d20 rolls, in the core rules; clarified mechanics of using a basic roll for a Trade-off
Wednesday, January 25, 2017
Change Log [2017/01/25] (Beta 4)
Here's a list of some of the changes that have been made to the various classes, since the start of the holiday break:
Sunday, January 15, 2017
Separation of Powers (Beta 4)
As part of the process of polishing up the character classes, I took a look at the distribution of trained skills and skill expertise. Most classes end up with 2 trained skill "lists" (i.e. Skillsets or Basic Abilities) with particularly skillful classes getting 3 or 4. In addition, most classes get expertise with one skill list. I might look into adjusting some classes to fit more closely into these general guidelines.
Another thing I want to work on is making the structure of the classes more unified, in terms of their Iconic Abilities, Archetypes, and so forth. I want to see if classes can be broken into smaller chunks, beginning simpler and adding layers of complexity. This is not meant as a leveling system, per se, but as a way to ease newcomers into the game, rather than front-loading all of the character generation. This could also potentially shape the "starter classes" quite significantly.
The problem is that currently Archetypes do different things for different classes. For example, the Sage's archetypes are essentially two distinct sub-classes (Wizard and Monk) whereas the Barbarian's archetypes prescribe slightly different playstyles, but don't significantly modify the base class. Further to that, some classes have additional layers of customization that others don't, such as Roles, or the Cleric's domains, the Guardian's totems, and the Sage's disciplines. I might be able to remedy this disjointed nature by simply altering terminology in a few places, or it might require more significant changes. The path of least resistance might be to simply take each class and break its parts down on a case-by-case basis.
As was mentioned in my previous post, my intention is to add power sources to each class; knowledge skills would be tied to these power sources, helping to flesh out your character's background. Another part of the intention for adding this layer of customization, is so that there can be a rule allowing players to change their class at narratively appropriate times, but limited to classes that share at least one power source with your current class.
The challenge then, is ironing out which parts of the existing framework to hang power sources on. In particular, I think it makes sense to have the Sage gain one power source based on the discipline they take, whereas tying power sources to Cleric domains or Guardian totems doesn't work as well. It could also be made completely independent, but too much customization goes against the design intent to have quick and simple character generation. On the other hand, a simple character could conceivably start with nothing but a background/power source, and then buy into a class later on.
...
Work on the "math pass" continues, along with other bigger and smaller edits as I go along; the 2nd slate (Magic & Shadow) is effectively done, though I may still take a hard look at the Sorcerer archetype. The 3rd slate (Wilderness) is probably done, particularly since most of its classes were completed/updated so recently, but I may give the Druid some closer scrutiny. The 1st slate (Martial & Divine) will get a once-over, but is probably mostly set; I've done considerable edits to the Acrobat already. Once I feel this iteration is "done," expect a long blog post with a log of all the changes.
...
One major change: "The Warrior" has been renamed to "The Adventurer"
I think that Scout/Skald wasn't quite war-like enough to merit the title of "warrior" so I think the new name is a better fit; Scout having been a class from the book "Complete Adventurer" back in D&D 3.5 sort of cemented this change.
...
Check back January 25th for the next post!
Another thing I want to work on is making the structure of the classes more unified, in terms of their Iconic Abilities, Archetypes, and so forth. I want to see if classes can be broken into smaller chunks, beginning simpler and adding layers of complexity. This is not meant as a leveling system, per se, but as a way to ease newcomers into the game, rather than front-loading all of the character generation. This could also potentially shape the "starter classes" quite significantly.
The problem is that currently Archetypes do different things for different classes. For example, the Sage's archetypes are essentially two distinct sub-classes (Wizard and Monk) whereas the Barbarian's archetypes prescribe slightly different playstyles, but don't significantly modify the base class. Further to that, some classes have additional layers of customization that others don't, such as Roles, or the Cleric's domains, the Guardian's totems, and the Sage's disciplines. I might be able to remedy this disjointed nature by simply altering terminology in a few places, or it might require more significant changes. The path of least resistance might be to simply take each class and break its parts down on a case-by-case basis.
As was mentioned in my previous post, my intention is to add power sources to each class; knowledge skills would be tied to these power sources, helping to flesh out your character's background. Another part of the intention for adding this layer of customization, is so that there can be a rule allowing players to change their class at narratively appropriate times, but limited to classes that share at least one power source with your current class.
The challenge then, is ironing out which parts of the existing framework to hang power sources on. In particular, I think it makes sense to have the Sage gain one power source based on the discipline they take, whereas tying power sources to Cleric domains or Guardian totems doesn't work as well. It could also be made completely independent, but too much customization goes against the design intent to have quick and simple character generation. On the other hand, a simple character could conceivably start with nothing but a background/power source, and then buy into a class later on.
...
Work on the "math pass" continues, along with other bigger and smaller edits as I go along; the 2nd slate (Magic & Shadow) is effectively done, though I may still take a hard look at the Sorcerer archetype. The 3rd slate (Wilderness) is probably done, particularly since most of its classes were completed/updated so recently, but I may give the Druid some closer scrutiny. The 1st slate (Martial & Divine) will get a once-over, but is probably mostly set; I've done considerable edits to the Acrobat already. Once I feel this iteration is "done," expect a long blog post with a log of all the changes.
...
One major change: "The Warrior" has been renamed to "The Adventurer"
I think that Scout/Skald wasn't quite war-like enough to merit the title of "warrior" so I think the new name is a better fit; Scout having been a class from the book "Complete Adventurer" back in D&D 3.5 sort of cemented this change.
...
Check back January 25th for the next post!
Wednesday, January 4, 2017
Turning the Page on 2016
I've been working on The Next Project for a while now, but I've only been blogging since this past August. In that time, the blog has received over 1000 views! Most posts have each gotten 30-40 views, but some have gone as high as 60-70.
Going forward, my intention is to post 3x per month. From January through June, I'll be posting on the 5th/15th/25th of every month; I'm going to take a break for a bit in July, so details for beyond then will be ironed out closer to the end of June.
Leading up to 2017, all 15 planned classes were completed, across the 3 slates: Heroes of Martial Might & Divine Power, Heroes of Magic & Shadow, and Heroes of the Wilderness. I'm hoping by the end of January to complete a "math pass," specifically focusing on the damage values for each class. To this end, I've worked out a few dice expressions that achieve the expected values; now it's just a matter of checking each class to make sure it fits within those guidelines. I'm also going to try and strip out excessive rolling if/when I can, and simplify things mechanically.
A few changes to player options will be forthcoming:
Beyond that, I will be seeking feedback on the writing/mechanics, hopefully getting a few extra sets of eyes on things. With this, I'll be looking to make sure the language is clear and there are no gaps in the rules, possibly resulting in an FAQ as well. I'm also going to try and get the formatting for classes into a more unified state.
The DM-side of the rules still need to be published, so that work may begin in parallel to the other revisions, or begin once those are completed.
...
Next post: January 15th!
Going forward, my intention is to post 3x per month. From January through June, I'll be posting on the 5th/15th/25th of every month; I'm going to take a break for a bit in July, so details for beyond then will be ironed out closer to the end of June.
Leading up to 2017, all 15 planned classes were completed, across the 3 slates: Heroes of Martial Might & Divine Power, Heroes of Magic & Shadow, and Heroes of the Wilderness. I'm hoping by the end of January to complete a "math pass," specifically focusing on the damage values for each class. To this end, I've worked out a few dice expressions that achieve the expected values; now it's just a matter of checking each class to make sure it fits within those guidelines. I'm also going to try and strip out excessive rolling if/when I can, and simplify things mechanically.
A few changes to player options will be forthcoming:
- Classes that have "Roles" will be able to change their role as part of their initiative check (currently includes Fighter, Bard, and Warrior.)
- Power Sources will be added to player-characters (Arcane, Divine, Martial, Primal, and Shadow); each character will have 2 Power Sources.
- Rules for changing your class/archetype between adventures; hybrid/dual-classing/multi-classing rules will be looked into.
- Knowledge Skills will be tied to Power Sources, helping to streamline these skills, and to give additional mechanical weight to Power Sources.
- Starter Classes will be finalized once the core classes are done; expect the text to be trimmed down and simplified as much as possible.
Beyond that, I will be seeking feedback on the writing/mechanics, hopefully getting a few extra sets of eyes on things. With this, I'll be looking to make sure the language is clear and there are no gaps in the rules, possibly resulting in an FAQ as well. I'm also going to try and get the formatting for classes into a more unified state.
The DM-side of the rules still need to be published, so that work may begin in parallel to the other revisions, or begin once those are completed.
...
Next post: January 15th!
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.)
With the Warlord polished up for Beta 4, their slate is now complete!
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.
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!
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!
Saturday, December 10, 2016
Blood from a Stone -- The Guardian and The Warrior (Beta 4)
Quickly posting the links for the new classes, then I will add content shortly:
Stay tuned!
As was mentioned in my post about The Rogue, I wanted to make a Scout class that was sort of like a "wilderness rogue." Simple enough, right? Well, the thing about that is, it means the class needs to be the skill specialist of its slate -- which is sort of hard, since a slate like "Heroes of the Wilderness" is bound to have a fair bit of redundancy in the skill department.
Originally, I was planning to have the class use the d6, and focus on two-weapon fighting (harkening to the Essentials version of the Scout -- a Ranger subclass.) A couple problems with this:
I could have easily just reused these mechanics, but it felt sort of wrong. I had "Guardian" penciled in for the d10 spot on this slate, but I decided to swap the two around. It was similar to how I moved Warlock to a d10 slot, when I split it off from the Sorcerer.
What results, is a melee-focused, damage-stacking class, built off exactly the die that is meant to be used that way. Making the "Skirmish" mechanic using a d10 necessitates it working and feeling differently than the Rogue's "Sneak Attack" and I think that's a good outcome.
Skills still presented a problem; I felt the class needed an "urban" archetype or possibly a "spy," to cover the more social-focused skills -- something a specialist should be able to do, but which didn't really fit with a Scout. After much mulling and conversation, the idea of making this archetype into a Skald just clicked.
As a class that exists in Pathfinder as having Bard and Barbarian as its "parent classes," it wasn't too much of a stretch to fit it onto this slate. Similar to a Bard, it made sense for the Skald to be good at social skills, as well as deception. It also gave me the opportunity to make a sort of "two-weapon fighting Barbarian," which I didn't feel worked well as a d12 class. It also sort of lends itself to the Skald being a class from "Heroes of the Feywild" in 4e D&D, as well as the dual-wielding, hidden Bard class from Diablo: Hellfire.
So what we end up with is a more narrowly-focused Fighter in terms of combat, and a more narrowly-focused Rogue in terms of skills. The Scout leans more towards a striker/lurker role, with Skald being more of a support class; each archetype then has a few Role options to choose from, to flesh them out and help them specialize a bit more.
The Guardian
As was mentioned in a previous post, the Guardian kind of grew from the necessity of a landing spot for the Shaman archetype, as well as wanting to do a take on the Warden from 4th Edition.
The name (I think) mainly came from the Warden's daily powers referencing them assuming a "guardian form." Essentially, what these powers do is give you a few passive bonuses (effectively, a stance) and then an attack power you can fire off on that turn, or later in the encounter. The idea from Essentials of using stance powers coupled with "Power Strike" (for both the Fighter and Ranger classes) sort of mimics this kind of mechanic.
However, the specific fluff for the Warden daily powers was not very consistent, so it was hard to come up with something that worked thematically, in as elegant a way as I would have hoped; I looked at the research I had done into the Warden, and mostly scrapped it all, instead going with something closer to the Essentials Ranger.
I tried to emulate something similar to the Stance/Power Strike mechanism, using the combination of totems and spirit manifestations, with burning reserves for more powerful effects. Combine all of that with the concept of using d6 as a damage-stacking class die, plus having a support archetype and a tank archetype (with totems allowing a further degree of role customization) and... there's a lot going on. I expect this class to change a fair bit in future drafts.
---
I was kind of on a tight schedule with this post, and these two classes were probably the most work-intensive of the classes that needed to be completed. I might try and rewrite both of them when I have more time, or let that part shake out in playtesting.
In any case, "Heroes of the Wilderness" for Beta 4 is now a complete slate!
As was mentioned in my post about The Rogue, I wanted to make a Scout class that was sort of like a "wilderness rogue." Simple enough, right? Well, the thing about that is, it means the class needs to be the skill specialist of its slate -- which is sort of hard, since a slate like "Heroes of the Wilderness" is bound to have a fair bit of redundancy in the skill department.
Originally, I was planning to have the class use the d6, and focus on two-weapon fighting (harkening to the Essentials version of the Scout -- a Ranger subclass.) A couple problems with this:
- Already having a d6 Fighter class, with two-weapon fighting as one of its options.
- Already having a d6 Rogue class, with skillfulness as a major focus.
I could have easily just reused these mechanics, but it felt sort of wrong. I had "Guardian" penciled in for the d10 spot on this slate, but I decided to swap the two around. It was similar to how I moved Warlock to a d10 slot, when I split it off from the Sorcerer.
What results, is a melee-focused, damage-stacking class, built off exactly the die that is meant to be used that way. Making the "Skirmish" mechanic using a d10 necessitates it working and feeling differently than the Rogue's "Sneak Attack" and I think that's a good outcome.
Skills still presented a problem; I felt the class needed an "urban" archetype or possibly a "spy," to cover the more social-focused skills -- something a specialist should be able to do, but which didn't really fit with a Scout. After much mulling and conversation, the idea of making this archetype into a Skald just clicked.
As a class that exists in Pathfinder as having Bard and Barbarian as its "parent classes," it wasn't too much of a stretch to fit it onto this slate. Similar to a Bard, it made sense for the Skald to be good at social skills, as well as deception. It also gave me the opportunity to make a sort of "two-weapon fighting Barbarian," which I didn't feel worked well as a d12 class. It also sort of lends itself to the Skald being a class from "Heroes of the Feywild" in 4e D&D, as well as the dual-wielding, hidden Bard class from Diablo: Hellfire.
So what we end up with is a more narrowly-focused Fighter in terms of combat, and a more narrowly-focused Rogue in terms of skills. The Scout leans more towards a striker/lurker role, with Skald being more of a support class; each archetype then has a few Role options to choose from, to flesh them out and help them specialize a bit more.
The Guardian
As was mentioned in a previous post, the Guardian kind of grew from the necessity of a landing spot for the Shaman archetype, as well as wanting to do a take on the Warden from 4th Edition.
The name (I think) mainly came from the Warden's daily powers referencing them assuming a "guardian form." Essentially, what these powers do is give you a few passive bonuses (effectively, a stance) and then an attack power you can fire off on that turn, or later in the encounter. The idea from Essentials of using stance powers coupled with "Power Strike" (for both the Fighter and Ranger classes) sort of mimics this kind of mechanic.
However, the specific fluff for the Warden daily powers was not very consistent, so it was hard to come up with something that worked thematically, in as elegant a way as I would have hoped; I looked at the research I had done into the Warden, and mostly scrapped it all, instead going with something closer to the Essentials Ranger.
I tried to emulate something similar to the Stance/Power Strike mechanism, using the combination of totems and spirit manifestations, with burning reserves for more powerful effects. Combine all of that with the concept of using d6 as a damage-stacking class die, plus having a support archetype and a tank archetype (with totems allowing a further degree of role customization) and... there's a lot going on. I expect this class to change a fair bit in future drafts.
---
I was kind of on a tight schedule with this post, and these two classes were probably the most work-intensive of the classes that needed to be completed. I might try and rewrite both of them when I have more time, or let that part shake out in playtesting.
In any case, "Heroes of the Wilderness" for Beta 4 is now a complete slate!
---
Coming up on the next blogpost:
- The Warlord
- The Spellbinder
Check back on Dec. 20th!
Tuesday, November 29, 2016
Of Holy Light and Vile Darkness -- The Cleric and The Mystic (Beta 4)
Today's post introduces two classes from two different slates:
In earlier betas, I had made a couple of unsatisfactory attempts at writing a cleric class. What started off as a d12 Warlord class morphed into a Cleric, but was ultimately scrapped. The big question I kept asking myself throughout this process was, "what is the Cleric's iconic attack?" In a system that doesn't utilize the wide spectrum of damage types or monster types that other RPGs tend to use, slapping "radiant" damage onto attacks or having a "Turn Undead" ability just doesn't work.
In earlier iterations, what now constitutes the Mystic were archetypes for two other classes. The original Mystic had Warlock and Sorcerer as its archetypes, and was a d6 class, sharing a focus on charisma. The original Necromancer was an archetype of a Summoner class (from which the Beastmaster archetype was ripped, and subsequently hung onto the Ranger.)
In earlier betas, I had made a couple of unsatisfactory attempts at writing a cleric class. What started off as a d12 Warlord class morphed into a Cleric, but was ultimately scrapped. The big question I kept asking myself throughout this process was, "what is the Cleric's iconic attack?" In a system that doesn't utilize the wide spectrum of damage types or monster types that other RPGs tend to use, slapping "radiant" damage onto attacks or having a "Turn Undead" ability just doesn't work.
When I finished the first two slates back in Beta 3, and then quickly thereafter completed the Archer (d4) and Fighter (d6), I had tentatively settled on rounding out the third slate with a Cleric (d8), Warden (d10), and Deathknight (d12). When I started looking at the possibility of expanding the roster to 5 slates, the idea of an Invoker class for the "divine" slate was something that popped up.
The 4th Edition take on Invoker was a controller class, that generally slapped debilities onto itself, in exchange for slapping bigger ones onto its enemies. This doesn't particularly translate to The Next Project, since I want to avoid "hard control" mechanics. So my idea for an Invoker more closely resembled this game's Sorcerer; a d6 class that focused on stacking damage and attacking crowds of enemies. Giving the class double its normal share of Reserves would put them on par with a d12 class in that regard, but those resources would be used to fuel damage -- an idea that mirrored the 4e namesake class a bit -- wounding yourself to smite your enemies even harder.
Eventually I settled on doing only 3 slates, and the Invoker idea was scrapped.
When I set out to work on this latest Cleric class, I had decided early on that d8 would be a good fit for more than one "support" class, and so I was leaning that way for their slot. When the slate itself came together, it was kind of the last piece of the puzzle.
After I had completed the "starter set" version of the Cleric, I let it sit for a while. When I picked it back up again to start work on the full class, I felt that I wanted to give it a ranged archetype, and a melee archetype (similar to how the Acrobat turned out.) It also seemed to make sense for a d8 class.
Invoker seemed like a natural fit for a more spellcasting-focused Cleric; as for melee, names like Knight, Warpriest, and Cavalier had been on my radar during the "5 slate" experimentation phase (particularly with this game being sort of a love letter to Essentials.) Ultimately, I settled on Crusader. I think the archetype itself feels more like the Warpriest of the Essentials line, but with Paladin already having a Priest archetype, I wanted a name that would avoid any confusion.
On top of this, I decided to keep the Domains as a layer of customization; I had originally intended to have about 6 or 8 Domains spread across 3 classes (had I kept with 5 slates) but they didn't all lend themselves well to the mechanics of this game. War and Life domains seemed the easiest to wrangle, and I think they both work with either of the archetypes presented.
In earlier iterations, what now constitutes the Mystic were archetypes for two other classes. The original Mystic had Warlock and Sorcerer as its archetypes, and was a d6 class, sharing a focus on charisma. The original Necromancer was an archetype of a Summoner class (from which the Beastmaster archetype was ripped, and subsequently hung onto the Ranger.)
The name "mystic" was sort of the first thing that popped into my head when I initially came up with the idea for the class, but looking it up, the word means someone who seeks lost or forbidden knowledge. I think thematically, this works really well for both a Warlock (someone who makes a pact with otherworldly powers) as well as a Necromancer (someone whose magic blurs the lines between the living and the dead.)
In the "5 slate" experimentation phase, the idea of having a slate based on a "shadow" power source was one I really wanted to work. But I found there just wasn't enough to flesh it out. The Deathknight never materialized (although what few ideas I could come up with for it may yet appear, elsewhere) and other than that, it never really got beyond the Rogue (namely, Assassin) and Mystic; having Blackguard already in place as a Paladin archetype also threw a wrench in the works.
At any rate, when I decided to separate the Warlock and the Sorcerer, it made sense to keep Warlock as a damage-stacking class, but didn't seem to make sense to have them as the exact same die; in that case, why bother separating them at all?
So Sorcerer merged with Bard to become the Trickster (d6), and Warlock merged with Necromancer to become the new Mystic (d10). The idea to give the Warlock a Reserve-burning mechanic came late in the lead-up to this post, but I think it fits both the themes of the class, and the mechanics of it using a d10. I like that the Warlock kind of straddles the same line between striker and controller that it did in 4th Edition; I also think the Necromancer does a good job of capturing the iconic abilities of its main inspiration (for me, it's the Diablo 2 version.)
---
Coming up on the next blogpost:
- The Guardian
- The Warrior
Check back on Dec. 10th!
Sunday, November 20, 2016
For Man or Beast -- The Druid and The Ranger (Beta 4)
Today's post focuses on two classes that appeared in 4e D&D's "Heroes of the Forgotten Kingdoms" (a book in the 'Essentials' line.) The four classes featured in that book could probably be glossed as the "2nd-team All-Stars" of D&D (particularly the 4e/Essentials paradigm) coming after the "big 4" of Cleric, Fighter, Rogue, and Wizard.
Without further ado, I present:
The Ranger was one of the original 5 classes, from the very earliest beginnings of The Next Project, holding down the d8 slot on that first slate. It seemed a fit for the weapons a Ranger would typically use in D&D, and for giving them a decent amount of HP; it also works really well for the prescribed function of the class die within this game's framework.
When the idea of expanding the game to a 2nd slate started to gain steam, Druid was one of the first two classes I was interested in doing (Monk being the other, with Warlord being a popular "fan favourite.") At the time, I felt it made sense to have the Druid as a d8 class -- middle-of-the road, sharing flavour and mechanics with the Ranger.
Through the process of paring down the list of classes I wanted to write, and settling on doing 3 slates, it became clear that Ranger and Druid belonged to the same "power source." And so, because of that, one of them would have to be moved to a different class die.
I decided to shift the Druid down to the d4 slot. It made sense as a die that could be used to add HP to the class when they shapechanged, without pushing those numbers outside of the existing bounds. And it seemed like a logical step to just convert the class from "1d8 math to 2d4 math."
I also wanted to use the d4 as the Summoner archetype's limit on how many 'minions' they could control, in contrast with the Mystic's utilization of the d10. However, this ended up being implemented differently than I had originally planned -- largely due to the move away from using abilities from other classes (as was also done with the new Bard.) The Summoner no longer uses pre-existing summoning abilities; instead, it has its own unique mechanic for summoning, which works similar to the new Ki mechanic for the Monk (itself a d4 class.)
Wanting to keep classes to only 2 archetypes, I knew that having Shapeshifter and Summoner under 'Druid' would mean moving the Shaman archetype off to somewhere else; stay tuned for the Guardian class in an upcoming post, if you're wondering where it ended up.
The Ranger hasn't changed a whole lot since its inception, aside from having the archetype framework added onto it; this was when the class inherited the Beastmaster archetype from a previous Summoner class. Likewise, the Druid was completed very late in Beta 3, and so hasn't seen nearly as many iterations as some other classes. Overall I think this update removes some of the clunkiness that the d8 version had, with trying to juggle its 3 archetypes.
In terms of skills, I decided to play with the math on these two classes a little bit; no guarantees I'll keep things this way, but we'll see how it shakes out in playtesting. I didn't want the Druid to be able to use its forms to always be the best at whatever the party needed for skills, so I like the interaction of the d4 class die with Expertise for them. Likewise, the Ranger using its class die for skills interacts in a neat way with its Expertise bonuses, and makes them truly the master of the outdoors.
Along with the Barbarian class (which was completed prior to kicking off "50 Days of Design") the Druid and the Ranger fit onto the slate I'm referring to as:
---
Coming up on the next blogpost:
Without further ado, I present:
The Ranger was one of the original 5 classes, from the very earliest beginnings of The Next Project, holding down the d8 slot on that first slate. It seemed a fit for the weapons a Ranger would typically use in D&D, and for giving them a decent amount of HP; it also works really well for the prescribed function of the class die within this game's framework.
When the idea of expanding the game to a 2nd slate started to gain steam, Druid was one of the first two classes I was interested in doing (Monk being the other, with Warlord being a popular "fan favourite.") At the time, I felt it made sense to have the Druid as a d8 class -- middle-of-the road, sharing flavour and mechanics with the Ranger.
Through the process of paring down the list of classes I wanted to write, and settling on doing 3 slates, it became clear that Ranger and Druid belonged to the same "power source." And so, because of that, one of them would have to be moved to a different class die.
I decided to shift the Druid down to the d4 slot. It made sense as a die that could be used to add HP to the class when they shapechanged, without pushing those numbers outside of the existing bounds. And it seemed like a logical step to just convert the class from "1d8 math to 2d4 math."
I also wanted to use the d4 as the Summoner archetype's limit on how many 'minions' they could control, in contrast with the Mystic's utilization of the d10. However, this ended up being implemented differently than I had originally planned -- largely due to the move away from using abilities from other classes (as was also done with the new Bard.) The Summoner no longer uses pre-existing summoning abilities; instead, it has its own unique mechanic for summoning, which works similar to the new Ki mechanic for the Monk (itself a d4 class.)
Wanting to keep classes to only 2 archetypes, I knew that having Shapeshifter and Summoner under 'Druid' would mean moving the Shaman archetype off to somewhere else; stay tuned for the Guardian class in an upcoming post, if you're wondering where it ended up.
The Ranger hasn't changed a whole lot since its inception, aside from having the archetype framework added onto it; this was when the class inherited the Beastmaster archetype from a previous Summoner class. Likewise, the Druid was completed very late in Beta 3, and so hasn't seen nearly as many iterations as some other classes. Overall I think this update removes some of the clunkiness that the d8 version had, with trying to juggle its 3 archetypes.
In terms of skills, I decided to play with the math on these two classes a little bit; no guarantees I'll keep things this way, but we'll see how it shakes out in playtesting. I didn't want the Druid to be able to use its forms to always be the best at whatever the party needed for skills, so I like the interaction of the d4 class die with Expertise for them. Likewise, the Ranger using its class die for skills interacts in a neat way with its Expertise bonuses, and makes them truly the master of the outdoors.
Along with the Barbarian class (which was completed prior to kicking off "50 Days of Design") the Druid and the Ranger fit onto the slate I'm referring to as:
"Heroes of the Wilderness"As of right now, the previously-mentioned 'Scout' class will instead be made an archetype, under the umbrella of a 'Warrior' class; along with the Guardian, these 5 classes complete this "3rd slate."
---
Coming up on the next blogpost:
- The Cleric
- The Mystic
Check back on Nov. 30th!
Subscribe to:
Posts (Atom)