> For the complete documentation index, see [llms.txt](https://docs.vames-store.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vames-store.com/assets/vms_tattooshop/compatibility.md).

# Compatibility

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td>✅  <strong>Officially Supported</strong></td><td>Veified compatibility and built in both resources.</td><td></td></tr><tr><td>✅  <strong>Supported</strong></td><td>Veified compatibility but possible code modifications.</td><td></td></tr><tr><td>⚠️ <strong>Supported</strong></td><td>Compatibility according to code from the resource, but has not been tested.</td><td></td></tr><tr><td>🚫 <strong>Not Supported</strong></td><td>Unsupported resource, you cannot use this resource compatibility.</td><td></td></tr><tr><td><strong>🕛 Soon...</strong></td><td>We plan to introduce compatibility soon.</td><td></td></tr></tbody></table>

## Skin Managers:

{% hint style="info" %}

### Custom Integration

If you don't find your skinmanager in the list below, don't worry!

It can be customized in **CL.ReloadSkin.** This allows you to introduce compatibility with your external resource.
{% endhint %}

| Resource                                                                              | Is compatible               |
| ------------------------------------------------------------------------------------- | --------------------------- |
| [**esx\_skin & skinchanger**](/helpful/prepared-resources.md#compatible-skinmanagers) | ✅  **Officially Supported** |
| [**qb-clothing**](/helpful/prepared-resources.md#compatible-skinmanagers)             | ✅  **Officially Supported** |
| [**fivem-appearance**](/helpful/prepared-resources.md#compatible-skinmanagers)        | ✅  **Officially Supported** |
| [**illenium-appearance**](/helpful/prepared-resources.md#compatible-skinmanagers)     | ✅  **Officially Supported** |
| **rcore\_clothing**                                                                   | ✅  **Officially Supported** |

## Maps:

{% hint style="info" %}

### Custom Integration

If you don't find your map in the list below, don't worry!

You can fully customize all coordinates in the config.lua file - but remember! **The script requires a bed-like chair where the player lies down. The character cannot sit.**

If your interior only has a regular seat instead of a lying one, ask the map creator if it's possible to choose or remove the existing chair.

(If it’s a custom object, you can remove it through the map files – ask someone experienced for help.)

After removing the built-in object from the map, you can spawn the correct one using our resource by configuring it in `Config.SeatSpawnsList` inside the config.lua.
{% endhint %}

| Map                 | Is compatible               |
| ------------------- | --------------------------- |
| **Default GTA 5**   | ✅  **Officially Supported** |
| **MXC Tattoo Shop** | ✅  **Officially Supported** |


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.vames-store.com/assets/vms_tattooshop/compatibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.