# Users: Troubleshooting Requirements
## Summary
Last documented update: January 19th, 2026 by [minnierylands](https://app.gitbook.com/u/VSIYzNHUyRPaBCk2ExHhQzpPfo82 "mention")
This page will give you an explanation of requirements ([#theory-what-is-a-requirement](#theory-what-is-a-requirement "mention")). After that, you will find a guide on debugging a dependency chain to troubleshoot a mod.
The example will use [Virtual Atelier](https://www.nexusmods.com/cyberpunk2077/mods/2987?tab=description), but the same principle applies to each and any mod.
{% hint style="success" %}
In the process of this guide, you will be told to check a certain mod's log file. If you don't know how to do that, check [finding-and-reading-log-files](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting/finding-and-reading-log-files "mention").
{% endhint %}
***
## Theory: What is a requirement?
It is something that your mod needs to work; for that reason, requirements are also called **dependencies**. The game will load them **first**.
Most of them are other mods.
{% hint style="info" %}
[Do you want to know more (about the core mods and what they do)?](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained)
{% endhint %}
### Can't I download a mod and be done with it?
Unfortunately, that is not how computers work.
### More detail
Cyberpunk 2077 offers native modding support via [redmod](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/redmod "mention"), but it is limited.
***
## Guide: Debugging a mod that's not working
Now that we've gotten the theory out of the way, let's get to the practical part. Below, you find an example of how the process will look – and after that, you find the steps to complete it yourself.
#### Example
You're trying to get **VirtualAtelier** to work. There is no log file and you want the full version, so you investigate **ArchiveXL**.
When you re-do [Level 1](#level-1-the-mod-itself), you can't find a log file for ArchiveXL either, so you look at its dependencies and find that you need **Red4ext**.
When you re-do [Level 1](#level-1-the-mod-itself) with Red4ext, you find an error in its log file that complains about **version incompatibility**. You realize that you forgot to complete [Level 2 Step 3](#level-2-the-requirements), update Red4ext, and Virtual Atelier starts working.
Rejoice!
***
## Level 1: The mod itself
### Situation
You're trying to install a mod — and it's not working. How do we fix this?
### Step 0: Open your Cyberpunk game directory
If you aren't there yet, open your Cyberpunk 2077 **game folder** ("Browse local files" in Epic/Steam/GOG). This is where you installed the game.
***
### Step 1: Try to find its log file
{% hint style="info" %}
* if you're debugging an Atelier Store, start with [Virtual Atelier ](https://www.nexusmods.com/cyberpunk2077/mods/2987)as a dependency.
{% endhint %}
1. Use the Windows Search to find a matching log file (e.g. search for the mod's name - [here](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting/finding-and-reading-log-files) are more instructions if you need them).
2. If you have found a log file, read on under [#a-log-file-exists](#a-log-file-exists "mention")
3. If you have not found one or if it contains no errors or warnings, go to [your-own-hud-icons](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/custom-icons-and-ui/your-own-hud-icons "mention")
### A log file exists
-> If you can't find one, read on under [#the-file-only-has-warnings](#the-file-only-has-warnings "mention").
#### The file is empty
This means that your mod is **loaded**, but never **initialized**. Go to [#there-is-no-log-file-or-its-empty](#there-is-no-log-file-or-its-empty "mention")
#### The file has errors
Something is wrong with the mod itself. [You can now go and troubleshoot it](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting/..#dealing-with-broken-mods).
#### The file only has warnings
Your mod is being loaded, so the dependencies are OK (if they aren't, the log file would tell you so).
Warnings in the log file don't necessarily mean that something is outright broken. But since you're here and your mod isn't working, that is probably the case. Proceed with [troubleshooting](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting/..#dealing-with-broken-mods).
### There is no log file, or it's empty
The good news: the mod itself is not the problem.
The bad news: you'll have to check its requirements.
[Let's do that now](#level-2-the-requirements): read on under [#level-2-the-requirements](#level-2-the-requirements "mention")
***
## Level 2: The requirements
### Step 1: Finding the requirements
Open the mod's Nexus page and check the **Description** tab (the first one). You will see something like this:
If you don't know if a mod is optional, it's most likely not.
***
### Step 2: Re-do Step 1 for each requirement
For each of the dependencies, repeat the following steps:
1. Check if it is **optional**.
* If there is a condition and you meet it (e.g. "if you are using Codeware" and you are using Codeware), consider it **not optional**.
2. If it's no optional, **install it**.
3. If you already have it installed, update it.
Now that you have the requirement installed, it's time to re-do [Level 1](#level-1-the-mod-itself), but do it with the **requirement**.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting/requirements-explained.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
