Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
They also mention map_sand.bin - but talk about the *client* deleting the file.
I have found that deleting the file on the *server* causes the server file to be re-created and all clients download the updated file.
In the multiplayer server where I am an admin, the Sandbox Settings shown in-game do not always match the settings in servertest_SandboxVars.lua - they often get stuck on a cached version.
When saving the Sandbox Settings, servertest_SandboxVars.lua is then overwritten with whatever values were shown, but after rebooting the server, the Sandbox Settings shown in-game revert to the old version again, no matter what changes were made.
Deleting map_sand.bin on the server results in the Sandbox Settings shown in game updating correctly to show the settings in servertest_SandboxVars.lua
As you have suggested, this issue is most likely caused by a mod doing something weird.
I was hoping that installing your mod would fix the issue. It does not.
My solution is to regularly delete map_sand.bin