Isolate plugin and platform conflicts

Plugins that change profiles, nicknames, tab lists, login state, or world state can replace skin data. A plugin name alone does not prove a conflict across all versions.

Reproduce on a separate server

1. Back up the configuration and data.
2. Create a test server with the same Minecraft version.
3. Install only SkinsRestorer on an upstream supported platform.
4. Apply a known skin and reconnect.
5. Add one suspected plugin or mod.
6. Repeat the same skin check.
7. Continue until the problem returns.

Keep the tested versions in your report. Do not remove plugins from a live server just to run this check.

Common overlap

• A skin plugin or script can apply another texture after SkinsRestorer.
• A login plugin can restore an account profile after a custom selection.
• A nickname or tab plugin can replace the visible player profile.
• A client skin mod can override only that client's appearance.

Inspect the competing integration's current configuration. For example, a login integration that forwards its own skin can conflict with server-selected skins.

Forks and hybrid servers

A fork or hybrid mod/plugin server can alter profile APIs and refresh behavior. Reproduce on upstream Paper, Spigot, or the matching mod platform before you report a SkinsRestorer bug.

Do not assume a historical incompatibility list applies to every current release. Report exact versions and a minimal reproduction.

Next

Use launcher troubleshooting for client-only differences. Include the reproduction and diagnostics in a server-side report.