This plugin allows your players to change their skins with a simple command. You can choose every skin that another Minecraft user currently has. It is also possible to set a custom standard skin. If you want to, this plugin can set this standard skin for all players who still have the default Steve or Alex skin.
/setskin <uuid> [keep] - Sets your skin to be the same as the player with the selected uuid. /setskin <username> [keep] - Sets the skin equal to the owner of that Mojang account with the given username. /setskin reset - Resets the skin of the invoker to his one. /setskin <onlinePlayer> <newSkinUUID|newSkinPlayerName> [keep] /skinupdate [onlinePlayer] - Invalidates the database entry and fetches the fresh skin from the Mojang servers. /skinupload <url> - Upload a skin to a mojang account /skin-select <name> - Choose a skin from the database which has a specified name /skinskull - Changes the skin of a holding skull from the database which has a specified name /skin-info - Show details about the currently assigned skin like skin url owner name, uuid and more
Keep prevents the skin from auto updating. See the config for more information about auto updating.
/skin, /set-skin, /changeskin can used as an alias for /setskin
For Sponge users:
Sponge uses a different permissions model. This means changeskin.command.setskin includes all child permissions. (Including changeskin.command.setskin.other). To workaround this please use changeskin.command.<command>.base instead of changeskin.command.<command> to give the permission only to modify their own skin. **This workaround will be removed in the next major version 4.0. Then the Bukkit and BungeeCord will have the same logic.
=> This means all skins are allowed except the ones with the uuid in the blacklist list
This plugin performs network requests to:
Development builds of this project can be acquired at the provided CI (continuous integration) server. It contains the latest changes from the Source-Code in preparation for the following release. This means they could contain new features, bug fixes and other changes since the last release.
Nevertheless builds are only tested using a small set of automated and a few manual tests. Therefore they could contain new bugs and are likely to be less stable than released versions.
bungeecord: truein spigot.yml)