# Cyber Engine Tweaks: the Lua scripting layer under most Cyberpunk 2077 mods

> Cyber Engine Tweaks is an MIT-licensed C++ framework that exposes Cyberpunk 2077's internal scripting to Lua, ships an ImGui overlay, console and TweakDB editor, and requires RED4ext before it will load. Here is what it does, how to install it, and where it stops being the right tool.

**maximegmd/CyberEngineTweaks** — Cyberpunk 2077 tweaks, hacks and scripting framework

- Repository: https://github.com/maximegmd/CyberEngineTweaks
- Stars: 4,806 · Forks: 309
- Language: C++
- License: MIT
- Published: 2026-09-23 · Updated: 2026-09-23 · Language: en
- Canonical page: https://hysenlabs.com/projects/maximegmd-cyberenginetweaks

## What Cyber Engine Tweaks actually provides to a Cyberpunk 2077 install

The README describes CET as "a framework giving modders a way to script mods using Lua with access to all the internal scripting features." That sentence is the whole product. CET is not a mod in the content sense. It is the layer that other mods attach to, and its value is proportional to how many of your installed mods expect it.

Three things ship in the same package. First, the Lua binding: mods are written in Lua and call into the game's scripting internals rather than into a reimplementation. Second, a Dear ImGui interface, pinned in the README to ImGui v1.82, which gives every mod a shared place to draw windows, plus a console and a TweakDB editor for direct manipulation. Third, a set of engine patches, listed in a table in the README, that the user turns on or off in the settings menu or in config files. The README is explicit that changing them requires a game restart to apply.

The audience is narrow and specific: people who write mods, and people who run mods that depend on CET. A player who wants a different combat system or new vehicles gets nothing from CET directly. A player who installed a mod whose page says "requires Cyber Engine Tweaks" is already a CET user whether they intended to be or not.

## The patch table is a compatibility list, not a performance suite

The README lists nine patches: AMD SMT, remove pedestrians and traffic, disable async compute, disable temporal antialiasing, skip start menu, suppress intro movies, disable vignette, disable boundary teleport, and disable Windows 7 VSync. Read the descriptions carefully, because several are conditional. AMD SMT is described as being for AMD CPUs "that did not get a performance boost after CDPR's patch," which means it exists to undo a regression rather than to add speed. Disable async compute is framed as helping "older GPUs (Nvidia 10xx series for example)." Disable temporal antialiasing carries the README's own warning: "not recommended but you do what you want!"

The non-performance entries are the more interesting ones. Suppressing intro movies and skipping the start menu are pure quality-of-life. Disable boundary teleport is a gameplay boundary change: it "allows players to access out-of-bounds locations," which is the kind of switch that can put you somewhere the game never intended to render. Disable Windows 7 VSync is a niche fix for a 60 FPS cap on an operating system most players have left.

The design implication is that CET's patch list is a set of opt-in toggles for known engine annoyances, each tied to a specific hardware or platform condition. Treat it as a checklist to consult when you have a specific problem, not as a recommended configuration. Enabling all nine because they are there is not what the descriptions suggest.

## Installing Cyber Engine Tweaks and opening the console for the first time

The README's usage section gives one hard prerequisite before anything else: "You first need to install RED4ext." CET does not load on its own. Install RED4ext following its own instructions first, then place the CET files from the releases page into the game directory. The README points to the wiki for the full procedure, so treat the wiki as the authoritative install document rather than this summary.

On Linux, the README links a dedicated page titled "Usage with Proton" in the wiki. That link is the only platform note in the README, and it is a link rather than inline instructions. If you are on a Steam Deck or another Proton setup, that page is your starting point.

Once CET is loaded, the console is the entry point for everything interactive. The README does not print the key binding in the text, so get it from the wiki rather than guessing. The console accepts Lua, and the official mod examples live in the WolvenKit cet-examples repository linked from the README. A minimal mod is a Lua file that registers a callback and draws an ImGui window; the examples repository is where the working skeleton lives, and copying it is faster than reconstructing it from the API.

For debugging, CET exposes development options in the same settings area as the patches. The README lists four: Draw ImGui Diagnostics Window, Remove Dead Bindings, Enable ImGui Assertions, and Debug Menu. The diagnostics window is described as showing "what is going on behind the scenes (good for mod debugging)." The assertions option comes with the README's own instruction: "use this option to check mods for errors before shipping!" If you are writing a mod, that pair is what you turn on first.

```bash
# Prerequisite per the README: install RED4ext first, then CET from the releases page.
# The README does not document a command-line installer; files are copied into the
# Cyberpunk 2077 game directory and the game is restarted.
```

The commands above are deliberately a comment block, because CET has no package manager, no CLI installer and no documented shell entry point in the README. Installation is file placement plus a game restart. Anyone telling you otherwise is describing a different tool.

## Where Cyber Engine Tweaks is the wrong tool

The clearest limitation is the dependency chain. CET requires RED4ext, and CET mods require CET. That is two layers of third-party code between the game executable and the mod you actually wanted. When the game patches, any layer in that chain can break, and CET's own release history shows the pattern: v1.36.0 is tagged "Patch 2.3" and v1.37.0 is tagged "Patch 2.31." The version tag tells you which game patch it targets. Running a CET build against a game patch it was not tagged for is the failure mode the tags exist to prevent.

Second, the patch toggles are coarse. They are global switches applied at startup, not per-session or per-mod settings, and the README states a restart is required. If you want to compare a run with and without a patch, you are restarting the game each time.

