Game: Cyberpunk 2077

PCGamingWiki

A Cyberpunk plugin update (PR) is included in MO 2.5 beta 14.

Requirements

• Only Cyber Engine Tweaks (CET) v1.27+ for Cyberpunk v2.01+ is compatible with MO! CET ≤1.26 is incompatible with MOs virtual file system USVFS!
• CET and RED4ext frameworks (not the dependent mods) need to be copied into game root.
  Optionally, this can be automated via RootBuilder (will get preconfigured if installed). Without RootBuilder, see Framework Installation below for details.
• REDmod will be automatically deployed when needed before game launch (with MOs load order).

If you encounter any problems, refer to FAQ & Troubleshooting.

Features

• Auto mod installation (ModDataChecker) of all mods (see table below)
• Profile specific config (.ini) and savegames
• Savegame preview & metadata
• REDMod: auto deployment before game launch (only when needed)
• Enforce MOs load for .archive (archive/pc/mod/modlist.txt) and REDmod (-modlist) Only REDmod load order is enabled by default (see Plugin Settings below)
• Optional RootBuilder default config for CET & RED4ext framework root auto install

Compatiblity of mods / frameworks

Here is an overview of the mod / framework support as of MO 2.5 beta 14 (Cyberpunk game plugin v2.2) and the compatibility with MOs virtual file system USVFS:

		Support: mods / framework
Mod type / framework	Mod folder (files)	Auto install*	USVFS
archive	archvie/... (.archive)	✔️/ –	✔️/ –
redscript	r6/... (.reds)	✔️/✔️	✔️/✔️
RED4ext	red4ext/... (.dll)	✔️/✔️root	✔️/❌
Cyber Engine Tweaks (CET)	bin/x64/plugins/... (.lua)	✔️/✔️root	✔️ 1.27 / ❌
REDMod	mods/* (info.json, ...)	✔️/❌(DLC)	✔️/❌(DLC)

root: Auto install only into (virtual) root folder, compatible with RootBuilder (copy/hardlink). Alternative: copy manually into game dir.

* Remarks

• RED4ext: Only the framework (2 .dll files) need to be copied / hard linked to root, dependent mods work with USVFS then.
• Cyber Engine Tweaks (CET):
  • Cyberpunk v2.01, CET ≥1.27: only CET framework needs to be copies / hard linked into root (all files), mods work with USVFS.
  • Cyberpunk v1.x, CET ≤1.26: is not compatible with USVFS, see CET issue / PR for details.
• RedMod: precompilation is supported with MO2 plugin update v2.1
• RootBuilder can be used to automate hard linking / coping root files into game dir (only frameworks RED4ext and CET, no mods)

Framework installation

Manual installation without RootBuilder

RED4ext installation: place framework (the .dll files) into root

root/
├── bin/x64/winmm.dll
└── red4ext/RED4ext.dll

RED4ext dependent mods can then be installed normally in MO2 and work with USVFS (red4ext/plugins/*)

CET ≥1.27 for Cyberpunk v2.01: Install CET framework itself into root, like this:

root/
└── bin/x64/
    ├── plugins/
    │   ├── cyber_engine_tweaks/
    │   │   ├── fonts/
    │   │   ├── scripts/
    │   │   └── tweakdb/
    │   └── cyber_engine_tweaks.asi
    ├── global.ini
    └── version.dll

CET dependent mods can then be installed normally in MO2 and work with USVFS (bin/x64/plugins/cyber_engine_tweaks/mods/*)

RootBuilder config

You can use RootBuilder to copy / hard link the framework files from virtual folder root automatically into game install dir, to keep it clean.

The following settings will be preconfigured if RootBuilder is installed (Tools/[Tool Plugins]/Root Builder/):

• Mode: Links (Copy works, too)
  • USVFS and USVFS + Links do not work!
  • Links = hard links only mode is available with RootBuilder ≥4.5
  • hard links do not consume extra space on disk, but work only on the same drive (as portable MO or `C:/.../AppData``)
• Exclusions: archive,tools,setup_redlauncher.exe
• Check Backup, Cache, Autobuild

Delete Backup and Cache when updating Cyberpunk!

Plugin Settings

Under Settings / Plugins / Cyberpunk 2077 Support Plugin:

• skipStartScreen=True: Skips the "Breaching..." start screen on game launch by adding -skipStartScreen to Cyberpunk command line args
• enforce_archive_load_order=False: Enforce the MOs load order of archive files (via archive/pc/mod/modlist.txt, generated in overwrite). Disabled by default to load archives alphabetically.
• enforce_redmod_load_order=True: Enforce the MOs load order for REDmods on deployment
  (via redMod.exe deploy -modlist=r6/cache/modded/MO_REDmod_load_order.txt, generated in overwrite)
• auto_deploy_redmod=True: Deploy REDmod before game launch if necessary. You can use the alternative executable with "... skip REDmod deploy" to not load REDmods at all, too.
• configure_RootBuilde=True: Configures RootBuilder for Cyberpunk if installed and enabled (only once per instance, will be toggled off)

FAQ & Troubleshooting

Mod specific

• Load order / priority in MO can be relevant for some mods (besides the obvious file conflicts/overwrites): E.g.: presets for Appearance Menu Mod need to be loaded first (with lower priority, like preset: 0, AMM: 1)

General

• overwrite contains files written after game launch, including mod settings
• If any REDmods are installed, the precompilation / deployment progress will show in a console window before game launch
• MO2 creates the load order files archive/pc/mod/modlist.txt (.archive) and r6/cache/modded/ (REDmod) for Cyberpunk when necessary there, too.
• A virtual root folder in Data view is normal for compatibility with RootBuilder
• Always start with a clean Cyberpunk folder before using RootBuilder's backup option.
  • Backup is build on first game launch with above settings
  • Backups are stored in MO/plugins/data/RootBuilder

To reset the game folder and MO if anything goes wrong:

Without RootBuilder:

1. delete all CET & RED4ext framework files (after backup), including both red4ext and bin/x64/plugins folders
2. make sure Cyberpunk starts without MO (otherwise see below)
3. install fresh CET & RED4ext again into game folder (not via MO)
4. clear overwrite (backup any mod settings etc. you want to keep beforehand)
5. (reset mods and their config by reinstalling and replacing them)

With RootBuilder:

1. if your game folder is not clear: select Clear from Tools/[Tool Plugins]/Root Builder/Clear to restore game folder (writes changed files to overwrite/root)
2. check that the game folder is actually clean (from framewoks, too) and test if it starts without MO (otherwise see below)
3. open RootBuilder menu, Delete Backup and Cache, double check exclusions and create the Backup again
4. clear overwrite, but backup any mod settings etc. you want to keep beforehand
5. (reset mods and their config by reinstalling and replacing them)

If Cyberpunk does not start without MO after cleaning (steps above):

• restore the original r6/cache/final.redscript from either final.redscript.bk (can be in overwrite) or by verifying game files

Version Changelog:

• MO v2.4.0: Added initial plugin
• MO v2.5.0 beta 14 (plugin v2.2.2): Added support for Cyberpunk 2.01 with CET ≥1.27
  • Auto mod installation (ModDataChecker)
  • Profile specific config (.ini) and savegames
  • Savegame preview & metadata
  • RedMod: auto deployment before game launch
  • MOs load order is enforced for REDmod (-modlist) and optional for .archive (modlist.txt)
  • RootBuilder default config for CET & RED4ext framework root auto install