Finding and reading log files
This page will tell you how to find the right log file for your problem.
A list of framework logfiles
This section has a list of log files by framework. If you've arrived here from one of the troubleshooting channels on Discord, the file you're supposed to find is most likely in this list.
If you aren't looking for a particular log file, please proceed to the next section.
redscript
r6\logs\redscript_rCURRENT.log
red4ext
red4ext\logs\red4ext.log
ArchiveXL
red4ext\plugins\ArchiveXL\ArchiveXL.log
TweakXL
red4ext\plugins\TweakXL\TweakXL.log
Cyber Engine Tweaks
bin\x64\plugins\cyber_engine_tweaks\cyber_engine_tweaks.log
Finding the log files
If you don't want to download and run script files from the internet, you can go here and complete the steps by hand. Otherwise:
Download this script (right-click -> save as) You can (but probably don't want to) look at the code on Presto's github repository.
Now, do either of the following things:
Move it to your and double-click it
Drag-and drop your on the file that you downloaded
The script will have created a folder
_LOGS
in your , where you will find a file with everything it has found..
Alternatively: By hand
Browse to your and use the windows search to search for *.log.
Make sure to include the asterisk and the dot: *.log
, as you will otherwise see files that you don't care about.
The list of results should look like this:

With a few exceptions, log files have the name of their mod. If they don't, check what folder they're in.
There's too many of them!
If you're drowning in log files and have no idea how to filter them, you can delete or remove them. Don't worry, they will be re-created on next launch.
Don't delete anything that isn't Type: Text Document
ending in .log
! Doing that will break other mods or even your entire install.
Now, restart your game and do whatever you did to make the error appear. Then, search the Cyberpunk directory for *.log
again.
Finding the relevant log file
Sort the files by
size
(if you just deleted them) or bydate modified
(if you didn't)Open each of the files in a text editor (such as Notepad, it's installed with Windows). The relevant information will be at the very bottom.
You are looking for lines with
error
orwarning
. If you want to see what they look like, scroll down to the next section.If the log file doesn't have any, ignore it. Close it and proceed to the next file.
You found errors: Congratulations, you've found at least silver. Check here for how to proceed.
You found warnings: These might indicate that you're on to something, but don't let them panic you. If the mod is doing what it should, just ignore them. You can start troubleshooting already, or keep looking for errors.
Making sense of them
Error
There's definitely something going on here, you're on the right track!
Errors look like this:
[2023-04-15 12:04:18.956] [error] |Something| Some Explanation
[2023-04-14 20:28:18 UTC+01:00] [1234] [ErrorSource] DoSomething(): Error ! Some Explanation: Some Details
An error in the log files almost always means that something exploded in a way that nobody has planned for.
If the file is directly in
bin\x64\plugins\cyber_engine_tweaks
, that means CET is broken and you need to troubleshoot it.If the file is in a subfolder of
bin\x64\plugins\cyber_engine_tweaks
, you have found a broken mod, but CET mods won't break the game. In this case, treat it like a warning.If the log is anywhere else, you have found something to troubleshoot.
Warning
If your warning isn't listed below, use your own best judgement.
Field with this name is already defined
[WARN - Thu, 13 Apr 2023 21:54:13 +0200] At Path\to\Cyberpunk 2077\r6\scripts\something.reds:1234:1:
@addField(inkScrollArea)
^^^
field with this name is already defined in the class, this will have no effect
This might indicate that a Redscript mod is loaded twice. Search the Cyberpunk root folder the mod name and make sure that you have no duplicates. If you're uncertain about this, try the bisect method on your r6
folder.
Last updated