On a couple of my spells i submitted, I later realized I made a little goof after I submitted them. It is possible to edit the spells after you share them? I don't see the edit button anywhere.
Once content has been published, other users can add it to their collection and use it on their character sheets.
It's for this reason that you're no longer allowed to edit it once submitted.
Imagine someone likes a magical assassin dagger they found on homebrew, and gives it out to one of their players as a reward, then the author "edits" the dagger to give it a vastly different powers instead.
When you click the "new version" it creates a copy of your existing published homebrew, that you can then edit and submit when you're happy it's fully tested and working.
That's the key bit here - please only publish homebrew once you've tested it and checked it for typos etc.
That's the key bit here - please only publish homebrew once you've tested it and checked it for typos etc.
Yep. Published content is thrown out of your hands and given to the community at large. Once it's published, it's no longer yours, it belongs to everyone.
You don't have to publish any homebrew for you and your players to use it. Even if you don't publish, you can freely use it in your own campaigns have have campaign members utilize it.
We don't have paid editors for our content that are going to proof read every single nuance of a spell, inevitably many of the spells in homebrew are going to have errors, especially since the spell creation system here is very limiting. So not allowing editing of published works to be edited by the creator just makes no sense. Just because someone uses one of your spells shouldn't matter, the nature of homebrew is that magic is not a fixed thing, it can change over time.. If they are using an app on this site, the app should just be updated to the current version whenever they use the spell again..
This is really no big deal, it just takes a few lines of code to fix.
If someone takes your spell and makes it their own, that's fine.. it has no bearing on my comment.
The homebrew spell bloat is out of control, there must be so many versions of the same spell running around because we can't simply edit them.
Which means you have to be your own Playtestor and Editor. Once a homebrew is “written,” that doesn’t mean it is “finished.” Always take the time to thoroughly playtest and edit your homebrews prior to publishing them to avoid this issue in future.
Published is permanent, just as if you had sent it to the printer and had a bajillion copies made and distributed like WorC does. They also do not have the luxury of editing something that is published. They have to issue formal errata and then subsequent copies of those books will reflect those changes, like they did for the Bladesinger. (To be fair, DDB does update the books to reflect any errata, but that has to all be done manually and they don’t have enough interns to go through every Homebrew individually like that. And they cannot automate the process or you could publish something, wait until a bunch of people have added it, and then change it to something offensive like inappropriate language, or political/religious propaganda. They do what they do for the entire comunity, not any one user like you or I.
As Dr. Spok would point out, the needs of the many outweigh the needs of the few or the one.
Every other homebrew site allows stuff to be edited after it is created.. this is just a totally lazy way of coding.. It's not like this website is a book or a magazine. This is just a deterrent from people posting and signing up for the paid part of this site. Why would I pay to use this site, when it doesn't even have basic homebrew functionality. You can't create new classes on this site..
What a joke..
I figured out that be making a new version of a spell, you can correct the editing mistakes, but the older spells stay in the data, you can't even delete them. RIP, the site's storage drives..
My advise is to do what I do, don't publish anything. You can share in your campaigns without publishing, and if someone else wants it, direct them to this forum, or walk them through the steps to make their own version (and they can then tweak it as they see fit). And if you really want to publish, there is the amazing homebrew community here. Let us give it a quick glance / second set of eyes to spot imbalance / clarity / typo issues before you do that which can never be undone.
But I agree that DDB has a peculiar take on homebrew publishing. If Github, Wikipedia, & DDB itself can have editing of published material while being way more accessible to & used by the general public than our homebrew will ever be, DDB can also allow it for us. It ain't exactly dragon magic.
We cannot have a situation where a stranger is able to change other people's character sheets without their knowledge - the reasoning for this should hopefully be obvious.
Let me take it a step further than the assassin dagger I mentioned before.
Imagine a user creates and publishes a homebrew barbarian subclass, which proves popular and many hundreds of other users add it to their collection. Imagine you're one of those users and you've been playing that barbarian character for several sessions and are really enjoying it. It's time for your D&D game and you're super-excited and you open your character sheet, to discover that all of the subclass abilities your character has have changed - because the author got bored of the design and edited it. Your character is now wrecked and the game just started.
This is the reason why homebrew is immutable once published and why you need to create new versions.
It is not "lazy design" and it isn't something that requires a fix.
It's also why we ask that people test their homebrew before they publish. 😊
I will note that we recognise that the whole homebrew solution is far from perfect and DOES need an overhaul. Ultimately, if someone publishes an update to a piece of homebrew, the vision is that users who currently use that homebrew would be notified and given the option on whether they wish to update.
Response #1 (admittedly snarky): Amazing how 99.99% of the Internet, which is updated constantly, and thousands (tens of thousands?) of other sites that hold user-created content used by 3rd parties don't have this issue. My, what a special snowflake DDB must be.
R #2 (less snarky, more helpful): It seems like it is mostly a basic UI/UX issue. Let creators update Homebrew#CurrentVersion, which is also what initially displays to other users. Put the earlier versions, if any, behind a "Previous Versions" button. Users can link their Homebrew Collection to either a specific version (Homebrew#1.0, #1.5, and so on) or to Homebrew#CurrentVersion. Everyone wins.
The root of the problem seems to be DDB's insistence on saving all homebrew versions *and* displaying them as completely independent items. There is a reason that as far as I know no other site does this, and that's because it's a hot mess of a bad creator experience (see the OP here, along with dozens of others) AND a bad user experience (multiple, nearly identical, versions of the same thing to slog through OR incomplete items never get updated so that everyone has the same reference point). You can delete tweets on Twitter, and videos on YouTube, update code on Github, blog posts on Medium, and forum posts on DDB. It's on the 3rd party user to save the text or video if they believe it is worth archiving. Even your own UA policy archives outdated items, and puts the responsibility of saving it on the user (either by never changing that aspect of the character, or recreating it as homebrew).
Everywhere except DDB's homebrew section... which will only get worse as more features are added, and old homebrew gets updated to use them.
Make Version 1, publish it. People add it and use it.
Oh no you've noticed something is wrong or something needs an edit. Make Version 2.
In the search listings Version 1 disappears and it now brings up Version 2.
People using Version 1 keep using Version 1 and get a notification there's a Version 2 which they can optionally choose if they want.
Everybody wins here: new people see Version 2 and add that. The peeps with Version 1 continue to use that if they prefer it.
All good an' gravy.
So what is the issue?
Rollback Post to RevisionRollBack
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond. Need help with Homebrew? Check out ✨ thisFAQ/Guide thread ✨ by IamSposta.
My main issue with it is whenever you go to add that spell to another Homebrew like a subclass, when you are in there the builder still shows you every version of that spell even if only the one version. In your our collection, even the Failed Deleted copies. So now you wanna add ”Spell X” when you do all you see are multiple versions of “spell X” being listed with absolutely no indication whatsoever as to which is which. Since nobody ever warned me about that limitation I didn’t notice it was happening until I started finding a bajillian dupes in my Homebrewer.
On a couple of my spells i submitted, I later realized I made a little goof after I submitted them. It is possible to edit the spells after you share them? I don't see the edit button anywhere.
Thanks
Grum El Tres.
you have to create a new version and publish it after you've edited it, you can't actually edit any brew you've published.
Feel free to check out my hombrew: Magic Items, Spells, Monsters, Species, Feats, Subclassses, and Backgrounds. More detail in my Homebrew Compendium.
If you have any comments, suggestions, or ways to improve my homebrew, tell me, I'm always looking to improve!
Map commission Here.
Thanks for that, but seems like a cumbersome system that just bloats the spell lists... I might go back to D&D Wiki if that is the case..
Once content has been published, other users can add it to their collection and use it on their character sheets.
It's for this reason that you're no longer allowed to edit it once submitted.
Imagine someone likes a magical assassin dagger they found on homebrew, and gives it out to one of their players as a reward, then the author "edits" the dagger to give it a vastly different powers instead.
When you click the "new version" it creates a copy of your existing published homebrew, that you can then edit and submit when you're happy it's fully tested and working.
That's the key bit here - please only publish homebrew once you've tested it and checked it for typos etc.
Pun-loving nerd | Faith Elisabeth Lilley | She/Her/Hers | Profile art by Becca Golins
If you need help with homebrew, please post on the homebrew forums, where multiple staff and moderators can read your post and help you!
"We got this, no problem! I'll take the twenty on the left - you guys handle the one on the right!"🔊
Yep. Published content is thrown out of your hands and given to the community at large. Once it's published, it's no longer yours, it belongs to everyone.
You don't have to publish any homebrew for you and your players to use it. Even if you don't publish, you can freely use it in your own campaigns have have campaign members utilize it.
We don't have paid editors for our content that are going to proof read every single nuance of a spell, inevitably many of the spells in homebrew are going to have errors, especially since the spell creation system here is very limiting. So not allowing editing of published works to be edited by the creator just makes no sense. Just because someone uses one of your spells shouldn't matter, the nature of homebrew is that magic is not a fixed thing, it can change over time.. If they are using an app on this site, the app should just be updated to the current version whenever they use the spell again..
This is really no big deal, it just takes a few lines of code to fix.
If someone takes your spell and makes it their own, that's fine.. it has no bearing on my comment.
The homebrew spell bloat is out of control, there must be so many versions of the same spell running around because we can't simply edit them.
Which means you have to be your own Playtestor and Editor. Once a homebrew is “written,” that doesn’t mean it is “finished.” Always take the time to thoroughly playtest and edit your homebrews prior to publishing them to avoid this issue in future.
Published is permanent, just as if you had sent it to the printer and had a bajillion copies made and distributed like WorC does. They also do not have the luxury of editing something that is published. They have to issue formal errata and then subsequent copies of those books will reflect those changes, like they did for the Bladesinger. (To be fair, DDB does update the books to reflect any errata, but that has to all be done manually and they don’t have enough interns to go through every Homebrew individually like that. And they cannot automate the process or you could publish something, wait until a bunch of people have added it, and then change it to something offensive like inappropriate language, or political/religious propaganda. They do what they do for the entire comunity, not any one user like you or I.
As Dr. Spok would point out, the needs of the many outweigh the needs of the few or the one.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Every other homebrew site allows stuff to be edited after it is created.. this is just a totally lazy way of coding.. It's not like this website is a book or a magazine. This is just a deterrent from people posting and signing up for the paid part of this site. Why would I pay to use this site, when it doesn't even have basic homebrew functionality. You can't create new classes on this site..
What a joke..
I figured out that be making a new version of a spell, you can correct the editing mistakes, but the older spells stay in the data, you can't even delete them. RIP, the site's storage drives..
My advise is to do what I do, don't publish anything. You can share in your campaigns without publishing, and if someone else wants it, direct them to this forum, or walk them through the steps to make their own version (and they can then tweak it as they see fit). And if you really want to publish, there is the amazing homebrew community here. Let us give it a quick glance / second set of eyes to spot imbalance / clarity / typo issues before you do that which can never be undone.
But I agree that DDB has a peculiar take on homebrew publishing. If Github, Wikipedia, & DDB itself can have editing of published material while being way more accessible to & used by the general public than our homebrew will ever be, DDB can also allow it for us. It ain't exactly dragon magic.
I explained the reasoning in my post above.
We cannot have a situation where a stranger is able to change other people's character sheets without their knowledge - the reasoning for this should hopefully be obvious.
Let me take it a step further than the assassin dagger I mentioned before.
Imagine a user creates and publishes a homebrew barbarian subclass, which proves popular and many hundreds of other users add it to their collection. Imagine you're one of those users and you've been playing that barbarian character for several sessions and are really enjoying it. It's time for your D&D game and you're super-excited and you open your character sheet, to discover that all of the subclass abilities your character has have changed - because the author got bored of the design and edited it. Your character is now wrecked and the game just started.
This is the reason why homebrew is immutable once published and why you need to create new versions.
It is not "lazy design" and it isn't something that requires a fix.
It's also why we ask that people test their homebrew before they publish. 😊
I will note that we recognise that the whole homebrew solution is far from perfect and DOES need an overhaul. Ultimately, if someone publishes an update to a piece of homebrew, the vision is that users who currently use that homebrew would be notified and given the option on whether they wish to update.
Pun-loving nerd | Faith Elisabeth Lilley | She/Her/Hers | Profile art by Becca Golins
If you need help with homebrew, please post on the homebrew forums, where multiple staff and moderators can read your post and help you!
"We got this, no problem! I'll take the twenty on the left - you guys handle the one on the right!"🔊
Response #1 (admittedly snarky): Amazing how 99.99% of the Internet, which is updated constantly, and thousands (tens of thousands?) of other sites that hold user-created content used by 3rd parties don't have this issue. My, what a special snowflake DDB must be.
R #2 (less snarky, more helpful): It seems like it is mostly a basic UI/UX issue. Let creators update Homebrew#CurrentVersion, which is also what initially displays to other users. Put the earlier versions, if any, behind a "Previous Versions" button. Users can link their Homebrew Collection to either a specific version (Homebrew#1.0, #1.5, and so on) or to Homebrew#CurrentVersion. Everyone wins.
The root of the problem seems to be DDB's insistence on saving all homebrew versions *and* displaying them as completely independent items. There is a reason that as far as I know no other site does this, and that's because it's a hot mess of a bad creator experience (see the OP here, along with dozens of others) AND a bad user experience (multiple, nearly identical, versions of the same thing to slog through OR incomplete items never get updated so that everyone has the same reference point). You can delete tweets on Twitter, and videos on YouTube, update code on Github, blog posts on Medium, and forum posts on DDB. It's on the 3rd party user to save the text or video if they believe it is worth archiving. Even your own UA policy archives outdated items, and puts the responsibility of saving it on the user (either by never changing that aspect of the character, or recreating it as homebrew).
Everywhere except DDB's homebrew section... which will only get worse as more features are added, and old homebrew gets updated to use them.
I don't understand what the issue is, here.
Make Version 1, publish it. People add it and use it.
Oh no you've noticed something is wrong or something needs an edit. Make Version 2.
In the search listings Version 1 disappears and it now brings up Version 2.
People using Version 1 keep using Version 1 and get a notification there's a Version 2 which they can optionally choose if they want.
Everybody wins here: new people see Version 2 and add that. The peeps with Version 1 continue to use that if they prefer it.
All good an' gravy.
So what is the issue?
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond.
Need help with Homebrew? Check out ✨ this FAQ/Guide thread ✨ by IamSposta.
My main issue with it is whenever you go to add that spell to another Homebrew like a subclass, when you are in there the builder still shows you every version of that spell even if only the one version. In your our collection, even the Failed Deleted copies. So now you wanna add ”Spell X” when you do all you see are multiple versions of “spell X” being listed with absolutely no indication whatsoever as to which is which. Since nobody ever warned me about that limitation I didn’t notice it was happening until I started finding a bajillian dupes in my Homebrewer.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting