> For the complete documentation index, see [llms.txt](https://hayston.gitbook.io/flp-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hayston.gitbook.io/flp-wiki/compatibility-and-integrations/skins.md).

# Skins and SkinsRestorer

`forwardSkin: true` allows FLP to carry a verified Java profile's textures to the server. The Mojang `textures` property can contain both skin and cape data, so disabling it affects both, not just the skin image.

On a standalone server FLP uses its Bukkit/Paper-specific application path. Behind a proxy, the **proxy's** `forwardSkin` controls the forwarded profile; changing the backend copy does not override it. Other plugins or server profile caches may still supply a skin, so `forwardSkin: false` is not a universal "nobody has a skin" switch.

## SkinsRestorer

Install SkinsRestorer only on supported platform/version combinations according to its own guide. FLP's compatibility path checks for a custom skin and avoids overwriting it. When connection UUIDs are offline, identity-sensitive lookups must still use the verified Mojang identity where appropriate, rather than assuming the connection UUID is Mojang's UUID.

To diagnose a conflict:

1. Record server, FLP, proxy and SkinsRestorer versions and whether the player has an explicit custom skin.
2. Check `forwardSkin` on the identity-handling side and the selected `premiumUuid` policy.
3. Test a reconnect with one known custom skin and one default premium skin in staging.
4. Inspect debug logs for compatibility API failures and profile-cache effects before clearing data.

A visible premium skin is not an authentication result. This classic integration does not promise a SkinsRestorer API implementation inside the Fabric mod or compatibility with every skin plugin.


---

# 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://hayston.gitbook.io/flp-wiki/compatibility-and-integrations/skins.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.