Permitir que um bárbaro baseado em Dex faça multiclasse com base em Dex, em vez de Str, causará problemas futuros de equilíbrio?

11

A player of mine plays a dex barbarian and multiclassed into fighter for a fighting style. His strength score is 8 and he is using fitness weapons based on Dex for attacking. I didn't understand at that time that he can't do that without a strength score of 13 (which he doesn't have). I am leaning to houserule the multiclassing requirements for barbarian to be as the fighter, 13 strength or dex. Are there any problems as they level up that I should be aware of?

Why do I want to allow it? As I understand them, the multiclassing requirements are designed to avoid players to take another class for the features without having any of the stats that normally enable a character to have these features. Someone that is not intelligent can't suddenly become a wizard. Very logical.

However for the dex barbarian, it is not like he does not have the stats for his class. He has a 16 dex, that is above average and the main stat of a dex barbarian. So I do not see a reason why he can't multiclass.

por findusl 26.08.2019 / 22:32

2 respostas

The multiclass prerequisites, in my opinion, are best treated as suggestions rather than requirements. They do not serve any balance function—they serve primarily to help prevent players from falling into the trap of taking a class that their ability scores will not support. The reciprocal nature of the requirements, in my opinion, have more to do with making things symmetric and minimizing the degree to which the order you take classes matters than it does to do with anything concerned with balance.

As such, I have never stopped a player who knew what they were doing from doing any multiclassing they liked. This has caused zero problems, and I see no way that it could. The worst case scenario, as far as I can tell, is Paladin/Warlock using the Hexblade patron, which can now be done without needing Strength 13, which is quite desirable for this combination since Strength does little for them thanks to Hex Warrior. However, Hexblade is widely considered to be an anomaly in its own right, which means it would be quite sad indeed to limit everyone else for the sake of this one case. For me, even this combination has not caused any real problems. There is certainly nothing about a Dexterity-based Barbarian/Fighter that is going to cause more problems.

26.08.2019 / 22:39

There are edge cases where not enforcing multiclass requirements can lead to trouble

A lot of this depends on using either the standard array or point-buy system for determining ability scores. If using just die rolls, then it's possible to have a character with all 18s and multiclassing requirements are moot.

The first example that comes to mind is a Barbarian that wants a level of Hexblade. I know this because I recently tried theory-crafting one. Why make this combo? Because a 1st-level Hexblade can use a Hexblade's Curse with a really great power:

Any attack roll you make against the cursed target is a critical hit on a roll of 19 or 20 on the d20.

That same power doesn't occur until third level of a Fighter taking the Champion sub-class. So the Barbarian qualifies to multiclass into a Fighter as both require a Strength of 13, but it would take three levels to get that feature. But if we ignore multiclass requirements, then it only takes one. It also means that the Barbarian is not spending points to get the Charisma to 13 and can focus on Str, Dex, and Con. But to get that 13 in Charisma, they would have to sacrifice a large amount of points from their core stats.

There are likely other situations similar to this where ignoring requirements can cause some unforeseen over powering. So while I doubt it's game-breaking, it can become a slippery slope.

27.08.2019 / 21:54