I have a question. I made a homebrew of grogs bloodaxe before it was official in the Wildemount book. Because it’s now an official item shouldn’t I be able to delete it because it’s a purchasable item on beyond now?
You would have to report your own homebrew as a cult write thing and hope that the Mods agree and “reject” it for you.
I made a homebrew race only to realize that none of the race modifiers for ability score etc were showing up in my players character sheets, so now I am trying to go and fix that mistake, only to find I can't edit the published race, and the new version doesn't keep the four subraces the race has, so I would have to redo all four just to add two modifiers to features. this is frankly ridiculous and makes way more work than necessary. I already spent hours typing stuff up just to have to do it again because the whole thing is so confusing.
I made a homebrew race only to realize that none of the race modifiers for ability score etc were showing up in my players character sheets, so now I am trying to go and fix that mistake, only to find I can't edit the published race, and the new version doesn't keep the four subraces the race has, so I would have to redo all four just to add two modifiers to features. this is frankly ridiculous and makes way more work than necessary. I already spent hours typing stuff up just to have to do it again because the whole thing is so confusing.
While I do agree having to redo the subraces is a pain the arse, I do have to ask, though, why did you not test your homebrew before publishing it? You don't need to publish it to use it (and you don't need to publish it for people in your campaign to use it) and you should really be testing your homebrew on a test character before doing so.
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.
I made a homebrew race only to realize that none of the race modifiers for ability score etc were showing up in my players character sheets, so now I am trying to go and fix that mistake, only to find I can't edit the published race, and the new version doesn't keep the four subraces the race has, so I would have to redo all four just to add two modifiers to features. this is frankly ridiculous and makes way more work than necessary. I already spent hours typing stuff up just to have to do it again because the whole thing is so confusing.
While I do agree having to redo the subraces is a pain the arse, I do have to ask, though, why did you not test your homebrew before publishing it? You don't need to publish it to use it (and you don't need to publish it for people in your campaign to use it) and you should really be testing your homebrew on a test character before doing so.
This^^^
Please, thoroughly playtest and edit homebrews before publishing and it solves a lot of these problems.
Until any such feature is implemented, publicly submitted homebrew will become content for the community. As Filcat mentioned, users can submit updated versions, but we will not be fielding reports to delete public items. The 'Private' homebrew feature allows for testing and editing, which players can join into campaigns to do. Once submitted to 'Public', it becomes community-owned as a final draft.
I'm curious about what is meant by community-owned. Supposing I were to wrap up a bunch of my published homebrews for distribution on DMs Guild or something like that, would I be running afoul of IP rights?
The idea of entirely removing the option to delete a published homebrew is comedic and tragic.
i started on an idea for a homebrew species right when I got into dnd, and thought "oh hey, I'll publish what I have so far, so people who have been in this community longer than I have can help me *EDIT* it"
the entire text is so short, I can copy and paste it here
"long ago, before the world of (name of world) came to be, long before (if any previous versions of this world exist, i.e. creation story) ever existed, the demons were there, as the form of utmost evil. when the day of man came around, it was only natural for interest to be expressed. and from that interest, a race of half-demons was born, capable of super-human feats.
I'm new to dnd, I literally just started 5 minutes ago, so I might have to come back and edit this, please offer as much quality feedback as possible.
as a daemon, you're naturally charismatic, granting you +5 charisma. you're naturally fit, granting you +5 strength along with other skills such as +5 acrobatics this is a work in progress, I'll finish this after I make my character and figure out what the rest of the stats are lmao you have a keen sense of smell, hearing, and sight granting you the skills of echolocation, and another form of echolocation except for smell"
The fact that I ran into this problem back in 2020, and here I am in 2022 making my first ever character sheet because of the lack of user-friendly tools on this site, speaks volumes unachievable by the loudest roars of a dragon.
The idea of entirely removing the option to delete a published homebrew is comedic and tragic.
i started on an idea for a homebrew species right when I got into dnd, and thought "oh hey, I'll publish what I have so far, so people who have been in this community longer than I have can help me *EDIT* it"
D&D Beyond provides a set of homebrew rules and guidelines that are linked on the confirmation dialogue that appears when you attempt to publish something. These rules clearly state the following:
When using the homebrew features on D&D Beyond, it is important to note that while you have access to the tools to create homebrew, you do not need to publish it. Publishing it means it will be shared with the entire site and used for public consumption. You are always welcome to use your homebrew creations privately to avoid having it rejected from the public should it violate any of the guidelines listed below.
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.
...
Please ensure that any public homebrew content you submit contains all of the correct modifiers. Missing modifiers may cause issues with values not appearing properly within the character sheet/character builder.
Please ensure all properties/abilities (such as spells and modifiers) are listed in the description, as this is the only field seen when people view the homebrew listings.
If you wish for others to review your work in progress homebrew, you do not need to publish it. Instead, you can invite people to join a campaign (no subscription or content sharing required) and there they'll be able to access all your homebrew, regardless of being published or not.
We do ask people read the homebrew rules and guidelines before publishing content, they're not that long (certainly shorter than this thread)
the issue, Davyd, is that you cannot invite the forum as a whole to your campaign to help you review homebrew. You have to post snippet screenshots of your work if you want to ask for assistance in the Homebrew section, as one example. It makes it extremely difficult for people who do not have an already established circle of buddies to vet their work for them, and frankly it's even more difficult to get informed opinions from outside that circle of buddies.
Would it be possible to propose an intermediate step between "Private" and "Published", called "Prototype"? A setting that makes homebrew viewable to anyone with the link, but which disallows that homebrew to be added to collections or otherwise downloaded? Given that players can freely ignoring the versioning system and will always choose to use the oldest, shittiest, least refined and playable version of whatever it is you publish, the versioning system is a trap. I've wanted to fix up my homebrew kitsune species for ages now to make it pseudo-Tasha's compliant and sort out a few updates I'd like to make, but I LITERALLY CAN'T because everyone who bothers with it is actively encouraged to ignore the new updates and keep using the old bad version. It's why I don't really publish homebrew anymore, much as I'd like to offer up some of the cool ideas I've had for things that have really helped my game.
Wizards of the Coast is allowed to prototype content via UA, and to force users to use the latest versions of their content even when those users violently wish otherwise. You've seen that yourself lately, with all of the backlash and hooplah about the latest errata and now the M3 changes coming in a couple of weeks. Why are DDB's paying users required to forcibly commit to only the worst possible version of anything they've made?
Would it be possible to propose an intermediate step between "Private" and "Published", called "Prototype"?
This is something that has been historically suggested and passed along, multiple times if I recall correctly.
As it stands, the system works the way it does to ensure stability of user experience. Yes, it's rigid in its approach which is why it's detailed (multiple times) in the rules and guidelines.
I have been suggesting / advocating for an intermediate step between private and published homebrews for 2 & ½ years. My that would solve a lot of problems.
I don't know how it used to be, but now you can unsubscribe to older versions of your items so that people in your campaign will no longer see them. They might still be floating out there somewhere but as far as I'm concerned that's just as good as deleting it for real.
I don't know how it used to be, but now you can unsubscribe to older versions of your items so that people in your campaign will no longer see them. They might still be floating out there somewhere but as far as I'm concerned that's just as good as deleting it for real.
You mean remove them from your collection? It has always been that way.
The problem that is the reason this 4 year old thread keeps getting necro'd is that people don't read the warnings or seek out any of the plethora of tools available to them other than sending unfinished homebrew into the world outside their ability to take it back (which is made clear in the thread they are prompted to read everytime they try to publish).
It is like publishing a book. Once it has been sold, the author does not have the ability to take ot from people's homes.
At the very least it would be nice to have the "shadow" versions of old published homebrews removed to keep up with the most recent update. I update my published homebrews very frequently, especially now that D&D is undergoing a transitional phase. It has rendered the several of the menu functions I used to use completely useless.
This is not an issue of unfinished homebrews. As mentioned, it's about trying to get feedback en masse without inviting every user into a campaign.
It would be nice if it said something like "once published, this content can no longer be edited or deleted."
Without any warning to that,any users get stuck with excess homebrew items in their list they can't get rid of anymore.
To be fair, that wouldn't be true if it did. You can create new versions which replace the old ones.
I suppose they could make a pop-up warning that at least says "Only click the submit button if you want the entire DDB community to have access. View the Public Homebrew Content Rules & Guidelines." That way any literate person not randomly clicking buttons would be properly warned. Oh, wait...
If you have ever even try to learn about the homebrew tools, it would be impossible to not find out what publishing means.
It is actually harder to learn how to use the tools and publish something than it is to learn this information. Especially since the tools themselves prompt you to learn before doing so.
It isn't like I'm opposed to the idea, I just wish we didn't have to baby proof the interface so people stop blaming others for not reading. Or am I the only one too self conscious to publish crap homebrew that doesn't even work before looking up tutorials on how to properly use the tool?
If anything, I kind of wish they put more resources into curating the public homebrew collection. Maybe there could be 2 tiers of public homebrew: 1 that is where new homebrew lands, and a second where only approved homebrew gets promoted to.
It isn't like I'm opposed to the idea, I just wish we didn't have to baby proof the interface so people stop blaming others for not reading. Or am I the only one too self conscious to publish crap homebrew that doesn't even work before looking up tutorials on how to properly use the tool?
If anything, I kind of wish they put more resources into curating the public homebrew collection. Maybe there could be 2 tiers of public homebrew: 1 that is where new homebrew lands, and a second where only approved homebrew gets promoted to.
That “abomination” as you call it has 12 likes including a Moderator, and a staff member has endorsed it and passed it on to the Dev team. Sooo….
Hey, I feel ya, but the world has to protect ignorant people from themselves at times.
I suggested that 2 years ago and it got shot down as a non-starter.
Clearly the "clearly explained" ramification of published homebrew aren't reaching the bulk of users. I think a "are you SURE you want to do this?" would be worth a shot. Funny how a recent survey of up and down votes on homebrew was circulated. Given the literal dumping ground the bulk of published homebrew is, I for one would be all for the creator being the first line of QA. Lots of interfaces exist with someone on the engineering team tasked with a "I shouldn't have to write this, but..." notice alerting users to certain ramifications. I've held jobs where I had to write many "I shouldn't have to write this" memos and _really_ would have rather simply circulated "RTFM! The rules are there and clear" but if you got a system awash with unintended material, the only way you hone the system to be more of what you want is by belaboring the point, literally making it part of the work.
Rollback Post to RevisionRollBack
Jander Sunstar is the thinking person's Drizzt, fight me.
To post a comment, please login or register a new account.
You would have to report your own homebrew as a cult write thing and hope that the Mods agree and “reject” it for you.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I made a homebrew race only to realize that none of the race modifiers for ability score etc were showing up in my players character sheets, so now I am trying to go and fix that mistake, only to find I can't edit the published race, and the new version doesn't keep the four subraces the race has, so I would have to redo all four just to add two modifiers to features. this is frankly ridiculous and makes way more work than necessary. I already spent hours typing stuff up just to have to do it again because the whole thing is so confusing.
While I do agree having to redo the subraces is a pain the arse, I do have to ask, though, why did you not test your homebrew before publishing it? You don't need to publish it to use it (and you don't need to publish it for people in your campaign to use it) and you should really be testing your homebrew on a test character before doing so.
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.
This^^^
Please, thoroughly playtest and edit homebrews before publishing and it solves a lot of these problems.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Yeah, 9 out of 10 complaints about not being able to easily edit published homebrew is because they published something that didn't work.
Would it be possible to get a response to this?
The idea of entirely removing the option to delete a published homebrew is comedic and tragic.
i started on an idea for a homebrew species right when I got into dnd, and thought "oh hey, I'll publish what I have so far, so people who have been in this community longer than I have can help me *EDIT* it"
the entire text is so short, I can copy and paste it here
"long ago, before the world of (name of world) came to be, long before (if any previous versions of this world exist, i.e. creation story) ever existed, the demons were there, as the form of utmost evil. when the day of man came around, it was only natural for interest to be expressed. and from that interest, a race of half-demons was born, capable of super-human feats.
I'm new to dnd, I literally just started 5 minutes ago, so I might have to come back and edit this, please offer as much quality feedback as possible.
as a daemon, you're naturally charismatic, granting you +5 charisma. you're naturally fit, granting you +5 strength along with other skills such as +5 acrobatics
this is a work in progress, I'll finish this after I make my character and figure out what the rest of the stats are lmao
you have a keen sense of smell, hearing, and sight granting you the skills of echolocation, and another form of echolocation except for smell"
The fact that I ran into this problem back in 2020, and here I am in 2022 making my first ever character sheet because of the lack of user-friendly tools on this site, speaks volumes unachievable by the loudest roars of a dragon.
D&D Beyond provides a set of homebrew rules and guidelines that are linked on the confirmation dialogue that appears when you attempt to publish something. These rules clearly state the following:
If you wish for others to review your work in progress homebrew, you do not need to publish it. Instead, you can invite people to join a campaign (no subscription or content sharing required) and there they'll be able to access all your homebrew, regardless of being published or not.
We do ask people read the homebrew rules and guidelines before publishing content, they're not that long (certainly shorter than this thread)
Find my D&D Beyond articles here
the issue, Davyd, is that you cannot invite the forum as a whole to your campaign to help you review homebrew. You have to post snippet screenshots of your work if you want to ask for assistance in the Homebrew section, as one example. It makes it extremely difficult for people who do not have an already established circle of buddies to vet their work for them, and frankly it's even more difficult to get informed opinions from outside that circle of buddies.
Would it be possible to propose an intermediate step between "Private" and "Published", called "Prototype"? A setting that makes homebrew viewable to anyone with the link, but which disallows that homebrew to be added to collections or otherwise downloaded? Given that players can freely ignoring the versioning system and will always choose to use the oldest, shittiest, least refined and playable version of whatever it is you publish, the versioning system is a trap. I've wanted to fix up my homebrew kitsune species for ages now to make it pseudo-Tasha's compliant and sort out a few updates I'd like to make, but I LITERALLY CAN'T because everyone who bothers with it is actively encouraged to ignore the new updates and keep using the old bad version. It's why I don't really publish homebrew anymore, much as I'd like to offer up some of the cool ideas I've had for things that have really helped my game.
Wizards of the Coast is allowed to prototype content via UA, and to force users to use the latest versions of their content even when those users violently wish otherwise. You've seen that yourself lately, with all of the backlash and hooplah about the latest errata and now the M3 changes coming in a couple of weeks. Why are DDB's paying users required to forcibly commit to only the worst possible version of anything they've made?
Please do not contact or message me.
This is something that has been historically suggested and passed along, multiple times if I recall correctly.
As it stands, the system works the way it does to ensure stability of user experience. Yes, it's rigid in its approach which is why it's detailed (multiple times) in the rules and guidelines.
Find my D&D Beyond articles here
I have been suggesting / advocating for an intermediate step between private and published homebrews for 2 & ½ years. My that would solve a lot of problems.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I don't know how it used to be, but now you can unsubscribe to older versions of your items so that people in your campaign will no longer see them. They might still be floating out there somewhere but as far as I'm concerned that's just as good as deleting it for real.
You mean remove them from your collection? It has always been that way.
The problem that is the reason this 4 year old thread keeps getting necro'd is that people don't read the warnings or seek out any of the plethora of tools available to them other than sending unfinished homebrew into the world outside their ability to take it back (which is made clear in the thread they are prompted to read everytime they try to publish).
It is like publishing a book. Once it has been sold, the author does not have the ability to take ot from people's homes.
At the very least it would be nice to have the "shadow" versions of old published homebrews removed to keep up with the most recent update. I update my published homebrews very frequently, especially now that D&D is undergoing a transitional phase. It has rendered the several of the menu functions I used to use completely useless.
This is not an issue of unfinished homebrews. As mentioned, it's about trying to get feedback en masse without inviting every user into a campaign.
It would be nice if it said something like "once published, this content can no longer be edited or deleted."
Without any warning to that,any users get stuck with excess homebrew items in their list they can't get rid of anymore.
To be fair, that wouldn't be true if it did. You can create new versions which replace the old ones.
I suppose they could make a pop-up warning that at least says "Only click the submit button if you want the entire DDB community to have access. View the Public Homebrew Content Rules & Guidelines." That way any literate person not randomly clicking buttons would be properly warned. Oh, wait...
If you have ever even try to learn about the homebrew tools, it would be impossible to not find out what publishing means.
It is actually harder to learn how to use the tools and publish something than it is to learn this information. Especially since the tools themselves prompt you to learn before doing so.
You mean like this?
https://www.dndbeyond.com/forums/d-d-beyond-general/d-d-beyond-feedback/125389-an-easy-win-win-win-for-everyone-or-the-layup-hat
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Ugh, what is that abomination? /joke
It isn't like I'm opposed to the idea, I just wish we didn't have to baby proof the interface so people stop blaming others for not reading. Or am I the only one too self conscious to publish crap homebrew that doesn't even work before looking up tutorials on how to properly use the tool?
If anything, I kind of wish they put more resources into curating the public homebrew collection. Maybe there could be 2 tiers of public homebrew: 1 that is where new homebrew lands, and a second where only approved homebrew gets promoted to.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Clearly the "clearly explained" ramification of published homebrew aren't reaching the bulk of users. I think a "are you SURE you want to do this?" would be worth a shot. Funny how a recent survey of up and down votes on homebrew was circulated. Given the literal dumping ground the bulk of published homebrew is, I for one would be all for the creator being the first line of QA. Lots of interfaces exist with someone on the engineering team tasked with a "I shouldn't have to write this, but..." notice alerting users to certain ramifications. I've held jobs where I had to write many "I shouldn't have to write this" memos and _really_ would have rather simply circulated "RTFM! The rules are there and clear" but if you got a system awash with unintended material, the only way you hone the system to be more of what you want is by belaboring the point, literally making it part of the work.
Jander Sunstar is the thinking person's Drizzt, fight me.