# ArchiveXL: body mods and refits
## Summary
**Published:** ?? by [mana vortex](https://app.gitbook.com/u/NfZBoxGegfUqB33J9HXuCs6PVaC3 "mention")\
**Last documented update:** April 21 2025 by LadyLea\
**Minimum required ArchiveXL version:** 1.5
This page explains how to enable **body mod support** in ArchiveXL:
[#body-modders-adding-support](#body-modders-adding-support "mention")
[#clothing-mods-making-use-of-the-tags](#clothing-mods-making-use-of-the-tags "mention")
To learn more about body mods, check the [Texture Frameworks for Player V](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/npcs/custom-tattoos-and-scars/converting-between-tattoo-frameworks) page.
{% hint style="info" %}
**NOTE**
The past method of adding the components to each individual appearance [does still work](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained/archivexl/archivexl-body-mods-and-refits/archived-registering-the-body-tag). However, you'll want to use the new method (for version >= 1.14), since it is both more robust and less tedious.
{% endhint %}
## Checking the current body
Run the following code snippet in CET to see which body is currently installed:
```
print(Game.GetScriptableSystemsContainer():Get("PuppetStateSystem"):GetBodyTypeSuffix(ItemID.new(), GetPlayer(), nil))
```
## Body modders: Adding support
{% hint style="success" %}
Starting with version **1.14**, you can use [archivexl-resource-patching](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained/archivexl/archivexl-resource-patching "mention") to inject your tags into the existing files!
You can download the [template from Nexus](https://www.nexusmods.com/cyberpunk2077/mods/14793), or create one yourself.
{% endhint %}
### 1. Registering the body mod
1. Create an .xl file in your Wolvenkit Project's resources folder (File -> New file -> ArchiveXL)
2. **Optional**: Name it the same as your current project (e.g. boobs\_for\_back\_problems.archive.xl)
3. Put the following file content:
player:
bodyTypes: [ NewBody ] # for substitutions, this will be converted
# to snake case: new_body
### 2. Patch the player entity files
We'll make use of [archivexl-resource-patching](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained/archivexl/archivexl-resource-patching "mention") for this.
#### Set up the patch .ent
If you downloaded the template project, a patch .ent will already be included.
Create your own patch .ent
1. In Wolvenkit, select File -> New File
2. Scroll down the menu until you find the one with the extension `.ent` (should be EntEntityTemplate)
3. Add a new, blank EntEntityTemplate to your project
4. Give it a good name and move it somewhere
5. Open the file and select the `components` array
6. Add a new `entMeshComponent` and name it `Body:YourBodyTag`
7. Now, proceed with the rest of the guide
1. Inside the patch .ent, find the `entMeshComponent` under the `components` array.
2. Change its `name` to match your body mod, e.g. `Body:BoobsForBackProblems` -> `Body:NewBody`
#### Register the patch .ent
Make sure that your patch .ent is added to the game by telling ArchiveXL about it. Add the following block to your `.xl` file:
```yaml
resource:
patch:
path\to\your\patch_file.ent:
- !include player_wa.ent
- !include player_ma.ent
```
Include only the relevant body gender!
### 3. Test
That's it, everything should work now! Let's test.
1. [Install your project](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/menu/toolbar#install-and-launch)
2. Launch the game and load into a save
3. [check if the body tag registers](#checking-the-current-body-mod) by running the CET command.
If yes: Congratulations, you've made it much easier for people to add refits for your body!
### Troubleshooting
#### General errors
The process is so simple that there aren't many things to go wrong:
1. Update [ArchiveXL](https://www.nexusmods.com/cyberpunk2077/mods/4198?tab=files)
2. Double-check your `.yaml` via [yamllint](https://www.yamllint.com/) and make sure you don't have syntax errors (indent matters)
3. Check [ArchiveXL's log file](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting/finding-and-reading-log-files#a-list-of-framework-logfiles)
If that doesn't work, check if the component gets added correctly. There are two ways to do this:
#### CET:
```
print(GetPlayer():FindComponentByName("Body:NewBody"))
```
#### [RedHotTools](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/modding-tools/redhottools):
If that still doesn't work, consider using the [template from Nexus](https://www.nexusmods.com/cyberpunk2077/mods/14793), which has been tried and tested on May 18 2024 with ArchiveXL
#### Invisible mesh for body xyz
Make sure that your mesh has appearances and materials. If you are using [archivexl-resource-patching](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained/archivexl/archivexl-resource-patching "mention"), it's easy to forget a new body's mesh in the list like a gonk. This has never happened to the author, by the way.
## Clothing mods: Making use of the tags
### The problem
Even with the [AKL AutoRefitter](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/modding-tools/wolvenkit-blender-io-suite/wkit-blender-plugin-akl-autofitter), the process of supporting body mods is tedious. And even worse: you then have to pack everything separately for Nexus:
Realistic refitting experience
### The Solution
If a mod supports **body tags**, ArchiveXL can detect the current body mod, and conditionally load the correct mesh. Now, everything can be put into a single .archive!
### Dynamic Appearances
If you're using [dynamic appearances](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained/archivexl/..#dynamic-appearances), you don't need to register a suffix and can simply match or substitute for the body tag:
```
appearance name:
t0_recoloured_netrunner_suit&body=new_body
substitution:
*my\mod\meshes\p{gender}a_netrunning_suit_{body}.mesh
```
{% hint style="warning" %}
If no body mod is installed, the value will be `base_body`, so make sure to name your files and folders accordingly!
**NOTE**: `base_body`is also meant for body mods that are vanilla based shaped - for instance [EVB](https://www.nexusmods.com/cyberpunk2077/mods/11489) and [VTK Vanilla HD FemV](https://www.nexusmods.com/cyberpunk2077/mods/7054)
{% endhint %}
### Suffixes
If you're sticking to the classical approach, you need to add the following lines to your `.yaml`:
```yaml
appearanceSuffixes:
- !append itemsFactoryAppearanceSuffix.BodyType
```
Now, you can use the suffixes in your [root entity](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#root-entity) just like camera states or body genders:
```
appearanceName: my_custom_shirt&FPP&NewBody
```
{% hint style="info" %}
If you know something that should be on the list, please edit [the-wiki](https://wiki.redmodding.org/cyberpunk-2077-modding/the-wiki "mention")!
{% endhint %}
## Supporting mods
The following body mods support dynamic body switching.
**NOTE: These tags are not required unless your mod specially modifies body meshes for these body mods. Otherwise the value is base_bodysince these bodies are Vanilla shaped (see official mod page for further info.)
---
# 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-creators-theory/core-mods-explained/archivexl/archivexl-body-mods-and-refits.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.
