🔒 Permissions

Complete list of permission nodes for controlling access to WeaponSkin commands.

🗂 Overview

WeaponSkin uses a granular permission system that allows fine-grained control over who can use each command. All permissions default to OP (server operators) unless otherwise configured.

💡 Tip

The weaponskin.admin permission grants access to all other permissions automatically. This is useful for server administrators.

📋 Permission Reference

Permission Description Default
weaponskin.admin Full access to all WeaponSkin commands (parent node) OP
weaponskin.give Give skin items to players OP
weaponskin.remove Give Skin Remover items to players OP
weaponskin.list List all registered skins OP
weaponskin.reload Reload configuration files OP
weaponskin.pack Build and apply resource packs OP

📊 Permission Hierarchy

The weaponskin.admin permission is a parent node that automatically grants all child permissions:

weaponskin.admin
↳ weaponskin.give
↳ weaponskin.remove
↳ weaponskin.list
↳ weaponskin.reload
↳ weaponskin.pack

⚙ Setting Up Permissions

Using a Permissions Plugin

For servers using permissions plugins like LuckPerms, PermissionsEx, or GroupManager:

🔐 LuckPerms Example
# Give admin full access
/lp user  permission set weaponskin.admin

# Give moderator only give and list permissions
/lp user  permission set weaponskin.give
/lp user  permission set weaponskin.list

# Create a group for skin management
/lp group skinadmin permission set weaponskin.admin
🔐 PermissionsEx Example
# Give admin full access
/pex user  add weaponskin.admin

# Give moderator only give and list permissions
/pex user  add weaponskin.give
/pex user  add weaponskin.list

Server Operators (OP)

By default, all permissions are granted to server operators. To make a player an operator:

/op

To remove operator status:

/deop

👥 Common Scenarios

👨‍💻 Scenario 1: Server Admin

Full access to all commands:

weaponskin.admin
👨‍👔 Scenario 2: Moderator

Can give skins and list them, but cannot reload or build packs:

weaponskin.give
weaponskin.remove
weaponskin.list
👭 Scenario 3: Support Staff

Can only view skins and give skin removers:

weaponskin.list
weaponskin.remove

🚫 Negative Permissions

With permissions plugins that support negative permissions, you can deny specific permissions even if the parent is granted:

⚠ Note

Not all permissions plugins support negative permissions. Check your plugin's documentation.

🔐 LuckPerms Example
# Grant admin but deny pack building
/lp user  permission set weaponskin.admin
/lp user  permission set weaponskin.pack false

🔗 Command-Permission Mapping

Command Required Permission
/ws give weaponskin.give
/ws remove weaponskin.remove
/ws remover weaponskin.remove
/ws list weaponskin.list
/ws reload weaponskin.reload
/ws pack build weaponskin.pack
/ws pack apply weaponskin.pack

📖 Next Steps

💻
Commands
View all available commands and their usage.
🎨
Custom Skins
Create and add your own custom weapon skins.