Multi classing Objections: Rules vs. Fluff?

[abirdcall]

I think the whole LG drow paladin of the sun is a great story. Imagine living in darkness your whole life and then, after a harrowing journey upwards, you stand in a cave mouth and see the sun in all its glory, feeling its warmth wash over you, tears flowing because the sight is so beautiful to you and your eyes are super sensitive to sunlight. That's a great story and I'd be perfectly fine with a LG Drow paladin devoting himself to worship of the sun/sun god.

The sun is a very threat to your existence. It wouldn't feel good.

But that is beside the point, why a Drow? Why not any of a myriad of other races?

1. To be the centre of attention.
2. To tell a story to a captive audience rather than to create a story with friends.

It's just disrespectful. At our table we don't allow any of that sort of thing. You're here to contribute to the group or you should go write a novel on your own.

 

[Unwise]

[MENTION=6788732]cbwjm[/MENTION] The reason I came up with that example is that I actually played a Dwarf from a clan that prided itself on never having been in sunlight. They felt that sunlight would weaken both them and their culture, like it must have done to humans. He of course saw the sun for the first time and fell in love with it and the outside world. I chose deep-dwarf over Drow because it would not have the issues I mentioned above. To me that is the trick, something can be a great story yet shift the view of the world. In my Warhammer campaign example, my players all had great back stories (which they never do normally) but the end result was that it was a group that did not fit in the world at all.
[MENTION=6748898]ad_hoc[/MENTION] I can see where you are coming and agree, but don't have that experience myself. Frankly if they engage in RP or backstory at all I am thrilled, we don't have people competing for the spotlight.

 

[cbwjm]

The sun is a very threat to your existence. It wouldn't feel good.

But that is beside the point, why a Drow? Why not any of a myriad of other races?

1. To be the centre of attention.
2. To tell a story to a captive audience rather than to create a story with friends.

It's just disrespectful. At our table we don't allow any of that sort of thing. You're here to contribute to the group or you should go write a novel on your own.

That's where we'd have to agree to disagree. The sun isn't a threat to their existence, that's just rubbish and saying it's disrespectful is going too far in my opinion.

 

[Shiroiken]

1. It is clunky. The game is designed so that at level 1 the class has chassis abilities. Things like armour, weapons, skills, HP, etc. Multiclassing combines 2 chassis together and it is clunky.

I always felt this was a missed opportunity. During the playtest, I had concerns that 5E was going to be unplayable for me and my group (thankfully, I worried needlessly). However, I did spend time using the various playtest material we had to mash together my own version of 5E... just in case.

When they mentioned that levels 1-2 were going to be "apprentice tier," that got me thinking. What if the game default started at level 3. You could play levels 1-2, but that would be similar to playing 0 level characters from earlier editions. With this in mind, you could easily set up a workable multi-class system using the 3E model 5E eventually used. Instead of a level 1 fighter getting proficiency in all weapons and armor, they only get some (more than non-warrior type classes, for sure). Clerics worship a concept or pantheon before settling in to a single deity (i.e. domain). You get the idea, but it would allow characters to dip for some benefit, but not the massive benefit most commonly seen today. Single class characters, however, would start off pretty much as you expect them to now. Oh well.

 

[Keravath]

In my opinion, multiclassing can be just as much a mechanism for character development as any other. It is up to the DM as to whether they allow multiclassing in general but disallowing it for certain classes based on some pre-conceived idea of how a particular class should be played seems arbitrary.

There are lots of class combinations that would appear to be DESIGNED to go together.
- hexblade warlock and shadow sorceror - both draw power from ties to the plane of shadow - very easy to picture a character with both a shadow patron and the ability to harness shadow power to cast spells as well
- oath of ancients paladin and a fey warlock
- fallen paladin and a fiend warlock
- oath of devotion paladin and either a celestial warlock or divine soul sorcerer
- divine soul sorcerer and celestial warlock
- trickery cleric and rogue (arcane trickster?)
- ranger and druid
- nature cleric and druid
- war cleric and fighter

All of these multiclass combinations have significant synergies in terms of backgrounds/goals/fluff. Combining them creates characters that become more effective at some things and less at others. A Fighter/war cleric will have less spells but may be a better fighter than a pure war cleric. The character could also be fully devoted to their god while just learning to fight better, that could be a large part of the motivation for such a character.

