Server generates map with wrong salt
Hey Guys,
My Server (Started with LGSM) generates the Map with a wrong Server Salt.
If i type "server.salt" i get a answer with "168"
But the Mapname was "proceduralmap.4000.248364334.169"

I have this Problem Since the last Rust update. In addition, since then I have the problem that the MiningQuarries at the monuments no longer generate resources.

At the Rustserver Config from LGSM i set the Salt to 168. at RCON i see that this is right.

Any Idea?
Or your config file if you rent hosting
i mean server salt. and its a Linux Server.
Seed: "248364334"
Salt: "168"  or erroneously "169"
Size: "4000"

(13:44:47) | server.seed: "248364334"
(13:44:51) | server.salt: "168"
(13:45:51) | server.worldsize: "4000"
(13:45:54) | Saved 98,159 ents, cache(0.31), write(0.04), disk(0.02).
(13:45:54) | Saving complete​




The filename contains all these informations. But the Salt ist wrong..

Configfile:

# Advanced Start Settings
seed="248364334"
salt="168" # default random; range : unknown range ; used to recover a known setting from an existing map
worldsize="4000" # default 3000; range : 1000 to 6000 ; map size in meters
saveinterval="300" # Auto-save in seconds
tickrate="30" # default 30; range : 15 to 100


I host it on our own Root with LGSM.. As I mentioned above.

@BattleSheep  the last number, actually the "169", is'nt the salt, it's the "SaveFileName"s revision count. This counts up with every protocol changes, equal to a forced wipe
The last three numbers are not server.salt. This is just a number that gets incremented with each forced map wipe.
You know remembering back, I could have swore "salt" had something to do with how ore nodes popped up...
In response to Oddyseous ():
You know remembering back, I could have swore "salt" had something to do with how ore nodes popped u...
Thats still correct :)
In response to FuJiCuRa ():
Thats still correct :)
Hurray, I knew something! lol