Once you publish a race with subraces you can no longer simply edit either one anymore. You will need to “create new version” for the base race, and then recreate each of the subraces from scratch.
This is just one of the many, many reasons it is always best practice to always fully proofread, playtest, and edit all homebrews prior to publishing them.
Understood. I had assumed that with the new versions created of the main race, the subraces would associat the latest version with being the parent race, like they were before. At least I know for future and can safely recreate them knowing they're functional already.
Fairly frustrating that you can't delete old versions after making a new version of the same homebrew, though. So embarrassing to see old me's stuff.
No, it won’t. And you don’t have to start completely over from scratch, just go to the details page for your base race and click “create new version.” Then you can update that and recreate all your subraces attached to that version. Whenever you eventually publish it again it will push the older version of the race into the background so to speak. People will still be able to access, read, and add the old version to their collections if they want to, but the new version will be what they see first.
When I wrote “fully cooked” I meant no disrespect. But if you’re making edits and republishing, then the old version couldn’t have been quite finished yet or you wouldn’t need to, even if it was just for something like spelling and typos for instance.
No, it won’t. And you don’t have to start completely over from scratch, just go to the details page for your base race and click “create new version.” Then you can update that and recreate all your subraces attached to that version. Whenever you eventually publish it again it will push the older version of the race into the background so to speak. People will still be able to access, read, and add the old version to their collections if they want to, but the new version will be what they see first.
I'm doing this now. I'm glad only one other person had added it to their collection, so it shouldn't be a hassle. I suppose the new subraces I'd made will just be floating around until I decide to remake them with a (Discontinued) tag. I was worried that due to being copies they'd break DDB's Copyright protection and I'd get a strike of some sort.
And I can understand how frustrating it must be for you to have to repeat this kind of thing to every Tom, Dick, and Harry that asks the same question every other day, so thank you for taking a moment to answer. The previous versions were up to date at the time of their publication, but over a year had passed since I'd written them and I'd been making non-published revisions during that time due to lore changes and personal view changes on the race. I was naive in hoping thew create new version this time would compensate for the hassle of remaking things from scratch.
No, it won’t. And you don’t have to start completely over from scratch, just go to the details page for your base race and click “create new version.” Then you can update that and recreate all your subraces attached to that version. Whenever you eventually publish it again it will push the older version of the race into the background so to speak. People will still be able to access, read, and add the old version to their collections if they want to, but the new version will be what they see first.
I'm doing this now. I'm glad only one other person had added it to their collection, so it shouldn't be a hassle. The new subraces that I'd made will just be floating around until I decide to remake them with a (Discontinued) tag, I suppose. I was worried that due to bein copies they'd break DDB's Copyright protection and I'd get a strike of some sort.
And I can understand how frustrating it must be for you to have to repeat this kind of thing to every Tom, Dick, and Harry that asks the same question every other day, so thank you for taking a moment to answer. The previous versions were up to date for the time of their publication, but over a year had passed since I'd written them and I'd been making non-published revisions during that time due to lore changes and personal view changes on the race. I was naive in hoping this time would make up for the hassle of needing to remake things from scratch.
Nah, DDB & WotC hold the rights to whatever we publish here, so they can’t conflict with themselves. It is a little frustrating, thank you for your understanding of that.
Exactly as the title says, I'm not sure if this is a bug or D&D Beyond just doesn't link new versions of homebrew this way.
https://www.dndbeyond.com/races/875674-ruhardian
https://www.dndbeyond.com/subraces/646017-royal-ruhardian
https://www.dndbeyond.com/subraces/646003-ashiibasa
Kan#6969
Once you publish a race with subraces you can no longer simply edit either one anymore. You will need to “create new version” for the base race, and then recreate each of the subraces from scratch.
This is just one of the many, many reasons it is always best practice to always fully proofread, playtest, and edit all homebrews prior to publishing them.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Understood. I had assumed that with the new versions created of the main race, the subraces would associat the latest version with being the parent race, like they were before. At least I know for future and can safely recreate them knowing they're functional already.
Fairly frustrating that you can't delete old versions after making a new version of the same homebrew, though. So embarrassing to see old me's stuff.
Kan#6969
Yet another of the excellent reasons not to publish stuff that isn’t quite fully cooked yet.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
If I remake a new version identical to it, will it not get flagged as a copy of someone else's work?
In my defence, the races are fully cooked and ready to go. I was not expecting D&D Beyond not to maintain the linkage between them...
Kan#6969
No, it won’t. And you don’t have to start completely over from scratch, just go to the details page for your base race and click “create new version.” Then you can update that and recreate all your subraces attached to that version. Whenever you eventually publish it again it will push the older version of the race into the background so to speak. People will still be able to access, read, and add the old version to their collections if they want to, but the new version will be what they see first.
When I wrote “fully cooked” I meant no disrespect. But if you’re making edits and republishing, then the old version couldn’t have been quite finished yet or you wouldn’t need to, even if it was just for something like spelling and typos for instance.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I'm doing this now. I'm glad only one other person had added it to their collection, so it shouldn't be a hassle. I suppose the new subraces I'd made will just be floating around until I decide to remake them with a (Discontinued) tag. I was worried that due to being copies they'd break DDB's Copyright protection and I'd get a strike of some sort.
And I can understand how frustrating it must be for you to have to repeat this kind of thing to every Tom, Dick, and Harry that asks the same question every other day, so thank you for taking a moment to answer. The previous versions were up to date at the time of their publication, but over a year had passed since I'd written them and I'd been making non-published revisions during that time due to lore changes and personal view changes on the race. I was naive in hoping thew create new version this time would compensate for the hassle of remaking things from scratch.
Kan#6969
Nah, DDB & WotC hold the rights to whatever we publish here, so they can’t conflict with themselves. It is a little frustrating, thank you for your understanding of that.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I always forget this ;-; If I published it elsewhere would I be liable? Or am I still considered the owner, and therefore, I can do so without worry?
Kan#6969