Basically, from my perspective, there are very good reasons from both a mechanical and a role play sense for quite a few multiclass combinations.

On the other hand, there are some multiclass combinations that would need a really good back story and a lot of role playing effort. For example an oath of devotion paladin/fiend warlock would be a character that would be very divided internally and would have a lot of difficulty reconciling the two parts of the character. Divine soul sorcerer and hexblade warlock might be another character that might find the two classes in opposition to each other. In a homebrew game, a DM might ask for some really good back story and role playing ... on the other hand, in AL, any combination is acceptable.

Finally, in general, multiclassing delays the acquisition of higher level abilities and as a result can be quite well balanced. A caster with a two level dip in another class will always be a level of spells behind equivalent single classed characters. Even if they have the spell slots, they won't have the spells. A figher with a 2 level multiclass will have to wait until 13th level to get their 3rd attack. A 5th level wizard with a 2 level dip will have to wait until 7th level to get their 3rd level spells.

Basically, if you are going to multiclass, it is either for role playing reasons to create a character with an interesting back story that you want to play or if the abilities offered by the multiclass compensate for the delayed progression. For example, I have a 7th level character that is a 5th level lore bard/2nd level hexblade warlock (his mother was part shadow elf and father a human paladin). The two levels of hexblade have added general utility and the ability to do some at will damage but at level 5 and 6 the character did not have some of the better CC and AoE spells from 3rd level. He is also still missing out on the magical secrets spells which he won't obtain until level 8 .. but which a straight bard would have had last level. As a result, mechanically it is pretty balanced and from a role playing perspective the combination fits the characters back story.

 

[Hawk Diesel]

So I am very much one that separates mechanics and fluff. When I look at the pure numbers and abilities of the different classes, I don't see anything that would inherently make one a Fighter versus Monk versus Sorcerer versus Wizard. Yes, some of the abilities we have come to understand represent things like Sneak Attack, but that is still more of a colloquialism or short-hand, and doesn't mean that the way it's represented couldn't change.

For example, I can play a barbarian that is not a savage or tribal. I can play them as a mad scientist. Rage does not mean he gets really angry, but could be the result of an injection or potion. Or it could be a form of lycanthropy. Mechanically it works the same, but with that slight reskin I have changed the class completely. It works the same, sure, but the way I play it will be quite different.

A paladin does not have to be a Holy Warrior. It could just as easily be a sorcerer. They are descended from some powerful entity, and at their whim they can burn their foes with their strikes and have regenerative abilities to mend their wounds and even those of others. Suddenly a Paladin is no longer about their code, and is transformed into someone born with their powers like a Sorcerer.

Same thing with a Fighter. I look at those mechanics, and I can easily reflavor it into a Monk or a Ninja. Sure, fighters use weapons, but a warhammer can be reflavored into brass knuckles and it works the same. And you change it to versatile by the classic move where you bring your interlocked fists down upon an opponent's head.

So yea, a multiclass Sorcerer/Paladin may not make sense if you only subscribe to the lore that we associate with those mechanics. But the Paladin levels could easily be explained as an extension of the sorcerer's bloodline based power. Or the Paladin may describe their sorcerery powers as an extension of their will to remain faithful to their oath. Or, it could be a really wiry inventor that wears a power armor suit and uses their gadgets to replicate all the powers of the sorcerer and paladin (especially if it's a gnome, eh [MENTION=6799753]lowkey13[/MENTION]?).

 

[Keravath]

I agree.

I think a lot of people are also selfish in character creation. They want their character to be the protagonist rather than part of an ensemble.

Not only is that character representing Drow, but the character is also going to be hogging screen time.

Backstories only exist if they influence the story. Background traits through Inspiration allow for the backstory to shine through. But that's it, 4 things that sum up the character. Everything else about that character is created during play.

A player could write an entire novel's worth of backstory for their character and it still wouldn't exist. To all of the viewers (other players) they are just a LG Drow who wants to hog the game by telling everyone about it.

...Instead...make a character who will bolster the story and the other characters. Or in other words, it isn't 1 player's story.

Umm ... In my opinion and experience, the only way that one character dominates and gets more "screen time" is if the DM allows it and caters to the player. A good DM can make almost any party composition work.

