> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/cyberpunk-2077-modding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants/dynamic-appearances-fine-tuning-visibility-conditions.md).

# Dynamic Appearances: fine-tuning visibility conditions

How dynamic appearances can use different meshes/submeshes in a single root entity file.

## Summary

**Published**: Sep 09 2024 by [Sumi](mailto:undefined)\
**Last documented edit:** Dec 14 2025 by [Sumi](mailto:undefined)

This page is an extension of [ItemAdditions: Dynamic Appearances](/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants.md) and explains how to fine-tune item visibility conditions beyond the basic scope.

Please also check [ItemAdditions: Dynamic Appearances](/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants.md) -> [ItemAdditions: Dynamic Appearances](/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants.md#step-1-connecting-the-decal-and-understanding-variants) for more examples.

## Via root entity

You can use yaml instances to create different appearance names. These let you use different root entity entries which can point at different appearances in the .app file – letting you use `partsOverride` to show or hide different parts of your item!

Let's look at an example.

### Editing the .yaml

We're adding the `type` parameter to the custom t-shirt's definition array.

<pre class="language-yaml"><code class="lang-yaml"><strong>  $instances:
</strong>    - { type: sleeves, base_color: white, ribbons: red,  icon: 01 }
    - { type: nosleeves, base_color: black, ribbons: red,  icon: 02 }
</code></pre>

Since the `variants` only start after the exclamation mark, we can generate different appearance names:

before:

```yaml
appearanceName: root_entity_dynamic_appearance_!$(base_color)+$(ribbons)
```

after:

```yaml
appearanceName: root_entity_dynamic_appearance_$(type)_!$(base_color)+$(ribbons)
```

This will look up the following names in your root entity:

`root_entity_dynamic_appearance_sleeves_`

`root_entity_dynamic_appearance_nosleeves_`

Then you would add the following entries to your `.app` file with the `name`s :

`root_entity_dynamic_appearance_sleeves_`

`root_entity_dynamic_appearance_nosleeves_`

Now you have options. The next step will depend on your goals. In the `.app` file, you could use `partsOverrides` to hide different parts of the mesh for each appearance (like the sleeve submesh for the no-sleeve version. See [Chunkmasks: partially hiding meshes](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/file-formats/3d-objects-.mesh-files/submeshes-materials-and-chunks.md#chunkmasks-partially-hiding-meshes)), or you could set `partsValues` to different `mesh.ent` files (like a standard and looser-fitting version).

## But wait, couldn't I accomplish this by doing \[x] instead?

Yes, there are several ways to organize your item variants. The benefit is that you can use a single entry in your .yaml file for multiple variations, but it's just a matter of preference and what works best for your project.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants/dynamic-appearances-fine-tuning-visibility-conditions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.