-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tr1/objects/scion3: save scion hitpoints #1820
Conversation
Download the built assets for this pull request: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This bugfix is working perfectly, thank you. 👍
@@ -12,6 +12,7 @@ void Scion3_Setup(OBJECT *obj) | |||
obj->control = Scion3_Control; | |||
obj->hit_points = 5; | |||
obj->save_flags = 1; | |||
obj->save_hitpoints = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh no – we can't do it like this, or else it'll break legacy saves. We need to force disable saving the hitpoints in the legacy reader.
Should be easy to test – just grab a TombATI save from that level, try to load it with TRX containing the fix from this PR, and it shouldn't crash.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, thanks!
Pushed a fix, and test saves attached. This loads OK (and can confirm it certainly did crash before fixing this).
874ef8c
to
5f230c1
Compare
This ensures the shootable scion's hitpoints value is saved so if it's still active on reload, Lara can't continue to target it. Resolves LostArtefacts#1819.
5f230c1
to
d72d14d
Compare
Resolves #1819.
Checklist
Description
This ensures the shootable scion's hitpoints value is saved so if it's still active on reload, Lara can't continue to target it.
Existing saves would continue to have this bug, so it's a going-forward fix.