I'd also add, that in most of the world, the LG Drow Paladin of the sun is far more likely to see LESS "screen time" than the other characters since the reaction of NPCs in towns is likely to be extremely negative. LG Drow are an extreme rarity unless the DM rebuilds the world to accomodate the character (which shouldn't usually happen unless it just happens to be a world where the drow lore is completely different). However, assuming the standard world, drow are hated and feared. They are quite likely to be lynched. Other adventurers in the town will have likely only encountered the evil versions and are probably not above taking revenge on a random drow.

So ... a lot of the time that LG Drow Paladin of the sun is going to be hiding in their room trying not to be found. The rest of the party will get the screen time with social interactions and if the Drow shows their face they could end up jailed, dead or worse. Never mind the fact that they attack with disadvantage when in the sun.

Mechanically, a stronger race is likely the Yuan-ti pureblood. Unlike Drow, they can usually pass for human. However, they still won't be the center of attention unless the DM lets it happen.

 

[abirdcall]

I always felt this was a missed opportunity. During the playtest, I had concerns that 5E was going to be unplayable for me and my group (thankfully, I worried needlessly). However, I did spend time using the various playtest material we had to mash together my own version of 5E... just in case.

When they mentioned that levels 1-2 were going to be "apprentice tier," that got me thinking. What if the game default started at level 3. You could play levels 1-2, but that would be similar to playing 0 level characters from earlier editions. With this in mind, you could easily set up a workable multi-class system using the 3E model 5E eventually used. Instead of a level 1 fighter getting proficiency in all weapons and armor, they only get some (more than non-warrior type classes, for sure). Clerics worship a concept or pantheon before settling in to a single deity (i.e. domain). You get the idea, but it would allow characters to dip for some benefit, but not the massive benefit most commonly seen today. Single class characters, however, would start off pretty much as you expect them to now. Oh well.

That would be a good way to do it.

Personally I like how subclasses fill the role of multiclassing and prefer it to your way, but I could live with yours.

I think for the popularity of the game it was better that they made multiclassing an optional module rather than something they designed around. Works well for me too as I just don't use it.

 

[Li Shenron]

I am wondering why the lore of spellcasters is so sacred to some?

...

So this leads me to ask: of all the things we home brew and change, why are these seemingly sacred cows so sacred to some? Do we think the RP aspect is a balancing factor in some way?

I observe that many who dislike multiclassing seem to dislike deviation from very traditional fluff elements in classes.

Though I actually used it in the past for a couple of characters, I dislike multiclassing in all combinations. Each class is both a strong archetype and a flexible canvas for good players.

I generally find that roleplay reasons for multiclassing are weak. IMXP the real reasons for most players are most commonly (1) believing they can get an advantage from combining the abilities of different classes, and (2) wanting to play two characters at the same time. Now, whether the player is aware that these are his true reasons, or he genuinely believes he's doing it for the "character concept" is another matter.

I think that the idea of trying to figure out a synergy between the mechanics of two classes is a more valid reason, but I still don't like using multiclassing to achieve that, because it's still too big a tool for the job. I prefer using feats that grant a class' signature ability to other characters, because they get to the point without baggage.

 

[Li Shenron]

I think this is a symptom of some classes being mechanical-only but other classes being mechanics and story.

The idea of a fighter doesn't rely on any fluff. You know how to fight. There's no reliance in anything in the game world. A warlock or cleric, however, is bound up with something in the game - a patron or deity. D&D 5E has tried to remove the link between clerics and paladins and in-game deities, but most of us players ignore that.

It is a failure of description, both designers' fault and players' fault. If you start seeing the Fighter more like a budoka or dedicated student of the martial arts as a way of life (whatever style, nothing to do with the oriental), it can be on par with all other classes. Instead people insists on thinking of the Fighter as a mere collector of useful techniques, and then blame it because is doesn't have a purpose. You have to try and think that the martial arts are the purpose for the Fighter, and no one else.

I loved 4th Edition most because it explicitly stated that fluff is malleable: let the players' and dungeon masters' imagination soar: create your own worlds, characters and backstories.

As a dungeon master in 5th Edition, I allow my players the same leeway. They are limited to the mechanics of the rules; but they can change the appearance, background, names, etc to fit their own concepts.

Some people see this as the reason why multiclassing is good. I see this as the reason why multiclassing is unnecessary.