To qualify for a new class, you must meet the ability score prerequisites for both your current class and your new one, as shown in the Multiclassing Prerequisites table.
I'm curious whether these prerequisites are still being enforced in the character builder. One of my players decided to start with a Cleric/Paladin multiclass, and they were able to do so even though their STR is only 8.
I'm curious whether these prerequisites are still being enforced in the character builder. One of my players decided to start with a Cleric/Paladin multiclass, and they were able to do so even though their STR is only 8.
There is an option in the character builder (Home Section >> Use Prerequisites >> Multiclass Requirements) that when off/left/grey will allow characters to multiclass even if by RAW they shouldn't be able to. Your player almost certainly turned that option off to do so. Whether they did it knowingly is a matter to discus with them.
I know that option. I expressly instructed my players to have that toggled on, and the character sheet does indeed have it on. I decided to test myself, and I was able to multiclass despite not having a 13+ STR with the toggle on.
Ah I think I see what happened. It looks like you can get around that requirement by choosing the classes prior to selecting any ability scores. Once I selected ability scores, I went back and removed the Paladin levels, and when I tried to add them back, it prevented me from choosing them. It seems like ability scores should be chosen prior to class, although if the bug is simply that it doesn't enforce them after selecting ability scores, a player could still get around by jumping to class first regardless of what order the tabs are in...
Was that before or after filling in the ability scores? If you multiclass before filling in ability scores you can do so as much as you like - but once you've filled in the ability scores it should restrict them properly.
Yep it was before. I imagine it will almost certainly be before for 99% of players out there simply due to the order in which the builder is organized. If the application is going to rely on order-of-entry to enforce these things, then it really should put things in the "proper" order. However, as someone in the software development industry with a focus on complex UIs, I would suggest that relying on "order of operations" to enforce rules is not the best way to go about things. I mean, ultimately the DM can just tell the player to fix it, but that's an annoying UX. The system should be smart enough to enforce these rules regardless of what order the user goes about data entry.
It seems like ability scores should be chosen prior to class,
I whole heartedly agree with this. But DDB has us build characters in the order the PHB suggests we build them (with class before abilities). I respect DDB's decision to follow the books, but sometimes (only "sometimes"?) the books are less than optimal.
Though technically, those guidelines in the PHB are only for building level 1 characters, so if the builder is going to be used to level up characters, it is already going beyond the purposes of that chapter of the PHB.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
When attempting to multiclass from paladin to warlock or sorcerer I have been unable to do so as it says a 13 strength is required.
The character abilities are all 7 except for charisma which is 20. The only requirement to multiclass to either of those classes is 13 charisma.
Player & DM with 20+ years of dice rolling behind me.
If you go here: https://www.dndbeyond.com/sources/phb/customization-options#Prerequisites you'll see the prerequisite for multiclassing into paladin is 13 strength and charisma
Find my D&D Beyond articles here
I am not multiclassing into paladin but from paladin to Warlock.
Player & DM with 20+ years of dice rolling behind me.
This is correct, as per the rules.
https://www.dndbeyond.com/sources/basic-rules/customization-options#Prerequisites
The first sentence of these rules states:
Pun-loving nerd | Faith Elisabeth Lilley | She/Her/Hers | Profile art by Becca Golins
If you need help with homebrew, please post on the homebrew forums, where multiple staff and moderators can read your post and help you!
"We got this, no problem! I'll take the twenty on the left - you guys handle the one on the right!"🔊
I'm curious whether these prerequisites are still being enforced in the character builder. One of my players decided to start with a Cleric/Paladin multiclass, and they were able to do so even though their STR is only 8.
There is an option in the character builder (Home Section >> Use Prerequisites >> Multiclass Requirements) that when off/left/grey will allow characters to multiclass even if by RAW they shouldn't be able to. Your player almost certainly turned that option off to do so. Whether they did it knowingly is a matter to discus with them.
Mega Yahtzee Thread:
Highest 41: brocker2001 (#11,285).
Yahtzee of 2's: Emmber (#36,161).
Lowest 9: JoeltheWalrus (#312), Emmber (#12,505) and Dertinus (#20,953).
I know that option. I expressly instructed my players to have that toggled on, and the character sheet does indeed have it on. I decided to test myself, and I was able to multiclass despite not having a 13+ STR with the toggle on.
Ah I think I see what happened. It looks like you can get around that requirement by choosing the classes prior to selecting any ability scores. Once I selected ability scores, I went back and removed the Paladin levels, and when I tried to add them back, it prevented me from choosing them. It seems like ability scores should be chosen prior to class, although if the bug is simply that it doesn't enforce them after selecting ability scores, a player could still get around by jumping to class first regardless of what order the tabs are in...
Was that before or after filling in the ability scores? If you multiclass before filling in ability scores you can do so as much as you like - but once you've filled in the ability scores it should restrict them properly.
Mega Yahtzee Thread:
Highest 41: brocker2001 (#11,285).
Yahtzee of 2's: Emmber (#36,161).
Lowest 9: JoeltheWalrus (#312), Emmber (#12,505) and Dertinus (#20,953).
Yep it was before. I imagine it will almost certainly be before for 99% of players out there simply due to the order in which the builder is organized. If the application is going to rely on order-of-entry to enforce these things, then it really should put things in the "proper" order. However, as someone in the software development industry with a focus on complex UIs, I would suggest that relying on "order of operations" to enforce rules is not the best way to go about things. I mean, ultimately the DM can just tell the player to fix it, but that's an annoying UX. The system should be smart enough to enforce these rules regardless of what order the user goes about data entry.
I whole heartedly agree with this. But DDB has us build characters in the order the PHB suggests we build them (with class before abilities). I respect DDB's decision to follow the books, but sometimes (only "sometimes"?) the books are less than optimal.
Though technically, those guidelines in the PHB are only for building level 1 characters, so if the builder is going to be used to level up characters, it is already going beyond the purposes of that chapter of the PHB.