Ctrlk
HomeDiscordGitHubEdit
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Troubleshooting

If your mods are causing trouble, here's what you can do

Summary

Last documented update: January 20th, 2026 by minnierylands

This page contains troubleshooting information for people who are using mods. You will find step-by-step guides, grouped by different problems.

Before you get lost in error messages and log files, you should check Troubleshooting - First Steps - you might get lucky with an easy fix!

To save you from scrolling through the entire page, check the list on the right side of the page to find the section you need!

Did you know? You can press Ctrl + F on your keyboard to quickly find your problem on the page – simply type a word from your error message or related to your issue.

Cover

Need a hand?

Join us on Discord in #mod-troubleshooting!

Interactive Guide

Use the interactive guide below to quickly figure out your problems. Can't guarantee that it'll give an immediate fix, but it'll point you in the right direction!

Need the guide to be bigger? Open it in a new window!

spinner

Troubleshooting - First Steps

Before you start debugging, make sure that

  • Your graphics driver is up-to-date

  • Your Windows is up-to-date (no, really) and that you are at least on Windows 10

  • You have the most recent version of .NET Desktop Runtime installed

  • You have Visual C++ Redistributable 2022 installed (direct download, Microsoft)

  • Your game is running from an SSD (Solid State Disk) rather than a HDD

  • If you have an Intel i7 or i9, and your game is randomly crashing, check this forum post. If that doesn't help, read on.

1

Update All Your Mods

Mods receive updates regularly. The easiest way to keep on top of potential errors is keeping them all updated. Even if you're sure you have the latest version, re-download them.

If a mod hasn't been updated in a long time and keeps throwing errors, you may just have to live without it, or politely drop the mod author a comment on Nexus. Modding is a hobby, and sometimes mod authors move on from modding games.

Also keep in mind that many mods, especially core mods and script mods, are prone to breaking with every update, or are waiting for its dependencies to be updated first.

The most important ones are the core mods. Not sure what they are? Here's a list:

You can click the "Track" button on Nexus to get a notification when a mod gets updated. If you use a mod manager (which you should), you can click "check for updates". Even easier!

2

Update Your Game

Core mod makers update their mods to work with the latest game version, and do not offer support for the old versions.

If you previously downgraded your game or prevented auto-updates, you need to reverse this.

3

Don't Use Collections

Collections require constant upkeep, and most collection makers just don't do that.

You can use collections as a reference list, though. Just download the mods you want individually; that way you definitely have the latest versions of them all.

Collections will download the version of a mod that the collection author added. That may have been the latest version of the mods one year ago, but if they aren't constantly updating the collection every time a mod updates, they very quickly become outdated.

4

Read Mod Descriptions

Most mods will tell you exactly what a mod does, how to use it, how to install, uninstall, and use them. A lot of them will even tell you exactly which other mods you can or cannot use at the same time.

90% of the time, you can save yourself some time (and potentially some embarrassing Nexus comments) by just reading the mod descriptions.

It's also worth checking a mod's comments section. Chances are, if it's an issue with the mod itself, users have already reported issues!

5

Download Mod Requirements

Most mods will rely on other mods to work. If you're unsure why a mod isn't working, check that you have the mods it requires first.

On each mod page, make sure you actually look in the Requirements tab; don't just rely on mods giving you a pop-up before you download it.

Not only do mod authors have the option to disable this pop-up, but sometimes you might be downloading a load of mods you don't actually need.

These are the mods for Virtual Atelier.

To learn more about requirements, have a look at this page.

6

Remove Cybercmd

If you're using any REDmods, you've probably been told to download cybercmd. Likelihood is, you've also downloaded RED4ext.

These two cannot be used together, and cybercmd should be removed.

Ever since RED4ext version 1.13 (which was uploaded in May 2023!), you do not need cybercmd, as the functionality was added to RED4ext.

Even the cybercmd mod page says "recent versions of RED4ext provide the same functionality as cybercmd". Just remove it, I promise you don't need it.

7

Disable All Your Mods

If your game is crashing during gameplay, you'll need to check Game Crashes During Gameplay or Bisecting

Tried all of the above and still run into issues? Disabling all mods and launching your game can establish if the issue is caused by mods. If the issue still persists without any mods enabled, it's an issue with your game.

If your game crashes on startup, disable all your mods.

But how do I do that?

If you're using Vortex: Press CTRL + A on your keyboard, then click Disable at the bottom of Vortex. You can also press the Purge button at the top. If you want to be extra sure, do both.

If you're using MO2: Press CTRL + A on your keyboard, right mouse click, and then click Disable Selected

If you're manually installing (or want to be extra sure after disabling in your mod manager): Check out the Mod Remover

If you're dealing with a glitch or bug, and you're pretty sure it's caused by mods, disable everything apart from core mods.

If you're loading a save that was created with New Game Plus - Native, keep it enabled.

If you're loading a save that had a weather mod active such as Nova City 2 or Enhanced Weather, you should reset the weather state to vanilla before disabling them.

8

You Pirated The Game

There's a >95% chance we already found the source of your problems — pirated copies just don't mod well.

CDPR needs to earn money to pay people to make games. If you can afford it, please buy the game.

You're welcome to read through the troubleshooting guide - it might even help you. But know that pirated copies will never be explicitly supported.

Specific Troubleshooting Tips

I'm On Linux/Steam Deck

I'm playing the game on macOS

TL;DR: modding on Mac natively is in the very early stages, and there are very few mods available to use.

I'm Using Vortex

  • You need to make sure the "Automatically convert legacy-style ".archive" mods to REDmods on install (NOT recommended)" toggle is off. This is under V2077 in Settings. If it was enabled, check here for what to do.

I'm Using MO2

  • You need to make sure you always run the game through MO2.

  • You also need to make sure you have Cyber Engine Tweaks and RED4ext manually installed, or follow this guide to properly set up the script extender plugin.

Whoa! Cyberpunk 2077 Has Flatlined.

By far the most common way your game will crash.

This popup looks useful, but it's not great for figuring out what caused your game to crash.

That doesn't mean we can't get anything out of it. You can click "What does this report contain?", which will bring you to a folder.

This is where the game's crash logs live. Open the stacktrace.txt in this folder. It might seem like nonsense, but it can sometimes be a good starting point.

But what do they all mean?!

Below you'll see "meanings" listed for each error. Some of these are just the most common causes for the error, and not necessarily the inner workings of what they mean!

