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
2) Enter your game's installation path in the textbox at the top.
3) Click "Refresh" button above the "Conflicts" list.
4) If mergeable conflicts are detected, repeat these steps until the conflicts are resolved:
> Choose 2 or more versions of any file(s) to merge.
> Click "Create Selected Merge" button.
> If the mods have differences that don't overlap, KDiff3 can merge them automatically.
> If the mods have differences that overlap, KDiff3 will appear so you can merge them manually. See below for tutorial videos.
> If Script Merger can't find the vanilla version of the modded file, you must merge all differences manually when KDiff3 appears.
5) If non-text conflicts are detected, Script Merger displays them but can't merge them. So, one of the mods in each conflict will "win" & override the others. Here's how the winner is decided:
> By default, the game loads mods in order of folder names — numbers first, then underscores, then letters (not case-sensitive).
> Or, you can right-click one of the mods to set its priority (1 to 9999, lower number loads first). Here's an excellent detailed explanation by Kad_Venku.
6) Play!
7) When you uninstall or update one of the mods included in a merge, Script Merger will detect the change & prompt you to delete affected merges. If you update a mod & Script Merger doesn't prompt you delete any of that mod's merges, then they weren't affected by the update.
These are the directions on the nexus so I'm confused on why you are directing it to 3 different files. You only need the install path. For example c:/program files (x86)/steam/steamapps/common/witcher 3
Error [content0]game\player\playerwitcher.ws(11787): Could not find function 'SetRadialPotionLowerTimer'
Error [content0]game\gameplay\effects\effects\other\oil.ws(177): Could not find function 'ShouldAutoApplyOil'
Error [content0]game\gui\main_menu\ingamemenu.ws(1516): Could not find function 'SetAutoApplyOils'
Error [content0]game\gui\main_menu\ingamemenu.ws(1518): Could not find function 'SetAutoApplyOils'
Error [content0]game\player\states\vehicles\horseriding.ws(141): Could not find function 'ShouldAutoApplyOil'
Warning [modsharedimports]engine\environment.ws(30): Global native function 'EnableDebugOverlayFilter' was not exported from C++ code.
Warning [modsharedimports]engine\environment.ws(32): Global native function 'EnableDebugPostProcess' was not exported from C++ code.
Warning [content0]engine\showflags.ws(11): Global native function 'DebugSetEShowFlag' was not exported from C++ code."
Erm... what the spruce?