GPT Patches a Broken Save

I see it now. I’m opening the EXE and checking the save-related code paths directly. I found the save cipher path in the EXE. It is not generic compression. It is a custom XOR stream with a deterministic byte schedule, and the EXE has separate encrypted/plain save handlers. I’m extracting the exact keying behavior now so I can test whether your .sav can be decoded cleanly. Yeah, and now I did. The earlier issue was just that the EXE was not visible on my side yet. Now it is, and I decoded the save format. What I found • .sav is not compressed • it is XOR-encrypted • the byte mask is: mask = (file offset * 0x65) & 0xFF So I can decrypt and re-encrypt it cleanly. Important result Your broken 1.sav has the museum city exit still disabled. The relevant block in your save says: • areaName=exit2city • nameID=-1 • isLevelSwitch=0 • noHint=1 In battle.sav, that same block is: • nameID=237 • isLevelSwitch=1 • noHint=0 That strongly suggests the museum progression flag got stuck after the red-card monitor event. I already made you a patched save Use this file as a replacement for your current 1.sav: patched 1.sav

A screenshot shows an AI assistant reverse-engineering a 26-year-old game's EXE and save-file format. It discovers that the save is XOR-encrypted, identifies a disabled museum city exit, and provides a patched save file. The joke is that GPT is acting like an expert game hacker and successfully repairing an ancient corrupted save. EN: A screenshot shows an AI assistant reverse-engineering a 26-year-old game's EXE and save-file format. It discovers that the save is XOR-encrypted, identifies a disabled museum city exit, and provides a patched save file. The joke is that GPT is acting like an expert game hacker and successfully repairing an ancient corrupted save.

• @eternalclassic / 84425 2026-03-06