3
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jul 2023
3 points (100.0% liked)
D&D Next - 5e Discussion
2 readers
2 users here now
A place to discuss the latest version of Dungeons & Dragons, the fifth edition, known during the playtest as D&D Next.
Join our discord! https://discord.gg/dndnext
-- Rules --
- Be Civil. Unacceptable behavior includes name calling, taunting, baiting, flaming, etc. Please respect the opinions of people who play differently than you do.
- Use Clear, Concise Titles.
- Limit Self-Promotional Links. External links to blogs, kickstarters, storefronts, YouTube channels, etc, must be related to DnD and posted no more than once every 14 days. Affiliate links are never allowed.
This is a new community and the rules are in flux. Please bear with us (and give your feedback!) as we navigate building this new community. Thank you!
founded 2 years ago
MODERATORS
The only reason this is a "house rule/variant" is because everybody allows the optional rules by default and doesn't understand what "optional" or "check with your DM first" means.
I don't allow multi-classing. Subclasses do it better and are actually balanced. When I don't disallows multi-classing I get 1-3 hexblade dips every group because of how OP the dip is.
I've had a ton of Paladin/hexblades, more than a few Wizard (Bladesinger)/hexblades, and even a rogue/hexblade with a fucking double-scimitar.
I'm sick to death of hexblades.
Fuck hexblades. No more multiclassing in my games. Assholes abused it so much it's no longer an option because I like my hair where it is, and the alternative is for me to quit DMing altogether.
...and nobody else seems willing to run the fucking game...
Why not try a different system?
Seems a bit overkill to ban all multiclassing when all you really want to ban is hexblade dips! I think you really just need to ban munchkins from your table ;)