while talking with a friend recently, I realized that he has far more information on a monsters page. https://www.dndbeyond.com/monsters/boneclaw for example doesn't have any information for me, a shared content user, while a friend that bought Mordekainen's book has more info about it, for which I need to go to https://www.dndbeyond.com/sources/mtof/bestiary#Boneclaw. I was thinking a couple of time, that the extra information would be nice to have.
Is that intentional design, as an incentive to get everyone to buy the book or a bug?
Yeah, but if you search for it, it generally directs you to the monster page. Setting it to sources only is an extra step which is overall just annoying.
Hey
while talking with a friend recently, I realized that he has far more information on a monsters page. https://www.dndbeyond.com/monsters/boneclaw for example doesn't have any information for me, a shared content user, while a friend that bought Mordekainen's book has more info about it, for which I need to go to https://www.dndbeyond.com/sources/mtof/bestiary#Boneclaw. I was thinking a couple of time, that the extra information would be nice to have.
Is that intentional design, as an incentive to get everyone to buy the book or a bug?
Thanks for letting me know.
That is weird, and I can confirm that accounts accessing it using content sharing do not see the details.
You can go to the book and see it though
https://www.dndbeyond.com/sources/mtof/bestiary#Boneclaw
Site Info: Wizard's ToS | Fan Content Policy | Forum Rules | Physical Books | Content Not Working | Contact Support
How To: Homebrew Rules | Create Homebrew | Snippet Codes | Tool Tips (Custom) | Rollables (Generator)
My Homebrew: Races | Subclasses | Backgrounds | Feats | Spells | Magic Items
Other: Beyond20 | Page References | Other Guides | Entitlements | Dice Randomization | Images Fix | FAQ
Yeah, but if you search for it, it generally directs you to the monster page. Setting it to sources only is an extra step which is overall just annoying.
Thanks for the report - I'll do some digging around to see if this is the intended interaction, and if it isn't, I'll pass the issue over to the devs.
Heya -
This issue has been fixed.
Thanks!