Reply to Re: New D-Mod: Cursed Blades Part 1: Charlie's Legacy
If you don't have an account, just leave the password field blank.
The only thing that should make a save#.dat get "banananized" is a cheat save, if you cheat save, then regular save at a save machine BEFORE you load, it will not bananaize it. So no, your example should not have done that.
The only other thing I can think of is a save machine in the game that for some reason has a different script attached that I overlooked and isn't being detected as a "normal save", but I don't think that's the case so I dont know what's going on. When you send me the saves, I'll investigate.
EDIT:
Also this:
"Yeah, but every save gets corrupted. Even ones where cheat wasn't used."
Literally makes no sense to me. The anti cheat-save measure is based on certain globals, compared with &cur_weapon/&cur_magic which is all set right before the game is saved, and is checked on load. Nothing can change the global variables set in another save.dat, so it's not possible for one cheat save to change other saves. Weird.
EDIT2: I replied to your PM you sent me.
The only other thing I can think of is a save machine in the game that for some reason has a different script attached that I overlooked and isn't being detected as a "normal save", but I don't think that's the case so I dont know what's going on. When you send me the saves, I'll investigate.
EDIT:
Also this:
"Yeah, but every save gets corrupted. Even ones where cheat wasn't used."
Literally makes no sense to me. The anti cheat-save measure is based on certain globals, compared with &cur_weapon/&cur_magic which is all set right before the game is saved, and is checked on load. Nothing can change the global variables set in another save.dat, so it's not possible for one cheat save to change other saves. Weird.
EDIT2: I replied to your PM you sent me.
