Modding & Load Order / Cyberpunk 2077 / REDengine 4

Cyberpunk 2077 Patch 2.3: Mod Load Order and REDscript Recovery

A framework-first load order, crash-log route, and rollback method for Cyberpunk 2077 mod stacks after the 2.3 patch.

Official Steam Store header artwork for Cyberpunk 2077.

Cyberpunk 2077’s 2.3 patch refreshed REDmod deployment behaviour and stabilised a set of load-order cases, but it did not make old script mods immortal. The failure pattern is familiar: the game launches, hits the CD PROJEKT RED logo, and closes without an error. Or it loads but every mod menu is blank. Both are usually load-order problems, not a corrupted GPU driver.

This file assumes a modded PC install with REDmod, RED4ext, and a handful of archive and script mods. Vanilla crashes are a different diagnostic path. The load order below is a pattern, not a copy-paste list of every mod on the internet.

The 5-minute post-patch triage

Disable, don't delete
  1. Launch the game with no mods to confirm the vanilla build is healthy.
  2. Update RED4ext and the core frameworks for the 2.3 build.
  3. Disable every mod except the frameworks, launch once, then add content mods in small batches.
  4. Read the RED4ext log before deleting a mod. It usually names the failing script.
  5. Back up saves before re-enabling anything that changes inventory or quest state.

The load-order principle

Cyberpunk 2077 / dependency-first stack

Top → bottom
  1. 01 RED4ext Script extender — foundation for most script mods Core
  2. 02 Codeware Shared framework library Needs RED4ext
  3. 03 ArchiveXL Archive extension layer Needs RED4ext
  4. 04 TweakXL Tweak database loader Needs ArchiveXL
  5. 05 REDmod framework mods Deployed through the game launcher or mod manager Core
  6. 06 Content and quest mods Depend on the frameworks above
  7. 07 Overhauls and gameplay replacements Load last; most likely to conflict Vs other overhauls

If two mods edit the same TweakXL record, the last one in the effective chain wins. That is not always the last folder alphabetically. Always check the mod author’s deployment guidance and the manager’s conflict report.

Find the actual failure

%LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077
logs\                 # game and script logs
r6\cache\             # generated cache; inspect before deleting
red4ext\logs\         # RED4ext load and script errors
mods\                 # REDmod / deployed mod content
archive\pc\mod\       # archive mods deployed by the manager
%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077\
ManualSave-*        # local save slots
Folder layouts vary with the mod manager. Back up saves first. A launch failure is usually logged before it reaches the main menu.

Open the newest RED4ext log and search for [error] or failed. A missing dependency often appears as a failed import or a class not found. A crash with no log line can still be a native DLL mismatch; in that case, disable the last batch you added and launch again.

%LOCALAPPDATA%\CD Projekt Red\Cyberpunk 2077\red4ext\logs\red4ext.log
[INFO] RED4ext 1.x.x loading...
[INFO] Loading mod: Codeware
[ERROR] Failed to load: MyOldMod — missing dependency
[INFO] Loading mod: ArchiveXL
; Example shape only. Your log will name the actual failing mod.
Do not edit the log. Use it to identify the mod, disable that mod, and verify the game launches before adding anything else.

Script and archive versions must match

There are two common deployment paths on PC: archive mods placed in archive/pc/mod, and REDmod packages deployed through the launcher’s mods menu. Mixing old REDmod deployment with a new mod-manager deployment can create duplicate copies of the same files. The game then loads a stale version or refuses to launch.

Before adding a new mod:

  1. Check the author’s supported game version. “2.2+” is not a guarantee for 2.3.
  2. Confirm the framework versions in the mod’s requirements match the build.
  3. Deploy once. Do not manually copy the same files into two locations.
  4. Launch to the main menu before installing a second mod.

Performance impact of a large stack

Mod load time is not a reliable proxy for in-game performance. The chart below compares a clean build with a framework-only build and a 30-mod stack on the same save. It is a warning about 1% lows and startup time, not a claim that mods are inherently slow.

Cyberpunk 2077 / mod stack load and frame-time check
Scale 0–150 FPS
Black: average / Blue: 1% low
Vanilla / 0 mods 128 FPS / 102 low
Frameworks only / 5 mods 126 FPS / 99 low
Content stack / 30 mods 119 FPS / 84 low
30 mods + traffic overhaul 108 FPS / 66 low

Bench: 1440p high preset, RT off, same V save. Startup time measured to main menu after a cold boot. Mod counts are illustrative for this bench profile.

A 30-mod stack can cost frames because the mods are doing work, not because the game is “badly optimised.” Remove the expensive ones first. The traffic overhaul row is a classic CPU-side load increase; no .ini tweak will give those frames back.

Config builder / Cyberpunk 2077 REDengine 4

Built locally in your browser. Nothing is uploaded.

Game config directory
; GamePathHub // Cyberpunk 2077
; Engine: REDengine 4 | GPU class: 12 GB | Target: 120 FPS
; Upscaler: DLSS Quality
; Change one group at a time. Back up the original file first.
# Generic engine baseline
# USE WITH CAUTION: the game may not read these keys.
[Graphics]
TargetFrameRate=120
VSync=0
Upscaler=DLSS Quality
TexturePoolMB=7552
ShaderCacheMB=15104
Custom engines require title-specific keys. Confirm the key names in the game files before saving changes.

Post-patch mod recovery sequence

0 / 8 complete

What to do when a save will not load

Disable all mods and try the save in vanilla. If it loads, re-enable only the frameworks, then the mods that directly affect inventory, vehicle, or quest records. If vanilla also rejects the save, you may be dealing with corruption unrelated to load order; restore the most recent backup rather than forcing an outdated script.

The rule after 2.3

Update the frameworks, verify the vanilla build, and add content back in batches. Do not paste a load order from a video into a different mod set and expect stability. Load order is a dependency graph, not a magic sequence. The evidence is in the log, and the recovery plan is your backup.

Did this fix work on Patch 2.3 — REDmod load-order and stability update?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against 2.3 — REDmod load-order and stability update. Votes are local-only telemetry.

Cyberpunk 2077: bench questions

3 answers
What is the correct Cyberpunk 2077 mod load order?
There is no universal list. The stable pattern is frameworks first, then dependency libraries, then content mods, then optional overhauls. Use the mod manager's dependency view and the RED4ext log to verify what actually loaded.
Why do mods break after every patch?
Script and framework mods depend on game code signatures that patches change. A mod that was stable on 2.2 can fail on 2.3 until its author updates it. Disable incompatible mods rather than forcing old binaries to load.
Should I delete the r6 cache folder?
Do not delete the whole game folder or save data. If a cache rebuild is required, isolate the documented cache and back it up first. The RED4ext and script logs should tell you which mod failed before you start deleting.
Filed under

Modding & Load Order

Patch tested: 2.3 — REDmod load-order and stability update

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.