安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題








I don't think the mod has been totally dropped, but it might be a while yet before it's fixed.
https://gtm.steamproxy.vip/workshop/filedetails/discussion/2631943123/597400677712434842/
What sucks is that this bug persists even after deselecting Gun Game. And it only started after I verified my files to try and deal with another bug (the game bizarrely starting in Windowed mode even though I always have it set to full-screen, and this time I couldn't even see the game unless I hovered over the taskbar icon). I tried testing if it was just affecting custom maps, but it does it for base-game maps as well. Then again, I've only tested Chronicles maps, but would assume it's the same for the others.
I don't think it's BO3 itself, though, as the game hasn't been updated in years. But even when I unloaded this mod and tried firing up UEM as a plan B (that mod also has a gun game mode)... I get stuck on the menu, but it now has no text except at the top right where it tells you what mod is loaded. At that point, I've got no choice but to close the game. Luckily I can still ALT-TAB out whatever happens.
I tried verifying the files, but no dice there.
EDIT: Duke is right about the game starting if you wait a bit. You just need patience. And yes, that problem is only on Gun Game for some reason. The other modes seem to work without issue.