Well I ended up just ditching dnd and going with pathfinder in the end not having access to the monsters I had purchased was kinda a bummer :(

according to the Mods on discord they are working on a fix.

Quote from bartvangramberen >>

according to the Mods on discord they are working on a fix.

 
Oh, I don’t doubt that in the slightest. Like I said, one of these days everything will suddenly work again as if by magic. 

Since I own everything I was trying to find all the books where the monsters are not working before opening a request for them. Not sure if this helps anyone but as of today these seem to be the books with problems.

Dungeons & Dragons vs. Rick and Morty
Eberron: Rising from the Last War
Explorer's Guide to Wildemount
Infernal Machine Rebuild
Locathah Rising
Mordenkainen's Fiendish Folio Volume 1
Mordenkainen’s Tome of Foes
Mythic Odysseys of Theros
Sapphire Dragon
The Sunless Citadel

100%

Quote from IamSposta >>

Quote from jl8e >>

I doubt he can, because nobody out here knows why it's happening.

They're clearly changing something on the back end, and it breaks the permissions lookup in maps and the encounter builder for the changed monsters. I have a theory, but it's based on a lot of speculation and the assumption that they're doing some really bad software development practices.

 
I have the luxury of not needing to make that assumption. I know for a fact that when they were scrambling to slap this site together as fast as they could that they gave 0 ****s about future proofing a damned thing, or coding the site to make it flexible enough to build onto it once it was up and running, or making things stable so that it could more easily withstand retrofits. They cut every corner they could and the ones they couldn’t cut they cemented firmly into the bedrock of the site and now it’s a major fluster cluck. Half of the website is effective welded to the earths mantle it’s so immutable, and the other half is barely held together with chewing gum and duct tape. That’s what’s causing all the issues. It’s not so much that “they're doing some really bad software development practices,” it’s that they already did those bad practices 6 years ago when they were building the site, and now they’re trying to do a combination of fixing those mistakes, and just working around the ones that’re too big, or too ingrained, or too fragile to fix.

 No matter how badly built the site is, making breaking changes in production is an independent bad practice. 

Quote from jl8e >>

Quote from IamSposta >>

Quote from jl8e >>

I doubt he can, because nobody out here knows why it's happening.

They're clearly changing something on the back end, and it breaks the permissions lookup in maps and the encounter builder for the changed monsters. I have a theory, but it's based on a lot of speculation and the assumption that they're doing some really bad software development practices.

 
I have the luxury of not needing to make that assumption. I know for a fact that when they were scrambling to slap this site together as fast as they could that they gave 0 ****s about future proofing a damned thing, or coding the site to make it flexible enough to build onto it once it was up and running, or making things stable so that it could more easily withstand retrofits. They cut every corner they could and the ones they couldn’t cut they cemented firmly into the bedrock of the site and now it’s a major fluster cluck. Half of the website is effective welded to the earths mantle it’s so immutable, and the other half is barely held together with chewing gum and duct tape. That’s what’s causing all the issues. It’s not so much that “they're doing some really bad software development practices,” it’s that they already did those bad practices 6 years ago when they were building the site, and now they’re trying to do a combination of fixing those mistakes, and just working around the ones that’re too big, or too ingrained, or too fragile to fix.

 No matter how badly built the site is, making breaking changes in production is an independent bad practice. 

 
True, but knowing how hard the devs work to prevent that, we’re honestly probably lucky it’s not worse.

Jumping on to say that I am having this issue too with Explorer's Guide to Wildemount. Glad to hear that a fix is being worked on, but it was very annoying when trying to run an encounter with moorbounders...

Add to this the Frozen Sick basic campaign for beginners.  The Final BBEG for the first cave complex comes back as unable to be added, even though there isn't a purchase necessary to get it. 

I am Having the Same Issue. 

I'm having this issue with Changlings, and Warforged are also affected on my account. Oddly Warforged Titan and Colossus work fine (I created a test encounter and tossed a few more Eberron creatures at it to see what would stick.)

I'm having the same issue with the Tortle package

This is currently happening to me as well with the Hundred-Handed One from MOoT

i mean for those saying "glad its being worked on", not to rain on anyone's parade here but we were told back in December it was a known bug and was being worked on... since then its only gotten worse. Not to mention not hearing a damn thing from support or anyone else other than the occasional mod.

It's really just not good enough!

Agree. Customer support and communication is terrible. It might lead one to have the perception that they don’t care about us. It might lead one to believe they say one thing and do another. It might be perceived as pretending to be fixing something when they really aren’t.