Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
The most effective, the best approach to do there is to:
1. Do save achiving. Create a new archive every time you stop playing, so, even if your save ends up corrupted after you close the game - you'd still have access to your *.bak files. And you need access to the *.bak files, because everytime you launch the save, those files are rewritten. If you happen to have a corrupted main file, you'll kill your *.bak files by launching the save.
2. If you have a suspicion that your save file might be corrupted(after a blackout/game crash/PC crash) - you need to refrain from launching that save until you make a backup of it. After that, you can try and launch it to see if everything is okay. if something went wrong - you can always restore core file from their corresponding *.bak files.
Minecraft had the exact same issue, previously. Hope TFP would figure out a way to report suspicious save structure and would suggest the player to automatically restore it from the *.bak files. That would make the save ressurrection a way more friendly to people who can't just spend hours to figure out and fiddle with data files of their saves.
Wouldn't have helped with the most recent issue though, without losing hours of progress. Been DIYing through the day, so pop back to the PC occasionally to have another go but to lose half a day of progress and go back to the prior save would also be quite frustrating.
I only stepped in because of A20, think its better to leave it for a while. Thanks for the affirmation of it being a legit problem though.
If you are on a20 experimental, be sure to wipe all data from previous versions and try a new map with a new seed you have not used previously.
Bedroll is already supposed to prevent POI reset.
But yeah, building a base away from POIs is all well and good but I'm on Survival, with 50% loot, 75% player block damage, 150% zed block damage, 300% blood moon zed block damage and running zeds. Can't whip up a base strong enough against that, without enough time to prepare.
In A19, the POI reset boogeyman only seemed to me to affect POIs that are useable for quests. There were several remnant POIs that could only be returned to default by entering console commands to forcibly reset chunks.
Because of the sweeping changes brought on by the tile system that the Pimps brought us in A20, my paranoia about losing bases to POI reset has returned and I built my permanent homebase from scratch, well away from any POI.
My horde bases, OTOH, I feel less concern for due to reasons we all understand, and these get built anywhere that fits the need. In the most recent update for Experimental, I lost a horde base that I had build out of one of the new remnants and it happened on day 42. Much fun was had?