SkinList
SkinList
The short version:
Allows server owners to blacklist list player skins, and reserve skins for specific players.
The Long version
Using this plugin will check a players skin at login to see if it is on a blacklist. If the players skin is blacklisted, it promptly kicks the player from the server, as not to scorn the eyes of your other players. In game commands are available to ban skins. So when you see yet another nude skin you can just ban that skin forcing the player to change there skin if they want to join the server.
A bypass permission has also been included allowing a player to ignore the blacklist altogether. So admins can login using banned skins. A per-skin permission is also included allowing a player to use a specific skin. By putting a players skin on the blacklist and giving them the permission to login using there skin you have effectively blocked every other player from "stealing" that skin. This can be used to let server staff have access to a special skin or just for a single player.
Feature Requests
Please submit a ticket.
Commands
Note: player names are case sensitive and need to be in full.
- /skin [player] - Gets a players skin hash. If the players name is left blank then it will return the hash of your skin.
- /sban [player] - Bans a players skin.
Permissions (superperms)
- skin.admin - Allows a player to get and ban skins
- skin.bypass - Bypasses the blacklist for that player
- skin.default - Allows player to use the Steve skin ( If its on the Blacklist )
- skin.<hash> - Allows player to bypass a specific hash on the blacklist
eg) skin.64cf779f6fb9c6e35d8a265764f143f6: true
blacklist.hash
Found in /plugins/SkinList/blacklist.hash
Its a list of banned player skin hashes, one per line.
Note if you put the word "default" in that file on its own line it will block the Steve skin.
@x8105
Are you talking about onLogon event or can you be more specific. Because the server already generates a hash for every player. If you want I can have the server echo the hash in console.
there would be a great benefit to automagically generating a hash, and then the admin can ban slap pwn freeze lock from there. makes for easier selection and descision making at a later point.
@tihmstar
I was not planning on supporting permissions 3.1 due to the fact that it is inactive but if you want I can compile you a jar with permissions and whatever bukkit build you want.
don't work with permissions 3.1.6 (Yeti)