[PF2E] Latest Update Broke Resistance/Vulnerability/Immunity, Amongst Other Things...

[FloofzyKitty]

After the latest FantasyGrounds update (v5.1.0 I believe) broke the processing for Res/Vuln/Immunity based on the creature's stat sheet. Nothing is being processed automatically, not even condition immunity, unless we specifically put an effect for that condition on it.

Additionally, the Favorites tab is just broken in various ways now. Skills are appearing in the wrong locations, or the headings are missing entirely. A glitched, blank skill also appeared in my Favorites that doesn't even have the star on marking it as a Favorite activity and I don't have a way to remove it.

Basically: Various small things broke with the PF2E ruleset, and I don't know how to fix it. There are other things broken that other players were noticing, too many to put all in one post. Is there a way to go backwards to a more stable version?

[Trenloe]

I can't recreate these issues in a base PF2 campaign with no extensions.


After the latest FantasyGrounds update (v5.1.0 I believe) broke the processing for Res/Vuln/Immunity based on the creature's stat sheet. Nothing is being processed automatically, not even condition immunity, unless we specifically put an effect for that condition on it.
Can you provide specifics of this please? Is it that effects aren't being created when an NPC is added to the Combat Tracker? Or is it that effects such as RESIST aren't being applied when damage is rolled?

If you could provide a specific example (creature name and source) and what doesn't work that would be great.


Additionally, the Favorites tab is just broken in various ways now. Skills are appearing in the wrong locations, or the headings are missing entirely. A glitched, blank skill also appeared in my Favorites that doesn't even have the star on marking it as a Favorite activity and I don't have a way to remove it.
We added some additional code to rebuild the Favorites tab when the PC is first opened each session to try to alleviate issues such as this. Please export the problem PC(s) and attach the XML here so I can take a look.

[FloofzyKitty]

I can't recreate these issues in a base PF2 campaign with no extensions.


Can you provide specifics of this please? Is it that effects aren't being created when an NPC is added to the Combat Tracker? Or is it that effects such as RESIST aren't being applied when damage is rolled?


I think it is specifically affecting legacy creatures from my experience. Previously, using legacy creatures in the Remastered ruleset worked without issue. For example, the session before this we triggered a Fire weakness and it automatically handled it since it was in the creature's sheet. After the update, the legacy Wood Golem from Bestiary 2 (I believe it has no direct Remaster equivalent) was not having its Resistance work, and before that a Terra-Cotta Soldier's immunity to Sickened was not applying. It let me put the effect on, was also reducing their stats, and there was no mention in the logs that it even had an immunity to it.

Sadly I'm not the owner of the campaign so can't give the XML right now, but can export at another time.

[Trenloe]

Thanks for providing the examples.

Golem's antimagic ability needs to be handled manually because it's not possible to reliably automate how that ability works. Otherwise, the physical resistance works fine in my test - when the Wood Golem from Bestiary 3 is added to the combat tracker an effect of RESIST: 5 physical,!adamantine is added - which resists bludgeoning, slashing or piercing damage. If this is not working correctly for you please provide more details.

Immunities are only currently automated against damage - e.g. IMMUNE: slashing immunity to conditions isn't implemented, hence the Terra Cotta soldier would not stop the Sickened condition being added. It's something we plan to implement in a future release.

From my testing both of these creatures are working correctly within the bounds of the available automation. Theis hasn't changed with recent releases. If you have any other examples that aren't working, please provide them.

Regarding the PC XML - as a player you can export your PC XML, which is cached on the computer where you played. Details on how to access that PC data is provided in this video: https://youtu.be/30o7jjJpLoo It's a little bit dated (in terms of the FG graphics) but is still accurate.

[Trenloe]

I've been looking into implementing condition immunity effects. The code is in a low-risk area of the ruleset for change and should be fairly straightforward to implement.

[Trenloe]

Support for condition immunities has been released today. https://www.fantasygrounds.com/forums/showthread.php?86677-Release-Updates-for-January-27th-2026

[Surge]

Additionally, the Favorites tab is just broken in various ways now. Skills are appearing in the wrong locations, or the headings are missing entirely. A glitched, blank skill also appeared in my Favorites that doesn't even have the star on marking it as a Favorite activity and I don't have a way to remove it.
We added some additional code to rebuild the Favorites tab when the PC is first opened each session to try to alleviate issues such as this. Please export the problem PC(s) and attach the XML here so I can take a look.

The favorited activities disappear from the Favorites category for the player when the GM opens the Activities or Favorites tab for the first time.

Also, what can occur is activities being Favorited and correctly appearing in the Favorites tab, but do not appear in the Favorites group (see image)

https://www.fantasygrounds.com/forums/attachment.php?attachmentid=66432&stc=1&d=1769906787
66432

Thanks

[Trenloe]

The favorited activities disappear from the Favorites category for the player when the GM opens the Activities or Favorites tab for the first time.

Also, what can occur is activities being Favorited and correctly appearing in the Favorites tab, but do not appear in the Favorites group (see image)

https://www.fantasygrounds.com/forums/attachment.php?attachmentid=66432&stc=1&d=1769906787
66432

Thanks
Sorry for the delayed response. I've fixed this issue in the next release. Thanks for letting us know about the problem.