Since the 2024 rules came out and D&D beyond has STILL not added support for all legacy (non-updated) subclasses, I've been making a homebrew version by selecting the 2024 class I want and picking the legacy subclass as the base to copy. Then I just change the subclass name to subclass name - 5.5e and done. Now, it doesn't give me the legacy options when I select the 2024 class, only the ones available currently.
DDB... I've bought the source material, I paid for the new rules set, and we were "promised" compatibility for ALL legacy subclasses. This change either is a bug, or it's direct malicious and anti-customer behavior. Because I'm not copying a subclass I don't already have access to, I'm just getting a 5.5e character have 5e subclass without starting from scratch or relying on the Homebrew options available when people tweak it to better suit how they think 'should' be.
And I want to make clear, these are NOT the subclasses that have been updated already, these range from third party to expanded rule sets that still are not re-released in 5.5e. It is not that hard to update on D&D Beyond's end to fit the new progression system. If I can do it in just a couple of minutes, there's really no excuse they can't have gone through them all by now.
All official sources have any non-updated subclasses bumped up to the 2024 ruleset. While there were a couple that didn't immediately make the jump (which was a bug and has been fixed since), all third-party subclasses must have the 2024 versions submitted by the IP holders, and Beyond has no ability to unilaterally convert said subclasses to the 2024 ruleset. This includes ALL Critical Role content, which is officially considered third-party, even those books released as part of an official partnership with WotC (such as Wildemount).
If you took even two minutes to read any threads talking about this dating all the way back to the release of the 2024 PHB, you'd have already seen this information.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Since the 2024 rules came out and D&D beyond has STILL not added support for all legacy (non-updated) subclasses, I've been making a homebrew version by selecting the 2024 class I want and picking the legacy subclass as the base to copy. Then I just change the subclass name to subclass name - 5.5e and done. Now, it doesn't give me the legacy options when I select the 2024 class, only the ones available currently.
DDB... I've bought the source material, I paid for the new rules set, and we were "promised" compatibility for ALL legacy subclasses. This change either is a bug, or it's direct malicious and anti-customer behavior. Because I'm not copying a subclass I don't already have access to, I'm just getting a 5.5e character have 5e subclass without starting from scratch or relying on the Homebrew options available when people tweak it to better suit how they think 'should' be.
And I want to make clear, these are NOT the subclasses that have been updated already, these range from third party to expanded rule sets that still are not re-released in 5.5e. It is not that hard to update on D&D Beyond's end to fit the new progression system. If I can do it in just a couple of minutes, there's really no excuse they can't have gone through them all by now.
All official sources have any non-updated subclasses bumped up to the 2024 ruleset. While there were a couple that didn't immediately make the jump (which was a bug and has been fixed since), all third-party subclasses must have the 2024 versions submitted by the IP holders, and Beyond has no ability to unilaterally convert said subclasses to the 2024 ruleset. This includes ALL Critical Role content, which is officially considered third-party, even those books released as part of an official partnership with WotC (such as Wildemount).
If you took even two minutes to read any threads talking about this dating all the way back to the release of the 2024 PHB, you'd have already seen this information.