EXCEPTION_ACCESS_VIOLATION

  • The game tried to access information that it can't read. Usually signifies a broken mod file.

Detected integer overflow

  • Something is causing the game to allocate a larger memory buffer than it actually can.

Gpu Crash

  • Your GPU is struggling to run the game.

Watchdog Timeout!

  • The game took to long to load something, and timed out.

A watchdog is a background process (daemon!) to keep an eye up for crashes. If the application it's watching hasn't responded after time interval X, the watchdog will assume that it died, and cause a crash. This prevents quiet crashes in the background.

Error Listed
Solution

EXCEPTION_ACCESS_VIOLATION

(This may also say 'The thread attempted to read inaccessible data at 0x000000')

Bisect your mods

Detected integer overflow

Bisect your mods

Gpu Crash

Make sure your PC meets the minimum specs to run Cyberpunk 2077 (yes, really).

Try disabling any graphics mods you have, as well as external programs such as ReShade.

If the game opens but cannot load a save, try lowering graphics settings in the main menu.

If you still get this crash, disable all your mods.

If this fixes the issue, try again with just core mods enabled.

If it's still launching fine, re-enable your mods in batches until the game cries.

If it still crashes in an unmodded state, you may need to update your graphics drivers. You can find more information on that here.

Watchdog Timeout!

Bisect your mods.

If you still get the error, keep reading:

If the game doesn't even launch, check your antivirus. Make sure that you have an exception for the Cyberpunk 2077 game directory (guide on rackspace)

If it happens in photomode, turn down your graphics settings, or try disabling your photo mode mods.

If the error is absolutely persistent and you're sure you've tried everything, you can try increasing the Watchdog Timeout.

Increasing the Watchdog Timeout

The below should be a last resort, and is geared towards people who have crashes while trying to render screenshots taken in photo mode.

There may be an easier fix before you reach this point!

If you are dead-set on that photo, you can try increasing the watchdog timeout to give the game more time. Open the following file with a text editor (create it if it doesn't exist):

... and add the following lines (original source):

This will set the timeout to something over 2 hours, and should hopefully be long enough to render that screenshot for you.

The Game Doesn't Launch

... And You Get a Pop-up

ValidateScripts.cpp:44 / codeware.global.reds

It might look a little different, but it will always have this error somewhere.

To fix this:

  1. Navigate to Cyberpunk 2077\r6\ and delete the entire cache folder (Yes, the whole folder)

  2. Verify your game in the store you bought it from (GOG/Steam/Epic)

  3. To be extra safe, reinstall redscript

RED4ext Error 1114 - A dynamic link library (DLL) initialization routine failed

The first part of the file path will be the drive you have Cyberpunk 2077 installed on

To fix this, you need to download Visual C++ Redistributable 2022 (direct download, Microsoft)

Download and run the executable file linked above, then restart your computer. If you already have it downloaded, or it doesn't work the first time, you need to open the file again, click Repair, then restart your computer.

You have to restart your computer after installing/repairing. It can take several repairs for it to work. Blame Microsoft!

Redscript Compilation Error

Redscript is quite good at telling you where to look for issues, but the mods it lists may not actually be the problem. Confused? Don't worry! We're going to get through this together.

You may only have one mod listed here, or an even longer list

Redscript Log

The pop-up mentions consulting the logs for more information. It can be helpful to double check if you have duplicate files, making sure you have script files for specific mods, or just for reference.

You can find the redscript log here: r6/logs/redscript_rCURRENT.log

Common Errors and Quick Fixes

All of the mods listed are atelier stores

  • You don't have Virtual Atelier installed. Install it, and all of its requirements too.

  • You did install Virtual Atelier, but it's missing script files. Reinstall it. If you're not sure, reinstall it anyway.

  • You have an old version of Virtual Atelier installed. If there's log entries for virtual-atelier and virtual-atelier-full, remove all Virtual Atelier files and redownload the newest version.

There's only one mod listed

  • Check your log to make sure it's not installed twice. Sometimes mod authors change their folder structure, causing a duplicate file. Remove both versions and redownload the latest version.

You have cybercmd installed

  • Uninstall it

Clearing the Redscript Cache

Sometimes, the cache goes stale. Thankfully, it's an easy fix. If you're really at a loss for your redscript compilation error, try this first.

This is where your redscript cache lives!

  • Navigate to Cyberpunk 2077\r6\ and delete the entire cache folder (Yes, the whole folder)

  • Verify your game in the store you bought it from (GOG/Steam/Epic)

  • Reinstall redscript

Still Getting Compilation Errors?

One of your redscript-dependent mods might be causing issues. This could mean you're using two mods that are not compatible with each other, or you're using an old mod that needs an update.

But how do you figure out which one it is?

If you're using a mod manager, you can pull up your redscript_rCURRENT.log to check which of your mods rely on redscript and just bisect those.

If you're manually installing, you'll find all your redscript mods in Cyberpunk 2077/r6/scripts

It Still Doesn't Compile

Launch the game with only the core mods.

If the game launches, the issue definitely lies with one of your other mods. You need to bisect your mods.

Still. Doesn't. Compile.

It might be time to start afresh. Try running Mod Remover and start re-modding your game from scratch. If you're using a mod manager, disable/purge your mods there first before running the Mod Remover.

If you've been manually installing your mods, please consider using a mod manager going forward. It's far less error prone, and makes troubleshooting your mods way easier.

Failed to resolve address for hash

The numbers after 0x may be different, but the advice below applies to them all

To fix this:

  1. Update/Buy the game

Core mods will not work on outdated/pirated copies of the game.

  1. Update your core mods - you can find links to all of them here

  2. If you are a mod dev, update RedHotTools

Corrupted Or Missing Archives

This error means "bisect your mods"

If you get an error message that says Cyberpunk 2077 encountered an error caused by corrupted or missing archives and and will now be forced to close, you have a broken .archive file and need to bisect your mods.

Corrupted Or Missing Scripts

If you're here because you used Mod Remover and didn't verify your game, you need to read the instructions thoroughly

If you get an error message that says Cyberpunk 2077 encountered an error caused by a corrupted or missing scripts file and and will now be forced to close, you need to verify your game in your launcher (GOG/Steam/Epic).

Not sure how to verify your game files? Click here!

To make sure it's really verifying, you can try running the Mod Remover (don't worry, it creates a backup of all your files!)

