roger semerad
Explorer
This is what gets me about multiclassing in 5e. When you already have various ways of being a sneaky person who does magic, or a fighty person who does magic, why do you need to create the option for a fighter/thief or a a fighter/wizard?
That's an honest question. I feel like these discussions about the changes people want in D&D are often driven by conflicting, or simply incommesurable, motivations. Is multiclassing needed because subclasses don't offer people the thematic flexibility they want? Or is it just a cool mechanical trick?
This comes down to the inherent strengths and weaknesses of class based systems vs. a classless one. A classless system has unmatched ability to express the most character concepts, while the class based one makes it easier for new players by constraining choice down to the bare essentials and is easier to balance very flavorful and unique abilities for each class because there's a limited amount of ways for them to be combined. If you character concept matches the class based options well it's a great way to make a character. If your idea isn't really supported that's where multi-classing comes in. It slightly pushes the class based system more towards the classless side, without completely crossing over. For example the Eldritch Knight gives magical ability, but it's very focused on damage spells and combining them with melee strikes. That's very emblematic of class system, give you a very flavorful class that can only be a narrow set of ideas. If say you wanted to play a mercenary that has spent a lot of time in the Feywild and was a master of combining enchantment, illusion and swordplay, confusing and debuffing your enemies before dispatching them with your blade. Then the Eldritch Knight just doesn't support that idea. That's where multiclassing comes in. The multiclass Fighter/Wizard allows something like this, at the cost of having no specifically flavored abilities tied to it. It's more generic and combines the abilities less well than a fully fleshed out class or subclass would, but it at least is able to support the concept. You could try to make classes and subclasses for every possible concept, but then you end up with 3.5's bloat of literally hundreds of classes and prestige classes.
Last edited: