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.
The thing is, this already exists. Publishing homebrew is a two-action process with the second action being a confirmation dialogue that links to the homebrew rules. Unless you're suggesting a three-action process with two confirmation dialogues, in which case we'll still have the same problem. People will just continue clicking through the dialogues without reading. You can take a user to water, but you can't make them read a dialogue box.
You'd be surprised at the number of times I deal with requests that say "I accidentally hit publish when I didn't mean to"....
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.
The thing is, this already exists. Publishing homebrew is a two-action process with the second action being a confirmation dialogue that links to the homebrew rules. Unless you're suggesting a three-action process with two confirmation dialogues, in which case we'll still have the same problem. People will just continue clicking through the dialogues without reading. You can take a user to water, but you can't make them read a dialogue box.
You'd be surprised at the number of times I deal with requests that say "I accidentally hit publish when I didn't mean to"....
Instead of "are you sure" it needs to be "don't publish this unless you are done making it."
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.
The thing is, this already exists. Publishing homebrew is a two-action process with the second action being a confirmation dialogue that links to the homebrew rules. Unless you're suggesting a three-action process with two confirmation dialogues, in which case we'll still have the same problem. People will just continue clicking through the dialogues without reading. You can take a user to water, but you can't make them read a dialogue box.
You'd be surprised at the number of times I deal with requests that say "I accidentally hit publish when I didn't mean to"....
Instead of "are you sure" it needs to be "don't publish this unless you are done making it."
Changing the verbiage won't make any difference to the people who don't read the dialogue and just hit confirm.
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.
The thing is, this already exists. Publishing homebrew is a two-action process with the second action being a confirmation dialogue that links to the homebrew rules. Unless you're suggesting a three-action process with two confirmation dialogues, in which case we'll still have the same problem. People will just continue clicking through the dialogues without reading. You can take a user to water, but you can't make them read a dialogue box.
You'd be surprised at the number of times I deal with requests that say "I accidentally hit publish when I didn't mean to"....
Instead of "are you sure" it needs to be "don't publish this unless you are done making it."
Changing the verbiage won't make any difference to the people who don't read the dialogue and just hit confirm.
True, but red warning text and a nice visible [CANCEL] button can’t hurt, and it has to mitigate the issue for those folks who do read the dialogue box. I mean, they put “caution, contents hot” on takeout coffee cups for crying out loud. Amending the current dialogue box to be more explicit and attention grabbing can do no harm and can only help, even to a minor degree. If it saves 1 user from mistakenly publishing their undercooked homebrew it will have been worth it. Everyone it helps beyond that is gravy. If it helps a gross of people, and they would each have published 5 things but hold off, that’s still 720 half-baked homebrews that get to stay in the oven a li’l longer. That’s better than a kick in the dangly bits any day. And the longer it exists, the more likely it will help more people. That’s potentially thousands of homebrews that could be saved the ignominy of being published while still unripe.
I had an old version of a homebrew I made, that for some reason did not update when I made a new version. Instead, it just created a new copy, and now there are two published copies of the exact same homebrew (though with one minor edit on one) taking up space. Renaming the old one & trying to edit it into a new race simply made yet another separate homebrew race, instead of updating the original.
I had an old version of a homebrew I made, that for some reason did not update when I made a new version. Instead, it just created a new copy, and now there are two published copies of the exact same homebrew (though with one minor edit on one) taking up space. Renaming the old one & trying to edit it into a new race simply made yet another separate homebrew race, instead of updating the original.
Any suggestions?
That’s exactly how the system is intended to work. It will never update the original version, simply publish another alternate version of hile still leaving the old version as available published homebrew. “Published is Permanent.” My suggestion, don’t publish anything that isn’t 1,000% finished from now on.
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.
The thing is, this already exists. Publishing homebrew is a two-action process with the second action being a confirmation dialogue that links to the homebrew rules. Unless you're suggesting a three-action process with two confirmation dialogues, in which case we'll still have the same problem. People will just continue clicking through the dialogues without reading. You can take a user to water, but you can't make them read a dialogue box.
You'd be surprised at the number of times I deal with requests that say "I accidentally hit publish when I didn't mean to"....
Yeah, I get it, but I guess I see it as a "if at first you don't succeeed try in an even more vibrant font."
But rather than belaboring the point more loudly, maybe make the labor of publishing more ... laborious?
Here's what I'm thinking, and this is thinking out loud: remove the publish button entirely from the homebrew building screen. Like make a separate publishing interface that branches from the "My Collections: Homebrew" page, and a player can toggle which ones they publish and publish from there after the requisite "are you really really sure? I mean, if you're not quite putting your A-game out there, people my laugh at you" warning. I think as is, it's easy to see how a user can falsely intuit that "publishing" is a requisite part of the homebrewing process (hence all those "wait! I didn't mean it" requests you get ... so in truth, I'm actually not surprised at the number of times you get the request). Removing "publish" literally from consideration on the homebrew building tools will greatly reduce misunderstood publication..
As someone who doesn't believe I've published a thing on homebrew (I may well have by mistake on my first ones), but very much enjoy the homebrew tools, I'd say my only disliking of the homebrew system is what in publishing would be called the slushpile of homebrew one needs to wade through when browser community homebrew ... so much of it clearly works in progress or probably not really intended for public consumption.
Anycase, I'm sure simply "moving the button" is actually not at all simple, but I'd say erroneous or version spamming homebrew affects not just the homebrewer but also the degree of community engagement with the published collections.
If there wont be any changes made allowing you to consolidate multiple versions of a homebrew into a single filed space, or to edit and delete the orginal, it should be stated an excessive amount of times that, after publishing, no edits can be made, the homebrew cannot be deleted, and it will be completely and entirely out of your control once published. Excessively. There should be more examples of that statement in the publishing u.i. than there are nouns in the bible, in big, flashy, *eye-catching red text*. Make it abundantly clear, not only that publishing will make this version of it permanant and unchangable, but also that publishing is unnecessary.
If there wont be any changes made allowing you to consolidate multiple versions of a homebrew into a single filed space, or to edit and delete the orginal, it should be stated an excessive amount of times that, after publishing, no edits can be made, the homebrew cannot be deleted, and it will be completely and entirely out of your control once published. Excessively. There should be more examples of that statement in the publishing u.i. than there are nouns in the bible, in big, flashy, *eye-catching red text*. Make it abundantly clear, not only that publishing will make this version of it permanant and unchangable, but also that publishing is unnecessary.
That is just how their system works. They don't delete old versions of playtest either, they just archive/unlist it.
Pretty sure published homebrew works the same way. When you create a new version, only the latest version shows up when searching for it, but the old version is still accessible to anyone that has it (including yourself obviously).
If there wont be any changes made allowing you to consolidate multiple versions of a homebrew into a single filed space, or to edit and delete the orginal, it should be stated an excessive amount of times that, after publishing, no edits can be made, the homebrew cannot be deleted, and it will be completely and entirely out of your control once published. Excessively. There should be more examples of that statement in the publishing u.i. than there are nouns in the bible, in big, flashy, *eye-catching red text*. Make it abundantly clear, not only that publishing will make this version of it permanant and unchangable, but also that publishing is unnecessary.
That is just how their system works. They don't delete old versions of playtest either, they just archive/unlist it.
Pretty sure published homebrew works the same way. When you create a new version, only the latest version shows up when searching for it, but the old version is still accessible to anyone that has it (including yourself obviously).
But they don’t archive it, the old versions are still made available for people to add to their collections instead of the new version. If they actually did archive the old versions then people wouldn’t be complaining.
If there wont be any changes made allowing you to consolidate multiple versions of a homebrew into a single filed space, or to edit and delete the orginal, it should be stated an excessive amount of times that, after publishing, no edits can be made, the homebrew cannot be deleted, and it will be completely and entirely out of your control once published. Excessively. There should be more examples of that statement in the publishing u.i. than there are nouns in the bible, in big, flashy, *eye-catching red text*. Make it abundantly clear, not only that publishing will make this version of it permanant and unchangable, but also that publishing is unnecessary.
That is just how their system works. They don't delete old versions of playtest either, they just archive/unlist it.
Pretty sure published homebrew works the same way. When you create a new version, only the latest version shows up when searching for it, but the old version is still accessible to anyone that has it (including yourself obviously).
But they don’t archive it, the old versions are still made available for people to add to their collections instead of the new version. If they actually did archive the old versions then people wouldn’t be complaining.
Ah. I have little experience with it since I've only published a handful of finished products that haven't needed updating, and don't care to have to test everyone else's homebrew to see if it matches my standard of effort so haven't interacted with more than 1 or 2 public homebrew long term.
I had an old version of a homebrew I made, that for some reason did not update when I made a new version. Instead, it just created a new copy, and now there are two published copies of the exact same homebrew (though with one minor edit on one) taking up space. Renaming the old one & trying to edit it into a new race simply made yet another separate homebrew race, instead of updating the original.
Any suggestions?
That’s exactly how the system is intended to work. It will never update the original version, simply publish another alternate version of hile still leaving the old version as available published homebrew. “Published is Permanent.” My suggestion, don’t publish anything that isn’t 1,000% finished from now on.
...Then why did that not happen for the other 3 homebrew things I created, when I used the "Create New Version" option? They all just put the old versions as links at the bottom of the newest update, instead of making completely new, entirely separate entries in my Collections page. And yes, the other homebrew items were published under their old versions, then updated later (mostly for minor text edits).
My Starlight Rapier entry, for instance, is on version 1.2... and it's never had more than one entry in My Collections or My Homebrew Creations page.
I had an old version of a homebrew I made, that for some reason did not update when I made a new version. Instead, it just created a new copy, and now there are two published copies of the exact same homebrew (though with one minor edit on one) taking up space. Renaming the old one & trying to edit it into a new race simply made yet another separate homebrew race, instead of updating the original.
Any suggestions?
That’s exactly how the system is intended to work. It will never update the original version, simply publish another alternate version of hile still leaving the old version as available published homebrew. “Published is Permanent.” My suggestion, don’t publish anything that isn’t 1,000% finished from now on.
...Then why did that not happen for the other 3 homebrew things I created, when I used the "Create New Version" option? They all just put the old versions as links at the bottom of the newest update, instead of making completely new, entirely separate entries in my Collections page. And yes, the other homebrew items were published under their old versions, then updated later (mostly for minor text edits).
My Starlight Rapier entry, for instance, is on version 1.2... and it's never had more than one entry in My Collections or My Homebrew Creations page.
See, that is how I thought it worked. But I have not had (read: bothered) to edit the (like 3) things I've published.
Wait, you mean that both are presented as two separate spells instead of one of them being listed as an “older version” that people could still add to their collections? Did you “create new version,” or did you use the original as a template?
Wait, you mean that both are presented as two separate spells instead of one of them being listed as an “older version” that people could still add to their collections? Did you “create new version,” or did you use the original as a template?
Can you post links & screenshots?
They are presented as two separate races instead of one being listed as an older version. I used "create new version," changing almost nothing except to tweak one little item.
For some reason, the version number is also missing from the new one. It should read 1.1, but that's now on a different NEW creation (Volpari) that got cut off in the screenshot.
For some reason, the version number is also missing from the new one. It should read 1.1, but that's now on a different NEW creation (Volpari) that got cut off in the screenshot.
You might have to submit a Support ticket if a Moderator can’t help you. You need someone official around here to help you with that.
With WOTC now saying they can, at any time, take something that's been published on DND Beyonds public homebrews, I feel they should at least give us the ability to retract our published content. I mean what if we make a race. Can they just take that and use it now because that's how it read to me.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The thing is, this already exists. Publishing homebrew is a two-action process with the second action being a confirmation dialogue that links to the homebrew rules. Unless you're suggesting a three-action process with two confirmation dialogues, in which case we'll still have the same problem. People will just continue clicking through the dialogues without reading. You can take a user to water, but you can't make them read a dialogue box.
You'd be surprised at the number of times I deal with requests that say "I accidentally hit publish when I didn't mean to"....
Find my D&D Beyond articles here
Instead of "are you sure" it needs to be "don't publish this unless you are done making it."
Changing the verbiage won't make any difference to the people who don't read the dialogue and just hit confirm.
Find my D&D Beyond articles here
True, but red warning text and a nice visible [CANCEL] button can’t hurt, and it has to mitigate the issue for those folks who do read the dialogue box. I mean, they put “caution, contents hot” on takeout coffee cups for crying out loud. Amending the current dialogue box to be more explicit and attention grabbing can do no harm and can only help, even to a minor degree. If it saves 1 user from mistakenly publishing their undercooked homebrew it will have been worth it. Everyone it helps beyond that is gravy. If it helps a gross of people, and they would each have published 5 things but hold off, that’s still 720 half-baked homebrews that get to stay in the oven a li’l longer. That’s better than a kick in the dangly bits any day. And the longer it exists, the more likely it will help more people. That’s potentially thousands of homebrews that could be saved the ignominy of being published while still unripe.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I had an old version of a homebrew I made, that for some reason did not update when I made a new version. Instead, it just created a new copy, and now there are two published copies of the exact same homebrew (though with one minor edit on one) taking up space. Renaming the old one & trying to edit it into a new race simply made yet another separate homebrew race, instead of updating the original.
Any suggestions?
That’s exactly how the system is intended to work. It will never update the original version, simply publish another alternate version of hile still leaving the old version as available published homebrew. “Published is Permanent.” My suggestion, don’t publish anything that isn’t 1,000% finished from now on.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Yeah, I get it, but I guess I see it as a "if at first you don't succeeed try in an even more vibrant font."
But rather than belaboring the point more loudly, maybe make the labor of publishing more ... laborious?
Here's what I'm thinking, and this is thinking out loud: remove the publish button entirely from the homebrew building screen. Like make a separate publishing interface that branches from the "My Collections: Homebrew" page, and a player can toggle which ones they publish and publish from there after the requisite "are you really really sure? I mean, if you're not quite putting your A-game out there, people my laugh at you" warning. I think as is, it's easy to see how a user can falsely intuit that "publishing" is a requisite part of the homebrewing process (hence all those "wait! I didn't mean it" requests you get ... so in truth, I'm actually not surprised at the number of times you get the request). Removing "publish" literally from consideration on the homebrew building tools will greatly reduce misunderstood publication..
As someone who doesn't believe I've published a thing on homebrew (I may well have by mistake on my first ones), but very much enjoy the homebrew tools, I'd say my only disliking of the homebrew system is what in publishing would be called the slushpile of homebrew one needs to wade through when browser community homebrew ... so much of it clearly works in progress or probably not really intended for public consumption.
Anycase, I'm sure simply "moving the button" is actually not at all simple, but I'd say erroneous or version spamming homebrew affects not just the homebrewer but also the degree of community engagement with the published collections.
Jander Sunstar is the thinking person's Drizzt, fight me.
If there wont be any changes made allowing you to consolidate multiple versions of a homebrew into a single filed space, or to edit and delete the orginal, it should be stated an excessive amount of times that, after publishing, no edits can be made, the homebrew cannot be deleted, and it will be completely and entirely out of your control once published. Excessively. There should be more examples of that statement in the publishing u.i. than there are nouns in the bible, in big, flashy, *eye-catching red text*. Make it abundantly clear, not only that publishing will make this version of it permanant and unchangable, but also that publishing is unnecessary.
That is just how their system works. They don't delete old versions of playtest either, they just archive/unlist it.
Pretty sure published homebrew works the same way. When you create a new version, only the latest version shows up when searching for it, but the old version is still accessible to anyone that has it (including yourself obviously).
But they don’t archive it, the old versions are still made available for people to add to their collections instead of the new version. If they actually did archive the old versions then people wouldn’t be complaining.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Ah. I have little experience with it since I've only published a handful of finished products that haven't needed updating, and don't care to have to test everyone else's homebrew to see if it matches my standard of effort so haven't interacted with more than 1 or 2 public homebrew long term.
I can appreciate that.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
...Then why did that not happen for the other 3 homebrew things I created, when I used the "Create New Version" option? They all just put the old versions as links at the bottom of the newest update, instead of making completely new, entirely separate entries in my Collections page.
And yes, the other homebrew items were published under their old versions, then updated later (mostly for minor text edits).
My Starlight Rapier entry, for instance, is on version 1.2... and it's never had more than one entry in My Collections or My Homebrew Creations page.
See, that is how I thought it worked. But I have not had (read: bothered) to edit the (like 3) things I've published.
Yea, maybe I'm just experiencing a bug, or did something wonky that caused it to decide there are 2 side-by-side copies now. I dunno.
Wait, you mean that both are presented as two separate spells instead of one of them being listed as an “older version” that people could still add to their collections? Did you “create new version,” or did you use the original as a template?
Can you post links & screenshots?
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
They are presented as two separate races instead of one being listed as an older version. I used "create new version," changing almost nothing except to tweak one little item.
Screenshots incoming.
the screenshot
For some reason, the version number is also missing from the new one. It should read 1.1, but that's now on a different NEW creation (Volpari) that got cut off in the screenshot.
You might have to submit a Support ticket if a Moderator can’t help you. You need someone official around here to help you with that.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
With WOTC now saying they can, at any time, take something that's been published on DND Beyonds public homebrews, I feel they should at least give us the ability to retract our published content.
I mean what if we make a race. Can they just take that and use it now because that's how it read to me.