Homebrew Subclass Validator Bug

*bump* after the July 21st, 2026 Release the problem still exists! 

https://www.dndbeyond.com/changelog

*bump* after the July 27th, 2026 Release the problem still exists! 

https://www.dndbeyond.com/changelog

I always was fascinated by the forum dwelvers that they are passionate about things and they come across a little bitter, I never thought I'll become one! :D
Anyhow, the last mention for homebrew in the channelog releases was in the June 1st so I am assuming that there is a great deal of backlog the dev team needs to tend!

Looking forward for the next one! :D

*bump* after the August 11th, 2026 Release the problem still exists! 

https://www.dndbeyond.com/changelog

Hey, bud? That's a lot of unnecessary self-bumping over nothing. 

Multiple threads in the Forums have found various fixes over time for these issues. Sometimes the fixes break again, sometimes they don't. Dummy features at various levels can sometimes fix it, based on where third-party features are. 

In the meantime, they've started in an AMA that this problem is one they're trying to snuff out entirely with the new builder due this year. 

As for why the already janky tools have even bigger issues when dealing with homebrew: The homebrew tools here are nothing but a stripped-down version of the dev tools. They weren't originally meant to exist at all.

Quote from Athanar90 >>

Hey, bud? That's a lot of unnecessary self-bumping over nothing. 

Multiple threads in the Forums have found various fixes over time for these issues. Sometimes the fixes break again, sometimes they don't. Dummy features at various levels can sometimes fix it, based on where third-party features are. 

In the meantime, they've started in an AMA that this problem is one they're trying to snuff out entirely with the new builder due this year. 

As for why the already janky tools have even bigger issues when dealing with homebrew: The homebrew tools here are nothing but a stripped-down version of the dev tools. They weren't originally meant to exist at all.

 Thank you for the heads up, and I am sorry if these bumps annoy you.
Every release I go and check the one error that still persists that is very simplistic and tracking it so no more threads are being generated for the same thing.

I have found a way to go around the problem but is not a solution is a messy workaround that literally inflates the backend with homebrew builds no one really needs.
So my bumps might be on face value be dry and repetitive but what happens every release from my end is the following:

1. I read the notes.
2. I try a new build to see if the persisting same error still happens.
3. I update the thread by bumping it.
4. I follow-up on an ongoing ticket.

I started this on May so for any other that might have end up here after that it might be beneficial to go and read....
 'Ow this is exactly what my problem is, and there is a weirdo that keeps cheking if it is fixed' just to avoid the ever increasing list of these...

Multiple threads in the Forums have found various fixes over time for these issues.

There are administrators that can completely shut me down if this is unnecessary self-bumping over nothing. 
I hope this message did not offend you further, and again I appreciate your critisism! 

The biggest thing is that you shouldn't hold your breath on any fixes like this one coming through before the new builder is online. When this is one of many fixes it's supposed to have baked in because it's a ground-up build instead of working around legacy code, the new builder IS the anticipated update. 

It's expected by the end of this year.