> For the complete documentation index, see [llms.txt](https://sebun1.gitbook.io/skins/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sebun1.gitbook.io/skins/schema/paths.md).

# Paths

{% hint style="info" %}
For those familiar with code / dotnet, you can checkout the [source](https://git.takina.io/gtfo/skins/-/blob/main/Skins/Data/ModData.cs?ref_type=heads) to see how each path is obtained exactly, thought on the Linux side of things it might not be what you expect because of Proton and Wine.
{% endhint %}

## Data Folder

This folder contains the global skins folder and any data that the mod dump/exports/stores persistently.

For the specific path to the data folder on different platforms, check out the sections below for each OS.

### Folder Locations

#### Windows

```
%APPDATA%\io.takina.gtfo.Skins\
```

{% hint style="info" %}
`%APPDATA%` is the Roaming AppData folder specifically
{% endhint %}

#### Linux

```
steamapps/compatdata/493520/pfx/drive_c/users/steamuser/AppData/Roaming/io.takina.gtfo.Skins/
```

{% hint style="info" %}
`steamapps` is the steam games install folder.\
`493520` is GTFO's AppID.\
This is the location because when GTFO runs through Proton (Wine) the dotnet runtime injected thinks it is running on windows, and thus writes to the Windows style folder, which then gets mapped to the above location.
{% endhint %}

#### Mac

```
N/A (GTFO does not run on Mac)
```

{% hint style="info" %}
However, you can still run the SkinGroup Editor on macOS, and it will expect the data folder to be located at

```
~/Library/Application Support/io.takina.gtfo.Skins/
```

{% endhint %}

### Folder Contents

#### Directories

<table><thead><tr><th width="189.9998779296875">Directory</th><th width="385.1666259765625">Purpose</th><th width="283">Relative Path to Data Folder</th></tr></thead><tbody><tr><td>Global Skins Folder</td><td>Stores global skin groups</td><td><code>./skins/</code></td></tr><tr><td>Dumps Folder</td><td>Debug dumps such as the Gear Tree dump</td><td><code>./dumps/</code></td></tr><tr><td>Skins Packages</td><td>Stores packages created in the Editor</td><td><code>./packages/</code></td></tr><tr><td>Staging Folder</td><td>Staging area for <code>.skinspkg</code> installation</td><td><code>./__staging__/</code></td></tr></tbody></table>

#### Files

<table><thead><tr><th width="219.1666259765625">Directory</th><th width="353.5">Purpose</th><th width="283">Relative Path to Data Folder</th></tr></thead><tbody><tr><td>Skins Config</td><td>Stores skin configuration for the Plugin</td><td><code>./config.json</code></td></tr><tr><td>Editor Settings</td><td>Stores settings for the SkinGroup Editor</td><td><code>./editor_config.json</code></td></tr><tr><td>Internal Data File</td><td>Game information used by the Editor</td><td><code>./internal_data.json</code></td></tr><tr><td>Internal Data Gear Dump</td><td>Gear information dump used by the Editor</td><td><code>./internal_data_gear_dump.json</code></td></tr><tr><td>Internal Data Mesh Dump</td><td>Mesh information dump used by the Editor</td><td><code>./internal_data_mesh_dump.json</code></td></tr></tbody></table>

## Per-Profile Skins Folder

The per-profile skins folder is where package installed (e.g. Thunderstore) skins are received. The global skins folder always takes precedence over the per-profile folder for skin groups, while the per-profile folder is always seen as more up-to-date version when both folders contain the same skin.

This folder is located at

```
<BepInEx>/Assets/Skins/
```

{% hint style="info" %}
Where `<BepInEx>` is the BepInEx folder for the specific modded profile.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sebun1.gitbook.io/skins/schema/paths.md?ask=<question>
```

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.