I am building an encounter using the warforged solider creature in the encounter builder. The stat block is blurred out and says that I can still add it but cant see the stat block. Issue us I do own the book so not sure where to go from here.
This is a problem we’ve been having for months now with MtoF monsters (support have not responded on this issue) however I think that monster is an Eberron monster - so not sure why it’s happening to that one.
Good to hear I'm not the only one! Sad its happening to others! The monster is from Eberron rising from the last war which is now legacy(I wonder if thats why) as the new book Way finders guide has been released. I may have that the wrong way round. Kinda sucks because I originally purchased these books in order to use the stat blocks and now I cant.
Isnt that like false advertising or something haha
Yep - me too. Husk Zombies are no longer owned for maps or encounters... and it looks like Explorer's Guide to Wildemount is missing from the Marketplace and when you view All Sources.
I own "Explorers Guide to Wildemount" but I'm trying to add a monster (Merrow Shallowpriest) and I keep getting the "you don't own this content" error.
I'm also having the same problem: I own Explorer's Guide to Wildmount, Mythic Odysseys of Theros, and Mordenkainen's Tome of Foes. Both encounter builder and maps say that I do not own the material.
I had a TON of encounters set up and because of whatever they changed, I can only use the homebrew encounters... HOURS of work wasted. I'm going to jump ship and use a different tracker.
I had a TON of encounters set up and because of whatever they changed, I can only use the homebrew encounters... HOURS of work wasted. I'm going to jump ship and use a different tracker.
I wanted to use a different one but wouldn't that mean making all the monster statblocks manually?
Hey, same from me! A bunch of encounters I have made suddenly don't work due to the site claiming I don't own the material. For some of them, I click the link to marketplace and it just takes me to the stat block, and for others the stat block used to be in a source I own, but now is in a new one? I am very confused.
I'm having the same issue y'all are. And it's for an Encounter in the Encounter Builder that I was able to run successfully in the past!!! If that screenshot shows up correctly, you can see that I own the book Mordenkainen's Fiendish Folio 1 and then you see in Encounter Builder, it's telling me that I don't own it.
You know what's more frustrating than the bug itself that caused me to have to roll manually this weekend during my game? The fact the D&D Beyond doesn't offer us a place to report bugs. THAT is infuriating. It shows how little they care about users.
> Gold Medal for "Outstanding Book of the Year" in 2012 Independent Publisher Book Awards > National Indie Excellence Book Award finalist > A Greater Monster named a "Top 10 Book of 2012" by Common Ills blog > Listed in "10 Hot Chicago Reads for Chilly Nights" on Refinery29.com
this bug has existed for MtoF since December... with literally zero response form support and zero ackowledgement of a timeline for fixing it. A moderator did kindly report back that the bug was known, but the problem has now got worse and has spread to other books.
It is massively annoying and I've taken to have to print out stat blocks and run combat manually because of this.
I am deeply unhappy with the level of support from customer support and the lack of any resolution. This is paid for content... i bought it because i wanted to use it the encounter tracker (as i already have the physical books) - so im deeply deeply miffed.
Thank for clearing up the Mordenkainen's tome of foes + encounter builder issue. Could you shed any light on why other, newer, properties are having the same problem with the encounter builder and the map tool?
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.
Thank for clearing up the Mordenkainen's tome of foes + encounter builder issue. Could you shed any light on why other, newer, properties are having the same problem with the encounter builder and the map tool?
I can’t say for certain. I don’t work here and I’m not a moderator or anything like that, I’m just on here a lot. What I can tell you is that the devs have been doing a lot of work on the backend on the graveyard shifts recently. I know this because I’ve learned to recognize the tiny little glitches that always happen when they’re actively banging away on the code or compiling or whatever, whenever they‘re working on stuff basically. And I have insomnia so I tend to be on late at night and have noticed those particular peculiarities happening a lot lately. And I know that they’re basically pouring all available resources into getting their announced VTT ready ASAP, and preparing for the release of the revised PHB that’s coming out in a few months, and that has necessitated a lot of overhauling on the backend because so many things are changing quite drastically in terms of how the basic framework for the character sheets is coded. And I know that the way this site got put together makes changing those types of things a MONUMENTAL job for the devs
My best guess is that whatever they’re doing to the Encounters App, the Maps App, the Characters App, and the Library & Content Builder to integrate everything and have it actually work together for the VTT is causing the problem. I suspect that work has somehow caused a major gremlin to manifest in their code that links the Encounter Builder to the content and it isn’t recognizing people’s license entitlements properly or something. It probably popped up with the Legacy content first because they figured that was the safest area for them to start messing around with stuff since new users can’t access it anymore anyway, and many of the older users have probably switched to using the MotM versions of those monsters primarily, so it wouldn’t be as big of an issue when things inevitably went pear shaped on them while they worked.
It suspect it has since progressively started affecting more and more of the content in regards to accessing it in the Encounters App because they probably need to do a massive, systemwide overhaul of some aspects of either the Encounters App, the Content Library & Builder, or both to make things work as needed. It’s probably gonna cascade even further before they’re done. Then one day, all of a sudden, like a switch has been flipped, everything is gonna magically work again like there was never any issue in the first place. That’s what happened the last two times the made major retrofits to the system. Only both of those times they were working on the character sheet framework so that’s where things were wigging out then. Since this time the gremlins are affecting the Encounters App, that’s what leads me to believe it’s because of them working to integrate that into their nascent VTT software.
Like I said before, I can’t really know any of that for certain, and can’t actually confirm any of it either. However, I have found that my theories about these things have had a pretty strong track record to date. So take that for what you will. Make sense?
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.
Hi all, wonder if this is a bug or not.
I am building an encounter using the warforged solider creature in the encounter builder. The stat block is blurred out and says that I can still add it but cant see the stat block. Issue us I do own the book so not sure where to go from here.
Not sure what to do.
Thanks,
Greg
This is a problem we’ve been having for months now with MtoF monsters (support have not responded on this issue) however I think that monster is an Eberron monster - so not sure why it’s happening to that one.
Good to hear I'm not the only one! Sad its happening to others! The monster is from Eberron rising from the last war which is now legacy(I wonder if thats why) as the new book Way finders guide has been released. I may have that the wrong way round. Kinda sucks because I originally purchased these books in order to use the stat blocks and now I cant.
Isnt that like false advertising or something haha
Same here! I hope there is an answer soon, the only reason I bought those books is for my encounters.
+1 to this with the Moorbounder and Bristled Moorbounder from Explorer's Guide to Wildemount.
Yep - me too. Husk Zombies are no longer owned for maps or encounters... and it looks like Explorer's Guide to Wildemount is missing from the Marketplace and when you view All Sources.
Hello, I'm adding to this thread!
I own "Explorers Guide to Wildemount" but I'm trying to add a monster (Merrow Shallowpriest) and I keep getting the "you don't own this content" error.
Any help??
Same issue here, with basically anything that isn't basic rules.
I'm also having the same problem: I own Explorer's Guide to Wildmount, Mythic Odysseys of Theros, and Mordenkainen's Tome of Foes. Both encounter builder and maps say that I do not own the material.
I had a TON of encounters set up and because of whatever they changed, I can only use the homebrew encounters... HOURS of work wasted. I'm going to jump ship and use a different tracker.
I wanted to use a different one but wouldn't that mean making all the monster statblocks manually?
Hey, same from me! A bunch of encounters I have made suddenly don't work due to the site claiming I don't own the material. For some of them, I click the link to marketplace and it just takes me to the stat block, and for others the stat block used to be in a source I own, but now is in a new one? I am very confused.
UUUGGHHH!
You know what's more frustrating than the bug itself that caused me to have to roll manually this weekend during my game? The fact the D&D Beyond doesn't offer us a place to report bugs. THAT is infuriating. It shows how little they care about users.
Join my homebrew campaign!
A Greater Monster, The Kickstarter Letters & Death by Zamboni
daviddavid.net
My art store on Etsy
> National Indie Excellence Book Award finalist
> A Greater Monster named a "Top 10 Book of 2012" by Common Ills blog
> Listed in "10 Hot Chicago Reads for Chilly Nights" on Refinery29.com
this bug has existed for MtoF since December... with literally zero response form support and zero ackowledgement of a timeline for fixing it. A moderator did kindly report back that the bug was known, but the problem has now got worse and has spread to other books.
It is massively annoying and I've taken to have to print out stat blocks and run combat manually because of this.
I am deeply unhappy with the level of support from customer support and the lack of any resolution. This is paid for content... i bought it because i wanted to use it the encounter tracker (as i already have the physical books) - so im deeply deeply miffed.
Same issue here with Mythic Oddyseys of Theros
https://www.dndbeyond.com/forums/d-d-beyond-general/bugs-support/186534-mordenkainens-tome-of-foes-encounter-builder
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Epic Boons on DDB
Thank for clearing up the Mordenkainen's tome of foes + encounter builder issue. Could you shed any light on why other, newer, properties are having the same problem with the encounter builder and the map tool?
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 can’t say for certain. I don’t work here and I’m not a moderator or anything like that, I’m just on here a lot. What I can tell you is that the devs have been doing a lot of work on the backend on the graveyard shifts recently. I know this because I’ve learned to recognize the tiny little glitches that always happen when they’re actively banging away on the code or compiling or whatever, whenever they‘re working on stuff basically. And I have insomnia so I tend to be on late at night and have noticed those particular peculiarities happening a lot lately. And I know that they’re basically pouring all available resources into getting their announced VTT ready ASAP, and preparing for the release of the revised PHB that’s coming out in a few months, and that has necessitated a lot of overhauling on the backend because so many things are changing quite drastically in terms of how the basic framework for the character sheets is coded. And I know that the way this site got put together makes changing those types of things a MONUMENTAL job for the devs
My best guess is that whatever they’re doing to the Encounters App, the Maps App, the Characters App, and the Library & Content Builder to integrate everything and have it actually work together for the VTT is causing the problem. I suspect that work has somehow caused a major gremlin to manifest in their code that links the Encounter Builder to the content and it isn’t recognizing people’s license entitlements properly or something. It probably popped up with the Legacy content first because they figured that was the safest area for them to start messing around with stuff since new users can’t access it anymore anyway, and many of the older users have probably switched to using the MotM versions of those monsters primarily, so it wouldn’t be as big of an issue when things inevitably went pear shaped on them while they worked.
It suspect it has since progressively started affecting more and more of the content in regards to accessing it in the Encounters App because they probably need to do a massive, systemwide overhaul of some aspects of either the Encounters App, the Content Library & Builder, or both to make things work as needed. It’s probably gonna cascade even further before they’re done. Then one day, all of a sudden, like a switch has been flipped, everything is gonna magically work again like there was never any issue in the first place. That’s what happened the last two times the made major retrofits to the system. Only both of those times they were working on the character sheet framework so that’s where things were wigging out then. Since this time the gremlins are affecting the Encounters App, that’s what leads me to believe it’s because of them working to integrate that into their nascent VTT software.
Like I said before, I can’t really know any of that for certain, and can’t actually confirm any of it either. However, I have found that my theories about these things have had a pretty strong track record to date. So take that for what you will. Make sense?
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Epic Boons on DDB
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.
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Epic Boons on DDB