Change a Java skin while keeping the same identity
A skin change should change appearance rather than the player’s identity. Skins saves an official signed Java texture for the next connection, keeping the existing UUID and permissions. Pick a known Java account name and plan to reconnect before judging whether the change worked.
Add Skins to your world
- Open the plugin page and choose an existing world you own, or create a new world with the plugin selected.
- Check the included requirements. Each world supports up to eight plugins, including dependencies.
- Start a sleeping world, or use the dashboard restart option for a running world. Adding, removing and updating plugins takes effect when the world restarts; coordinate with anyone playing.
Choose the source account carefully
A Java player can set a Minecraft account name whose skin they intend to use. Replace Alex with that exact account name; it is a name lookup, not a place to paste an image URL. The provider must return an acceptable signed texture, and an unavailable lookup should not be treated as a successful selection.
/skin set AlexReconnect and compare identity as well as appearance
Leave and reconnect normally to apply the saved choice. Ask another player to inspect the appearance and confirm that your existing rank and command access remain. Do not repeatedly submit the same change while still in session expecting an instant refresh; the saved selection and the displayed current connection are different states.
Reset or tune the selection policy
Reset returns to the usual profile when you reconnect again. Operators can inspect configuration, set a cooldown in seconds and reload saved settings. Keep a reasonable cooldown rather than encouraging repeated provider requests. The plugin also has a bounded world-wide lookup rate and selection limit.
/skin reset
/skin config
/skin set cooldown_seconds 300
/skin reloadCheck the result
- Check that a successful selection survives a normal restart and applies on the next Java connection.
- After reset and reconnect, confirm the usual profile returns without changing the player’s saved rank or permissions.
Limits and compatibility
- Bedrock players keep their Minecraft Dressing Room skin; this release does not refresh Java selections on Bedrock.
- Arbitrary image uploads and instantaneous in-session replacement are not included. Provider failures or rate limits can refuse a lookup.
These instructions are for JetRift’s own Skins plugin. JetRift does not install arbitrary Paper, Spigot, Forge or Fabric extensions. Commands use player names from your world; replace example names before running them. Operators can use the dashboard Console without the leading slash.
Full command reference · Current client and hosting limits