ModSafe

Games › Cyberpunk 2077

Cyberpunk 2077 key art

Is it safe to update Cyberpunk 2077?

Likely safe for Patch 2.31

Script and native frameworks (CET, RED4ext, redscript, ArchiveXL, TweakXL, Codeware) usually break on every official patch until their authors ship updates.

Verdict for Patch 2.31

Likely safe

No breakage evidence for Patch 2.31: redscript, TweakXL have no release that names the patch, but there are post-patch releases or no breakage reports since. Probably fine; skim the notes.

Latest patch
Patch 2.31
Released
2025-09-11
Source
Patch 2.31
Data refreshed
2026-10-15 (UTC)

Core frameworks & loaders

FrameworkStatusLatest releaseReleasedLink
Cyber Engine Tweaks Safe v1.37.1 2025-09-28 Source
RED4ext Safe v1.30.0 2026-03-09 Source
redscript Likely safe v0.5.31 2025-08-28 Source
ArchiveXL Safe v1.27.4 2026-10-05 Source
TweakXL Likely safe v1.11.4 2026-07-28 Source
Codeware Safe v1.20.5 2026-09-20 Source
Why these statuses?
  • CET: Latest release is on/after patch Patch 2.31; an earlier post-patch release (v1.37.0) explicitly mentioned that version.
  • RED4ext: Latest release is on/after patch Patch 2.31; an earlier post-patch release (v1.29.0) explicitly mentioned that version.
  • redscript: Latest release predates patch Patch 2.31; compatibility is unverified — check the project page. No open breakage reports 399 days after the patch.
  • ArchiveXL: Latest release is on/after patch Patch 2.31; an earlier post-patch release (v1.26.0) explicitly mentioned that version.
  • TweakXL: Latest release is newer than patch Patch 2.31, but notes do not explicitly mention that version.
  • Codeware: Latest release is on/after patch Patch 2.31; an earlier post-patch release (v1.18.0) explicitly mentioned that version.

Statuses are inferred from public release data (Steam news, GitHub, Thunderstore, Mojang/Fabric/Forge/NeoForge/Modrinth APIs). They are not guarantees — verify on each project's page before updating. Items marked “Check manually” are not counted in the verdict.

Patch-day alerts

Get patch-day alerts: know if your mods survived before you update.

Form not loading? Subscribe on beehiiv →

Cyberpunk 2077 modding FAQ

Is it safe to update Cyberpunk 2077 with mods?

Current verdict: Likely safe. No breakage evidence for Patch 2.31: redscript, TweakXL have no release that names the patch, but there are post-patch releases or no breakage reports since. Probably fine; skim the notes. Latest patch tracked: Patch 2.31 (2025-09-11).

Why do Cyberpunk 2077 mods break after a patch?

Script and native frameworks (CET, RED4ext, redscript, ArchiveXL, TweakXL, Codeware) usually break on every official patch until their authors ship updates.

Which Cyberpunk 2077 frameworks does ModSafe track?

Automatically: Cyber Engine Tweaks, RED4ext, redscript, ArchiveXL, TweakXL, Codeware.

What do the status labels mean?

Safe: a release explicitly supports the current patch (release notes, the maintainer's official page, or a stable build for that game version). Likely safe: a release is dated after the patch but doesn't name it, or the patch is over a week old with no breakage reports on the project's issue tracker. Just patched, wait: the patch is under 7 days old and the framework hasn't updated. Breakage reported: open issues report the framework broke after the patch. Not ported yet (Minecraft): no build exists for that version. Not affected by patches: version-agnostic tools such as mod managers or generic loaders; they don't count toward the verdict.

Where does the data come from?

Game patches come from official Steam announcements (app 1091500). Framework data comes from public release APIs (GitHub, Thunderstore, Fabric/Forge/NeoForge meta, Modrinth). ModSafe does not scrape Nexus Mods or SteamDB.

Patch history → · JSON → · Modding resources →