I'm all for nerfing multiclassing. Normally, no character would have to multiclass since, for that, subclasses are included that give you a bit of the flavor of another class. So the ideal is to make multiclassing a worse option than a single class. In short, the single class should be the usual, since the core of a character in D & D is her class. Multiclassing should be reserved for very specific cases where the narrative calls for it, or rare mechanical experiments. In addition, multiclassing raises a number of serious design problems. It is very difficult to control the balance of the game when a simple DIP in another class makes you ignore your weaknesses (the most paradigmatic case are those MAD classes that stop being so when they include a level in another class. Example: The hexadin). And as a final addition, we must also take into account that now you are going to have a "free" feat at level 1. The monstrosities that can be made by combining that with depending on what multiclasses, is uncontrollable. So it is normal that they limit them. And my suspicion is that they don't remove them because there would be a lot of complaints. But if it were up to Jeremy Crawford, he would remove the multiclass option.
Yeah, the Hexblade is just poor design. From a mechanics/min-max standpoint, every single class that has CHA-based casting should take a level of Hexblade. Medium armor, shield, martial weapons, no need to worry about any other stat for gishing, and access to the best cantrip in the game.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm all for nerfing multiclassing. Normally, no character would have to multiclass since, for that, subclasses are included that give you a bit of the flavor of another class. So the ideal is to make multiclassing a worse option than a single class.
In short, the single class should be the usual, since the core of a character in D & D is her class. Multiclassing should be reserved for very specific cases where the narrative calls for it, or rare mechanical experiments.
In addition, multiclassing raises a number of serious design problems. It is very difficult to control the balance of the game when a simple DIP in another class makes you ignore your weaknesses (the most paradigmatic case are those MAD classes that stop being so when they include a level in another class. Example: The hexadin).
And as a final addition, we must also take into account that now you are going to have a "free" feat at level 1. The monstrosities that can be made by combining that with depending on what multiclasses, is uncontrollable. So it is normal that they limit them. And my suspicion is that they don't remove them because there would be a lot of complaints. But if it were up to Jeremy Crawford, he would remove the multiclass option.
Yeah, the Hexblade is just poor design. From a mechanics/min-max standpoint, every single class that has CHA-based casting should take a level of Hexblade. Medium armor, shield, martial weapons, no need to worry about any other stat for gishing, and access to the best cantrip in the game.