Saving, relaunching, and reloading clears Curse

[NQNStudios]

Encountered while testing VoDT. Steps to reproduce

• Checkout the first new commit on branch NQNStudios/2.0b1-c (which is not yet a PR)

• Run this replay: VoDT_05-04-2025_14-32-10.xml.zip

  • Without 2.0b1-c, it will end with the game crashing and no fatal error message (because it's a segfault, I think).

• When the replay ends without crashing, note that the whole party is cursed.

• Save As and store the save file.

• (required) Quit and relaunch Blades of Exile

• Load the save file.

• Note that no one is cursed.

[NQNStudios]

Related to this: If you play the replay, and immediately load a different file that's in a scenario, the party will be cursed in that file.

[NQNStudios]

For the first case, the status gets written out to pc{n}.txt correctly. After you load it in a fresh game session, and save again, pc{n}.txt will not have the status encoded in it. So it must be a flaw in extractSparse() which happens here.

[NQNStudios]

I want to make sure monsters save/reload their statuses too when this is fixed.

[NQNStudios]

Fixed by 877e6d2 which will come in the 3rd beta 1 PR.