I have a Master Tier subscription and tons of homebrew content which I share with my players in our shared campaigns via the character builder and digital character sheets. 

I thought the shared homebrew content (i.e. homebrew monsters in this case) would also appear in the Encounter Builder of players within a shared campaign, but that doesn't seem to be the case. Someone else is currently DMing Curse of Strahd, but I have my character in the campaign with Content Sharing Enabled (by me, Benz74M). Shouldn't that DM be able to see the shared homebrew monster in the Encounter Builder when selecting Curse of Strahd in the Manage Characters section of the Builder?  ("Homebrew" filter is "SHOW BOTH" [homebrew and official].

I spent a lot of time adding these homebrew monsters especially for that campaign, thinking that the shared content would be... well... shared.

Content sharing is not required to share homebrew. All homebrew in everyone’s collection is automatically shared within a campaign. The content is shared within the campaign itself, not with the player. Therefore, your friend cannot use your homebrew outside of that campaign. That typically includes the encounter builder as well. Have they specifically designated that campaign for the encounter they are building? If not, that would be why. The other thing is, filtering by homebrew in the encounter builder doesn’t work. They have to turn the filters off and then search for the monsters by name. If that still doesn’t solve the problem, you can send that player the URLs for your monsters, and they can as long as they have a subscription, add them to their own collection and use them then.

Quote from IamSposta >>

Content sharing is not required to share homebrew. (...) Have they specifically designated that campaign for the encounter they are building? If not, that would be why. The other thing is, filtering by homebrew in the encounter builder doesn’t work. They have to turn the filters off and then search for the monsters by name. 

 Pretty sure they had designated the campaign for the encounter they were building, but I will double-check tonight when we meet up for our game. 

If that still doesn’t solve the problem, you can send that player the URLs for your monsters, and they can as long as they have a subscription, add them to their own collection and use them then.

Would that work for homebrew that isn't Public but private only? 

Thanks for your help!

(Congrats for your 25,000 posts! I thought I was spending time on D&D Beyond 😅.)

Quote from Benz74M >>

Quote from IamSposta >>

Content sharing is not required to share homebrew. (...) Have they specifically designated that campaign for the encounter they are building? If not, that would be why. The other thing is, filtering by homebrew in the encounter builder doesn’t work. They have to turn the filters off and then search for the monsters by name. 

 Pretty sure they had designated the campaign for the encounter they were building, but I will double-check tonight when we meet up for our game. 

If that still doesn’t solve the problem, you can send that player the URLs for your monsters, and they can as long as they have a subscription, add them to their own collection and use them then.

Would that work for homebrew that isn't Public but private only? 

Thanks for your help!

(Congrats for your 25,000 posts! I thought I was spending time on D&D Beyond 😅.)

 
Yes, as long as you are in a campaign together you can send someone the URL for a private homebrew and they can add it.

Thanks!!

So... after verification, even if you select a specific campaign in the Encounter Builder (My Encounters > Filter By Active Campaign OR via Encounter Builder > Manage Characters > Select Preset (Campaign), --- AND you have a character in said campaign -- private homebrew created by another player doesn't show up, nor does Public homebrew added to someone else's Collection. At least with a basic D&D Beyond account (no subscription)... even if the person with the homebrew has a Master Tier subscription with content sharing enabled (which shouldn't matter, as you said IamSposta, since homebrew items are shared in shared campaigns).  Homebrew monsters stats blocks do appear, however, on the digital character sheet in the Manage Extras section. 

I believe that homebrew monsters in Collection not showing up in the Encounter Builder for someone in a particular campaign using the Builder is an oversight and should be fixed by the Dev team. Copy/pasting URL of homebrew monsters and sending them one at a time to the person building a campaign's encounters isn't a practical solution when you have dozens if not hundreds of homebrew creatures.

The system was designed under the assumption that the DM, the originator of the campaign, and the creator of homebrewed monsters would all be the same individual using the same account. Therefore, such homebrewed monsters wouldn’t have to be shared across accounts and populate the encounter builder. It is shortsighted, but it also prevents players from spoiling their DM’s encounters by making their own using the DM’s ‘brewed monsters. so there’re pros and cons to both.

Quote from IamSposta >>

The system was designed under the assumption that the DM, the originator of the campaign, and the creator of homebrewed monsters would all be the same individual using the same account. Therefore, such homebrewed monsters wouldn’t have to be shared across accounts and populate the encounter builder. It is shortsighted, but it also prevents players from spoiling their DM’s encounters by making their own using the DM’s ‘brewed monsters. so there’re pros and cons to both.

There could be some sort of toggle in the Homebrew Collection or Homebrew Creation section that allows sharing of homebrew monsters for purpose of Encounter building (or any homebrew, for that matter, for any shared campaign). We have four or five DMs in our group of players that share campaigns on D&D Beyond, but only one that often adds homebrew / 3rd party material in the system (me). The intent is for all DMs in our group(s) to use that content. Sharing my login and password to allow them to use MY Encounter Builder isn't a solution either, security-wise :P 

I feel ya. My group is in the similar boat. Luckily for us I’m also the only one who really uses the encounter builder.