Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Hello Games really dropped the ball when they opted to do it this way instead of simply loading other players' edits into a separate (preferably temporary) set of buffers.
but i think you restored the old savefile huh? ;) - less work *g*
https://steamuserimages-a.akamaihd.net/ugc/1625195069393583829/19F780A298D5D4767F43B189C4CC0A1C09D80A65/?imw=5000&imh=5000&ima=fit&impolicy=Letterbox&imcolor=%23000000&letterbox=false
No, unfortunately I didn't know about that and my last backup was so old that I would have lost several newer bases anyway.
But last night I learned how to manually backup the TerrainEdits portion of the JSON and reapply your saved edits to ANY existing save file. Wish I'd known about that before all this happened.
At least now if anything like this ever happens again, I'll know what to do.
For those who don't know, using the NMSSaveEditor, you can open up the JSON portion of your save file, open PlayerStateData, scroll down to the TerrainEditData section, and then Ctrl-A/Ctrl-C copy the *entire* JSON array (all 15,000 entries!) containing your terrain edits. Save that chunk of JSON code into a backup text file and then you basically have a permanent backup of your custom terrain edits in case anything ever goes wrong.
I'd always thought of the save editor as just a cheat tool, so I never bothered with it (because I don't cheat). But the fact that it can create permanent terrain edit backups AND delete individual "parasitic" edits from your buffers is pretty awesome.
Likewize, every day a base gets filled in with soil every day, i have about 7 small bases, they all backfill . I assumed it was just bug number 101 in a long list of things that never get fixed. hmm will look at this JSON thing, sounds liek a job for a bit of script automation.
How other players see your base mostly depends on what your base looked like when it was last uploaded. Once you get a base how you want it, you don't ever have to "refresh" it via re-uploading unless you actually make additional changes later on. That's not to say that other players will *always* see you base exactly the same -- it's possible for the edit buffers in anyone's save file to go all wonky from being exposed to too many edits too quickly, causing rendering issues as buffers are dynamically recycled to make room for new data.
There isn't really a global edit buffer per se. It's more precise to say that everyone has their own individual edit buffers in their save files that *can* be affected by being exposed to terrain edits made by other players. If you upload a base with customized terrain to HG's servers, then even if your own save file's terrain data gets wiped, your base would theoretically still look okay to everyone else but you, because HG is streaming your uploaded base data to other players via their servers. In other words, your own bases don't get streamed to you from HG's servers -- they are loaded directly from your save file. So if your save file's terrain data gets wiped and you don't have your own personal backups then you're pretty much screwed.
Basically, after a wipe, if you need to use the Save Editor to restore any lost terrain edits to your save file, then re-uploading *may* help lock in and protect your restored edits in YOUR save file, but otherwise HG's servers will continue to send other players your base in whatever state it was in when you last uploaded it.
Again, the important thing to remember is that any parasitic terrain data from other players that clogs up the buffers in YOUR save file won't actually become permanent unless you actually save your game! If you mostly play solo then quitting without saving can avoid terrain regen after visiting someone else's base!
However, if you play a lot of multiplayer or have a base in a hub around a lot of other players, then as others have said your only real option is to totally avoid relying on terrain edits.
(Sorry about the long winded explanation.)
Yes, that's exactly what I meant :)
Sure you can cheat with the SE but in the first place it's a tool to fix small and big problems in the game ;)