SkinsRestorer Commands and Permissions Explained

Published: July 30, 2026 · Reading focus: usage

Commands are simple for players, but permissions should be deliberate. SkinsRestorer uses parent and child permission nodes, so granting only a deep child without its required parents can make a correct-looking setup fail.

Player command basics

The `/skin` command changes the current player’s skin. Named skins are convenient for normal use, while `/skins` opens the GUI. Update, clear, random, undo, history and favourites provide additional self-service features when enabled.

URL and upload permissions

URL-based skins require a dedicated permission because they accept remote input. Keep this capability limited, use allowed-domain restrictions and teach users to keep direct PNG URLs quoted.

Setting another player

Commands that target another player should be reserved for moderators or administrators. They can affect someone else’s visible identity, so log their use and avoid giving them to broad default groups.

Useful command examples

Set your own skin from an allowed name.

Clear the current selected skin.

Open the GUI when `skinsrestorer.command.gui` is available.

Administrative commands

The `/sr` command family covers status, custom skins, global operations and data management. Database removal or purge actions can be destructive. Back up data and test the exact scope before running maintenance commands.

Build a least-privilege role

Start with the smallest working set: parent command access, named-skin selection and GUI access. Add update or URL features only when there is a clear use case. Keep wildcard admin permissions out of default groups.

Test permission inheritance

Use a fresh non-admin test account. Confirm each intended command works and each restricted command is denied. Testing only as an operator can hide missing nodes because elevated accounts bypass normal permission behaviour.

Document your policy

Write down which roles may select skins, use URLs, target others or create custom server-wide entries. A short policy makes future staff changes safer than relying on memory or an unexplained wildcard.

Related SkinsRestorer guides

• How to Set Up SkinsRestorer on Aternos
• SkinsRestorer Proxy Setup for Velocity and BungeeCord
• SkinsRestorer Fabric, NeoForge and Forge Compatibility

This guide is an independent resource. It does not replace the documentation shipped with the exact build you install. Return to the SkinsRestorer guide library or review the download safety notice.