# ELI5: Validate Functionality
## Section Brief
This section is about validating the modding tools and potentially building your first mod.
Learning objectives:
* Understand how file types relate to each other,
* Identify assets with clothes in the game,
* Create and add assets to projects,
* Searching the Asset Browser,
* Understand the Project Explorer,
* Review log for activity,
* Understand the purpose of the Archive folders versus Raw folders,
* Look at assets in File Editor,
* Convert to-and-from JSON files,
* Opening files from the Asset Browser to plugins,
* Use the Import/Export tool,
* Install a REDmod type of mod,
* Look at installed mods in WolvenKit Mod Manager.
### Overview steps
1. Use the name of the game item to find the asset files in WolvenKit,
2. Find all the asset files for the item,,
3. Create the GLB and DDS file for MlSetupBuilder models,
4. Open an asset in MlSetupBuilder and change its color from green to orange,
5. Import the edited asset back into your project,
6. Install the mod,
7. Party like it’s 2077 in your new orange tank.
{% hint style="info" %}
Some of the steps below are unnecessary, but it's important to see how:
* An in-game item is used to find the ENT file,
* The ENT file is used to find the APP file,
* The APP file is used to find the MESH file,
* The MESH file is used to find the MLMASK and MLSETUP files,
* The MLSETUP file is used to find the MLTEMPLATE file,
* MLMASK file is used to find the DDS files,
* DDS file is used to find the XBM file.
Understanding this topology will help with your future mod development.
{% endhint %}
{% hint style="danger" %}
These steps get confusing. Just remember that we’re using the entity file **tshirt\_08\_old\_02\_w\.ent** to find the material layer file **t1\_080\_\_leather\_croc.mlsetup**
{% endhint %}
## Steps
1. To make sure you do not have any mod conflicts, please uninstall all Cyberpunk mods except for Material and Texture Override. This can normally be done by disabling the mods in Vortex or whatever mod managing application you use for your normal gameplay.
2. Launch Cyberpunk 2077 and either load an existing woman character, or start a new one if you have to. If you start a new game, then you'll have to play up to the scav hunt with Jackie before you can swap your clothes.
3. Once you reach a point in the game when you can change your clothes, run the Cyber Engine Tweaks (CET) command “Game.AddToInventory("Items.TShirt\_08\_old\_02",1)”. This will load Judy’s Tank in your torso inventory.
4. Wear the shirt, take a screenshot, save the game, and then exit the game. This screenshot will be your reference to compare against when you have made the edit.
5. The name of the shirt is **Secondhand Knotted Tank** and it’s an **Inner Torso** item
6. Navigate to Fandom’s Cyberpunk clothing page and find the asset name for Judy’s tank. Since we know the item is an inner torso shirt, please add #Inner\_Torso to the end of the URL. This convention works for all other items as well. If we want to find V’s Pants then you would add #Legs to the end of the URL. If you’re looking for blades, use Fandom’s menu to navigate to the weapons section Gameplay > Items > [Weapons and then add #Blade](https://cyberpunk.fandom.com/wiki/Cyberpunk_2077_Weapons#Blade) to the end of the URL. But in this case, we’re looking for Judy’s shirt.
7. Launch WolvenKit and [WolvenKit Projects](/wolvenkit/wolvenkit-app/usage/wolvenkit-projects.md#create-a-new-wolvenkit-mod-project):\
Project Name: `judys_orange_tank` \
Creation Location as `C:\Cyberpunk2077Mod\Projects`\
8. In the menu bar click on View and click on Reset Layout to make sure your screen matches the screenshots in this guide.
9. Click on the Asset Browser and search for the asset name we found on Fandom. \
Start by searching for the entire name `tshirt_08_old_02`, then start deleting characters from the end of the name until the entity (ENT) file shows up.
10. Right click the `t1_tshirt_08.ent` file and open the file without adding it to your project. \
\&#xNAN;*Notice that the file opens in the File Editor and is not listed in the Project Explorer.*
11. In the File Editor, expand appearance and locate the full asset name we found on the Fandom website. \
\&#xNAN;*Notice that in the appearances array, the name ends in “w” which stands for woman (aka “wa” which stands for woman average). Cyberpunk uses postfixes m, ma, mb, mf, w, wa, wb, and wf to describe the gender of the asset and the body type it goes to. A is average, and b and f are synonymous for big/fat. There are other postfixes, but that’s the general concept.*
12. In the File Editor, expand appearance 7 for `tshirt_08_old_02_w`. Click on the blue button for `apperanceResource` to open the APP file without adding it to the project.
13. Now that the file editor has switched to the .app file, expand the `appearances` array. \
The asset name we got from the Fandom website is **tshirt\_08****\_****old\_02**, which is a mashup of its entity name **tshirt\_08** and one of its appearance names **old\_02**. We want the woman version of that appearance, so we're looking for **old\_02\_w**. \
Expand the old\_02\_w **appearance** and expand its **components**. \
The component name will say `tank__judy`. The **meshAppearance** has a value of **leather\_croc**, and the mesh file is listed right next to it. That mesh file is used to create the GLB file that MlSetupBuilder uses to generate the tank's 3D model. \
Click on the **yellow button** for the mesh file to add it to your project, only files added to your project will show up in the Import/Export Tool.
14. In **Project Explorer**, double-click on the file, or hover your mouse cursor over the mesh file and click on the blue button to open the file in **File Editor**. \
Expand the arrays `localMaterialBuffer` > `Materials` > `leather_croc` > `values` > `0` and `1`. \
`[`**`0`**`]` contains the **.mlsetup** file, which you'll import into MlSetupBuilder to change Judy's Tank from green to orange. Click on the yellow button for the **MLSETUP** file to add it to your project.
15. Right click the **mlsetup** file.
{% tabs %}
{% tab title="With the MLSB Wolvenkit plugin" %}
Right-click on the file, and select the first menu entry, Open in MlSetupBuilde
{% endtab %}
{% tab title="Without the MLSB Wolvenkit Plugin" %}
Right-click the json file in your raw folder, and hold down the `SHIFT` key to activate the contextual menu entries, then select "Copy absolute path":
You can now click into your Windows Explorer's task bar, select or delete everything, (Hotkey: `Ctrl+A`), and paste the copied path (Hotkey: `Ctrl+V`):
{% endtab %}
{% endtabs %}
16. Over in MlSetuipBuilder (MLSB), close the developer tool, then savagely and with mercy throw more coffee at Neurolinked#4973 (the author of this guide is not Neurolinked), and then click anywhere off the Welcome popup to get into the building tool.
17. On the left side, you will see a panel with the MLSetup preview. Click the "Import" button — important, do not skip this step:\
18. Notice that the material layers loaded but not the model. Click on **Library** to bring up the frame with the available models.\
\&#xNAN;*On newer versions of MLSB, you will find the Models Library button at the top.*
If all of your layers say "(null null) unused", then you haven't imported the mlsetup correctly
19. Search for the mesh name from step 13 in MLSB's model library and select it. \
You will see an error `The searched file does not exist`. Close that error by pressing OK - MLSB will now ask you if you want to uncook the file. Click "Yes":
20. This can take a minute or two. Click on the console icon to keep an eye on the log - it should tell you when you're good to go.
21. Back in MlSetupBuilder, click the refresh button at the bottom of the screen. The model should load without errors and the multilayers display on the right.
> **Attention:** As of MLSetupBuilder 1.6.8, the model will only **highlight the affected region**. A full material preview is planned for 1.6.9.
22. Let's change material first: \
select the leather\_croc layer and then click the **Material** dropdown. Type spandex into the search box and select `spandex_clean_02_30` material.
> **Attention:** A MultilayerMask file supports 20 layers; computers start counting at 0 rather than 1. The number in the name describes the corresponding mask layer.
23. **Normals**, **Metal Out**, **Rough In** and **Rough Out** represent how light interacts with the material surface:
The hex values in the dropdown represent lookup keys - the important value is in the brackets behind it
* **Normals**: Intensity of the [normal map](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/self-made-normal-maps)
* **Metal Out**: Defines the outside of the material as diffuse with a white dielectric coating (0.0) or metallic (1.0)
* **Rough Inside**/**Rough Outside**: Sets the roughness of the surface, where 0.0 is completely smooth, and 1.0 is completely rough (wholly diffuse).
24. Set the Normals to `1.66`, Metal and Rough Inside to null, and Rough Outside to `0.3333,0.6666`.
25. Scroll down the color grid, select orange, and then click the Apply Edits button. Notice that the wording in the layer changes to match your selections.
> **Attention:** Set Opacity to 1.0 (100% visible) — the first layer does not allow transparency.
26. With the layer updated, click on `Export` (Hotkey: `Ctrl+E`). The dialogue should already show you the exported file; overwrite it.
When you click on Save, click on **Yes** to replace the existing file. There is no need to save a copy of the original, because you can repeat step 16 to re-create it.
27. Back in WolvenKit, right click on the JSON file and select the second entry to convert it back:
28. Our MLSetup is now imported (you can check the log view to sere a success message).
29. We will now **install our mod**. For that purpose, we'll use the Install and Launch button:
\
*You can also pack your mod as* [*REDmod*](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/modding-tools/redmod)*. By default, that button is hidden from the toolbar — you can re-enable it in settings. As pretty much everyone defaults to the vanilla format, we're going to do the same.*
30. This will do the following things:
1. pack your mod to the packed folder in your project directory
2. install the created .archive to [`Cyberpunk 2077`](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/the-cyberpunk-2077-game-directory)`\archive\pc\mod`
3. launch the game for you.
31. Load your saved game from step 4. How you launch the game doesn’t matter because the mod is deployed directly to the game’s install directory. Enter your inventory and you’ll notice that the tank you created in step 3 changed from green leather to orange spandex.
32. Congratulations! You have now validated that WolvenKit is deployed and setup correctly on your computer. Happy modding!
---
# 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/wolvenkit/getting-started/eli5-getting-started/validate-functionality.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.