When trying to add the spells to a homebrew subclass:
Armor of Agathys
Swift Quiver
i get an error:
> This homebrew Subclass has data mapped to it that is licensed content or private homebrew. This typically occurs when licensed or private homebrew spells are linked to the Subclass.
After having removed these spells, everything is fine...
That is correct. Both of these spells are licensed content, meaning they have to be paid for here. They are contained within the Player's Handbook, not the Basic Rules which are free to use.
Rollback Post to RevisionRollBack
Lightning Strike - A rebranded Fire Bolt for Wizards & Sorcerers.
Spirit Bomb - A holy fireball for Clerics, Paladins, & Divine Soul Sorcerers!
Sword Dancer - A Cleric subclass specifically for the Drow goddess Eilistraee.
It does make sense that they are indeed licensed content :)
Subclasses from the PHB do get to use such spells though. It really sucks that published homebrew is more limited in options then a vanilla Tempest Domain Cleric :(
That only stops you being able to publish the material. You don't need to do that if you're just intending on using it within a campaign. All homebrew regardless of published status can be shared in a campaign.
It does make sense that they are indeed licensed content :)
Subclasses from the PHB do get to use such spells though. It really sucks that published homebrew is more limited in options then a vanilla Tempest Domain Cleric :(
That’s because WotC owns the legal rights to those spells, and we do not.
WotC gave away free rights to everything published in the SRD, which DDB combined into the Basic Rules for us. So DDB’s “Basic Rules” is really the “Basic Rules & SRD.” WE own the rights to those spells because WotC gave them away for free. Make sense?
WotC gave away free rights to everything published in the SRD, which DDB combined into the Basic Rules for us. So DDB’s “Basic Rules” is really the “Basic Rules & SRD.” WE own the rights to those spells because WotC gave them away for free. Make sense?
Well, if that means that DDB is legally prohibited to publish homebrew referring to these spells, then yes :)
But I doubt that. The reason being: right now if I buy the XGTE and not the PHB, I will be able to create a Conquest Paladin, referring to Armor of Agathys, a licensed spell that I have not purchased.
Apparently PHB spells are not off-limits for Wizards when creating new subclasses, why should they be for us homebrewers?
All homebrew regardless of published status can be shared in a campaign.
Yeah, I understand that. It just boggles me that I cannot publish a subclass made according to the same rules WotC adhere to when creating new classes. No biggie though :D
The problem stems in the fact the Homebrew system does not factor what happens if somebody adds that homebrew but doesn't have access to non-free content mapped to it.
This is being looked into and is planned to be supported in the future.
Just clarifying from some posts: the issue isn't actually licensing permissions, since you are not giving people access to licensed content. It's a homebrew tool system issue because it is not able to correctly handle for such events (homebrew is handled differently to the official stuff). D&D Beyond don't need to obtain any extra rights or permissions or anything from WotC - it's a system issue not a licensing one. At an, as of yet, undetermined point in the future this will likely stop being a problem.
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.
When trying to add the spells to a homebrew subclass:
i get an error:
> This homebrew Subclass has data mapped to it that is licensed content or private homebrew. This typically occurs when licensed or private homebrew spells are linked to the Subclass.
After having removed these spells, everything is fine...
That is correct. Both of these spells are licensed content, meaning they have to be paid for here. They are contained within the Player's Handbook, not the Basic Rules which are free to use.
Lightning Strike - A rebranded Fire Bolt for Wizards & Sorcerers.
Spirit Bomb - A holy fireball for Clerics, Paladins, & Divine Soul Sorcerers!
Sword Dancer - A Cleric subclass specifically for the Drow goddess Eilistraee.
Quicksilver & The Scarlet Witch - A pair of magical firearms for your Gunslinger or Artificer.
It does make sense that they are indeed licensed content :)
Subclasses from the PHB do get to use such spells though. It really sucks that published homebrew is more limited in options then a vanilla Tempest Domain Cleric :(
That only stops you being able to publish the material. You don't need to do that if you're just intending on using it within a campaign. All homebrew regardless of published status can be shared in a 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).
That’s because WotC owns the legal rights to those spells, and we do not.
WotC gave away free rights to everything published in the SRD, which DDB combined into the Basic Rules for us. So DDB’s “Basic Rules” is really the “Basic Rules & SRD.” WE own the rights to those spells because WotC gave them away for free. Make sense?
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Thanks for the replies,
Well, if that means that DDB is legally prohibited to publish homebrew referring to these spells, then yes :)
But I doubt that.
The reason being: right now if I buy the XGTE and not the PHB, I will be able to create a Conquest Paladin, referring to Armor of Agathys, a licensed spell that I have not purchased.
Apparently PHB spells are not off-limits for Wizards when creating new subclasses, why should they be for us homebrewers?
Yeah, I understand that. It just boggles me that I cannot publish a subclass made according to the same rules WotC adhere to when creating new classes. No biggie though :D
Well WotC and DDB both have the rights to publish using that content. We only have the rights to use the content - if we purchased it.
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).
The problem stems in the fact the Homebrew system does not factor what happens if somebody adds that homebrew but doesn't have access to non-free content mapped to it.
This is being looked into and is planned to be supported in the future.
Just clarifying from some posts: the issue isn't actually licensing permissions, since you are not giving people access to licensed content. It's a homebrew tool system issue because it is not able to correctly handle for such events (homebrew is handled differently to the official stuff). D&D Beyond don't need to obtain any extra rights or permissions or anything from WotC - it's a system issue not a licensing one. At an, as of yet, undetermined point in the future this will likely stop being a problem.
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.
Thank you for the answer, Cyb3rM1nd.
I'm looking forward to this undetermined point in the future with hope :)
Five and half years later and we are still waiting lol.