If you don't want to do that, here's a more hands-on method

Unless you back up your mods and scripts, all your settings and manually installed mods will be lost.

Rename or remove the following folders, then verify your game:

If you do not have them, you don't need to do anything.

If you just want to reinstall the game

Consider just using Mod Remover. It will reset your game to an unmodded state.

If you're set on reinstalling completely, you can find a full reinstall guide on CDPR's support page.

Corrupted Or Incomplete Game Data

This error has a few possible fixes

If you get an error message that says Cyberpunk 2077 encountered an error caused by corrupted or incomplete game data, check below for some potential solutions:

Workaround Suggested By CDPR

  • Set Power Limit (TJ max) for CPU to 150W

  • Reduce Long and Short Duration Package Power Limit to 150 W (Intel default is 253)

  • Set the maximum CPU Core Temperature to 98°

  • Reduce the P-Core ratio of the processor

  • Deactivate Turbo Boost of the CPU

  • Disable CPU Hyper-Threading

Or check Reddit:

Run Without Antivirus

  • Turn off your antivirus and your firewall - anything that counts as "System Protection".

    • Yes, that includes Windows Defender

Yes, all of it. That includes your computer's bodyguard if it has one.

  • Now, start the game.

  • If the error persists, verify game files through your launcher (GOG/Steam/Epic)

  • Start the game again

If it works now, you need to find out how to keep your antivirus away from your game directory. If it doesn't, then you can turn the stuff back on now.

Run As Admin

Generally, you'll be told not to run the game as admin! Only try this if nothing else works!

Configure the REDprelauncher.exe in the Cyberpunk root directory to always run as administrator.

  • Right-click on the file and select Properties

  • Switch to the Compatibility tab

  • Check the box Run this program as an administrator

It should look a little like this!

Files / Permissions Errors

There's a few different pop-ups relating to file errors. These are caused by access errors – Cyberpunk is trying to read or write a file, and for some reason, it can't. Check below for some potential solutions.

These errors may look like the following:

  • Access is denied

  • Can't access file 'FILENAME'

  • Could not move file from 'file\path\file\path.tmp' to 'path\Cyberpunk 2077\subdir\name.file'

  • An exception occurred while creating the logger

You may also see 'EXCEPTION_ACCESS_VIOLATION' or 'The thread attempted to read inaccessible data at 0x000000' (numbers may differ). If you have already tried the fixes listed above for these errors, keep reading.

Make sure that the file path exists

  • If Cyberpunk is trying to move files to a subdirectory that it can't access, make sure the directory actually exists. If it doesn't, create it.

  • The most frequent candidate for this is /r6/cache/modded

You can ignore this if there's no file path in your error.

Make sure that no previous game instance is running

  • Sometimes, the game doesn't shut down properly and still runs in the background. You can check this - and also actually close the game process - through the task manager.

How to end the game's process in task manager

  • Press CTRL + SHIFT + ESC on your keyboard to open your task manager

  • Switch to the Details tab

  • Sort by Name and scroll to C

  • Check if you can see anything Cyberpunk in the list.

  • If yes, right-click on it and select End Task

Reboot your PC

  • If in doubt, you can just reboot your computer. It's a good idea to do this sometimes – in this case, it could make the error go away.

Make sure that all files in the game directory are writable

  • Sometimes, files in your game directory are set to read-only. You can fix this either via Windows Explorer or via system console, the results will be the same. Check below to see how.

Windows Explorer

  • Navigate to the Cyberpunk 2077 game directory and right-click on it

  • Select Properties (the last entry in the drop-down menu)

  • Uncheck the "Read-only" box

After unchecking and applying changes, the box will jump back to maybe-checked. That's because Windows can't tell if the folder contains read-only files. However, since you just made sure that it doesn't, you can ignore this.

System Console

  • Press Windows + R on your keyboard

  • type cmd and press Return to open the command line

  • run the following command (replace the path with your actual game directory):

Failed To Initialize Script Data

If you get this error check your NVidia Control Panel. If power saving options are enabled, turn them off.

If you don't have them enabled, check for other power config options in your operating system.

This is where the setting will be in the NVidia Control Panel

... And You Don't Get Pop-up

The game isn't launching and doesn't even give you an error. How are you supposed to troubleshoot that?! Thankfully, there's a few things to try before diving into the deep end.

Stop! Check the following first:

  • Make sure all your mods are updated. Yes, all of them.

  • If you're using RED4ext, uninstall cybercmd

  • If you're using any FrameGen/DLSS/FSR mods, like OptiScaler, remove them

  • If you're using any external programs like ReShade, remove them

  • If you're on Linux, double-check the launch options. Steam sometimes resets these between updates.

Check Your RED4ext Log

To find out more about log files, take a look here!

Find the folder Cyberpunk 2077/red4ext/log. Check for a file named red4ext-0000-00-00-00-00-00.log - the numbers will look different for every log. Sort your files by Date Modified and open the most recent one.

If you don't have a log here, RED4Ext is not installed correctly. You need to fix this before troubleshooting further.

If you're manually installing:

If you're using MO2:

What Am I Looking At?

If you get one of these errors, check here to see what to do!

  • Message: Watchdog timeout! (120 seconds)

  • Message: Gpu Crash for unknown reasons!

Press CTRL + F on your keyboard and search for error. Sometimes, there will be an error that tells you what's wrong. Some tell you the exact issue, such as:

[error] To use this version of RED4ext, ensure your game is updated to patch __ or newer

This means you need to update/buy the game!

Sometimes, the error is a little less specific. If you see the following error, you need to go back to the start of the troubleshooting guide and start from step 1:

[error] Could not attach the hook for the main function. Detour error code: 6

I Don't Have Errors, I Have Warnings

If your log has no errors, but you have lines that say warning, it's usually warning you about a specific mod. You can try reinstalling the mod it's complaining about, but if it still throws the same warning, it may not be compatible with the current version of the game.

If your warning says scc invocation failed with an error: REDScript compilation has failed, you need to check here instead.

My Log Doesn't Have Either

If your RED4ext log has no errors or warnings, it's worth checking where your log ends.

The bottom of your RED4ext log should always look something like this:

[RED4ext] [info] _ plugin(s) loaded [RED4ext] [info] RED4ext has been started [RED4ext] [info] Scripts BLOB is set to 'Your:\Drive\Cyberpunk 2077\r6\cache\modded\final.redscripts' [RED4ext] [info] scc invoked successfully, 22077 source refs were registered [RED4ext] [info] Scripts blob path was updated to 'Your:\Drive\Cyberpunk 2077\r6\cache\modded\final.redscripts.modded'

