Originally posted by oldskool
Originally posted by dkgojackets
Originally posted by oldskool
There isn't a single section of the code that would ever WRITE an energy setting. It's a read-only action, there's no way the game is going to change your settings, and if it did it would have broken the entire game sim, not just changed a bunch of settings while leaving one different.
We would appreciate your explanation of what actually happened then.
Somebody fucked with your settings, it's that simple.
I don't know who it was or why they did it; maybe they GM more than one team and mixed the two up, if you want a legit non-trying-to-screw-you-it-was-accidental reason.
But there's no way the game sim would ever write to the energy settings page, it only reads them; and since the game only reads, that means a user must have written, and that means you've got yourselves a problem.
Bugs can do strange things... I've written code and had it do screwy things that it shouldn't have even been capable of doing, like, say, write to values that it should have only been reading.
There's always database errors as well. What if, say, some erroneous code somewhere wrote bad values to that portion of the database; the code that reads energy levels error-checked the values it read (as it should), detected bad values, and is coded to write 1/0 as new values as the default error indicator? Certainly possible.
The weirdness of bugs (including inconsistent and unreproduceable bugs, the software tester's worst nightmare) tends to increase proportionately with the size and complexity of the code in question. I can guarantee that GLB has large and complex code; it is constantly changed as Bort updates things; it's probably not written with the sort of clean and tidy (and time-consuming and potentially inefficient) software architecture that everyone preaches but few practice; and the game's in beta, which means bugs are expected. The way the code is implemented - it's thoroughly tested on the test server, from my understanding - means that the obvious bugs are weeded out before the code goes live here, which leaves us with the weird, unexplainable, inconsistent, and unreproduceable bugs, like this would be if it's verified that it wasn't user error.