Curiously there's not a single line I can find that interacts with client preferences or would manually write to that file. My only conclusion is that somehow the variable and the value is being set as a blank variable.
$P["ref::Something = 1;"] = "";The preference system uses a method
setGlobalByName which could potentially cause this (will be adding safeguards) however theres no reason it should. Adding a safeguard will prevent the issue from repeating, however how I am still trying to find the source of the problem.
My leading theory is that it was caused by an alteration in file format for preferences, although I don't recall that being changed. It could be that, as preferences have never fully worked before, old changes and incompatibilities are now being exposed as it's working properly with data that was written by previous, buggy versions.
This would be surprising because it means every beta user had their preferences wiped and said/noticed nothing.
i just dont get how bugs like this just filter through testing. i should probably be a beta tester so i would be less frustrated with these things and help you guys more instead of release it through annoying posts
I'm really curious how this was never uncovered. My settings were never reset and I did a whole bunch of testing, more than ever before. Multiple servers per run, resets between servers, clean installs, dedicated, dedicated clean installs, upgrade tests, read-only tests. We had a decent number of beta users and I tried to interact with them often.
Edit:
4.0.2 download. I don't have a copy of 4.0.3 and a fix should be out soon for 4.1.