If your log doesn't have this, but the last line says something like:

Loading plugin from 'Your:\Drive\Cyberpunk 2077\red4ext\plugins\ModFolder\ModName.dll'...

Your game is dying before it's able to load that mod. Make sure you have the latest version of that mod. If it's not a core mod, remove it. If your game now launches, you may have to wait for it to be updated, or live without it.

If your log doesn't have this line:

scc invoked successfully

Redscript is not being called. To fix:

  • Navigate to Cyberpunk 2077\r6\ and delete the entire cache folder (Yes, the whole folder)

  • Verify your game in the store you bought it from (GOG/Steam/Epic)

  • Reinstall redscript

Disable Your Mods

This is an easy way to check if the issue is mod-related or not. Disable all your mods and try launching the game. If it launches, the problem lies within your mods somewhere. If not, the problem is with your game itself.

  • If you're using a mod manager, disable/purge your mods there. If you want to be extra cautious, you can also try the below

  • If you're manually installing, run the Mod Remover

If your game launches now, we know the issue is mod-related.

If it still doesn't launch, you should try this next (VERIFYING FILES LINK)

I Disabled My Mods, Now What?

Do a fresh reinstall of all the core mods, then run the game. Hopefully, your game now launches. Now, you can either start modding the game again from scratch, or reinstall them and bisect your mods.

This is a lot easier to do with a mod manager.

The Game Crashes Before the Menu

Your game launches, but crashes before you make it to the menu. Sometimes you'll get an error for this, sometimes you won't. Don't worry, there's a few things you can do in either case!

If you get a "Whoa! Cyberpunk 2077 has flatlined" pop-up, check here first!

... And Doesn't Give An Error!

If you haven't already, try these steps first before doing anything else. They're there for a reason.

Most likely culprit is a mod. Unfortunately, there's no magic way to tell which one it is. You're going to have to bisect your mods to find the issue.

To make sure, you can disable every mod you have installed apart from the following:

You can disable these mods one by one to narrow down what type of mod is causing your game to crash.

Example: If you disable ArchiveXL and the game launches fine, a mod that relies on ArchiveXL is broken.

You can check here to see where each type of mods are kept on your computer

If your game launches, the problem lies in your mods somewhere.

If it still doesn't launch, it's Mod Remover time.

... And Says Missing TweakDB File / Inaccessible Memory

This error was common when 2.0 and Phantom Liberty launched

If you run into this error:

Or if the game complains about attempting to read inaccessible memory, do this:

  1. Navigate to your game directory and find the folderr6\cache

  2. Find the file tweakDB.bin and copy it (Press Ctrl + C on your keyboard)

  3. In r6\cache, find the folder modded

    • If it doesn't exist, create it!

  4. Paste tweakDB.bin here (Press Ctrl + V on your keyboard)

  5. If asked to overwrite, select Yes

  6. If you have Phantom Liberty, repeat the process with tweakdb_ep1.bin

That didn't fix anything!

If that doesn't fix it, your problem most likely related to Cyber Engine Tweaks. Try disabling it.

If you have it installed with a mod manager

  • Disable it in your mod manager

If you have it installed manually

  • Find the folder Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks and move it out of plugins (e.g. put it on your desktop)

If you'd rather delete it, make a copy of your mods and plugins directories. They contain your mod settings.

Check if the problem is gone.

If it is, put the folder back and bisect your CET mods. You can find these in:

  • cyber_engine_tweaks\mods

  • cyber_engine_tweaks\scripts

If you're using a mod manager, bisect through your mod manager and use the folders to check which mods you should be looking for

Game Crashes Loading a Save

Your game launches fine, the menu loads, but you can't load your save. Don't panic! It probably isn't lost forever.

If you're reinstalling your mods, or you're in the process of bisecting, check below. It's always good to keep in mind that:

If you're loading a save that was created with New Game Plus - Native, you need to keep it enabled.

If you're loading a save that had a weather mod active such as Nova City 2 or Enhanced Weather, you should reset the weather state to vanilla before disabling them. If you can't do that because you can't load the save regardless, re-enable it until you can.

Where To Start?

It's frustrating to diagnose a crash with no information. If you're sure none of the above applies to your game, try these steps next:

  1. Try starting a new save

If this works, there's one more thing we can do to see if your save is truly lost

  1. Go back to the main menu and try loading an older save from the same playthrough

If that doesn't work, you can also try loading a different playthrough if you have one, just to be really sure

It's a Broken Mod

Vague, right? Unfortunately, that's the most likely reason for your crash. It's time to bisect your mods.

If you want the nucelar option, run the Mod Remover. If you had any of the following mods enabled on your save, reinstall them and their requirements to see if you can now load the save:

If you've done all this and still can't load your save, check the next section for a potential reason.

Corrupt-ish Saves

You only need to read this if you can start a new game without mods, but crash on loading a previous save game.

Some mods store data in save files. Removing those mods may lead to your save game crashing until you install them again.

If you messed with any quest flags, or played around too much with the Save Editor, let this be a lesson in never doing that again. Quest flags can and will break your game if you mess with them, and the Save Editor is no longer supported.

This is commonly seen with the following mods:

  • New Game Plus - Native

    • You cannot load a save that was made with this mod without this mod enabled

  • Weather mods that have custom weather states such as Nova City 2 or Enhanced Weather

    • These mods allow for custom weather states. If you saved while one of these custom states was active, the game is trying to load something that doesn't exist. The weather needs to be one available in the vanilla game before it can load without these mods.

  • Immersive Rippers

    • If you remove Immersive Rippers, you need to save more than 100m away from a Ripperdoc before uninstalling the mod. From the mod page itself:

Make sure you save away from a Ripper (+100m should be plenty) And then delete the ImmersiveRippers.archive file from the "Cyberpunk 2077\archive\pc\mod" folder.

If your save won't load no matter what you try, I'm sorry. It might just be time to start a new save.

Game Crashes During Gameplay

You were just about to wipe out a bunch of Scavs, or you were just driving around the city, and your game crashed out of nowhere. Keep reading to find out what to do.

If you get a "Whoa! Cyberpunk 2077 has flatlined" pop-up, check here first!

