A mod is crashing and you know which — what now?
This page assumes that you have made use of the troubleshooting guide, have identified a broken mod and want to help fixing it.
It will help you rule out side effects and collect e necessary information for a bug report. Of course you can always reach out, but there's a good chance that you'll be asked to do the stuff on this list, so you might as well do it first.
If you can't or won't do that, please check at least Step 0!
Without people like you, many bugs would never be discovered and fixed, and modding would be even more frustrating than it already is. So thank you for taking the time!
"Crashes when you equip your strap-on? I fixed that a month ago. Just update! :)"
Make sure that you're on the most recent version of both the mod. You probably are, but — better double-check.
This recommendation comes from a professional software developer, who has "fixed" more than one software problem by just updating the software.
Maybe the mod author knows about this problem and hasn't been able to fix it. If they do, then either the description will mention it, or there will be a pinned post in the comments section.
If there isn't either, then you have found something new. Exciting!
The first step is to isolate the problem. Make sure that it is exactly this mod and no other. It works like this:
Temporarily remove all mods from your game.
Install only the problem child together with all dependencies. Make sure that they're all on the most recent version. Does the problem still happen? (If not, then it's something else)
Now, disable only the problem child. Does the problem go away? (If not, then it's one of the dependencies)
If the problematic mod is a core framework, please read the next section as well.
If you can reliably reproduce the problem (that's Netrunner speech for "it happens every time without fault"), then you have everything you need for a bug report.
If your problem child isn't one of these mods, you don't need to read this.
The core frameworks are generally extremely stable. That's not to say that they don't have bugs, but such bugs are generally found and fixed quickly.
If you suspect that one of them is the cause of your crash, make very sure that you have no dependent mods installed, since those will be inactive as long as the dependency isn't there (think of it like a fuse box: without electricity, the fridge can't keep making that noise).
Since your problem could be anything, we'll go about it the other way. I'll list everything that you could include, and tell you when it's needed.
When: Always
Any information you collect is helpful, but fixing a bug is easiest if you can watch it with your own eyes. For that reason, we need a list of the exact steps needed to make the problem happen.
Write the steps they need to do, not the ones they don't.
When: If the problem happens
at a certain location or a certain quest phase
when loading into exactly this save (if it happens for all of your saves, then it's probably not needed)
Your save games can be found in the following folder:
which is the same as
Find your individual save game folder (e.g. AutoSave-0) and create a zip.
When: If the problem child
adds an error in any log files that doesn't happen without it (use the error checker tool)
Is a plugin (lives in Cyberpunk 2077/bin/x64/plugins)
Is dependent on a plugin (like above, but with more subfolders)
What:
The log file with the error
If it's a plugin mod, then add the plugin's log. Most common here is Cyber Engine Tweaks; the log file is Cyberpunk 2077/bin/x64/plugins/cyber_engine_tweaks/cyber_engine_tweaks.log
When: If the problem child is one of the core frameworks.
These mods are the foundation that everything else builds on, and the people who develop and maintain them are incredibly competent. Please don't waste their time — make very sure that you have isolated the problem. You don't call your internet provider before checking your network cable and restarting your router!
You can find the crash reports in this folder:
which is the same as
Find the most recent one (e.g. Cyberpunk2077-20230816-225038-11372-16140) and create a zip.
You're 100% sure that the mod is the cause of the problem, and you have collected the necessary information, so now you can reach out and provide a helpful bug report.
The first place to go is the mod's Nexus page.
If there is a Bugs tab, you can create a new bug report
If there is a Posts tab, you can leave a post
If there is a Comments tab, you can drop a comment
If there is neither, you can try and message the author (click on their Nexus profile name)
If you can't reach the mod author, you're welcome to hit up the redModding Discord, for example in #mod-troubleshooting. Someone there might be able to get the word out.
If you have found a mod that corrupts save games until it is installed again, please let us know so that we can update the troubleshooting guide!