Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.