Reply to thread

Message

<blockquote data-quote="billd91" data-source="post: 7802007" data-attributes="member: 3400">This has been a trend since 3.5 stepped back a bit from multiclassing in D&amp;D 3.0. A big problem is classes start with a bunch of initial abilities that any new character belonging to that class should have. Weapon proficiencies, armor proficiencies, and class core abilities. Anyone multiclassing into that class would get them all and in 3.0, a lot of class abilities were heavily front-loaded. 3.5 spread them out a bit more over initial levels so you couldn't get too much value out of a 1 level dip into the class. Star Wars Saga Edition took things a step further and multiclassing into a new class only got you one of the new class's starting feats rather than all of them.So I'd say it's an ongoing trend - balancing multiclassing so that the sudden influx of a new class's level can't involve an outsized growth in a character's power, either as a spike or in breadth.</blockquote>

[QUOTE="billd91, post: 7802007, member: 3400"] This has been a trend since 3.5 stepped back a bit from multiclassing in D&D 3.0. A big problem is classes start with a bunch of initial abilities that any new character belonging to that class should have. Weapon proficiencies, armor proficiencies, and class core abilities. Anyone multiclassing into that class would get them all and in 3.0, a lot of class abilities were heavily front-loaded. 3.5 spread them out a bit more over initial levels so you couldn't get too much value out of a 1 level dip into the class. Star Wars Saga Edition took things a step further and multiclassing into a new class only got you one of the new class's starting feats rather than all of them. So I'd say it's an ongoing trend - balancing multiclassing so that the sudden influx of a new class's level can't involve an outsized growth in a character's power, either as a spike or in breadth. [/QUOTE]

Verification