It doesn't make any sense that it auto adds EVERY PLAYER's homebrew to my Spell/Item list if I am in a campaign with them. If I toggle disable homebrew, it should, disable homebrew. It confuses me, my players, and clutters spell lists when you see stuff that they make for themself.
Disabling homebrew SHOULD disable all homebrew, but I've found homebrew spells on my spell list of caster characters even when homebrew was turned off at the beginning of character creation and kept off. In my case, they are my own homebrew, not shared homebrew. I think I never got around to reporting it myself, but I've seen similar posts from others.
One of my players recently informed me that a TON of homebrew spells popped up on their character sheet. I only have a handful of homebrew items that I created but there were so many more. We did recently invite a few new players to the table so it could be that they are the culprit. I would really love an option where only the DM's homebrew collection is enabled. I would love to give them homebrew items or spells but the campaign I just started the new player at level 1 had the most OP cantrip I had ever heard of. I went into the campaign sharing settings and while it allows for the selection of individual source books and adventure books I own to be shared it does not allow me to turn off homebrew that isn't in my own collection.
The problem comes about from homebrew spells that were added to particular subclasses of prepared spellcasting classes, like cleric or paladin. Those are treated as Always Prepared and can't be turned off; the only way to do so is have the player/DM with the homebrew spell in their homebrew collection Remove it from their collection.
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
The problem comes about from homebrew spells that were added to particular subclasses of prepared spellcasting classes, like cleric or paladin. Those are treated as Always Prepared and can't be turned off; the only way to do so is have the player/DM with the homebrew spell in their homebrew collection Remove it from their collection.
That shouldn't even be a thing homebrew lets you mess up. Classes tag the spells, not the other way around.
The problem comes about from homebrew spells that were added to particular subclasses of prepared spellcasting classes, like cleric or paladin. Those are treated as Always Prepared and can't be turned off; the only way to do so is have the player/DM with the homebrew spell in their homebrew collection Remove it from their collection.
That shouldn't even be a thing homebrew lets you mess up. Classes tag the spells, not the other way around.
You'd think so, but if for example you add a homebrew spell to your Homebrew Collection that has "Cleric - Trickery Domain" in its Available for Class(es) list in the spell's Basic Information, then it'll show up as Always Prepared for any Trickery Clerics that are in a campaign with you.
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
The problem comes about from homebrew spells that were added to particular subclasses of prepared spellcasting classes, like cleric or paladin. Those are treated as Always Prepared and can't be turned off; the only way to do so is have the player/DM with the homebrew spell in their homebrew collection Remove it from their collection.
That shouldn't even be a thing homebrew lets you mess up. Classes tag the spells, not the other way around.
You'd think so, but if for example you add a homebrew spell to your Homebrew Collection that has "Cleric - Trickery Domain" in its Available for Class(es) list in the spell's Basic Information, then it'll show up as Always Prepared for any Trickery Clerics that are in a campaign with you.
Right, I understand how it gets messed up, but that isn't how it should work. Subclasses tag the spells, not the other way around. It shouldn't let the other way around be done.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
It doesn't make any sense that it auto adds EVERY PLAYER's homebrew to my Spell/Item list if I am in a campaign with them. If I toggle disable homebrew, it should, disable homebrew. It confuses me, my players, and clutters spell lists when you see stuff that they make for themself.
I agree that DMs need a way to control which homebrews are shared.
But I dont know what you are asking for. Disabling homebrew on a character DOES disable all homebrew.
Disabling homebrew SHOULD disable all homebrew, but I've found homebrew spells on my spell list of caster characters even when homebrew was turned off at the beginning of character creation and kept off. In my case, they are my own homebrew, not shared homebrew. I think I never got around to reporting it myself, but I've seen similar posts from others.
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
One of my players recently informed me that a TON of homebrew spells popped up on their character sheet. I only have a handful of homebrew items that I created but there were so many more. We did recently invite a few new players to the table so it could be that they are the culprit. I would really love an option where only the DM's homebrew collection is enabled. I would love to give them homebrew items or spells but the campaign I just started the new player at level 1 had the most OP cantrip I had ever heard of. I went into the campaign sharing settings and while it allows for the selection of individual source books and adventure books I own to be shared it does not allow me to turn off homebrew that isn't in my own collection.
The problem comes about from homebrew spells that were added to particular subclasses of prepared spellcasting classes, like cleric or paladin. Those are treated as Always Prepared and can't be turned off; the only way to do so is have the player/DM with the homebrew spell in their homebrew collection Remove it from their collection.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
That shouldn't even be a thing homebrew lets you mess up. Classes tag the spells, not the other way around.
You'd think so, but if for example you add a homebrew spell to your Homebrew Collection that has "Cleric - Trickery Domain" in its Available for Class(es) list in the spell's Basic Information, then it'll show up as Always Prepared for any Trickery Clerics that are in a campaign with you.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
Right, I understand how it gets messed up, but that isn't how it should work. Subclasses tag the spells, not the other way around. It shouldn't let the other way around be done.