Reply to thread

Message

<blockquote data-quote="Blue" data-source="post: 8832929" data-attributes="member: 20564">Personally, I'm a fan of 5e's &quot;you really hit stride in your class at 3rd&quot; and not overloading 1st level.&nbsp; It lets new players grow into your characters, lets veterans get some experience with their party dynamics and synergies before having to commit, and stops low levels from being overloaded and ripe for cherry pocking via multiclass.But there are issues.&nbsp; Like when you suddenly get skills that really make more sense having the whole time when you get your multiclass (like the Rogue Scout).&nbsp; And pushing it back for everyone would take away some needed bits, like clerical domains.I've seen a lot of people pushing for subclass choices at 3rd - get all of the flavor and right into player the character you envision from session 1.&nbsp; And I can't say that is wrong either.I would have to be a tradeoff with new player friendliness and low complexity - that compromise would need to be worked out.&nbsp; (My way of working it out in 5e is just allowing 3rd level starting characters for veteran players if we want to.)But there's still muticlassing.&nbsp; I do enjoy the freedom of 5e multiclassing to pic your direction as you go, but some of the other multiclassing options would avoid the cherry-picking.&nbsp; Like TSR era multiclassing, where you pick 2-3 classes and split between them.&nbsp; Or feat-based multiclassing.&nbsp; Or something else.How would you do it to grant subclass at 1st but also keep single classed and multiclassed characters balanced over the various levels of play?</blockquote>

[QUOTE="Blue, post: 8832929, member: 20564"] Personally, I'm a fan of 5e's "you really hit stride in your class at 3rd" and not overloading 1st level. It lets new players grow into your characters, lets veterans get some experience with their party dynamics and synergies before having to commit, and stops low levels from being overloaded and ripe for cherry pocking via multiclass. But there are issues. Like when you suddenly get skills that really make more sense having the whole time when you get your multiclass (like the Rogue Scout). And pushing it back for everyone would take away some needed bits, like clerical domains. I've seen a lot of people pushing for subclass choices at 3rd - get all of the flavor and right into player the character you envision from session 1. And I can't say that is wrong either. I would have to be a tradeoff with new player friendliness and low complexity - that compromise would need to be worked out. (My way of working it out in 5e is just allowing 3rd level starting characters for veteran players if we want to.) But there's still muticlassing. I do enjoy the freedom of 5e multiclassing to pic your direction as you go, but some of the other multiclassing options would avoid the cherry-picking. Like TSR era multiclassing, where you pick 2-3 classes and split between them. Or feat-based multiclassing. Or something else. How would you do it to grant subclass at 1st but also keep single classed and multiclassed characters balanced over the various levels of play? [/QUOTE]

Verification