Third, CET gives you an editor and a console, not a safety net. The TweakDB editor and the console let you change game state directly. The README does not document rollback, undo, or a sandbox for console commands, and it does not document save-file validation. If you change something through the console and save, the README offers no statement about what happens next. That silence is worth taking seriously before you experiment on a save you care about.

Finally, if your goal is a curated mod collection with conflict resolution, CET is not that. It is a runtime and a scripting API. Load order, conflicts and content curation are somebody else's problem.

## How CET differs from RED4ext, and why the distinction matters

The most useful comparison is the one the README forces on you: CET against RED4ext. They are not competitors so much as layers, and confusing them is the most common way to end up with a non-working install.

RED4ext is the prerequisite. The README says to install it first, and CET does not function without it. RED4ext's job is to load native plugins into the game. CET is one such plugin, and a large one: it carries the Lua runtime binding, the ImGui overlay, the console, the TweakDB editor and the patch table.

The practical difference shows up in what each one gives a mod author. A RED4ext plugin is written in C++ and compiled against the game's native interfaces. A CET mod is written in Lua and calls the scripting API that CET exposes. If you are writing Lua, you want CET. If you are writing a native plugin, you want RED4ext and you may not need CET at all. If you are only installing mods, you need to read each mod's requirements, because some want one, some want the other, and some want both.

The second real alternative is not installing any of this. Cyberpunk 2077's own settings cover a subset of what CET's patch table does, and the game has shipped its own fixes over time, which is exactly why CET's AMD SMT patch is scoped to CPUs that "did not get a performance boost after CDPR's patch." For a player with no interest in scripting and no mods that declare CET as a dependency, the correct number of CET installs is zero.

## Maintenance, licensing and what you are signing up for

The repository is MIT licensed, and the README restates that in its contributing section: contributions should not use code that is not yours "unless the license is compatible with MIT." There is also a ThirdParty_LICENSES file at the top level, which is where the bundled dependencies' terms are recorded. MIT is permissive, so redistributing CET inside a mod pack is not obviously blocked, but the bundled third-party components carry their own terms and the ThirdParty_LICENSES file is the place to check them. That is a factual pointer, not legal advice.

The maintenance picture is mixed and worth stating plainly. The last push to the default branch was on 2026-05-09. The most recent release listed is v1.37.1 from 2025-09-28, with v1.37.0 tagged for Patch 2.31 and v1.36.0 tagged for Patch 2.3. So there is commit activity on master more recent than the newest tagged release. The README's own claim is that CET "tracks the current release of Cyberpunk 2077 closely," and the version tags are the mechanism by which that claim is made checkable.

Upgrade cost is the part people underestimate. A CET update is not a background patch. You replace files in the game directory, restart, and then find out whether the mods you run still bind. The development option Remove Dead Bindings exists precisely because mods fail to load and leave bindings behind, which tells you the maintainers expect that to happen. Budget for a re-test of your mod list after every CET update, not just for the download.

## Conclusion

Adopt Cyber Engine Tweaks if you are writing Lua mods against Cyberpunk 2077's scripting API, or if the mods you already run declare it as a dependency; it is the runtime those mods bind to, not an optional extra. Do not adopt it if you want a curated mod list or a gameplay overhaul, because CET itself only patches a fixed set of engine behaviours and exposes tooling; the actual content comes from other mods. Before installing, verify that RED4ext is present in the game directory, that your CET build matches your game patch (v1.37.0 is tagged for Patch 2.31, v1.36.0 for Patch 2.3), and that your distribution is covered, since the README's only platform note is a separate Proton page for Linux. If the console does not appear in game, check the development option that toggles the ImGui diagnostics window before you file anything.

## FAQ

### How do I install Cyber Engine Tweaks for Cyberpunk 2077?

Install RED4ext first, which the README states as a prerequisite, then place the CET files from the releases page into the game directory and restart the game. The README points to the wiki for the full procedure, and to a separate wiki page titled Usage with Proton for Linux setups.

### How do I use the Cyber Engine Tweaks console in game?

CET ships a console alongside its ImGui interface, and the README directs users to the wiki for usage and configuration. The README does not print the key binding in its text, so the wiki is where the binding and the console workflow are documented.

### I can't open Cyber Engine Tweaks. What can I do?

Check that RED4ext is installed, since the README lists it as the prerequisite before CET will load. If it still does not appear, the README's development options include Draw ImGui Diagnostics Window, which it describes as showing what is going on behind the scenes and as good for mod debugging.

### How do I use Cyber Engine Tweaks on a Steam Deck or Linux?

The README links a wiki page called Usage with Proton, which is its only platform-specific note. It does not give inline Linux instructions, so that page is the starting point rather than the README text.

### How do I use Cyber Engine Tweaks commands?

Commands go through the console that CET ships alongside its ImGui interface, and the README points to the wiki for usage and configuration. The README does not list individual commands, so the wiki and the WolvenKit cet-examples repository are where the concrete syntax lives.

## Sources

- [Issues](https://github.com/maximegmd/CyberEngineTweaks/issues)
- [License: MIT](https://github.com/maximegmd/CyberEngineTweaks/blob/master/LICENSE)
- [maximegmd/CyberEngineTweaks on GitHub](https://github.com/maximegmd/CyberEngineTweaks)
- [README](https://github.com/maximegmd/CyberEngineTweaks/blob/master/README.md)
- [Releases](https://github.com/maximegmd/CyberEngineTweaks/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/maximegmd-cyberenginetweaks