(adsbygoogle = window.adsbygoogle || []).push({});
First off, this thread is strictly theoretical, so for now there is no need to panic. However if more developers start to protect their saves like devs from MachineGames studio, then we could tell “good bye” to save editing very soon.
As you may already know I was onto find a way to change Wolfenstein II difficulty by modding a save file. When I was reading people complains about insane difficulty of “Mein Leben” trophy, an idea came into my head. Without waiting any longer, I’ve submitted my save files to Save Wizard company, including instructions and my theory. In the meantime I’ve tried to test my theory on PC game version and the results doesn't look very promising…
Next few sentences would be my research about game saves from PC version, but the one on consoles could have the same structure.
After I’ve created new game save on “I'm death incarnate” (highest possible difficulty on which saving is enabled), I opened directory where the save files are stored. There were following files:
You must login or register to view this content.
Next thing I’ve done was opening “game.details” in Hex Editor. I found there exactly what I was looking for:
You must login or register to view this content.
If
“I'm death incarnate” id number is
“5” then id number of
“Mein Leben” difficulty is
“6”!
I was right about that, but there my luck has ended. This file has its own checksum inside of it and every file has the second file with “.verify” extension. Those files contains 39 bytes of data which is Hash code generated to verify if save file has been tampered. If you change any value without generating new hash then this happens:
You must login or register to view this content.
On PC we can reverse engineer apps to learn how they generate those hashes, but on consoles we can’t. Not without jailbreak or kernel access. :/
I hope this method isn’t present on consoles version of Wolfenstein II, but we can expect moves like this in the future…
Tell me what you think in the comments.