How to fix Witcher 3 Script Compilation Errors?

Script compilation errors mean The Witcher 3 could not build its scripts at startup, almost always because a mod's script does not match your game version or another mod. Each error line names the mod folder and the script file at fault. Remove or update that mod first, and after the Remastered update (5.x) clear old mods and Steam Workshop subscriptions.

Facts checked on 14 October 2026. Steps written for The Witcher 3: Wild Hunt Remastered 5.01, Next-Gen 4.04 and Classic 1.32 on Windows 11 and Windows 10 PCs.

What Script Compilation Errors mean in The Witcher 3

The Witcher 3 keeps a large part of its game logic in plain text files with the extension .ws. CD PROJEKT RED's REDkit documentation says these scripts are compiled when the game starts, and that this is the moment you are told about files that cause issues. When one file cannot be compiled, the game stops before the main menu and shows the list.

The same documentation gives the usual reason in one sentence: "This error is caused because multiple mods edit the same files." Since 29 September 2026 there is a second big reason. With the Remastered update (version 5.0), script mods made for older versions stopped working.

How to read the error lines: mod folder, script file, line number

The window looks like a wall of text, but every line is built the same way. Once you can read one line, you know which folder to open. Here are four real lines that players posted on the CD PROJEKT RED forum.

Lines from players' reports on the CD PROJEKT RED forum

Error [mod0000_mergedfiles]game\player\r4player.ws(11212): syntax error, unexpected TOKEN_VAR, near 'var'
Error [modsorteverything]game\gui\menus\alchemymenu.ws(62): Could not find function 'GetAlchemyFilters'
Error [content0]game\gameplay\alchemy\alchemymanager.ws(196): Could not find function 'GetUnusedMutagensCount'
Warning [content0]engine\environment.ws(30): Global native function 'EnableDebugOverlayFilter' was not exported from C++ code.

Start with the first Error lines. One wrong file can produce many lines, because every script that depends on it fails too. In one forum report, 25 Error lines named only two sources: content0 and a single mod.

What causes Witcher 3 script compilation errors, from most to least common

Most often a mod's scripts were written for another version of the game. Less often two mods edit the same script and were never merged, or an old merge was left behind. Rarely the game's own script files were overwritten or damaged. Hardware and drivers are not on the list.

Where mods, merges and the game's own scripts are stored

The fixes below move or delete folders, so it helps to know the places first. CD PROJEKT RED Support gives C:\Steam\steamapps\common\The Witcher 3 as an example of the game folder. In Steam you reach yours this way: right-click the game, select Properties, open Installed Files and select Browse.

How to fix Witcher 3 script compilation errors

Fixes 1 to 3 solve most cases and take a few minutes each. Fix 4 is for merges that need a decision from you. Fixes 5 and 6 restore a clean base and rebuild the mod list. Fixes 7 and 8 are the two official ways out: the older Classic version, or a clean install.

Fix 1. Remove or update the mod that the error lines name

2 to 5 minutesLow riskThe first Error lines carry the name of one mod folder in the square brackets.

The compiler prints the folder that each failing script was loaded from. When that folder is gone, the script is no longer part of the next compilation and the game uses its own copy of the file.

1. In the error window select Copy to Clipboard, open Notepad and press Ctrl + V.
2. Read the name in the square brackets on the first lines that start with Error. Leave the Warning lines aside for now.
3. Select Exit Application.
4. Open the game folder and then the Mods folder inside it. In Steam: right-click the game, select Properties, open Installed Files and select Browse.
5. Find the folder with the name from the brackets. The message prints it in lower case, the folder itself may use capitals.
6. Move that folder to a place outside the game folder, for example the desktop. Do not delete it yet.
7. If the mod's install instructions also had you copy a folder into DLC, move that folder out as well.
8. Start the game.
9. If it starts, look on the mod's page for a version made for your game version before you put the mod back.

