If you have ever opened a Cyberpunk 2077 mod page and seen a wall of requirements like Cyber Engine Tweaks, RED4ext, redscript, ArchiveXL and TweakXL, you are not alone in wondering why one mod needs five other downloads. These are not mods in the usual sense. They are frameworks: tools that sit underneath the actual mods and give them a way to talk to the game. Without the right framework installed, the mod simply will not load, or it will crash the game on launch.
Once you understand what each one does, the requirement lists stop being confusing and start making sense. Most mods only need one or two of these, not all five, and the install process is the same every time: get the frameworks working first, then drop in the mods that depend on them.
Why mods list frameworks as requirements
Cyberpunk 2077 was not built with modding tools baked in. Modders had to build their own ways to inject scripts, read and change game data, and add new assets without touching the original game files directly. Those tools became the frameworks you see listed everywhere. A mod that adds a new weapon, changes AI behavior, or adds a console overlay has to use one of these frameworks to actually reach into the game. The framework does the technical heavy lifting; the mod just tells it what to change.
This is also why framework requirements show up on almost every serious mod. It is not padding or bloat, it is a genuine dependency, the same way a Windows program might need a specific runtime library installed before it runs.
What each framework actually does
Cyber Engine Tweaks (CET)
CET gives the game a scripting layer built on Lua and adds an in-game overlay you can open to run console commands, tweak settings on the fly, or launch mod menus. A lot of quality-of-life mods and bigger overhaul mods use CET as their backbone because it lets them hook into game events and run custom logic while you play.
RED4ext
RED4ext is a plugin loader that lets modders write native code extensions for the game, rather than being limited to scripts. It is lower-level than CET and redscript, and a number of other frameworks, including ArchiveXL and TweakXL, actually run as RED4ext plugins themselves. If RED4ext is missing or out of date, those plugins will not load either.
redscript
redscript is a compiler for a scripting language that lets modders write and compile .reds script files that hook into the game’s own scripting system. Mods that change gameplay logic, like how quests behave or how an ability works, often rely on redscript rather than touching the base game scripts directly. This keeps multiple script mods from fighting over the same files.
ArchiveXL
ArchiveXL extends how the game reads .archive files, which is how new items, outfits, vehicles and other assets get added to the game without overwriting the originals. Before ArchiveXL, adding new content often meant replacing existing game files, which caused conflicts between mods. ArchiveXL lets multiple content mods coexist.
TweakXL
TweakXL does something similar but for game data tweaks rather than assets, things like item stats, crafting recipes or vehicle handling values. Instead of a mod overwriting the game’s base tweak files, TweakXL lets mods add their own tweak definitions on top, which again cuts down on conflicts between mods that all want to touch similar data.
Install the frameworks first
The order matters less than making sure everything is actually in place before you add mods that depend on it. A practical approach:
- Install RED4ext and Cyber Engine Tweaks first, since a large share of other tools and mods build on top of them.
- Install redscript if any mod you plan to use calls for it.
- Install ArchiveXL and TweakXL if your mod list includes anything that adds new items, outfits, vehicles or data tweaks.
- Launch the game once with just the frameworks installed to confirm it starts normally.
- Add your actual mods one at a time, checking that the game still launches after each one.
Each framework usually comes as a separate download with its own installation notes, and most of them drop files into specific folders inside your Cyberpunk 2077 installation, such as plugin folders or script folders. Follow the instructions that come with each framework’s download rather than guessing, since exact folder names can change between framework versions.
Frameworks need to match your game version
This is the part that trips people up the most. These frameworks are built against a specific version of Cyberpunk 2077. When the game gets patched, internal structures the frameworks rely on can shift, and an outdated framework may fail to load, cause crashes, or silently break the mods built on top of it.
After any game update, treat your frameworks as suspect until proven otherwise. Check whether RED4ext, CET, redscript, ArchiveXL and TweakXL have released updates matching the new game version before you assume your mod list still works. If you load into the game after a patch and mods stop appearing or the game crashes on startup, outdated frameworks are the first thing to check, not your actual mods.
It also works the other way: some frameworks are built for specific game versions and will refuse to load on a newer or older one, which is actually safer than silently breaking something, because at least you know immediately that something needs updating.
Check the mod page before installing anything
Every mod page worth using will list its exact requirements, usually near the top of the description or in a dedicated requirements section. Before you install anything, read that list and compare it against what you already have installed, including version numbers if they are listed.
- Note which frameworks are required, not just mentioned in passing.
- Check if a specific minimum version of a framework is called out.
- Look for notes about compatibility with the current game version, since mod authors often flag known issues after a patch.
- If the mod depends on another mod rather than a framework, install that dependency first too.
Skipping this step is the most common reason people end up with a broken install and no idea which mod caused it. Reading the requirements first takes a minute and saves you from guessing afterward.
Questions people ask
Do I need to install all five frameworks for every mod?
No, most mods only need one or two of them. Check the specific mod’s requirements list rather than installing everything up front.
What happens if a framework is out of date after a game patch?
The framework may fail to load, the game may crash on launch, or mods built on it may silently stop working. Update the framework to match your current game version first.
Where do framework files actually go in the game folder?
This varies by framework and version, so follow the install instructions that come with each download rather than guessing at folder names.
Is Cyber Engine Tweaks considered cheating?
It gives you an in-game console and scripting access, which some people use for tweaks and others use for cheat-like commands, but using it itself is not something that affects other players since Cyberpunk 2077 is single player.
Browse all Cyberpunk 2077 mods on CrashMods
