Cosmetic

Skins+

Skin restoration and skin management.

Description

Skins+

Skin restoration and skin management.

Give players cleaner control over their Minecraft skin identity. Skins+ provides skin set, clear, update, random, list, and info workflows with familiar command aliases for communities that care about cosmetic polish.

Built for server owners

Servers that care about player identity, cosmetic polish, and reducing skin-related support friction.

Overview

Skins+ gives communities skin management tools so player identity and cosmetics remain consistent. It is especially useful where skins need to be restored, managed, or surfaced cleanly for players.

Key features

  • Player skin set, clear, none, update, status, list, info, and random workflows
  • Automatic skin behavior options through the skin command
  • SkinsRestorer-compatible permission names for easier migration
  • Admin reload command
  • Useful cosmetic layer for servers where player identity matters

Common server use cases

  • Communities where players frequently change skins or need to restore identity
  • Cosmetic-focused servers that want skin commands available in game
  • Networks migrating from familiar skin command permissions
  • Owners reducing support requests around skin updates and resets

Commands

  • /skin - set, auto, clear, none, update, status, list, info, and random
  • /skins - alternate skin command
  • /sr reload - administrative reload

Permissions

  • skinsplus.command.skin - allow player skin commands
  • skinsplus.admin - administrative Skins+ commands
  • skinsrestorer.command.set, clear, update - compatibility-style player permissions
  • skinsrestorer.admin and admincommand - compatibility-style admin permissions

Dependencies and hooks

  • No required third-party dependency is listed.

Compatibility

  • Paper 26.1.2

Installation

  • Download the plugin file after purchase.
  • Place the .jar file in your server plugins folder.
  • Restart the server so the plugin can generate its configuration.
  • Review the generated config, permissions, and messages before opening it to players.
  • Test the core flow on a staging server before deploying to production.

Rollout notes

Review which skin actions normal players should have. Keep admin reload and migration permissions restricted to staff.

Source

Source: Skins+ on GitHub
Reference update: May 28, 2026
Publisher: SQWARE