Plugins Wardrobe | Roleplay Skins 1.1.0

Tested Minecraft Versions:

• 1.13
• 1.14
• 1.15
• 1.16

Dependencies: ProtocolLib

Wardrobe grants you the opportunity to either allow or force your players to select a RP fitting skin for your server. Those skins are persistent and can be configured and selected from different categories which allows easy integration into complex existing systems like different categories to choose from based on gender, fantasy race, job, etc.

• You can use any skin you want by utilizing mineskin
• You can configure as many skins and as many categories as you want
• Skins are persistent and visible to all players including the affected one
• Through the skin unlock feature you have a EULA conform way to receive support from your community through selling access to specific skins (per player)
• You can limit how often a specific skin can be used
• Easy integration into existing server concepts, more on that later
• Option to force players to select a skin
• Per category permissions
• Configurable navigation buttons per category
• Command list option that runs once a player selected a skin for the first time for better integration
• Skins and wardrobes are client sided (changed skins are still visible for players)
• Easy to use and feature-rich API

If you want to integrate the plugin into your existing server concepts you have multiple ways of doing so:

• Force skin integration: Using the force-skin configuration option you can force players to select a fitting skin on their next server join, you are also able to configure a safe location where they are getting teleported to for selection since they are unable to move until they selected one.
• Tutorial integration: To easily force new players to select a new fitting skin you can utilize the command list option. By using a third party plugin or a pressure plate and a command block you can open the force selection for the player per command. This way you can for example first let them select their fantasy race and gender and then teleport them to a skin selection area where they'll get teleported out and their role assigned to by the plugin once they selected a skin.
• Permission integration: Another way to force your existing players and new players to select a skin is by removing mandatory permissions from them by default and then utilizing the command list to give them their permissions back once the selected a skin.
• General integration: This way you can for example reward players for selecting a skin yet again by utilizing the command list that will only execute when the player selected a fitting skin for the first time. (Note that resetting a players skin through the reset command will also reset the selection state)

If you have suggestion for other ways feel free to contact me.


Potential difference between a medieval RPG server without and with the plugin:




Code (Text):
< > = Required
( ) = Optional

/wardrobe download (Category) <Mineskin Link>
→ Used to download and add skins directly from mineskin.
→ https://mineskin.org/
→ wardrobe.download
→ wardrobe.download.category

/wardrobe force <Player> (Category)
→ Used to open a wardrobe that forces the player to select a skin.
→ wardrobe.force

/wardrobe open (Category) (Player)
→ Used to open a wardrobe with a specific skin category.
→ wardrobe.open
→ wardrobe.open-others (Only for last arg)

/wardrobe override <Player> <Skin Data> <Skin Signature>
→ Used to override a players current skin with a pseudo.
→ wardrobe.override

/wardrobe reload
→ Used to reload the configuration files.
→ wardrobe.reload

/wardrobe reset (Player)
→ Used to reset a active player skin.
→ wardrobe.reset
→ wardrobe.reset.self

/wardrobe save <Id>
→ Used to save the current skin in the players personal wardrobe.
→ wardrobe.save

/wardrobe set <Player> <Category> <Skin Name>
→ Used to directly set a players skin.
→ wardrobe.set

/wardrobe unlock <Player> <Category> <ID>
→ Used to unlock a skin for a specific player.
→ wardrobe.unlock

Code (Text):
default-left-button-texture: <Texture>
default-right-button-texture: <Texture>
skin-categories:
<Category Name>:
id: <ID>
left-button-texture: <Texture>
right-button-texture: <Texture>
skin-collection:
<Skin Name>:
data: <Data>
signature: <Signature>
max-distance: <Distance>
default-skin-id: <Id> (Optional)
force-skin: <True/False>
force-skin-category: <Category>
first-skin-selected-commands:
- 'say Example Command (%player%)'
- 'say Second Example'
- '...'
preview-entity-name: '<Name>'
left-button-entity-name: '<Name>'
right-button-entity-name: '<Name>'
force-skin-location: (Optional)
==: org.bukkit.Location
world: <World>
x: <X>
y: <Y>
z: <Z>
pitch: <Pitch>
yaw: <Yaw>

Code (Text):
wardrobe.skin-category.<ID>
wardrobe.reset.others
wardrobe.force-skin.bypass