mirror of
https://github.com/RetroPortingToolKit/psxrecomp
synced 2026-10-28 10:59:16 -04:00
71e77f91cd
`default: return 0` made every savestate written by a build with one extra section a poison pill for every build without it. Worse than unloadable: by the time the apply loop hit the unknown tag it had already restored RAM, VRAM and CPU state, so the refusal left a HALF-RESTORED machine that wedged or died at PC=0 -- which presented as "loading a save crashed the whole thing", with the restored-but-untracked VRAM showing low-res in the wreckage. A sectioned state format exists precisely so readers can step over what they do not know. Known-but-malformed sections still fail as before; only genuinely unknown tags are skipped. This also makes the states saved during the short-lived BS_SEC_TEXPACK window load cleanly again (the extra section is now ignored), and it is the forward-compatibility prerequisite for ever adding that section back. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>