Known Issues

Material and Texture Override (MTO)

This is the old version of MTO

TL;DR: There is a new version of this mod. If you actually need this mod, you can download the updated version here.

This tends to make the game crash somewhere in Japantown because of a mesh with a broken material. Material and Texture Override removes the cache and forces the game to re-create this material, making the game crash.

MTO is a well made mod, and the crashing issue is an edge case. This is not a guaranteed fix to any crashing you might have, but removing it is something worth trying if this sounds like your issue.

Many mods list MTO as a dependency, but it's usually optional. You only need it to force changes to original game materials.

As of 24 October 2025, a separate updated version has been uploaded. If a mod lists MTO has a hard requirement (not an optional one!), try this one instead.

This is the new version of MTO

Too Many Mods!

Yes, seriously, too many mods. This number seems pretty random, but generally doesn't start below 460.

The solution? Toggle off Enable Analytics in settings:

... And The Crash Is Easily Replicated

You're lucky - you can easily troubleshoot this. You need to bisect your mods, and see if it crashes at the same point with each set of mods. You'll know when you've found the issue because it won't crash anymore, yippee!

If you're manually installing your mods, start with your .archive mods. If that doesn't fix it, continue bisecting the rest.

Keep in mind that bisecting is a lot easier when using a mod manager, and it's never too late to start!

... And The Crash Is Completely Random

The most annoying type of crash, and unfortunately much harder to diagnose. A lot of long-time players just deal with the game crashing sometimes, like when tabbing in and out of the game occasionally.

If you can't deal with the crashes, you'll have to put in some work. There's a few options:

Game Starts, Mods Are Broken

If you've tried solutions from this page and still no luck, find us on Discord in #mod-troubleshooting.

Your game starts, but something is broken. Maybe a menu doesn't look right, maybe all the game sound is missing, maybe something else entirely.

While it's difficult to write troubleshooting for every possible thing that can go wrong with your mods, there will be a few common issues below.

External programs can cause issues. Rule it out by deactivating them while you're debugging.

These include things like:

  • Antivirus

  • ReShade

  • Hotsampling programs

FrameGen/DLSS/FSR files can also cause issues. Remove them before continuing.

If your issue is not listed here, or any of the above sections, you need to bisect your mods.

Common Issues

Have a look below to see if your issue is listed here. If not, you'll need to head on to the next section.

If you try a fix for your issue below and it doesn't make a difference, you need to bisect your mods.

Above all else, please make sure to read the descriptions of mods. They usually have install instructions and tell you exactly what you need to do to make everything work.

Did you know? You can press Ctrl + F on your keyboard to quickly find your problem on the page – simply type a word from your error message or related to your issue.

Cyber Engine Tweaks Isn't Working

Cyber Engine Tweaks needs at least VisualC 14.40.33810.0 - you can download it from the official Microsoft website (direct link)

To check if it's working, navigate to Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks

  • If there's a file called cyber_engine_tweaks.log in this folder, CET is running

  • If there isn't, you may need to redownload VisualC from the link above and click Repair when you run the file.

You need to restart your PC whenever you download/repair VisualC!

Some users may find they need to repair it multiple times before it works. Blame Microsoft!

I Forgot My Cyber Engine Tweaks Keybind

Delete the file Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\bindings.json.

The game should let you bind a new key at the next startup.

You can find more troubleshooting help for Cyber Engine Tweaks in the corresponding wiki: Cyber Engine Tweaks -> Troubleshooting

Your Icons Are A Jumbled Mess

You have an old version of a mod that interacts with icons in some way. If you have any of the following mods, you need to update them:

If you don't have any of the mods listed above, you need to bisect your mods to find the issue.

If you manually installed your mods, start in archive\pc\mod. Your issue likely lies there.

Your Icons Are Missing / Blank

  • Reinstall ArchiveXL

  • Reinstall the mod that is missing icons

V's Skin Texture Is Broken / Shiny / Striped / Messed Up

  • Exit out to the main menu.

  • Open the settings and set your Textures to High

V Is All Grey

  • If you are a VTK user, tattoos 6 and 7 are not available for your V and show as grey-ish blue. Sorry!

  • Make sure you only have KSUV or VTK, not both!

  • Make sure you only have one tattoo mod

    • If you do, make sure it's compatible with the body mod you have

  • Make sure you don't have multiple skin texture mods

V's Eyes Are Grey / Black / Missing / Sunken In

There is a newer mod called Unique Eyes to CCXL, which adds the eye colours to the bottom of the eye colours instead of replacing any of them. Try this one instead!

  • If you have both versions of Unique Eyes, remove the older one.

  • If you have multiple eye replacer mods, choose one. You can't have multiple.

  • If you have Unique Eyes - Core - 2.2 - Temporary Update Mod but no compatible eye mods, you need to download one. Unique Eyes Core does not add any eye textures.

  • If you just uninstalled an eye mod, try redownloading it and then swapping to a vanilla eye colour before uninstalling again.

V Clips Through All Their Clothes

You need to check that you:

  • Are not using a Spawn0 mod

  • Only have one body framework installed (VTK or KSUV, not both)

  • Only have one body mod installed

If you are using a VTK-based body, chances are you only need the VTK head file

  • Only have one rig installed

  • Have the correct clothing refits for the body you're using

If the clipping is minimal, it may just be the mod itself. Mod authors need to manually fix Garment Support on their clothing mods. If it tends to happen when you're posing V in Photo Mode, that's just something that happens. Try a clever camera angle, or a different piece of clothing.

V Is Missing A Body Part

  • Try a different piece of clothing - if the issue goes away, the clothing may not be compatible with the player body/your body mod.

  • Try installing JB - FPP Nude Patch (yep, seriously)

  • Check you don't have multiple mods affecting the same part of your V (two tattoo mods, two cyberarms mods). If you do, remove one.

  • If it's V's face, make sure you have the correct EKT / EKT Asian to work with other mods you have downloaded

V Has A Neck Seam / Different Coloured Head

You need to make sure you

  • Have the correct files and requirements for your body mod

    • If you are using a VTK body, you usually only need the VTK head file from the framework page

  • If you're using a skin tone mod like Universal Skin Texture, make sure you have the corresponding head file

Sometimes, this is just a part of using a body mod. Players have reported this happening with Solo Body 2.0, and the "Max Muscle Normal Texture (No Veins)" file has a similar neck seam

