You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pal Calc currently parses the whole save file when reading, which makes the reader sensitive to any format changes in any part of the file.
Pal Calc is only interested in certain sub-structures. A change to an irrelevant part of the file shouldn't cause issues elsewhere in Pal Calc.
We should prefer to parse the whole save file for correctness, but if there's an error, we should fall back to a "skip-loading" process which searches for known markers of relevant sections (e.g. .worldSaveData.CharacterSaveParameterMap) and resumes parsing from that point.
The text was updated successfully, but these errors were encountered:
Going to close this without changes. Implementing this would require significant changes and increase drift vs. palworld-save-tools which is used as a reference. In practice this doesn't seem like much of an issue
Pal Calc currently parses the whole save file when reading, which makes the reader sensitive to any format changes in any part of the file.
Pal Calc is only interested in certain sub-structures. A change to an irrelevant part of the file shouldn't cause issues elsewhere in Pal Calc.
We should prefer to parse the whole save file for correctness, but if there's an error, we should fall back to a "skip-loading" process which searches for known markers of relevant sections (e.g.
.worldSaveData.CharacterSaveParameterMap
) and resumes parsing from that point.The text was updated successfully, but these errors were encountered: