- Prepare Cyberpunk 2077 Having the correct frameworks and paths is essential for mods to work.
- Some mods integrate well with Vortex, but many require careful manual installation.
- Mods like Wilson's Range, Preem Scopes, or Hidden Gems depend on placing files in very specific folders.
- Combining multiple mods requires organization, checks, and attention to compatibility after each patch.
If you're wondering how to install mods in Cyberpunk 2077 without messing things up, whether manually or using Vortex, here you'll find a complete, clear guide designed for the current version of the game with Phantom Liberty. We'll cover what you need to install first, how to prepare the game, the difference between manual mods and those managed by a mod manager, and how to get specific mods working, such as Wilson's Range, Preem Scopes, Hidden Gems, or "mod-of-mods" compilations.
Many players encounter the same problem: they download the mods, extract them , launch them with Vortex, or copy them manually, but absolutely nothing happens in the game. This is usually due to a missing basic framework, an incorrect installation path, or the mod not being compatible with the current version of Cyberpunk 2077. We'll go step by step, calmly and in detail, so you understand what each step does and can have your Cyberpunk fully ready to experiment with mods without fear.
Prerequisites before installing mods in Cyberpunk 2077
Before you start copying files like crazy, it's essential to prepare your Cyberpunk 2077 installation to accept mods without problems, especially if you're on version 2.31 with Phantom Liberty.
Check the game version
The first thing to do is make sure you're actually playing Cyberpunk 2077 v2.31 (or a very close and current version). Every major patch has broken or changed how many mods work, so:
- En Steam, GOG or Epic, open the game properties and check the information tab or the game's home screen.
- Keep in mind that if your version doesn't match the one supported by a mod, It may not work or may cause errors..
Back up your installation and saved games
Although it might seem a bit tedious, making a backup is key to avoiding problems if a mod breaks something.
- Copy the game's installation folder (at least the subfolder) r6 y archive) to another disk or folder.
- Save your saved games, which are usually in the user folder (Documents or similar depending on the platform).
This way, if a complicated mod or a "mod of mods" compilation causes the game to not even start , you can restore the original folder without having to reinstall everything.
Disable conflicting overlays and tools
Some problems attributed to mods actually originate from overlays and external tools (such as certain graphics card OSDs, capture tools, or injectors). To reduce risks:
- Disable overlays from Steam, GOG Galaxy, Discord, GeForce Experience, etc., at least while testing new mods.
- Avoid mixing other injectors (for example, very old ReShade) with modern Cyberpunk frameworks if you are not sure how they work together.
Essential frameworks and basic tools for mods
The vast majority of modern Cyberpunk 2077 mods don't work on their own; they rely on frameworks that extend the game and allow mod scripts to run correctly. Without these foundations, many graphics, weapon, or interface mods simply won't function.
REDmod: CDPR's official modding system
CD Projekt RED offers REDmod , which is the official modding system integrated with Cyberpunk 2077. It's important to understand what it does and how it affects the game:
- REDmod allows for a more integrated way of loading mods, especially those that add or alter content such as audio files, scripts, and resources.
- On Steam or GOG you can install REDmod as DLC or an additional tool; it's advisable to have it enabled if you're going to use mods that require it.
- Some classic mods still use the "legacy" file system in the folder archive/pc/modwhile others adapt to the REDmod scheme.
Many authors clearly indicate whether their creation requires REDmod or if it is installed using the traditional method; reading that part of the mod description is absolutely key to avoiding problems.
Cyber Engine Tweaks (CET)
One of the cornerstones of modding in Cyberpunk is Cyber Engine Tweaks (CET). It's practically a de facto standard because it provides:
- An in-game console to run commands.
- Support for Lua scripts and other advanced settings.
- Options to modify game performance, interface, and behavior.
Many mods that add advanced features, custom UI, or gameplay scripts require Cyber Engine Tweaks (CET). It's usually installed by copying its files to the game's main folder and is updated with each major patch. If a mod says "Requires Cyber Engine Tweaks," you need to have the CET version compatible with your game build.
RED4ext, ArchiveXL and other common components
Besides REDmod and CET, there are other very common frameworks that are considered almost essential in a modern modded installation of Cyberpunk 2077:
- RED4ext: a component that extends the functionality of the engine and that many mods use as a dependency.
- ArchiveXL: makes it easy to add new elements to the game without overwriting vanilla files, very useful for extra content.
- Other additional modules that you will see mentioned in Nexus Mods as requirements, depending on the type of mod you want to use.
Whenever an author marks these resources as required, you must install them before attempting to load the mod that needs them.
Installing mods with Vortex: advantages and limitations

