This doesn't seem to work. The string bIsAchievementsDisabled is only in saves_meta.sav and while that gets patched it doesn't seem to find any similar string in the actual save files themselves. The disabled achievements seems to be flagged in the files as saves_meta reverts back to having that flag set to 1 every time, even with cloud saves disabled. There's seems to be some other flag in the save file itself, possible obfuscated or encrypted or compressed or something.
Edit: I did a little more digging, in the save files themselves I found the string bIsAchievementsDisabl with a byte reading 01 right after it. I set that byte to 00(NULL) and then the broken achievement icon disappeared. This flag doesn't appear at all in saves that never had it and when I loaded the altered save and immediately re-saved it, the flag was also gone.
That's interesting. In my save files the flag was on different positions depending on whether it was an autosave/quicksave or a manual save. And the saves_meta file also had a different structure.
For saves_meta, the structure was dependent on the length of the fields.
where "BoolProperty" always comes after the flag name. So I had to search the entire window starting from bIsESS to get the correct offset.
For the manual saves it was pretty easy, you have "FlagName 00 0D 00 Bool XX" where XX was the actual flag. Like, Bool00 for false and Bool01 for true.
I'm curious what platform you're on. The weirdest thing is the flags differ between the two files. The save_meta has bNeedTheWholeGameDownloaded and bIsAchievementsDisabled but the manual saves have bNeedTheWholownloaded and bIsAchievementsDisabl which is why the script wouldn't match them. And the bIsAchievementsDisabl flag is just omitted from save files when it's false.
Thanks bro I was really pissed when I accidently opened the console and realized 3 hours later that my saves were had the disabled achievements symbol.
It shouldn't but it does. I accidentally hit tilde while trying to press enter in the arena and it disabled achievements. Didn't use it, didn't do a damn thing just closed it and continued.
It doesn't disable for when when I open it. I started typing stuff to see all of the command hints, just to see if that would trigger it (didn't send any commands), and then I saved, but I'm not achievement locked.
Hi! Those are false positives. To make it easier to use, I packed the python script as an EXE so that people don't have to use the Terminal. The code is fully open source so you can see for yourself what it does:
78 comments
Edit: I did a little more digging, in the save files themselves I found the string bIsAchievementsDisabl with a byte reading 01 right after it. I set that byte to 00(NULL) and then the broken achievement icon disappeared. This flag doesn't appear at all in saves that never had it and when I loaded the altered save and immediately re-saved it, the flag was also gone.
For saves_meta, the structure was dependent on the length of the fields.
bIsESS
BoolProperty bNeedTheWholeGameDownloaded
BoolProperty bIsAchievementsDisabled
BoolProperty SaveHash StrProperty
where "BoolProperty" always comes after the flag name. So I had to search the entire window starting from bIsESS to get the correct offset.
For the manual saves it was pretty easy, you have "FlagName 00 0D 00 Bool XX" where XX was the actual flag. Like, Bool00 for false and Bool01 for true.
Tested by saving before joining the fighters guild and then got the achievement for joining.
https://github.com/NullDev/Oblivion-Remaster-ReEnable-Achievements
I talked to nexus about the false detections, so they reviewed it for me and approved it