wopss/RED4ext

RED4ext is infrastructure for people modding Cyberpunk 2077, not a mod you install for gameplay changes. If you want to write a plugin that hooks REDengine 4, it is the documented entry point; if you just want to play with mods, it is a dependency someone else's mod may require.

The problem

A modder wants to add a new scripting function, call an existing engine function, or otherwise change game behavior beyond what the shipped scripting layer exposes. Without an extender, a plugin would have to carry its own engine bindings and loader logic, and each mod would solve the same problem differently. RED4ext changes that step: the loader manages plugins, and RED4ext.SDK supplies the reversed types and helpers used to extend the engine. The result is a plugin built against a shared interface instead of a one-off injection.

What's different

The README draws the comparison directly: RED4ext is in the same category as Script Hook V for GTA V and SKSE for Skyrim. The key design choice is the split. This repository is only the loader, responsible for managing plugins, while the SDK can be used independently. That matters if you are writing a new plugin, because the README says to add only RED4ext.SDK to your project structure. You get the engine-facing types without dragging the loader into your build, and the loader remains the piece players install to run plugins.

The trade-off is that the project does not try to be a complete modding framework by itself. It is a C++ library aimed at people comfortable working with reversed engine types; the README does not present a scripting language or a high-level content pipeline. Its usefulness is therefore proportional to whether the SDK's exposed types and helpers cover what your plugin needs. Anything not covered is still your problem, and engine internals can change with game updates, so plugin authors bear the upkeep of matching their code to supported game and SDK versions.

Who should try it

Good fit: a C++ modder with a concrete plugin idea for Cyberpunk 2077 who wants to add scripting functions or call existing engine ones without rebuilding a private engine bridge. Also a fit if you already depend on a RED4ext-based mod and want to understand what the loader is doing.

Poor fit: players looking for a ready-made gameplay mod. RED4ext is a dependency layer, and installing it alone does not change the game. It is also a poor first stop for someone who wants a no-code path to modding; the documented setup here is about installing the loader and building against an SDK, not authoring content in a visual tool. If your work can be done with the game's existing scripting facilities, adding a C++ plugin layer may be unnecessary overhead.

Requirements and limitations

Installation is documented separately at docs.red4ext.com, and building from source follows BUILDING.md; use those pages rather than improvising a layout. The README's central build rule is easy to miss: a new plugin should include only RED4ext.SDK, while the loader is a separate piece. That separation is a strength for development but means two artifacts to track in practice.

The README does not state which game versions or SDK releases are compatible, so that is the first thing to confirm for your target build before committing. Treat compatibility as an ongoing maintenance item for plugin authors, not a one-time install. The loader manages plugins but does not present itself as a general content or asset tool, and the README provides no install-time compatibility matrix.

HotRepo's take

HotRepo recorded the repository at 498 stars on both 2026-10-24 and 2026-10-25, with +19 on each of those two daily-board observations. That is a two-day sample, not a growth curve; whether interest persists cannot be judged from it. For a C++ modder on Cyberpunk 2077, the real question is whether the SDK's exposed types line up with your intended hooks, so check the SDK and its compatibility notes before investing in a plugin.