• Tags on Nexus Mods. Mod pages carry the tags Remastered Compatible, Next-Gen Update Compatible or Next-Gen Update Incompatible. A page without the first tag says that the mod may only work with older versions of The Witcher 3.
• No updated version. The community guide on mod.io asks players not to test old script mods on the Remastered version. Leave the mod out until its author updates it.
• The mod came from the in-game Mods menu. Open Mods in the main menu, go to the Installed section and clear the mod's check box, or unsubscribe.

Fix 2. Clear outdated mods and Steam Workshop subscriptions after the Remastered update

5 to 10 minutesLow riskThe errors started right after the game updated to version 5.x, or you did not install any mods this time.

CD PROJEKT RED Support states that mods with script, XML or w3strings files do not work after the Remastered update. Players report that Steam installs their old Workshop subscriptions again with the update, which explains errors on a game that looks unmodded.

1. In your Steam library select the game and open Workshop.
2. Select Your Files, then Subscribed Items.
3. Select Unsubscribe From All and confirm with OK. To keep some mods, unsubscribe from the others one by one.
4. Restart Steam before you start the game.

1. Open the game folder and move the whole Mods folder to a place outside it, for example the desktop.
2. If you use Vortex or The Witcher 3 Mod Manager, disable the mods there as well, so the manager does not put them back.
3. Start the game. With no outdated scripts left it should reach the main menu.
4. Add mods again only when they are made for the Remastered version: from Mods in the main menu, or one at a time from Nexus Mods.

Players also report a switch for mods behind the gear icon of REDlauncher, the window that opens before the game. We could not confirm it in CD PROJEKT RED's documentation. If your launcher shows the switch, turning mods off is a quick test.

Fix 3. Delete old merges and merge again with a merger made for your game version

10 to 20 minutesLow riskThe brackets say mod0000_mergedfiles, or you use several script mods that change the same files.

A merge is a snapshot of your mods and your game version on the day it was made. After a game update or a mod update it holds old code, and the game loads the merged folder before every other mod.

1. Close the game. Open the game folder, then Mods, and delete the folder mod0000_MergedFiles. The Script Merger documentation names this as the way to undo all merges. Your mods are not changed by it.
2. Download the merger that matches your version from its own page and extract it into a new, empty folder.
3. Start WitcherScriptMerger.exe. Enter the game's folder in the box at the top (Witcher 3 Directory), or confirm the folder that the tool found.
4. Select Refresh above the Conflicts list.
5. Tick the versions of each file under the script conflicts and select Create Selected Merge. In the Fresh and Automated Edition, Create All Script Merges does this for every script conflict at once.
6. If the tool merges without questions, close it and start the game.
7. If KDiff3 opens, continue with Fix 4.

• A merge can succeed and still be wrong. The Vortex edition now warns before it merges a mod built for another game version. Its notes give an example: merging a Next-Gen copy of r4Player.ws onto a Remastered install loses 941 lines of the game's own code, and the result looks like a successful merge.
• Old mods are marked. The Fresh and Automated Edition checks for mods made for an older game version and shows them in amber. Before merging such a mod you can choose to leave it out.
• Not Mergeable is not an error. Textures, models and menus cannot be merged. The tool lists them so that you can see which mod wins.
• Do not mix mergers. Before you go back to the original Script Merger, delete mod0000_MergedFiles first. Otherwise it treats the other tool's merges as a mod of their own.

Fix 4. Solve the conflicts that Script Merger hands to KDiff3

10 to 30 minutesLow riskKDiff3 opens during a merge, or a merged file fails with a syntax error.

KDiff3 merges text and does not understand the code. Where two mods changed the same lines it cannot choose, and a wrong choice leaves a missing brace or a doubled line that the game reports as a syntax error.

