Today I have included the second draft for the duelist, which now has the Arcane Blade duelist archetype which is based on the old 3.5 Arcane Duelist. I have expanded the abilities of the archetypes, as my original design was to be mechanically liken unto a spellcaster's ability to drop effects while still having the ability to actually participate in combat. Let me know what you think!
Heya! Really love the convenience of the PDF embedding! Also, arcane blade is intriguing! A lot of utility, but still quite capable in combat.
ReplyDeleteArcane blade is the archetype Daerthalion is in the Duel in the Clocktower story. I enjoy the utility of all of these, and with the edits I made in the other two, they should have somewhat equal utility.
ReplyDeleteI actually noticed the added options on the others. I still love the invisible blade more than anything... A martial character fighting almost entirely with your intelligence
DeleteI wanted to add more versatility to each so Arcane Blade didn't outclass them. So the pattern you can expect will be 3 talent features at 1 and 6, and then two "game changers" at 13 and 17
DeleteI noticed that the Invisible Blade Keen Edge features don't have durations for their debuffs
ReplyDeleteGood catch! Should be til the end of their next turn.
DeleteGeneral thing about the organization: a lot of these features use talent points (or are merely reliant on you having talent points remaining,) and it's very difficult to parse which sections make use of talent points, and which do not. I would recommend wrapping talent point based features under a mechanic like a maneuver, so that this is clearer. Additionally, if a main class feature gives out a maneuver (or two) they will also likely work better using subheadings, which makes them visually distinctive on a page.
ReplyDeleteI'm sure it seems weird that I'm pointing out an organizational thing, but like 90% of writing a class is making sure it comes across effectively when read for the first time.
So, if I understand correctly much like the way that Ki is written in the PHB?
DeleteThis seems like a fun yet potentially abused multiclass dip
ReplyDeleteDoes something stand out specifically that can be abused?
Delete