AUTOSAVE BUG: Since I've gotten the bug a couple of times I've begun to analyze what's going on when it happens to see if I can notice anything. So far it has only happened when interacting with something. When it happens the SAVING comes up on the screen but game continues, interactions are mostly disabled, and the game does NOT actually save..... I can offer a conceptual solution that might be quick or take some time to code, depending on existing code.... Autosave should occure in two phases.... Phase One simply checks to see if it is time for an autosave and if so sets a flag to do the save... Phase Two waites for the flag to be set. If the flag is set then it checks to see if the player is interacting with anything. If the player is interacting with something then it waits until next tick and checks again. If the player is not interacting with anything then launches Phase Three. Phase three is the actual execution of the Autosave which PAUSES the game (in an internal manner than the player cannot interrupt, in order to keep the player from causing a problem), saves, then unpauses... This should remove the problem... Also I'd allow the player to select frequency of autosave. Personally I would prefer the game autosave only at 06:00 of the game day. that way if there is a crash or if I encounter a game-ending bug then when I restore I know it is 06:00 of that day. I've started doing this manually at the beginning of each day but it would be fantastic if the autosave did it for me.... BTW, I realize that for the above to happen efficiently then all interactions would have to set an "interacting" flag when they begin and clear it only when they are done, which might take some time to implement. Loving the game btw, and other than the autosave failure and the periodic atv going crazy (rolling over for no reason as I begin moving, invariably crushing me) I've had no real problems with the game other than my own short-sightedness (food).

Bug

Happy

0.0333332

No

0.184.3