I'm not sure if homebrew other than subclasses are restricted in this manner because the only time I've seen this restriction in effect is when I tried to make a subclass with content from a non-SRD source.
I don't quite understand why this is an issue given that nobody who does not own that content, or doesn't have access to it through sharing, will see it anyway. They'll just get the standard warning that they need to purchase the content to see it; isn't this a good thing? It's essentially free advertising.
So is there some reason why this is restricted that I'm not seeing or understanding here?
Rollback Post to RevisionRollBack
"Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation."
This same block happens to Magic Items, Feats, Races, and Subclasses. This occurs because we cannot guarantee that the consuming user will have necessary access to the non-SRD content. The concern isn't so much in the ramifications of them viewing listings / details pages, but the potential for havoc in the character builder / sheet. Adding a licensed "blah" to your homebrew "bleh" from let's say XGtE, could lead to a situation where "bleh" becomes not entirely functional for the user as they don't, even through campaign sharing, have access to XGtE.
But again, you are free to add whatever you want to your homebrew that is kept private and shared within just your own campaigns. Since the expectation is, with enabled content-sharing, the consuming users would have access to the appropriate non-SRD information you've added to your homebrew.
OK, so the thing I was not understanding is that it'd break the system. Shame though as I would've loved to have published a few things that use non-SRD resources.
Rollback Post to RevisionRollBack
"Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation."
So, interesting development, after the change last night to how expanded spell lists work, I was able to publish my Shadow Weave warlock with the non-SRD spells. Is this intentional or do I have to rely on none of the moderators noticing for my warlock subclass to be approved? :D
Rollback Post to RevisionRollBack
"Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation."
HartlessD20, If a archetype linking to a non-SRD spell breaks the system, how do you handle it when a user purchases a book (such as XGtE)? The Oath of Conquest links to Armor of Agathys, and the Forge Domain links to both Searing Smite and Elemental Weapon - none of which are SRD spells. In both cases, it's not even an expanded spell list where it's an option, but divine spells that are automatically added to that class' character sheet. So why would that not break the character sheet in the way you mentioned?
If there's some exception-based programming behind the scenes (such as by purchasing those classes you also "purchase" those spells, even if you don't own them), then how about we implement a toggle in the homebrew archetypes that filters out content that uses sources you don't own? And/or make it where a user cannot add an archetype to his or her collection if that archetype links to spells he or she does not own? One thing I'm seeing a lot as a "fix" for the above issue is listing spells in the subclass description, but not linking them into the build itself. But this solution is an even more problematic issue to the community as it prevents even paying users from adding those subclass options to their sheet legitimately, causing confusion and an overall deterioration of the quality of homebrew listed on DnDBeyond.
It has more to do with the current functionality of the sheet, meaning we don't show data the user doesn't have legitimate access to and disable it. Once that is corrected in future improvements to the sheet, we will more than likely remove the publish block.
Don’t worry, we listen! We may not get things done as fast as people would like, but there are methods to our madness.
I, as well as the entire team, do sincerely appreciate everyone’s feedback. It drives the product more than you know. It just takes a while for it to show up :)
I'm not sure if homebrew other than subclasses are restricted in this manner because the only time I've seen this restriction in effect is when I tried to make a subclass with content from a non-SRD source.
I don't quite understand why this is an issue given that nobody who does not own that content, or doesn't have access to it through sharing, will see it anyway. They'll just get the standard warning that they need to purchase the content to see it; isn't this a good thing? It's essentially free advertising.
So is there some reason why this is restricted that I'm not seeing or understanding here?
"Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation."
― Oscar Wilde.
This same block happens to Magic Items, Feats, Races, and Subclasses. This occurs because we cannot guarantee that the consuming user will have necessary access to the non-SRD content. The concern isn't so much in the ramifications of them viewing listings / details pages, but the potential for havoc in the character builder / sheet. Adding a licensed "blah" to your homebrew "bleh" from let's say XGtE, could lead to a situation where "bleh" becomes not entirely functional for the user as they don't, even through campaign sharing, have access to XGtE.
But again, you are free to add whatever you want to your homebrew that is kept private and shared within just your own campaigns. Since the expectation is, with enabled content-sharing, the consuming users would have access to the appropriate non-SRD information you've added to your homebrew.
I am the Inquisitor Imperitus. I am judge, jury, and executioner. Draw your last breath now, as I send you to the Nine Hells.
OK, so the thing I was not understanding is that it'd break the system. Shame though as I would've loved to have published a few things that use non-SRD resources.
"Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation."
― Oscar Wilde.
So, interesting development, after the change last night to how expanded spell lists work, I was able to publish my Shadow Weave warlock with the non-SRD spells. Is this intentional or do I have to rely on none of the moderators noticing for my warlock subclass to be approved? :D
"Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation."
― Oscar Wilde.
Nope, I missed adding that additional mapping into the block publish check. Will do that on Monday. Thanks for the report!
I am the Inquisitor Imperitus. I am judge, jury, and executioner. Draw your last breath now, as I send you to the Nine Hells.
"Most people are other people. Their thoughts are someone else's opinions, their lives a mimicry, their passions a quotation."
― Oscar Wilde.
HartlessD20, If a archetype linking to a non-SRD spell breaks the system, how do you handle it when a user purchases a book (such as XGtE)? The Oath of Conquest links to Armor of Agathys, and the Forge Domain links to both Searing Smite and Elemental Weapon - none of which are SRD spells. In both cases, it's not even an expanded spell list where it's an option, but divine spells that are automatically added to that class' character sheet. So why would that not break the character sheet in the way you mentioned?
If there's some exception-based programming behind the scenes (such as by purchasing those classes you also "purchase" those spells, even if you don't own them), then how about we implement a toggle in the homebrew archetypes that filters out content that uses sources you don't own? And/or make it where a user cannot add an archetype to his or her collection if that archetype links to spells he or she does not own? One thing I'm seeing a lot as a "fix" for the above issue is listing spells in the subclass description, but not linking them into the build itself. But this solution is an even more problematic issue to the community as it prevents even paying users from adding those subclass options to their sheet legitimately, causing confusion and an overall deterioration of the quality of homebrew listed on DnDBeyond.
Subclasses: Path of the Marauder, Way of the Golden Fist, Way of the Yamabushi. Feats: Melee Training, Olympian Physique. Spells: Arcane Recall, Banker's Purse, Coin Shot, Moonfire Blade.
It has more to do with the current functionality of the sheet, meaning we don't show data the user doesn't have legitimate access to and disable it. Once that is corrected in future improvements to the sheet, we will more than likely remove the publish block.
Thanks for the feedback.
I am the Inquisitor Imperitus. I am judge, jury, and executioner. Draw your last breath now, as I send you to the Nine Hells.
That gives me hope for future designs then. Thanks @HartlessD20.
Subclasses: Path of the Marauder, Way of the Golden Fist, Way of the Yamabushi. Feats: Melee Training, Olympian Physique. Spells: Arcane Recall, Banker's Purse, Coin Shot, Moonfire Blade.
Don’t worry, we listen! We may not get things done as fast as people would like, but there are methods to our madness.
I, as well as the entire team, do sincerely appreciate everyone’s feedback. It drives the product more than you know. It just takes a while for it to show up :)
I am the Inquisitor Imperitus. I am judge, jury, and executioner. Draw your last breath now, as I send you to the Nine Hells.