Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Dessert Nomad" data-source="post: 7542573" data-attributes="member: 6976536">I don't believe that such a thing exists in 5e; forum angst over combos involves being them being able to score high numbers in white room example fights that won't work out in reality or only rarely occur. I have yet to see an actual example where a player put together a 5e character using the real rules (not UA or weird 'someone on the internet posted this' classes) and the combination of abilities was actually broken. So I simply wouldn't see that someone decided to multiclass two or three classes together and decide 'oh my god, that's broken'. I'd give a warning like 'you do realize you can't use monk abilities while wild shaped as natural weapons and unarmed strikes aren't the same thing' if they seem to have a rules error, but otherwise I really don't see why I'd lose sleep over someone combining hexblade with valor bard and mastermind rogue (or whatever the actual combo is), they're probably going to end up weaker than a straight character anyway. Looking through this thread, people's examples don't seem to have anything to do with a by-the-rules character that combines abilities in a way that mechanically breaks the games. They seem to be examples of characters that don't fit the world's background, characters that are made with bad personalities, characters made specifically to annoy someone else, and so on, but nothing that involves 'combining these classes is mechanically broken'. If a player is making a character to screw with another player, then I have a player problem, not a character mechanics problem, and I'll deal with the player directly. If a particular character doesn't fit the game world, then I'll explain how my world works to the player and let him make it into something that fits the campaign. Using 'make a backstory' as a response is just weird and nonsensical to me; if there's something mechanically wrong with the class then having a good backstory won't fix the mechanics, and having a crappy backstory won't suddenly break a good character into a bad one. I don't see what purpose this requirement is expected to serve. Also it's not some monumental task to come up with a backstory for any particular combination of abilities in a 'general D&D' world; if nothing else, you can just watch the youtube video about Abserd (character for a one-shot with one level in every class) and take out whichever classes you aren't using.</blockquote>

Verification