Vortex, Nexus' mod manager, allows for fairly automated installation , but it's not perfect for all Cyberpunk 2077 mods. Some authors still recommend manual installation, especially for complex or very recent mods.
Basic Vortex configuration for Cyberpunk 2077
For Vortex to properly manage Cyberpunk mods, you need to correctly configure the game path and deployment folders :
- In Vortex, add Cyberpunk 2077 as a managed game, indicating the correct path to the executable.
- Select the deployment method (symlink, hardlink, etc., depending on what Vortex recommends for your drive) and make sure it points to the actual game folder.
- Check in the mods view that when you install one, Vortex marks it as enabled and deployed, without critical conflicts.
Some mods, even those on Nexus, include a note like " Manual installation recommended " in their description. This isn't by chance: sometimes the folder structure or file type doesn't quite match how Vortex tries to deploy it.
When Vortex doesn't work: the case of Preem Scopes
A very common problem is installing a mod like Preem Scopes from Vortex and finding that, once in the game, you don't notice any changes. This usually happens for several reasons:
- The mod version is not compatible with your game version.
- Missing dependencies (for example, a framework like CET or RED4ext).
- Vortex has deployed the files in a wrong or incomplete route.
In these cases, many players choose to follow the author's recommendation and proceed to manual installation , verifying for themselves that the files end up in the exact folders that the mod requires.
Manual installation of mods in Cyberpunk 2077
Manual installation might seem daunting at first, but it actually gives you complete control over where each file goes . Furthermore, it's exactly what several authors recommend for mods like Wilson's Range, Preem Scopes, Hidden Gems, and certain mod collections.
Basic installation paths in the game directory
Although each mod may have its own structure, most manual mods for Cyberpunk 2077 share some key paths. It's important to familiarize yourself with them to know where everything should go.
- archive/pc/modThis is where many "legacy" mods usually go, especially .archive packages with modifications to textures, weapons or visual content.
- r6/scripts: is the usual place for scripts that extend game functionality.
- r6/config or other subfolders of r6Some mods include configuration or tuning files that go here.
- bin/x64 or similar: certain frameworks or executables associated with the mod can be placed alongside the game executable.
When you extract a mod, it usually comes with a folder structure that, when compared to the game directory, tells you where to copy each item . You must follow this hierarchy exactly.
General step-by-step guide to manually installing a mod
Although each specific mod may vary, the most common manual procedure can be summarized in a few very clear steps that should be followed carefully to avoid errors and duplicates :
- Download the mod file from Nexus (or the author's page) and save it in a temporary folder.
- Unzip the file using a tool like 7-Zip, WinRAR, or similar.
- Open the resulting folder and locate the main structure (you will usually see folders like archive, r6, bin, etc.).
- Open the Cyberpunk 2077 installation directory in another window.
- Drag or copy the mod folders onto the game's root folder, so that merge the routes (for example, the contents of the mod's archive/pc/mod folder must end up in the game's archive/pc/mod folder).
- If it asks if you want to merge folders, say yes; but if it asks if you want to overwrite specific files, double-check what you're replacing.
After this, when you start the game you should notice the effect of the mod if everything has been placed correctly and there are no serious conflicts.
Manual installation of specific mods: Wilson's Range, Preem Scopes, and Hidden Gems
Let's now focus on how some specific mods that are frequently mentioned by the community are usually handled, which often recommend manual installation instead of Vortex : Wilson's Range, Preem Scopes and Hidden Gems, as well as larger builds.
Wilson's Range: Weapon and Range Mods
Wilson's Range -type mods typically modify weapons, stats, or gunsmith-related elements, so they usually include:
- .archive files that should go in archive/pc/mod.
- Possible scripts or configurations in r6/scripts o r6/config if they add extra mechanics.
In many cases, the mod authors strongly recommend following a manual process because this ensures that the changes are applied to the exact files they need, preventing Vortex from unexpectedly reordering priorities . If you have already extracted the mod, simply locate the archive folder within the contents and copy it as is to the game's root directory, making sure the .archive files end up in the correct subfolder.
Preem Scopes: sights and visual elements
The common problem with Preem Scopes is that, even when installed with Vortex, no changes to the sights or optics are visible in the game. Often, the most reliable installation method is:
- Manually extract the mod.
- Copy the resulting .archive files to archive/pc/mod of the game.
- Check if the author specifies the need for a framework (such as CET or another) and make sure you have it installed beforehand.
If Vortex isn't working with this mod, the best solution is to disable it in Vortex , delete any deployed files (to avoid duplicates), and then follow the manual installation guide. Sometimes the problem arises because the mod was designed with the classic system, and Vortex tries to treat it as a REDmod when it isn't.
Hidden Gems: Hidden content and world settings
Hidden Gems -type mods typically alter locations, hidden content, or world elements that are unlocked in specific ways. These types of mods can mix textures, scripts, and game data, so it's vital to:
- Follow exactly the route indicated by the author in the mod description.
- Pay attention to whether it requires RED4ext, ArchiveXL or any other additional module.
- Verify that your game version is compatible, as internal changes between major Cyberpunk patches can greatly affect this type of content.
If the author specifies a manual installation, copy all the provided folders, respecting their structure. If you see files located in both r6 and archive , ensure they end up in the exact subfolders of the game directory to prevent unexpected behavior or crashes.
Mod packs and “mod of mods”: how to handle them without breaking the game
Mod bundles, also known as "mod of mods," can be very tempting because they promise a complete and pre-configured experience. However, they are also more complicated to install because:
- They group together many different mods, each with its own dependencies.
- They may demand very specific versions of Cyberpunk and the base frameworks.
- If something goes wrong, it's more difficult to know. which specific component is causing the problem.
For these types of packs, following the author's guide is essential. Manual installation is usually recommended, often including very detailed step-by-step instructions, and they emphasize the need to have components like REDmod, CET, and other auxiliary extensions installed beforehand.
Verify that the mod is working correctly
Once everything is installed, both manually and with Vortex, it is important to verify that the mod is actually active and has not been left in limbo.
In-game signals
Depending on the type of mod, there are different ways to check its functionality :
- If it's an interface mod, look for it. new menus, indicators, or visual changes in the UI.
- If it affects weapons like Preem Scopes or Wilson's Range, check your inventory and the gunsmith shop for any new options, sights, or stat changes.
- If it's a Hidden Gems-type content mod, explore the areas the author mentions, or check for new entrances or collectibles.
When the mod includes its own menu linked to Cyber Engine Tweaks , you'll usually have a key combination to open the overlay and check if the script has loaded correctly. If the mod panel appears, it's a good sign that the scripting part is working properly.
Review of logs and error messages
If you see error messages on the screen when you start the game, or if it simply closes on its own, it's a good idea to check the log files created by CET and other frameworks. These often contain clues such as:
- “Missing dependency…” indicating that a base framework is missing.
- Version errors, warning that the mod was made for a different build of the game.
- Conflicts between two scripts that attempt to modify the same function.
While you don't need to be a programmer, reviewing these logs can help you locate and uninstall the problematic mod instead of blaming the rest.
Best practices when combining multiple mods in Cyberpunk 2077
When you start adding mods like Wilson's Range, Preem Scopes, Hidden Gems and some "mod of mods", it becomes key to maintain a certain order and method to avoid turning Night City into an unstable chaos.
Install and test the mods one by one.
Even if you're eager to see everything working, it's best to install one mod at a time and test the game for a few minutes before adding the next one:
- Install a mod, run the game, and check that there are no crashes or strange behavior.
- If everything goes well, add the next mod and repeat the process.
- That way, if something goes wrong, you'll know clearly. Which mod was the last one added? and you'll be able to focus on him.
This system saves a lot of diagnostic time when, instead of one or two mods, you have a fairly large collection.
Keep a list of what you have installed
It is highly recommended to keep a short list (in a notepad or document) of all the mods you have incorporated , where you downloaded them, and if they depend on anything else:
- Write down the mod name and version.
- Indicate whether you installed it with Vortex or manually.
- Note the dependencies: CET, RED4ext, ArchiveXL, etc.
In the future, if a game patch breaks part of the modding, you'll know what things to update, disable, or uninstall first , instead of blindly deleting folders at random.
Update frames and mods carefully after each game patch
Following a major update to Cyberpunk 2077, many mods and frameworks become temporarily outdated. The wisest course of action is:
- Waiting for authors of CET, RED4ext, ArchiveXL and others publish compatible versions.
- Update the base frameworks first.
- Check the page for each critical mod (such as Preem Scopes or Hidden Gems) to see if they are already compatible with the new version.
If you update the game and then try to run a stack of old mods without checking compatibility, you're very likely to encounter unexpected crashes, errors, or features that stop working for no apparent reason.
With all of the above in mind, preparing Cyberpunk 2077 for mods on PC, especially version 2.31 with Phantom Liberty, involves understanding the essential frameworks , knowing when to use Vortex and when manual installation is preferable, and grasping the game's folder structure to place each file correctly. By following these principles and respecting each mod author's specific instructions, you can enjoy mods like Wilson's Range, Preem Scopes, Hidden Gems, and entire collections without crashing the game, maximizing the potential of Night City with a stable, customized installation tailored to your play style.
Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.