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






Soon/ I will try to prioritise it
This mod still works, it no longer requires the main CCP submod. It is now just a sub sub mod for Operation Deep Freeze.
I figured out from my tests, the deep freeze submod being one of the dependencies is what causes the map error
I get the map error message on the main menu and I noticed when there was a error, the main menu would show the 2WRW pictures while if there was no error the main menu would show the deep freeze pictures
I also checked the files of the 2WRW and they have made changes to one of the map files
What I think happened is by default, the 2WRW loads first and then deep freeze loads. My compatibility submod having deep freeze as a dependency, causes deep freeze to load first and then 2WRW loads over it. 2WRW and deep freeze have compatibility issue due to them both having changes in a map file. For some reason deep freeze loading over 2WRW doesn't cause a error (or not a bad enough error to cause a message) while 2WRW loading over deep freeze causes a error.