安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









The client <-> server connection may time out if the server takes too long to do something (without sending a keep-alive message). This may happen when generating big maps. The solution is to wait for the server to finish its work, then try loading the newly created map (use Load Game).
Turf 2 will have an integrated server (vtclient.exe and vtserver.exe will be in the same .exe) to prevent this
Vtserver also tends to be laggy when dealing with a freshly generated large map (like 8km or larger on my machines) for reasons unknown to me. Restarting the game will fix this.
Also see:
https://wiki.voxelturf.net/wiki/Troubleshooting#Connection_To_Server_has_Timed_Out_.28Singleplayer.29
And unless the cities actually overlap, they'll still be disconnected from each other.
Also, are cities still disconnected or nah? If not, I can just manually connect them. Not a big issue.