1. Read the Conflicts box and select OK. It gives the total number of conflicts, how many were solved automatically and how many are unsolved.
2. Know the three columns. A is the base, the game's own file. B and C are the two mods. The window below them is the merged output.
3. Use the toolbar buttons that go to the previous and the next unsolved conflict. In the output, an unsolved place shows a question mark and the text <Merge Conflict>.
4. For each conflict select the toolbar button A, B or C. To keep the lines of both mods, select B and then C.
5. Look at the result in the output window. Every opening brace needs its closing brace, and no line should appear twice.
6. Save with File > Save. KDiff3 does not let you save until every conflict is solved.
7. Close KDiff3. Script Merger finishes the merge and shows its report.
8. Start the game.

The Script Merger documentation is plain about the limits: conflicts that KDiff3 solves by itself are not guaranteed to be correct.

Fix 5. Restore the game's own scripts with a file check

5 to 30 minutesLow riskEvery line says content0 and no mods are left, or you once copied the Unification Patch or Community Patch - Base over the game.

Both patches work by overwriting the base scripts in the folder content\content0\scripts, and their pages say they are not needed for the next-gen version. A file check compares the game's files with the originals and downloads the changed ones again.

1. Open the game's Mods folder and delete the folder mod0000____CompilationTrigger if it is there. It comes with the two patches and has four underscores in its name.
2. Delete mod0000_MergedFiles as well. Merges made against patched scripts do not fit the restored ones.
3. Run the file check in the launcher that installed the game. The steps for Steam follow.

1. Restart and open Steam. Restart your computer and launch Steam.
2. Open the game's menu. Right-click the game in your Library, or open the game's Library page and select the gear icon on the far right.
3. Open Properties. Select Properties in the menu.
4. Verify the files. Select the Installed Files tab and select Verify integrity of game files.
5. Wait for the result. Steam checks the game's files. This can take several minutes.

These steps were written for Steam on Windows. The full page with the other versions and what each result means: How to verify game files in Steam, Epic Games, Xbox app, EA app, Battle.net and GOG Galaxy

• GOG GALAXY: select the game, open the customization button next to Play, then Manage installation > Verify / Repair.
• Epic Games Launcher: find the game in your Library, select the three dots, then Manage and Verify.
• Steam says that files failed to verify. Valve calls this normal for most games: these are local configuration files that are not replaced.

On Classic 1.32 some mod lists still need Community Patch - Base. Its page says it stays required for the version before next-gen. Install it again by hand after the check, because the page warns that a mod manager installs only a dummy script.

Fix 6. Start from zero mods and add them back one at a time

30 to 60 minutesLow riskYou run many mods and the error lines do not point at a single one.

This is the method a moderator of the CD PROJEKT RED forum gave for this error. With one new mod per launch, the launch that fails names the mod that caused it.

1. Move the whole Mods folder out of the game folder and keep it as your archive.
2. Start the game once without mods to confirm that it runs. If it does not, do Fix 5 first.
3. Put back the first mod that contains scripts and start the game.
4. Put back the next mod. From the second mod on, run your script merger after each one and merge what it finds.
5. Start the game again.
6. When a launch fails, the mod you added last is the cause. Leave it out, or look for the right version or a compatibility patch.
7. Go on with the rest of the list in the same way.

• The wrong variant. The moderator's own list of causes includes mods that offer different versions for users of other, specific mods. Read the Files tab of the mod before you pick one.
• A missing requirement. A mod that needs another mod fails with "Could not find function". Install the requirements that its page lists, and only those.
• Shared Imports on the Remastered version. According to the community guide on mod.io it is now part of the game. Do not add the old modSharedImports folder to a 5.x install.

Fix 7. Go back to the Classic version if your mods were built for it

30 minutes or more, depending on the downloadRead the warningYour mod list was made for version 1.32 and has no Remastered versions yet.

CD PROJEKT RED keeps the Classic version available as a beta branch on Steam and GOG. Mods written for 1.32 then compile against the scripts they were made for, and the version mismatch is gone.

