安装 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 am just some random gamer who has run into a similar issue. it was conflicting with another map I had. I ended up having to unsubscribe to the other map in order for it to allow me to play it
If you want some technical explanation though, read on:
Campaigns rely on a file called the "mission file", which tells the game what maps are part of it, in what order, which survivors to use, what the campaign's name is, where to apply unique models and textures, etc. - Each part needs to have this mission file.
However, the game isn't intelligent, so it just sees "All these different parts have this same file in common. WARNING, CONFLICT. WHICH ONE DO I USE?!".
The game doesn't know that all the parts are just individual chunks of a larger mod, it sees them all as seperate mods, so any files that are in common show up as conflicting.
All this means is "These seperate add-ons have a file that looks the same, and the game doesn't know which of those identical files to use".
The same thing can happen if a texture, model, or sound was accidentally duplicated between the different parts, but usually it's just the mission file, and it has zero effect on the gameplay.