V's Wearing Clothes But Still Naked

  1. Go to the vanilla wardrobe in your apartment

  2. Create an outfit (anything will do)

  3. Equip the outfit

  4. Un-equip the outfit

  5. Save and reload

If this happens in first person perspective (and you're using Equipment-Ex):

  1. Remove all Equipment-EX outfits by typing EquipmentEx.DeleteAllOutfits() in CET's console.

  2. Save and quit the game

  3. Uninstall all files related to Equipment-EX

If you're installing mods manually, this can be done by searching for EquipmentEx in the game's main directory, then launch the game.

  1. You should now no longer be naked.

  2. Reinstall EquipmentEx and start creating outfits again.

The Clothes I Just Downloaded Are All Purple

You are missing a dependency for the mod. Check again, and make sure to download it.

One Of Your Mods Isn't Loading / Triggering

Double check the mod description. Many of them have conditions to activate the mod, with the most common one being entering V's H10 apartment.

You're Trying To Get Biosculpted Exotics To Work

If you want to use Biosculpted Exotics, you should try using Biosculpted Exotics Expanded instead. Be aware that the updated version may still have its own quirks, but it is actively maintained.

You're Having Audio Issues

Make sure all your mods that could mess with audio have been updated since the 2.3 update. This update messed with a lot of audio mods, and they all needed to be updated.

If your CPU is too busy, the game will try to save resources by dropping audio, starting with dialogue audio. Disabling spatial audio from the main menu might help

The setting you need to disable!
You Get LocKey# Messages

If this is happening to an ArchiveXL item addition, such as clothing or weapons, try reinstalling ArchiveXL, and also the affected mod.

If it's happening to the journal, quests, text messages, or shards

And you're playing in a language other than English

  • The mod may not include translation files for your language. Check if there is a translated version, or change the game language to English.

And you're playing in English

  • Most likely, two mods are trying to change the same text archive or journal entry. You can bisect your mods, and once you've found the issue, you can try the below:

Sometimes, adding # or ! to the beginning of the .archive file name can fix this.

Double check the mod page first to see if the author has any suggestions or workarounds!

Press [none] To Continue / Can't Skip Loading Screen

That is due to Input Loader requiring an update. Double check you have the latest version.

Outdated Mods

There are probably hundreds, if not thousands of outdated mods, but these ones still get downloaded to this day. If you have any of these, remove them.

  • CTD Helper

    • This mod has been broken for a long time and will not work.

  • NPCs Gone Wild (NSFW)

    • In all versions since 2.0, this causes missing characters, missing body parts, exploding limbs, and other issues. Do not use the mod.

There are some mods that still cause issues despite not being available for download anymore. If you have these mods, they are seriously outdated and you need to delete them.

  • System-Ex (replaced by Cyberware-Ex, download this instead)

  • Respector

You Have Spawn0 Mods Installed

Most famous for physics-defying, back-breaking edits of the female body, Spawn0 has been around since the early days, and so have their mods.

Modding has come a long way since then, and Spawn0 never followed. Their mods are known to have compatibility issues with pretty much everything, including their own other mods.

With Phantom Liberty, Sp0 mods have been known to cause crashes to desktop near the dam.

Bisecting

Mod Managers

If you are using a mod manager, you should enable and disable mods through it rather than manually bisecting your game folders. Go to the Bisect with a mod manager section for instructions. If you do work directly through folders, do not save changes to files if Vortex prompts for it.

You have hundreds of mods, and one of them is broken. How do you find out which one it is without wasting the entire day?

Don't worry! As long as you have less than 2048 mods, bisecting can finds the problem child in 10 rounds. Even if you have more, it's still quicker than disabling them all one by one.

Bisecting With A Mod Manager

This is the easiest way to bisect your mods. Keep reading for a step by step guide on how to find that pesky mod breaking your game.

If you prefer a visual guide, check the bottom of this section!

You need to keep the core mods enabled while you bisect, otherwise none of your mods will work, and finding the issue will be impossible. Here's a list, to make it easier for you:

Tips For Vortex Users

If you're using Vortex, you can highlight mods so it's easier to remember which mods you've already tested.

You can also rename mods by double clicking them to open the side panel, so adding "CORE" to the start of the mods listed above might be helpful.

You can highlight mods here!
Double click a mod to bring this menu up!
1

Disable Half Your Mods

Not including the mods listed above, select half of your enabled mods and disable them.

This can be done easily by clicking on the mod at the top of the list, then scrolling down and pressing SHIFT on your keyboard when you select another mod.

2

Launch The Game

You need to launch the game to see what your next step is.

If the issue is gone

  • The problem mod exists in the mods you disabled. You need to continue to Step 3.

If the issue still occurs

  • The problem mod is in the mods you kept enabled. You need to repeat Steps 1 and 2 with these mods until you've found the problem mod.

3

Swap Halves

If your game launched with no issues in the previous step, disable the mods you just launched the game with and re-enable the other half. The problem mod should be in this set.

Now that you've narrowed it down slightly, you need to repeat Steps 1 and 2 with these mods until you've found the problem mod.

4

Remove The Problem Mod

Once you've bisected all the way down to enabling a single mod, you've found the one causing trouble. Remove the mod and launch your game again.

You can also check to see if it's recently been updated, but if it hasn't, you'll need to remove it

The issue should now be gone. Happy game!

A visual guide for bisecting with a mod manager!

Bisecting Manually

If you've manually installed your mods, you'll need to bisect them manually too. Even if it seems like a lot of work, it's the quickest way to find the problem mod.

If you already know which folder contains the broken mod, skip to Step 2.

You can find a video of the process below.

The table below shows which folders contain mod files. All of these can be found in your game directory. You'll need to reference this table to find where the broken mod is.

File Path
Explanation

\mods

Contains REDmods, can contain many file types in their own subfolders

\archive\pc\mod

Contains .archive and .xl files, for Archive-XL-based mods

\bin\x64\plugins\cyber_engine_tweaks\mods

Contains Cyber Engine Tweaks-based mods

\r6\scripts

Contains Redscript-based mods

\r6\tweaks

Contains RED4ext-based tweaks

Where Do I Even Start?

1

Find The Problem Folder

  • Navigate to Cyberpunk 2077\mods

    • Rename it by adding an underscore to the end. It should now be called mods_

    • Create a new folder called mods in your game directory

  • If this folder is empty, navigate to Cyberpunk 2077\archive\pc\mod

    • Rename the \mod folder by adding an underscore to the end. It should now be called mod_

    • Create a new folder called mod inside the \pc folder

You only ever need to rename the last subfolder in any file path, such as the plugins folder, scripts folder, or tweaks folder.

  • You now need to launch the game. You will now run into one of these two scenarios:

    • The problem is gone, which means you've already found where the problem mod is, and you can move on to Step 2

    • The problem persists, which means you need to repeat the above process with the rest of the folders in the table until you find the folder it's in.

You can put the innocent folders back, if you want. Due to the way mods are loading, there won't be side-effects.

2

Re-enable Half Your Mods

The process is the same if you are moving files or folders!

When you've found the folder with the problem mod, you're ready to actually bisect.

Open up the folder you added an underscore to. This is your backup folder.

Move half of the mods from your backup folder into the folder you created - the one that doesn't have an underscore. This is your game folder.

For all the visual learners out there

You'll need to remember (roughly) which batch you moved (e.g. "everything after E" or "the first 100 mods")

3

Launch The Game

You need to launch the game to see what your next step is.

If the issue is gone

  • The problem mod exists in the mods in your backup folder.

You now need swap the mods you have installed.

  • The mods you most recently put into your backup folder need to go into your game folder

  • Any mods currently in your game folder need to go into your backup folder

You can now proceed to Step 4!

If you've bisected to the point of only having one mod left to test, you can move on to Step 5!

If the issue still occurs

  • The problem mod is in the mods you re-enabled. You need to proceed to Step 4.

4

Disable Half Your Mods

Now, you need to take half of the mods in your game folder and place them into your backup folder.

Repeat Steps 4 and 5 until you find the problem mod!

5

Remove The Problem Mod

Now that you've found the problem mod, it's time to remove it from your game.

You can also check to see if it's recently been updated, but if it hasn't, you'll need to remove it

The issue should now be gone. Happy game!

Bisect: Video Guide

Log Files

The game's log files tend to be a bit unhelpful, but log files from mods tend to be more useful.

If you get a "Whoa! Cyberpunk 2077 has flatlined" error, click here to see more information.

Where Can I Find Mod Logs?

Quite a lot of mods will create a log file, but only a few of them are useful when it comes to troubleshooting. Check the table below to see where to find them!

Log File Name
File Path

redscript_rCURRENT.log

\Cyberpunk 2077\r6\logs

red4ext-[NUMBERS].log

\Cyberpunk 2077\red4ext\logs

cyber_engine_tweaks.log

Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks

ArchiveXL and TweakXL also have log files, but they're not as useful for troubleshooting as the ones listed above.

You can find these log files here:

ArchiveXL-[NUMBERS].log - \Cyberpunk 2077\red4ext\plugins\ArchiveXL

TweakXL-[NUMBERS].log - \Cyberpunk 2077\red4ext\plugins\TweakXL

Isn't There An Easier Way?

If you don't want to find logs individually, and just want a script that finds them for you, you're in luck!

Download Doctor Presto's FindAllErrors script

Click this button at the top!

Now, you can either:

  1. Move it to your Cyberpunk install folder and double-click it

  2. Drag-and drop your Cyberpunk folder on the file that you downloaded

After running, the script will have created a folder _LOGS in your Cyberpunk game directory, which contains a file listing all the log files for you.

The list will give you useful information along with a list of files to check. Once you've found the broken mod, you can go here for instructions on how to troubleshoot further – they also tell you when you should ask for help!

Removing All Your Mods

You've been troubleshooting for too long and just want to start over again. Lucky for you, we have instructions for that too.

By far, the easiest way to reset your install to an unmodded state is by using Mod Remover (also on GitHub). Thanks to our very own Manavortex, manually removing all your game folders is entirely unnecessary.

You can also use this to temporarily disable your mods, as it creates a full backup for you.

If you're using a mod manager, you need to purge/disable your mods there first.

Make sure to read the mod description, it has very thorough instructions. The mod remover itself also has instructions at every step of the way.

This is much, much quicker than manually removing all of your game folders. Promise.

Removing mods? We have a mod for that!

If you're absolutely set on doing it manually, you can follow the steps in the dropdown below.

Just reinstalling the game through GOG/Steam/Epic does not remove mods, and is a waste of time.

Manually Resetting Your Game Install

Unless you back them up, your mods and settings will be lost. If you don't want that, make backups of the following folders:

  • /mods

  • /archive/pc/mod

  • /bin/x64/plugins/cyber_engine_tweaks

  • /r6/scripts

  • /r6/tweaks

Mod Remover will do all of this for you! It's not too late to use that instead!

Option 1: Minimal (Re-download less than 1GB)

Unless you back up your mods and scripts, all your settings and manually installed mods will be lost.

Rename or remove the following folders. If you do not have them, you don't need to do anything.

Afterwards, verify your files.

Option 2: Quick (Re-download less than 4GB)

Unless you back up your mods and scripts, all your settings and manually installed mods will be lost.

The instructions below tell you which folders not to delete. Delete everything else.

  1. Go to the Cyberpunk 2077 directory

  2. Keep the archive folder. Delete everything else.

  3. Inside archive, keep the pc folder. Delete everything else.

  4. Inside pc, keep the content and ep1 folders. Delete everything else.

  5. Verify your files.

Option 3: Thorough (Re-download everything)

In case neither of the above options are good enough for you, you can find a full reinstall guide on CDPR's support page.

Deleting User Settings

You almost never need to do this.

If you want to remove anything that Cyberpunk might have stored on your disk, you need to find and delete the following folders (as per CDPR's own troubleshooting guide:

  • %userprofile%\Saved Games\CD Projekt Red\Cyberpunk 2077

  • %userprofile%\AppData\Local\REDEngine

  • %userprofile%\AppData\Local\CD Projekt Red

You can quickly navigate to the folders by pasting the path into your Windows Explorer's path bar, or pressing Windows + R, pasting the path there.

Doing Mod Remover's Steps Yourself

If you're curious to see (more-or-less) what Mod Remover does, don't want to download scripts from the internet, or just want to see what resetting your game was like before it was created, you can read below!

You can still follow these steps yourself, but rest assured that Mod Remover does the exact same thing far quicker!

Step 1: Disable REDmods And Archive Mods

Find The Following Folders:

Rename them to

The purpose of renaming them is that the game won't find them anymore, but you still have a back-up of the files inside. Feel free to achieve this goal however.

You can optionally create a new, empty folder with the same name.

Check if the problem is gone.

If it is, put the folders back one after the other and apply the bisection method.

Step 2: Disable CET

Find the folder:

Move it out of plugins (e.g. put it on your desktop).

If you'd rather delete it, make sure that you retain a copy of your mods and plugins directories, as they contain your mod settings (AMM decorations etc.)

Check if the problem is gone.

If it is, put the folder back and apply the bisection method to cyber_engine_tweaks\mods and cyber_engine_tweaks\scripts until you have found the culprit.

Step 3: Remove Scripts And Tweaks

First, remove (or rename) the cache:

Verify game files. Check if the problem is gone.

If that didn't do the trick, find the following folders:

Rename them. You know the drill.

Check if the problem is gone.

If it is, put them back one by one until you find the one that breaks it. If that is one of r6\scripts or r6\tweaks, apply the bisection method.

Step 4: Remove RedScript

Delete the following files and folders. You don't need a backup, as you can reinstall RedScript from Nexus. If any of them don't exist, that's okay — just means you don't have to delete them.

@Auska has compiled a handy script for unix people:

Step 5: Repair/Verify Game Files

You need to verify your game files through your launcher (GOG/Steam/Epic). If you're not sure how to do that, check here!

Step 6: Launch The Game

All files you deleted have been re-acquired. If there are no left-over files from earlier modding attempts, your game should work now.

If it does not and you have exhausted the reset options as specified in this guide and your game still does not start, then your problem exists outside of Cyberpunk. In this case, you can

Step 7: Install The Core Frameworks

Now that your un-modded game is starting, it's time to install the core frameworks, which you can find listed in Step 1 here.

Do this before you enable your other mods, as they won't work without their dependencies and can only add problems at this stage.

You can now re-enable your mods. Do it in chunks and check that the game keeps working so that you can narrow down where the problem is, in case it isn't gone for good.

Verify / Repair Game Files

If you're not sure how to verify your game files, click below to find the instructions for your game launcher.

Thanks to @ArsenicTouch for the guides!

  1. Go to Games -> Installed

  2. Right-click on your game

  3. Mouse over Manage installation

  4. Select the following menu entry:

  1. Open your library

  2. Right-click on Cyberpunk 2077

  3. Select Properties...

  1. Select Installed Files

  2. Click Verify integrity of game files

  1. Open your Library

  2. On the Cyberpunk 2077 tile, find the …

  3. Select Manage

  4. Click Verify

Mods Removed. Now What?

If you were manually installing before, please consider using a mod manager going forward!

Try launching the game completely unmodded to make sure you've done everything right. If you have, the game should launch without any issues!

If it doesn't launch, you either have leftover files and need to re-do your previous step, or you have a problem that is not related to Cyberpunk.

If you're sure all your files have been removed, double check everything below:

If your game does launch, and you want to mod the game again, re-install the core mods.

If you're using a mod manager, you can simply re-enable these mods through that, although you can remove and re-install them to be extra cautious.

Not sure what they are? Here's a list:

Once they're re-installed, launch the game.

Don't worry about your save games — they're fine, even if they don't load right now.

If you need to check in-game but can't load a save, try opening a non-modded one, or create a new one!

If your game launches without issue, you can re-install your mods through your mod manager or from your backup folders. If you want to be extra cautious, you can try a fresh download of them all. If you start getting errors when re-installing mods, you'll need to bisect your mods.

If you're unsure on how to mod your game, or just want a refresher, you can follow this page.

If your game does not launch, double check the red box above.

You need to complete this step before proceeding: if the core mods aren't working on their own, they won't work with other mods on top – adding anything else will make troubleshooting more difficult.

Install them one by one. If you need help, you can find us on Discord (#mod-troubleshooting)

Dealing With Broken Mods

You followed all the steps and your game launches, but you now have a mod on your hands that doesn't work, and you want it to. What do you do now?

Before you do anything listed below, go back to the very top of this page and double check you've done all the troubleshooting first steps.

Everyone messes up downloading mods sometimes, and it's never a bad idea to double check if it's user error first.

Contact The Mod's Author

Describe your problem as clearly as you can, and add any useful information.

Keep in mind that you're asking a favour. The modder doesn't know the issue, and if they do, they know exactly how to fix it. A lot of mod users will leave non-descript "mod broke" comments, and some leave abuse because of it.

A mod author is much more likely to respond if you're civil and give relevant information.

Example - Bad Bug Report

Fake Nexus comment that says "Your mod doesn't work lol pls help". The mod author responds "Can I get some more info? I can try to fix but what is the issue first?"
"Your mod doesn't work lol pls help" isn't useful to anyone!

Example: Good Bug Report:

Fake Nexus comment that reads: "Hi, installing your mod (manually and Vortex) causes a Redscript compilation error on startup (possible screenshot of error popup). this.log says <citation of error message>. All my dependencies are up-to-date, and I've ruled out that it's any other mod. Can you help me out?". The author replies "Hi, thanks for reporting! I will look into it for you. Edit: fixed in new update!"
This is much more useful to a mod author because they actually have information to work with

Fix It Yourself

At this point, you have exhausted all easily accessible solutions. If you want the mod to work, you'll have to get your hands dirty. That's the kind of passion the modding community thrives on.

This is the point where you might want to join the modding discord, because now you're entering the territory where other modders can actually help you. Head over to #mod-dev-chat first!

Checking Log Files

Not sure where to find log files? Click here!

Usually, there's a log file that points you to the source of the problem. If there isn't one, and the mod just fails silently, that means the error is inside the archive and you have to become a modder.

Fixing scripts

Sometimes, the error is in a script file. You can tell this by a log entry pointing to a file in your Cyberpunk folder (e.g. r6\scripts\mod_name.reds).

Open the file in a text editor like Notepad++ and try to fix the problem. Check to see if the log file has more information.

See if an online syntax check can help you — there isn't one for redscript, but it's fairly close to lua.

Occasionally, mistakes are simple — a forgotten , or incorrect file encoding. Often, they are not that simple.

A tip for nil access error in lua

Ascending From User To Modder

If the error isn't in any script files, you'll have to unbundle the .archive, load it in WolvenKit, and get your hands dirty. We'll be seeing each other, choomba!

PreviousModding on macOS
NextUsers: Troubleshooting after a game update

Last updated