1. Steam: go to your Steam Library, right-click The Witcher 3: Wild Hunt and select Properties.
2. Go to BETAS and select CLASSIC. The game updates automatically.
3. GOG GALAXY: open the Installed section, select the game and select Manage Installation, then Configure…
4. Change Beta Channels to Classic.
5. Disable the auto-updates option, choose your preferred version and select OK.
6. Delete Mods\mod0000_MergedFiles and merge again with the original Script Merger, as in Fix 3.

• The way back. On Steam select None in the BETAS menu. On GOG select Disabled in the Beta Channels menu.
• Epic Games Store. The platform only provides the latest version, so this fix is not available there.
• Next-Gen 4.04. The support page names Classic only. We could not confirm an official way to return to version 4.04.
• Launch problems. Hotfix 5.00c of 1 October 2026 fixed an issue where the Classic (1.32) version could not be launched. Let the launcher update the game first if Classic does not start.

Fix 8. Do the clean install that CD PROJEKT RED Support describes

1 hour or moreRead the warningNothing else worked, or you want the state that Support asks for before a report.

For problems with third-party mods, CD PROJEKT RED Support asks for a clean install. It removes the two places where leftovers survive an ordinary uninstall: the game folder and the game's folder in Documents.

1. Copy the folder %userprofile%\Documents\The Witcher 3\gamesaves to another drive or an external device.
2. Turn off cloud saves for the game in your launcher, if they are on.
3. Uninstall the game in the launcher.
4. Delete The Witcher 3 folder that is left in the launcher's game directory.
5. Delete The Witcher 3 folder in %userprofile%\Documents.
6. Restart the PC.
7. Install the game again and add no mods. Support advises a short path on the drive root, for example C:\Steam\steamapps\common\The Witcher 3.
8. Start the game. If it runs, copy your saves into the new gamesaves folder.
9. Turn cloud saves back on if you want them.

A clean game that still shows the window is the one case that belongs to CD PROJEKT RED. Use the Contact us button on the Support site and include the copied text. Support asks for any information or error code that is displayed.

If the script compilation errors are still there: what to collect and whom to ask

The error window is its own log. No separate log file is needed to find the cause: the lines say which folder, which file and which line. What helpers need is that text, complete, together with a few facts about your install.

• The full text. Use Copy to Clipboard and paste the text. A photo or a cut-off screenshot hides the first lines, which matter most.
• Game version and launcher. For example: Remastered 5.01 on Steam, or Classic 1.32 on GOG.
• The folder names in Mods and DLC. A list of the names is enough.
• The merger you use and its version. Say whether mod0000_MergedFiles exists.
• Subscriptions. Say whether you have mods from Steam Workshop or from the in-game Mods menu.

• It is not hardware. The window lists text files that failed to compile. Nothing in the sources connects these lines with a graphics card, a driver or memory.
• The game does not start and shows no such window. That is a different problem. CD PROJEKT RED's page "Game is not launching" lists the graphics driver, the Microsoft Visual C++ packages and a clean boot: Update, roll back or reinstall a driver

How to keep script compilation errors from coming back

The longer view comes from CD PROJEKT RED itself. Its documentation tells mod authors to use script overrides, introduced with the game patch of 6 June 2024, so that players only need to care about priority. A mod written that way adds to a script without replacing the whole file. Until every mod works like this, one habit prevents most of the trouble: after any change to the game or to the mod list, merge again before you play.

Frequently asked questions

What do script compilation errors mean in The Witcher 3?

They mean the game could not turn its script files into a working program when it started. CD PROJEKT RED documents that the scripts, text files with the extension .ws, are compiled when the game starts. If one file contains code the compiler cannot read, or calls something that does not exist, the game lists the problems and stops before the main menu. CD PROJEKT RED's documentation names the usual reason: several mods edit the same files. Since the Remastered update, script mods written for older versions are the other big reason. Each line of the list names the folder, the file and the line.

Why do I get Witcher 3 script compilation errors with no mods installed?

