Cyberpunk mods work when every file reaches its own layer.

Prepare the baseline

1. Confirm a legitimate, fully updated game launches and loads a save without mods.
2. Back up saves and record storefront, game version, expansion status, and install folder.
3. Choose a supported manager or a manual workflow. The REDmodding community recommends a manager for beginners because manual folder placement is error-prone.
4. Read the mod's requirements recursively. A visible clothing or gameplay mod may depend on multiple frameworks that have their own version requirements.
5. Install and test core frameworks before optional content. Do not install every “popular requirement” unless your chosen mods actually require it.

Read the package structure

• REDmod: place the named package folder under Cyberpunk 2077/mods; it normally includes info.json. Enable mods in the launcher and allow deployment.
• Legacy archive: .archive and related XL files commonly belong under archive/pc/mod, preserving the archive/pc/mod structure included by the author.
• redscript: .reds files commonly live under r6/scripts.
• TweakXL or RED4ext tweaks: .tweak or .yaml content commonly lives under r6/tweaks.
• Cyber Engine Tweaks: Lua mods belong inside the documented CET plug-in mod structure, not directly in archive/pc/mod.
• Engine configuration: author-provided INI changes may live under engine/config/platform/pc. Back up configuration and do not merge unknown “performance tweaks” blindly.

These are recognition patterns, not permission to ignore a mod's readme. If the archive has an extra wrapper folder or offers REDmod and legacy choices, follow the author's current installation page.

Update and failure recovery

1. After a game patch, check framework project pages first. A broken core dependency can make dozens of content mods appear broken.
2. Disable or purge manager-controlled mods before manually deleting files.
3. Test the game with current core frameworks only. Then restore archive, r6, bin, and other optional layers one group at a time.
4. Use a binary search within the failing folder when the group is large.
5. For REDmod deployment trouble, force a documented redeploy rather than duplicating files between REDmod and legacy locations.
6. Remember that verifying game files may restore originals but leave third-party files in place. A clean reset must account for added folders.