So, i just released a new version of a homebrew race, and the subraces from the previous addition have not been added to the new addition.

Overall, i've found the iterative nature of the homebrew publishing system quite painful to work with, especially since i cant edit something once its live. Im tempted to just give up on sharing my work and just use it in my own campaigns where i can manage it. The lack of correlation between races and their subraces, especially for 100% homebrew ones, is rather disconcerting, even in character builder, homebrew subraces are not put under their parent races at all. 

There are many upsides to DnD beyond, but its black marks are quite glaring.

Or at least  just to completely hide it from my account. 

Im tired of seeing the same homebrew name 10 times in my template options for making a new race. And im done with the public sharing. Theres no ability to manage the iterations and past versions of your creations.

I don't remember where they state this, but they do state somewhere that the reason you can't remove published homebrew content is that someone may be using that version and likes it the way it is. If you removed it, they would lose something they are using.

Sorry to necro this, but even if you remove them from your collection they all appear when you are creating other homebrew, example: https://pasteboard.co/IojBRMs.png.

This isn't how development works. Things occur in production systems that were not caught during testing all the time. Hotfixes are a reality in any system, and with hotfixes, not hosting obsolete versions of work is important as well. If someone likes an old version of your stuff, but Wizards releases a new sourcebook that makes your homebrew no longer compatible with RAW unless you've made a change, this is just one of many scenarios where the ability to deprecate old versions - the old version is still there, but important information about it no longer being D&D compatible is there as well with a link to a new compatible version - is important. And really, any situation where user feedback is implemented requires the ability to deprecate work. We absolutely need the ability to, at the very least, tag old versions of something obsolete or otherwise deprecate them, and link to new versions. Please consider this a bug, not a feature.

The expectation I have is this, and this would be ridiculously easy to fix.

When you visit the most recent version of an item, you can see previous versions. This is good and expected.

When you visit older versions of an item, you cannot see more recent versions of the item. This is not ok.

Being unable to delete something is fine. Being unable to deprecate it is not ok.

With all that said there is a work-around.

Since homebrew has a comments section, nothing is preventing us from using this to store metadata.

Of course this requires keeping a comments section up and maintaining it, so this is not a solution, as maintaining comments sections always carries with it an obligation even if the D&D community is generally well behaved.

But it's there already and it works.

And sorry for 3 posts in a row, but all _that_ said, deprecation does exist in one location. When you use the version tag, and you search for homebrew magic items ( https://www.dndbeyond.com/homebrew/magic-items ), I've just tested this, and only the highest numerical version result shows.

While I am at it there is one other related annoyance with homebrew - and before I get into it, thank you so much for making this service available to us, I wouldn't be making these comments if I didn't care and you weren't already doing an excellent enough job that I'd expect you to act on this feedback, I value my time too much - when making a new version of something, avatars have to be re-uploaded

Steps to reproduce secondary problem :

1. Create a homebrew magic item
2. Upload an avatar for the item
3. Visit the item's summary page to ensure the avatar was uploaded correctly
4. Create a new version of the item

Expectation : The previously used avatar is already linked

Observed behavior : The avatar is now empty

This is related, because 90% of the time when I need to create a "fix it" new version - which you are not supporting for good reasons, but which would be resolved if we could delete or hide homebrew nonetheless - it's over this problem with publishing. Which is to say, I made a major change to something in response to feedback and am not just fixing typos, I make a new version of the item, and I have to make _another_ new version of the item because the publishing system didn't link my avatar and I forgot to account for this idiosyncrasy. To make things worse, all basic details _are_ successfully copied. Inexperienced designers will assume all they need to do is to test their own changes and even experienced designers having become aware of this behavior through experience have a whole slew of points of failure that need to be tested against a checklist, and this testing surface would be dramatically reduced if additional details were copied.

This holds true for all additional details, they have to be manually copied with an old version of the item in another window, but it's especially problematic and time consuming with avatars since you have to use the slow file upload process. And I can't imagine this plays nicely with storage on your end either.

Same problem. Was this ever fixed or explained onnhow to fix this? 

Quote from WarWolf88 >>

Same problem. Was this ever fixed or explained onnhow to fix this? 

There is no fixing. It is best to not publish anything unless you are absolutely sure you know what you are doing. Once homebrew is published, it is final; you cannot unpublish it and you cannot make any changes. At best, you can publish new versions, but the old versions will always be there, so old versions WILL clog up your drop down menus over time if you keep publishing revisions.

If you want to share something to get feedback, you can simply ask the community on the forums, Facebook, Reddit, or whatever your social media of choice, and just write the description of the homebrew there.

For playtesting, you can invite some people to your campaign and have them playtest your private homebrew. If you are an average GM like me, I would stop here. You do not need to publish private homebrew to use it, and keeping it unpublished gives you the flexibility to keep making changes.

If you are an artist, influencer, or something along those lines and you need to publish it, make sure you go through multi rounds of playtesting first before you publish something. Publishing is final, so make sure you spend a lot of time playtesting things before you publish it.

Quote from WarWolf88 >>

Same problem. Was this ever fixed or explained onnhow to fix this? 

 There is no fix because it's not broken. It's explicitly by design that you cannot delete published homebrew content. This is something clearly stated in the homebrew rules and guidelines that you confirm you have read and acknowledged each time you publish homebrew content:

Please note that once you have published a homebrew creation, it cannot be removed. Once published, the creation can only be updated via the “Create new version” option.

Gotcha lesson learned.