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
When the game detects a conflict, it refers to a file called the addonlist.txt, which is really just a list of all installed mods. Mods higher on that list take priority over mods lower on that list to resolve conflict.
You can modify the addonlist.txt in almost any text editor to change priority order. If you have two mods that change the same sound set, for instance wooden and chrome shotguns, you place the mod you want to hear higher on the list than the mod you don't want to hear.
In the case of multi-part campaigns, like you find on the Workshop, you can usually ignore the conflict as all the parts use an identical file as part of the campaign. It will work.