Upgrade your account to a Community Supporter account and remove most of the site ads.
Rocket your D&D 5E and Level Up: Advanced 5E games into space! Alpha Star Magazine Is Launching... Right Now!

Reply to thread

Message: <blockquote data-quote="CleverNickName" data-source="post: 8106543" data-attributes="member: 50987">Like [USER=1465]@Li Shenron[/USER] said, the biggest problem with the Hexblade is multiclassing.  So if you ignore that optional rule, you will "fix" the Hexblade (and several other problems.)Or you can try to fix multiclassing.The easiest fix I can think of would be to rule that all classes must be within 1 level of each other, which eliminates the "level dip" problem that some folks mentioned above.  You have to decide whether or not you are going to multiclass before you reach 3rd level, and you have to spread your level-ups out among the classes you choose.Another fix would be to rule that character classes with the Spellcasting feature cannot multiclass with other classes that have the Spellcasting feature.  This doesn't stop the "level dip" phenomenon, but it does curb the cherry-picking of spells.Or, if you feel that is too harsh: you could rule that if you already have the Spellcasting feature, you cannot gain the Spellcasting feature again from another class.  Your sorcerer can take levels of druid, but she will always only ever know sorcerer spells, and will only gain more spell slots when she takes levels of sorcerer.  She still benefits from the better equipment, wild shape, and other abilities of the druid class.There are other fixes out there, of varying levels of complexity.  But these are the ones I would use if I wanted to allow multiclassing, while avoiding some balance issues of the Hexblade.</blockquote>

Verification