Version: [42.7.0] Mode: [Singleplayer/Multiplayer] Server settings: [Host/Dedicated/N/A] Mods: [None] Save: [New Save/Old Save] Reproduction steps: 1. Start game   It's just not on the map anymore, it hasn't been there since the launch of build 42, only forests of every possible kind, even if there isn't a single tree around a hundred cells, I've disabled mods, reinstalled the game, deleted the Zomboid folder, checked the entire map several times since of build 42 in unstable, but it's just not exist.

Hi! I'm not talking about fluids containers becoming unusable, as that's a known bug, but about another, much more problematic behavior for which I haven't yet found a solution.   Version: [42.7.0] Mode: [Singleplayer] Server settings: [N/A] Mods: [None] Save: [New Save] Reproduction steps:     1. Place a rain collector or even a bucket on a tile     2. Wait for a crash (or maybe just Alt+F4)     3. Reload your save and wait for the rain (or use debug mode)     4. Now the tiles where a fluid container existed can no longer collect rain at all Some additionnal infos : No, it's not the object itself that's bugged. If I take my rain collector (or a bucket) and place it on the next tile, it works. If I take it back and put it back on the bugged tile, it stops working again. So it's definitely the tile that's affected by the bug. If anyone has a solution (debug mode or even better... a mod) while waiting for a bug fix

Watch out what you say, the response is easy : Minecraft. Zomboid is not the only "black hole" game that disintegrate your time.

Did you keep animals? They sometimes breed exponentially in a blink of an eye. Something to do with how the game keeps track of time. I think fast forwarding has something to do with it. I once found hundreds of chicken eggs at the Muldraugh meth lab house barely a week into the game.

Yo! Steam has an 'Alternate Launch' option that may help? Would you be able to see if the game launches with that?   Additionally, if you can go to your C:\Users\%UserProfile%\Zomboid folder and find the options.ini file: Inside there may be a fullscreen=true line. If there is, try changing it to fullscreen=false If still no luck, post a link to your latest console logs and I can see if there's any clues pointing to the source of the problem?