FAQ
Common questions about updating Cyberpunk 2077 with mods installed.
Is it safe to update Cyberpunk?
It depends. Official patches from CD PROJEKT RED are safe for the vanilla game, but script and native frameworks (CET, RED4ext, redscript, ArchiveXL, TweakXL, Codeware) often break until their authors ship updates. If you use mods that depend on those frameworks, wait until this site (and the framework release notes) show support for the new patch — or block automatic Steam updates and play on your current build. We never claim certainty without evidence from release dates and notes.
Why did my mods break?
Most Cyberpunk mods that stop working after a patch fail because a core framework they require has not been updated yet. RED4ext-based plugins, CET scripts, redscript mods, and XL/Codeware mods are especially fragile across game versions. Update the frameworks first, then update dependent mods. See the official modding wiki troubleshooting guide for details.
What do the status labels mean?
Updated for latest patch: the framework's latest GitHub release notes explicitly mention the current game patch version. Likely OK: the latest release is dated on or after the patch, but notes do not name that version. Unknown / check: the latest release is older than the patch (or data is missing) — verify on GitHub/Nexus before updating.
Where does the data come from?
Game patches come from the Steam Web API ISteamNews/GetNewsForApp for app 1091500 (official community announcements). Framework versions come from the public GitHub Releases API for each project's repository. No Nexus API key is required for this MVP.