ILikeToHackThings

I've reported the bug, and found out the cause, Here's what I did to break it, in case anyone else catches that they're doing the same mistake Current game parameters of afflicted game; - No DLC Installed. - Survival mode - Interloper difficulty - day 6 - mystery lake camp office - blizard outside - male character - build # 2.12 112469 XO Steps to reproduce: 1) Exit camp office. 2) Re-enter camp office. 3) observe auto save. 4) Pause game and allow xbox to go into sleep mode and turn off. (I also change my HDMI input source to watch TV while I wait for the device to turn off.) 5) Use controller to turn console back on. 6) launch the long dark, you should be brought back to the pause menu as expected. 7) exit camp office and re-enter, observer auto save functioning as expected. 😎 press the guide button on the controller, and click Home to go to the xbox box menu. 9) open the long dark again, you should be booted back into the game exactly where you were, as expected. 10) exit and re-enter office again, observe that autosave did NOT happen. 11) Sleep in bed, observe that autosave, again, did NOT happen. 12) pause game and try to quite back to main menu, observe that the menu is frozen and you cannot leave the "Are you sure that you want to quit" menu. The above steps reproduce the bug every time.

There's a new bug that prevents you from writing down notes in your daily and general notes. That is all.

So there's a new bug in the game that will result in you losing all your progress. The bug causes the game's autosave feature to stop working. I think it gets triggered if your xbox goes into sleep mode. Some weird symptoms of the bug; You'll see a faint overlay of the long dark logo over your screen as you play. Trying to exit the game will cause the menu to freeze up, forcing you to close the software from the xbox main menu. You will put in multiple hours on interloper, just to resume the game back on day three or something. I'm taking a break from this game for a while.

I don't think that this would be too much of a challenge. I don't know what the code looks like, but I assume that most food items in the game are grouped in common class, if not then a common folder. Where certain things like the meats maybe are grouped under a common class and the main difference being the variables passed into their constructors. Meaning that each of the food item class would require a few parameters; such as freeze rate doubles, frozen boolean, structures/classes containing the graphics for the freeze meter. There would also need to be some modifications made to the function that handles the actual cooking. Since this feature is already built into the dead animals, clothing and boiling water, a good chunk of this stuff would be a copy and paste job. Could be tedious, but there isn't an overwhelming amount of food items in the game. ~source: I am a programmer

After playing a little too late into the night I had an idea! Does anyone else think that food items should freeze when left outside? Like, in real life if you wanted to preserve your food, you'd want to place it outside to save it's condition, which would cause it to freeze. And before you cook it, you'd need it to defrost it! I feel like this would add an extra bit of challenge and realism by forcing players using this setting to wait an extra bit of time to cook their food, while also adding an extra bit of balance to the game by putting a respectable penalty for plopping everything outside. A small thing, but it could have a nice impact on the game!