Cyberpunk 2077 Update 2.5 Mod Compatibility: What Broke, What Is Fixed, and What Is Still Waiting

The patch changed what the script frameworks hook into, so the old framework builds stopped working at once. Community fix guides from launch week describe the same sequence: outdated RED4ext and Cyber Engine Tweaks files in bin and x64, stale r6/cache and r6/scripts directories, and a game that flatlines on startup or closes seconds after starting. The community response was fast and explicitly temporary: unofficial 2.5 builds of RED4ext, ArchiveXL, and TweakXL circulated within days, with instructions to set the unofficial versions to win in Vortex. The modder notes page that hosted them is equally explicit about the end of that phase: on October 24, 2026, it announced the page was retired because the official 2.5 updates were out, removed the unofficial builds as promised, and told players to install the official versions. Any guide, video, or collection still pointing at an unofficial 2.5 build is describing a phase that ended on October

24. Do not follow it.

Two further breakage classes arrived with the same patch, and both are still worth knowing even though the frameworks are fixed. First, a script mod that is itself incompatible with 2.5 does not fail alone: a REDScript compilation failure turns off all script mods, and the fix is to move the mods named in the error message out of r6/scripts. Second, 2.5 tightened tolerance for custom head mods: a face shape file that does not match its head model now leaves V spiky or exploded, and the only fix is removing that mod until its author updates it. One symptom is not breakage at all: a big empty space in mirror customization is a 2.5 game bug that happens in the unmodded game too, so do not chase it as a mod conflict.

The practical meaning of that timeline is simple: any mod page whose newest file predates October 22, 2026, was written for a game that no longer exists in that form, unless its page names 2.5 support that was somehow already true. Conversely, a file dated October 25, 2026, is not automatically safe either: Night City Alive Lite 2.3.1 is dated October 24, 2026, and is explicitly a temporary build with enhanced reactions switched off. Date plus description together make the verdict; neither alone does.

The waiting list is not a quality judgment. Several of these mods are among the most endorsed in the game, and their authors may update them at any time; the statement here is only that, as of October 31, 2026, their pages do not give 2.5 evidence. JB Third Person Mod, newest build V133 from July 2025 for update 2.3, with no mention of 2.31. Let There Be Flight, version 0.3.18 from September 13, 2026, labeled for 2.31. Better Loot Markers, version 1.4.0 from March 2026, updated for patch 2.31. Stealth Finishers, page listing patch 2.31, with an author note that game updates almost never break it once frameworks update; that note is not a 2.5 file. Time Dilation Overhaul, version 2.36 from October 19, 2026, predating update 2.5. The GHXST PROTOCOL quickhacks and cyberware, pages stating tested on 2.31, with the author stating patch 2.5 broke the RED4ext plugins they need and advising to stay on 2.31 until those update. Appearance Change Unlocker preset manager ACU and PhotoMode-EX, pages listing 2.31. Browser Extension, latest file notes stating built for 2.3 and working with 2.31. Blur Begone, version 2.5.0 from October 22, 2026, whose changelog warns to expect it to break with update 2.5, so it is waiting for a fix, not for a first update. Untrack Quest Ultimate, version 3.5.2 from October 25, 2026, first file since update 2.5 but listed for game version

2.x, not 2.5 by name, so it stays on watch.

Stale advice is its own waiting-list trap. The GHXST PROTOCOL advice to stay on 2.31 was correct on October 23, 2026, when the official plugin updates were not yet all out, and it became outdated as those updates landed on October 24 and

25. The same applies to every launch-week guide that still points at unofficial builds or tells you to wait for frameworks that have already shipped. When advice and dates disagree, believe the dates, then recheck the mod page itself.

Console compatibility does not follow the PC timeline at all, because console mods do not use the PC frameworks. The in-game mod.io catalogue is curated: only mods prepared for cross-platform support and cleared for a specific console appear, and availability can differ between consoles, so the platform labels on each mod page are the authority. At launch on PlayStation 5 there were 52 mods, including new quests, romance enhancements, quality-of-life mods, and fixes; CD PROJEKT RED describes more becoming available over time. The Switch 2 version of update 2.5 follows later, so Switch 2 console-mod availability was not part of the launch list. The achievement rule is written for console: modded saves are marked with a dedicated icon in the Load Game menu, and achievements and trophies cannot be earned while playing on console from a modded save file. Do not carry that rule over to PC, and do not carry PC mod expectations over to console: they are two catalogues that happen to share one update number.

Only if a mod you cannot play without is still waiting and its author has not updated it. The framework story is over: the official 2.5 releases are out, and the October 25 content wave covered most major mods. Staying on 2.31 keeps the old list intact but forfeits dual-wielding, the new quests, Glamdoc customization, and console mod support, so weigh one waiting mod against the whole update.

Usually, if every mod in the list has its own 2.5 file and you update the frameworks first. Read each overhaul migration note first: Dark Future, for example, requires uninstalling version

2.x completely before installing 3.0.0, after which a save that ran

2.x can carry on. Back up the save before you try, and test on a copy, not the original.

A collection is only as current as its last update and its own stated game version. Collections published around October 25, 2026, targeting 2.5 are a reasonable starting point, but they bundle hundreds of mods whose individual pages you still have not checked, including adult-content and wardrobe packs that this article deliberately does not recommend by name. Treat a collection as a shopping list to verify mod by mod, not as a verified list.