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
We have 35 spawners now, 4 nests, spawning in 45 different vanilla/base-game creatures. Several of these are set to spawn 20-50 creatures with a max of 100 in radius (which was the max setting on spawner).
I have written down spawn locations, settings, creatures, etc, so if I were to add a new spawn today, and the server would crash tomorrow m orning, I can assume that newly added spawn is the culprit. Then I can test the same spawn to see if I can recreate the crash...
I have my servers' save files back up every night, and saved for 14 days.
Then they get backed up once a week and those weekly backups are saved for 5 weeks.
I'd rather not have to roll back a server by 5 weeks but I have the option to if something goes wrong.