I levelled up a Hex Blade warlock to plan future advances. I enabled a glaive as a pact weapon and then as a hex weapon. When I later removed warlock levels to revert the character back to its current play state the glaive remained flagged as a hex weapon.
When removing character levels this sort of thing should be checked and any options dependent on the removed levels should also be removed.
I also noticed the bug with pact weapon + hex weapon + polearm master not applying the CHA bonus to attack and damage. A forum search shows this was first reported in 2019 and has not yet been fixed…
A Hex Weapon is selected as early as 1st level, so you literally can’t level down your character enough to undo the Hex Weapon.
As for the Polearm Master feat, that Action is more of a reminder that you can do it than actually functional for anything other than a standard Str build. If you homebrew a copy of that feat you can adjust the relevant Ability score from Str to Cha and load that copy onto your character instead of the original feat.
It is still a bug. While the Hex Weapon feature is present from level 1, two-handed weapons are not permitted hex weapons unless Pact of the Blade is selected at level 3. Removing Warlock levels below 3 removes the pact feature and makes the glaive an invalid choice.
Not a bug. It's not RAW to remove levels. So, if you're removing levels it is up to you to check/uncheck what you need. The feature itself doesn't limit your option on hex weapon - and this allows customisation. For example you might be taking a weapon but customising it / reflavouring it to suit your DM approved purposes. Since this might make the weapon valid for your hex weapon feature, having the checkbox there is useful. Then, DMs might override the limits. Having the option be open - just reliant on you knowing the feature - is better than closing it off and pissing people off who might be houseruling (which is common and is the Rule Zero, and supported by RAW).
Rollback Post to RevisionRollBack
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond. Need help with Homebrew? Check out ✨ thisFAQ/Guide thread ✨ by IamSposta.
While it's not in the rules to remove levels, it is in the rules to entirely rebuild levels before level 4 in adventurers' league. The tool can also be used as a planner and people can change their minds of what they intend. A character building tool that can't ensure that a character complies with the rules is a poor tool.
The option for Hex Weapon on two-handed weapons is hidden without the Pact of the Blade feature. Clearly the intent is there to only allow valid weapons to be chosen. It's just not clearing the current state of the Hex Weapon property, and the hiding of the option means it can't be manually removed without first adding levels of warlock again. It is currently closed off and so it wouldn't be pissing any one off to change the behaviour. It pissed me off for not working correctly.
I've been writing software since the late 90s and on any team I've been a part of this would constitute a bug. The original post was aimed at DnD Beyond devs in the hope that they would fix it. Comments by anyone else are meaningless.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I levelled up a Hex Blade warlock to plan future advances. I enabled a glaive as a pact weapon and then as a hex weapon. When I later removed warlock levels to revert the character back to its current play state the glaive remained flagged as a hex weapon.
When removing character levels this sort of thing should be checked and any options dependent on the removed levels should also be removed.
I also noticed the bug with pact weapon + hex weapon + polearm master not applying the CHA bonus to attack and damage. A forum search shows this was first reported in 2019 and has not yet been fixed…
A Hex Weapon is selected as early as 1st level, so you literally can’t level down your character enough to undo the Hex Weapon.
As for the Polearm Master feat, that Action is more of a reminder that you can do it than actually functional for anything other than a standard Str build. If you homebrew a copy of that feat you can adjust the relevant Ability score from Str to Cha and load that copy onto your character instead of the original feat.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
It is still a bug. While the Hex Weapon feature is present from level 1, two-handed weapons are not permitted hex weapons unless Pact of the Blade is selected at level 3. Removing Warlock levels below 3 removes the pact feature and makes the glaive an invalid choice.
Not a bug. It's not RAW to remove levels. So, if you're removing levels it is up to you to check/uncheck what you need. The feature itself doesn't limit your option on hex weapon - and this allows customisation. For example you might be taking a weapon but customising it / reflavouring it to suit your DM approved purposes. Since this might make the weapon valid for your hex weapon feature, having the checkbox there is useful. Then, DMs might override the limits. Having the option be open - just reliant on you knowing the feature - is better than closing it off and pissing people off who might be houseruling (which is common and is the Rule Zero, and supported by RAW).
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond.
Need help with Homebrew? Check out ✨ this FAQ/Guide thread ✨ by IamSposta.
While it's not in the rules to remove levels, it is in the rules to entirely rebuild levels before level 4 in adventurers' league. The tool can also be used as a planner and people can change their minds of what they intend. A character building tool that can't ensure that a character complies with the rules is a poor tool.
The option for Hex Weapon on two-handed weapons is hidden without the Pact of the Blade feature. Clearly the intent is there to only allow valid weapons to be chosen. It's just not clearing the current state of the Hex Weapon property, and the hiding of the option means it can't be manually removed without first adding levels of warlock again. It is currently closed off and so it wouldn't be pissing any one off to change the behaviour. It pissed me off for not working correctly.
I've been writing software since the late 90s and on any team I've been a part of this would constitute a bug. The original post was aimed at DnD Beyond devs in the hope that they would fix it. Comments by anyone else are meaningless.