Thanks for the code, unfortunately the code doesn't work, the game wont finish loading the Loading Screen and stuck up eventually haha. But I got Sairoh anyways after 2.5 hours of waitingAssuming all that's true, it'd just be 2092A840 00000000, 2 being the 32-bit write command on every major PS2 cheat device I'm aware of, other than a couple of homebrew ones and the AR MAX, which would be 0492A840 00000000 (it uses the 3 unused address bits as size flags, among other things).
If it needs to be encrypted, that's another wrinkle, and I'd need to know the target device and possibly the master code for that. The AR MAX has obligatory encryption, so G9XC-72QD-51VZF on it. I vaguely remember Datel including a method for updating the encryption key in the master code, but never saw the option used. The default should always work, I think. Everything else has optional encryption, and the need for it, and the key, is generally down to who made the master code you're using for the game.
Ah I forgot to tell, I used a Codebreaker V10 if that helps.Well, hopefully you used it with a compatible cheat device. If so, I can't really say why it wouldn't work. The game could checksum some part of the save file after it's loaded into memory, or maybe it keeps trying to refresh the shops when they're zeroed on first load, and freezing the value to zero at that point causes it to just spend forever trying. Or it's just straight up wrong somehow. Can't say. I expect it's something along the lines of the second one, though. Usually a failed checksum would get you told off for having corrupted saves, and Z3R0's info is probably right. Most likely he just poked the value with a debug tool after loading into the game, and wouldn't have ever encountered any issues that might show up on the initial load.
Users browsing this forum: Google [Bot] and 17 guests