A skin change is not visible
Separate fetching, profile application, and client rendering problems.
SkinsRestorer 15.12.6All platformsReviewed
Use this guide when a command reports success but the player still looks unchanged.
Compare two views
- Run
/skin set xknatwith a Java client. - Ask another player to check the result.
- Disconnect and join again.
- Compare both views again.
If another player sees the new skin, the server applied it. Inspect the affected client's skin mods and launcher configuration.
Inspect the selected data
Run /sr info player <playerName> on the instance that owns storage. Inspect the texture and selected skin. On a network, use the proxy console for ordinary administrative commands.
If a texture cannot load, read service connections. If the stored selection is correct, continue with profile application.
Check the application path
- Proxy: Check forwarding and install SkinsRestorer on every backend. Use proxy troubleshooting.
- Join only: Inspect
advanced.disableOnJoinSkinsand online-mode behavior. Use skin resets. - Resource pack: Keep
server.resourcePackFixenabled unless another integration handles profile refresh. - Specific plugin or world: Reproduce without competing profile plugins on a separate test server.
Do not enable advanced.teleportRefresh as a first fix. It teleports players far away and back during refresh.
Still unchanged
Collect a diagnostic report and recent log, including whose client sees the problem and whether reconnecting changes it.
Did this page help?
Last updated on