Because something is still feeding old scripts to the game. Players report that Steam installs Workshop mods they subscribed to long ago when the game updates or is installed fresh. A Mods folder from an earlier install can also survive: CD PROJEKT RED's clean install deletes the game folder by hand after the uninstall for that reason. A third case is a game whose base scripts were once overwritten by the Unification Patch or Community Patch - Base. Unsubscribe on the game's Workshop page, move the Mods folder out and run the file check of your launcher. If the window still appears, do the clean install from CD PROJEKT RED Support.

Why did the script compilation errors start after the Remastered update?

Because the update changed what script mods are built on. CD PROJEKT RED Support says that mods containing XML files, script files or w3strings do not work upon the release of the update. The community guide on the game's mod.io hub lists the changes: text files moved from UTF-16 to UTF-8 and the script language received new built-in types. The page of one merger adds that a mod made for 4.04 replaces the game's own scripts and takes out what the Remastered version changed in them. Remove such mods and install only versions marked for the Remastered version. Texture and model mods are not affected.

Which Script Merger works with The Witcher 3 Remastered?

Three mergers state support for version 5.x as of 14 October 2026. Script Merger - Remastered on Nexus Mods is tagged Remastered Compatible. Script Merger - Fresh and Automated Edition 1.0.0 lists Remastered, Next-Gen and Classic. The Vortex edition 0.7.0 on GitHub names support for Witcher 3 5.0 in its release notes. The original Script Merger 0.6.5 is not among them: its own page says it cannot be used for the Remastered version, because all files changed from UTF-16 to UTF-8. Whichever tool you choose, delete the folder mod0000_MergedFiles first and create the merges again.

How do I resolve conflicts in Witcher 3 Script Merger?

Select Refresh, tick the versions of a file and create the merge. Most conflicts merge by themselves. When two mods changed the same lines, KDiff3 opens with three columns: A is the game's file, B and C are the mods. Go to each unsolved conflict and select the toolbar button A, B or C, or B and then C to keep both mods' lines. Check that the braces still match, then save. KDiff3 does not allow saving before every conflict is solved. If you cannot judge a conflict, close KDiff3 without saving and remove one of the two mods.

Do I still need the Unification Patch or Community Patch - Base?

Not on the Next-Gen or Remastered versions. The Unification Patch is marked obsolete on its page, which states that you do not need it for the next gen (4.0+) version of the game. Community Patch - Base replaced it for Classic 1.32, and its page says the patch is no longer required for the next gen version while it stays required for the version before it. Both patches overwrite the game's base scripts, so copying them over a newer game is a known way to produce this error. If you did that, run the file check of your launcher.

What does content0 mean in a Witcher 3 script compilation error?

It is the name of the game's own base content. Lines marked content0 point at scripts in the folder content\content0\scripts inside the game folder, not at a mod. That does not prove the game files are damaged. The game loads only one copy of each script, so an outdated mod that replaces one file can make an untouched game file fail, because the two no longer fit together. Take your mods out first. Only when the Mods folder is empty and no subscriptions are left is the file check of your launcher the right step.

Can I ignore the Warning lines in the script compilation window?

Treat them as the second priority. In the reports we read, lines that start with Warning are listed after the errors, for example the ones that say a function was not exported from C++ code. We found no CD PROJEKT RED page that explains these warnings or says that they stop the game. What the reports show is that the window appears together with lines that start with Error. Solve those first, in the order they are listed. If only warnings remain and the game still does not start, copy the text and ask on the page of the mod that is named.

Will I lose my saves when I remove mods or reinstall the game?

Your saves are kept in %userprofile%\Documents\The Witcher 3\gamesaves, outside the game folder, so removing mods or uninstalling the game does not delete them. The clean install from CD PROJEKT RED Support does delete the Documents folder of the game, which is why its first step is a backup of the saves. One more caution comes from Support: the consequences of mod usage may be kept in save files, and you might need to load an earlier save from before the mod. A save that depends on a removed mod may not behave as before.