> 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/for-mod-creators-theory/files-and-what-they-do/components.md).

# Components

This page contains documentation for the most common component types. WIP.

{% content-ref url="/pages/6vGtkQnnehtOfaDImzgK" %}
[Documented Components](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/components/documented-components.md)
{% endcontent-ref %}

{% hint style="info" %}
See the [Comprehensive Component Hierarchy List](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/components/comprehensive-components-list.md) for all possible components used in the game, organized by hierachy. Use for researching and documenting components.

For a json dump of all existing components and their properties, check [DrPresto's github repository.](https://github.com/DoctorPresto/Cyberpunk-File-Types/blob/main/lists/entComponent_types.json)

For a hands-on guide on how to safely change components in .app files, look [here](/cyberpunk-2077-modding/modding-guides/npcs/appearances-change-the-looks.md#safely-adding-components).
{% endhint %}

Components are not a file type but an internal data structure and part of [.ent](#.ent-entity) or [.app](#.app-appearance-definition) files.

Components are how the game adds anything to the in-game world, from pag3d data over player interaction prompts to explosion sounds.\
Entities and Appearances use **components** in order to slim down what data each game object has to carry, adding or removing them as needed.

## Component names

{% hint style="warning" %}
In general, these should be **globally unique** so you can target them via [partsOverrides](/cyberpunk-2077-modding/modding-guides/items-equipment/influencing-other-items.md#partsoverrides). Feel free to ignore this (almost everyone else does), but **do** read the next section.
{% endhint %}

### Body and clothing component prefixes

Body component prefixes affect how the game calculates [garment support](/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/garment-support-how-does-it-work.md) and you're strongly encouraged to stick to those naming conventions to make use of it.\
Please see the [corresponding wiki page](/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/garment-support-how-does-it-work.md#component-prefixes) for a list.

## Component Properties

Common component properties explained. For a more detailed list, please see [Documented Components](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/components/documented-components.md).

#### chunkMask

Only used for mesh components.

For documentation of this, see the [ChunkMasks](/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) section on [Submeshes, Materials and Chunks](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/file-formats/3d-objects-.mesh-files/submeshes-materials-and-chunks.md).

#### depotPath

Relative path to a resource within the game files. Used to load dependencies — meshes, rigs, animations, effects.


---

# 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/for-mod-creators-theory/files-and-what-they-do/components.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.