 |
1-2-LT1.save (592,955 bytes) |
 |
This is a weird one. The renpy save format is made of two parts, a snapshot of the game state, and a rollback log. This save (and the ones from others seeing this issue) appear to contain an accurate snapshot portion, but a rollback portion that's lagging behind. As yet I've been unable to recreate the conditions leading to the creation of such a save. When loading the mismatched save, the rollback portion wins out consistently against the more correct snapshot portion. However, it is possible to force-load the snapshot data into a separate rollback log which appears to recover the save, and allow progress to continue. Please note that due to the potential instability of this approach, it is not recommended for players to attempt to recover saves this way, rather it is noted here for the reference of developers in case it's useful. <code python> # first load save normally via UI (resulting in being in the wrong time/place), then in console: snapshot_data, frozen_rollbacklog = renpy.loadsave.loads(renpy.loadsave.location.load('1-2')) renpy.game.log.unfreeze(snapshot_data, label='_after_load') </code> Depending on where and what was taking place, it may be necessary to finish the current label's dialogue before play resumes from the freshly loaded save. |
|
|
At this time, do not examine the pieces of the statue in your inventory, as it will revert to that point, similar to how the Pregnex would revert back to that point in .17.1. This will be fixed in a future update. |
- Anonymous