Posted April 13, 2022
This didn't happen on my first playthrough this year, but now that I've restarted the game, it happens every time.
I finished the Forgotten Shrine of Neferti, the Obelisk, and the upper level of the Ruined Temple of Harvest, but when I went to the Temple of Set, it was laid out as though I had already completed it: all monsters killed, all treasures taken, all doors open, even though I had not been there at all in that playthrough. Then, I checked all my save files and ALL of them were corrupted, so the same thing happened in all of them. I uninstalled and restarted the game, but after a few launches, the bug recurred every single time and ALWAYS corrupted all my save files as well. Has anyone EVER had this problem? (I haven't checked any other sections of the game other than those mentioned above, so I don't know if it corrupted other dungeons, but I wouldn't be surprised.)
One other thing. I was using Gotcha download of the corrected Code.2 which I used to correct the freeze during the ending video. It solved that problem, but I'm wondering if it introduced this bug. Does anyone have any idea?
I finished the Forgotten Shrine of Neferti, the Obelisk, and the upper level of the Ruined Temple of Harvest, but when I went to the Temple of Set, it was laid out as though I had already completed it: all monsters killed, all treasures taken, all doors open, even though I had not been there at all in that playthrough. Then, I checked all my save files and ALL of them were corrupted, so the same thing happened in all of them. I uninstalled and restarted the game, but after a few launches, the bug recurred every single time and ALWAYS corrupted all my save files as well. Has anyone EVER had this problem? (I haven't checked any other sections of the game other than those mentioned above, so I don't know if it corrupted other dungeons, but I wouldn't be surprised.)
One other thing. I was using Gotcha download of the corrected Code.2 which I used to correct the freeze during the ending video. It solved that problem, but I'm wondering if it introduced this bug. Does anyone have any idea?