Since DDB isn't going to include any older UA I took it upon myself to do a community service and added the Oath of Treachery. Well, it was removed from publication today with the explanation that UA cannot be shared as it's copyright of WotC. This seems to put us in a poor position - we can't put up UA on our own and DDB won't do it either, so everyone that wants to use older UA has to code it into DDB themselves.
Any fix for this coming up? Why did my subclass get removed after being first approved and then left up there for some 6 months? Is DDB going to change their position and officially include older UA?
My understanding is that Wizards of the Coast specified that older UA couldn't be added officially or published as homebrew; DDB, as a licensee, has to follow WOTC's lead on this. It's also the case that the terms of service prohibit publishing any homebrew that is not your own work. So, for example, I am not allowed to publish any of the races or subclasses my son has created, although I can homebrew them and keep them private.
As to why the subclass stayed up for so long before being removed, originally verification was handled by moderators directly, and sometimes stuff got missed/not recognized. Then they shifted to a more automated check. Not sure which system was in use when you published, but either the moderator or the automated validation system missed that it was outdated UA. Either a new wave of checks was made or someone reported it.
Eyo,
Since DDB isn't going to include any older UA I took it upon myself to do a community service and added the Oath of Treachery. Well, it was removed from publication today with the explanation that UA cannot be shared as it's copyright of WotC. This seems to put us in a poor position - we can't put up UA on our own and DDB won't do it either, so everyone that wants to use older UA has to code it into DDB themselves.
Any fix for this coming up? Why did my subclass get removed after being first approved and then left up there for some 6 months? Is DDB going to change their position and officially include older UA?
My understanding is that Wizards of the Coast specified that older UA couldn't be added officially or published as homebrew; DDB, as a licensee, has to follow WOTC's lead on this. It's also the case that the terms of service prohibit publishing any homebrew that is not your own work. So, for example, I am not allowed to publish any of the races or subclasses my son has created, although I can homebrew them and keep them private.
As to why the subclass stayed up for so long before being removed, originally verification was handled by moderators directly, and sometimes stuff got missed/not recognized. Then they shifted to a more automated check. Not sure which system was in use when you published, but either the moderator or the automated validation system missed that it was outdated UA. Either a new wave of checks was made or someone reported it.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk