安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题








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.