安装 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 log doesn't look too bad (nothing obvious, I was able to start XCOM2 with a logging window) sadly, guess I have to dig deeper. I'll see what I can do.
Thanks again!
It looks like something very rare and unexpected happened on the GameState side of things. I'm pretty sure that this is easily fixable, I'll report back once I can give you a detailed analysis why this happened, and hopefully a fix as well ;)
The bug was a rare special case I failed to identify. There was a runaway loop which finally came to an end when the counter wrapped (which took several minutes). After that the game just continued as if nothing happened but the internal state of the mod was broken regardless.
The fix was very simple, here's the GitHub PR if anybody is interested: https://github.com/Luminger/xcom2-killcounter/pull/4/files
Thanks again Harddk, I wouldn't have been able to find this for a long time without your savegame!