Instalar o Steam
Iniciar sessão
|
Idioma
简体中文 (Chinês Simplificado)
繁體中文 (Chinês Tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Checo)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol de Espanha)
Español-Latinoamérica (Espanhol da América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polaco)
Português (Brasil)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar problema de tradução
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