So, I have a subclass heavily based off of Matt Mercer's Gunslinger subclass for Fighters, but it's a subclass for Rogues instead. I would like to share this with some friends that are not in any campaigns with me so they can give me their thoughts, but I can't do that unless I publish it to share with the community. However, I have two messages it tells me on why I can't do it yet.
The first makes sense, kinda, since it's based so heavily on the Gunslinger. I just don't understand why it would prevent it from being shared, seeing as how it's a subclass for Rogue instead of fighter. So I need some guidance on how to change it up enough while keeping the rules mostly the same to stop this from being a problem.
Second one, tho...idk. That one's got me confused. I don't know if I'm missing something or what, but it seems like it's just not working right.
Any advice anyone can provide would be much appreciated.
Don't publish homebrew that isn't finished - because once it's published - that's it - it can't be changed. You'll only be able to make new versions and bloat the homebrew database.
While testing it - just make a new campaign and give your friends an invite link. Like the second red paragraph says - private homebrew is automatically shared in all campaigns.
It's because once it's published - it could be in use by somebody else - and they likely wouldn't be happy having their character change for no apparent reason mid campaign.
Isn't that why there's a version field tho? Like, couldn't the DM be like "It's a MacGuffin Version 2. Don't use Version 3, it doesn't have the MacGuffin X power."? If they can't, what is the version field used for?
You can make new versions. Once something is published the edit button will change to "Create New Version" or words to that effect - but doing so leaves the old version completely intact - and it's just needless duplication. It's preferred if only complete and tested homebrew is published.
Yup, you can send them the link, but if your subclass has “option” those won’t be visible to them. You can however drag highlight the subclass text, and copy/paste it into a PM for them to read, or forum thread like this to get feedback from other users.
So, I have a subclass heavily based off of Matt Mercer's Gunslinger subclass for Fighters, but it's a subclass for Rogues instead. I would like to share this with some friends that are not in any campaigns with me so they can give me their thoughts, but I can't do that unless I publish it to share with the community. However, I have two messages it tells me on why I can't do it yet.
The first makes sense, kinda, since it's based so heavily on the Gunslinger. I just don't understand why it would prevent it from being shared, seeing as how it's a subclass for Rogue instead of fighter. So I need some guidance on how to change it up enough while keeping the rules mostly the same to stop this from being a problem.
Second one, tho...idk. That one's got me confused. I don't know if I'm missing something or what, but it seems like it's just not working right.
Any advice anyone can provide would be much appreciated.
Don't publish homebrew that isn't finished - because once it's published - that's it - it can't be changed. You'll only be able to make new versions and bloat the homebrew database.
While testing it - just make a new campaign and give your friends an invite link. Like the second red paragraph says - private homebrew is automatically shared in all campaigns.
Mega Yahtzee Thread:
Highest 41: brocker2001 (#11,285).
Yahtzee of 2's: Emmber (#36,161).
Lowest 9: JoeltheWalrus (#312), Emmber (#12,505) and Dertinus (#20,953).
Oh, that's...odd. I didn't know that.
I'll go ahead and do that then. Thank you for your help!
It's because once it's published - it could be in use by somebody else - and they likely wouldn't be happy having their character change for no apparent reason mid campaign.
Mega Yahtzee Thread:
Highest 41: brocker2001 (#11,285).
Yahtzee of 2's: Emmber (#36,161).
Lowest 9: JoeltheWalrus (#312), Emmber (#12,505) and Dertinus (#20,953).
Ah. I guess that makes sense.
Isn't that why there's a version field tho? Like, couldn't the DM be like "It's a MacGuffin Version 2. Don't use Version 3, it doesn't have the MacGuffin X power."? If they can't, what is the version field used for?
You can make new versions. Once something is published the edit button will change to "Create New Version" or words to that effect - but doing so leaves the old version completely intact - and it's just needless duplication. It's preferred if only complete and tested homebrew is published.
Mega Yahtzee Thread:
Highest 41: brocker2001 (#11,285).
Yahtzee of 2's: Emmber (#36,161).
Lowest 9: JoeltheWalrus (#312), Emmber (#12,505) and Dertinus (#20,953).
Alright, that makes sense. Thank you for your help! I'll go ahead and get my friends to join a campaign so we can share things like this.
Yup, you can send them the link, but if your subclass has “option” those won’t be visible to them. You can however drag highlight the subclass text, and copy/paste it into a PM for them to read, or forum thread like this to get feedback from other users.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting