0.9.3.2 is released. It fixes that stupid bug. Turns out it was actually simple and obvious.
For some reason, when I moved the cleaning harness into a somewhat reasonable location, I missed running the part that tells it to "optimize" the records and groups and such the way that xEdit does. One part of this "optimization" process that got skipped deletes the OFST fields from WRLD records, which xilav specifically confirmed to me is a necessary step of this process. Oops!
The fix was 1 line of code, but I also added a bit of an internal debugging tool for me to help make future bug fixes like this go faster, plus a very small performance optimization to the cleaning process.
Actually, i've installed it on a slow HDD because i've the SE on my SSD and i didnt wanted another skyrim installation on the same drive.
Looking at the issue of the last page, i actually found the cleaned esm's in the MO Virtual Folder, not in my DATA (probably because the HDD being slower drive compared to SSD) so i suppose that way im not affected of that bug?
If you set it all up using 0.9.3.1 or below and you didn't copy "known good" ESM files into the "Cleaned * ESM" folders or fix it up otehrwise, then you're definitely impacted by the bug. I'm 100% sure of this.
Instead of renaming the executable, is it possible to add the game specific switch instead? I download the latest version of xEdit, and name it as such, regardless if it was originally FO4Edit or TES5Edit or whatever.
I then use that one executable for all my MO controlled games, of which I have 4, and then add the switch to each so it functions in the game mode required.
ie. -tes5 for Skyrim, -tes4 for Oblivion, -fo3 for Fallout3, etc.
I could see doing that when I really seriously get into #6, but for the time being, I'm focusing solely on Skyrim 2011.
Edited by airbreather, 17 November 2016 - 10:00 AM.