Problems with homebrew subclass publication

Hi guys,

I'm currently trying to publish a homebrew subclass for the druid. However, Beyond is telling me that I don't have the needed features for each level of a Druid class, which is quite confusing, considering i indeed have one feature for each of the levels (3,6,10,14).

It's my first time creating a homebrew subclass, so I'm assuming I'm doing something wrong...

Has anyone had a similar problem before or does anyone know how to solve this?

Thanks in advance.

Are you trying to publish a subclass for the 2014/5e Druid class or the 2024/5.5e Druid class? If it's the former, you need a feature at level 2 rather than at level 3. 

There is also a bug that affects some classes, some of the time, where the thing that verifies this specific thing is sometimes expecting features at the levels for both versions of the class. This has been happening off and on since the release of the 5.5e Player's Handbook in 2024 and they keep allegedly fixing it and it keeps coming back. When this bug is occurring, people have usually found success with adding dummy features to match both sets of levels. In the case of the Druid class you'd want 2, 3, 6, 10, and 14 then.

It's also always worth pointing out that you only need to publish a homebrew thing if you want random strangers to be able to use it; you and the people in your campaigns can use it without it being published.

I'm actually using the 5.5e.

Thank you for your explenation too.

mine is on 5.5e with the subclass features on 3,3,6,10,14 and it doesn't bloody work somehow. (i've worked on this for 6 WEEKS BTW and the people on the discord are being absolutely unhelpful as HELL)

Quote from FireballFishballs >>

mine is on 5.5e with the subclass features on 3,3,6,10,14 and it doesn't bloody work somehow. (i've worked on this for 6 WEEKS BTW and the people on the discord are being absolutely unhelpful as HELL)

This is a bug that keeps coming back every once in a while, seemingly whenever new subclasses are released; what it seems like is happening at least some of the time is that it's getting its list of the "right" levels by checking an existing official subclass, and sometimes it's checking one that has a bunch of weird hidden features or something that throws it off. However, this is just a theory of mine, as they almost never even acknowledge that this problem exists even when a ton of people report it.

As I noted above, sometimes you can work around it by adding dummy features at certain other levels, but it's just guesswork as to which levels those are. Otherwise, you just have to wait until they fix it, whenever that will be.