Configure SkinsRestorer without changing account authentication
CloudExaSkinsRestorer helplets guide.a supported Minecraft Java server apply player skins and manage saved skin selections. A player's appearance is separate from whether their account is authenticated. Do not turn off online authentication or change a working proxy trust boundary just to repair a cosmetic problem.
Match the platform and network arrangement
Read the installation and compatibility guide for the exact SkinsRestorer release. Choose the artifact for Paper, your proxy or the supported mod platform. Minecraft and Java requirements depend on that choice; a filename that looks recent is not enough to establish compatibility.
The current official installation guidance says a proxy network needs SkinsRestorer on the proxy and every backend. Follow the full network instructions rather than placing an arbitrary combination of plugin files on a few machines. Preserve existing forwarding and backend access protection.
For a standalone Paper service, use plugin installation. Keep the existing configuration, stored skin data and external database export before an update. A database change can affect saved choices even when players' world files are untouched.
Test a simple player-name skin
- Install the supported release, start normally and read Console for successful loading and storage connection.
- Join with a controlled Java test account. Use the documented player skin command, such as
/skin set PlayerName, with a valid target skin name. - Check the result from another player's view as well as your own. Reconnect if the documented client refresh behaviour requires it.
- Test the documented reset/clear option when you want the account skin back; understand whether it removes the saved selection or only refreshes the current view.
- Repeat with an ordinary player account after applying the intended permissions.
Begin with a player-name skin before testing uploaded PNG files or URL skins. This separates a general plugin/storage failure from an image-format, URL-policy or upstream skin-generation problem.
Limit who can change what
Review SkinsRestorer's current command and permission reference. Self-service skin changes, URL uploads, menu access and changing another player's skin are distinct capabilities. Grant only what your community needs rather than the full administrative permission set.
If you offer custom uploads, publish a simple content policy and retain URL restrictions supported by the plugin. Do not paste private authentication or provider tokens into public image URLs, commands or screenshots. A skin command generated by an uploader is not an invitation to execute unrelated console text.
Diagnose the visible result
A cached or temporarily applied skin can differ from the saved selection. Inspect the documented lifecycle and refresh behaviour before deleting data. Check Console for rate limits, upstream service failures or storage errors; repeatedly reapplying the same skin can make a rate-limit problem harder to diagnose.
Bedrock users joining through Geyser have a different appearance path, so do not use their view as the only test of a Java skin change. Compare two Java accounts first. Record the platform, release, command and failed stage in a support request.
See Java and Bedrock crossplay for that separate setup. Further reading: installation, changing and resetting skins and permissions.
Looking for another plugin? Browse the Minecraft plugin guide directory.