Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

PF2 module NPC token stat blocks missing info

We have been playing the Abmonination Vaults module and suddenly this week the NPC stat blocks attached to the tokens do not have all the correct information. The correct values are visible in the stat blocks in the compendium, but not on the one attached to the token. Some monsters are listed as having 0 AC and 0 HP, while other monsters have correct AC and HP but do not have values for any saves. Ability descriptions are not populated. The damage and rider effects of melee and ranged strikes are also not populated, but additional damage is. This issue appears to affect every NPC in the module (at least the 15 or so that I checked), example screenshot: The issue exists for other players when they log into the game as GM, and in both Firefox and Chrome, so I do not believe the issue is on my end. The issue also persists when creating a brand new game from the module. I searched for similar issues, but wasn't able to find anybody reporting them, so I'm hopeful it's just user error somewhere. The stat blocks worked fine until this week. Anybody have a fix I could try? Thanks!
Thanks for reporting this! We got a few support tickets on this as well and have already passed things back to the sheet development team to take a closer look. No ETA but they will be addressing the issue! In the meantime, it was mentioned that you should be able to temporarily fix this by going into the NPC settings and toggling the "elite/weak" toggle to something else then back to normal. Sorry for the trouble on this!
Closing the loop on this to say that the sheets appeared to be working normally when I logged in today. I didn't do anything, so presumably it was fixed by the sheet development team. Thanks!