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








Either the scenario was not properly installed on the server, the bundle files got corrupted during a FTP upload (upload it as a zip and ask the host to unpack it for you), or the server is not up to running the scenario.
Validating files in steam also validates the scenario files which can fix issues with running an out of date version of the scenario because steam isn't the best at pushing workshop updates to people.
We started a new game with your 1.6 release (with much grumbling from the players). The files are DL directly to the server and moved/renamed as necessary from there. Twice now, we have had the validation process indicate a missing dedicated server file, which was supposedly downloaded. I'm pretty sure that it was the same file. We also installed a local version of the game on the server and ran a check with the mod installed, and the local game files validated.
Recently, we learned that the server owner had left the default dedicated.yaml name alone, so we have to back it up frequently to keep it from getting over-written when there are updates, which is a pain. Obviously, it is a potential problem source, but changing it now seems like a bad idea. I've walked through the rest of the mod settings and installation with the server owner, and it seems correct.
The mod mostly runs without issue for us, but there are those strange errors, from time to time.
We'll keep hammering away at it, of course. Maybe one day, Eleon will provide more mod support. One can hope.
Via this post in Discord:
Currently, the files are DL directly to the server from Steam and moved/renamed as necessary from there. Previously, however, we did rely on FTP, and apparently were not using binary transfer, so it is possible that the save file is corrupted.
We probably need a fresh start to go with the new server, but there's no way the player base will go for it right now. I'll have to wait for the next major version number.
I am going to be working on it early next year, so most likely a few months away before any major update.