Permissions 🔒
📄 Introduction
Permissions are essential to control who can access specific features and commands in the xSpawn plugin. By managing permissions, you can ensure that only authorized players can set, delete, or teleport to spawns. Below is a table listing all the permissions available in xSpawn, and a brief description of what they allow.
🔒 Plugin Permissions
| 🔒 Permission | 📄 Description |
|---|---|
| xspawn.command.help | Grants access to the /xspawn help command. Players with this permission can view all available commands. |
| xspawn.command.reload | Allows access to the /xspawn reload command. Players with this permission can reload the plugin’s settings. |
| xspawn.command.set | Grants permission to set spawns with /xspawn set. Includes first spawn, team spawns, and player spawns. |
| xspawn.command.tp | Allows players to teleport to defined spawns using /xspawn tp. Supports first, team, and player spawns. |
| xspawn.command.del | Grants permission to delete spawns with /xspawn del. Can remove first, team, or player spawns. |
| xspawn.command.info | Allows access to a plugin info command if implemented. |
| xspawn.admin | Full admin rights for all xSpawn commands and features. Gives the player complete control over the plugin. |
📜 Explanation
- Command Permissions: Each command has an associated permission that controls who can use it. For example, to allow a player to set a team spawn, they need the
xspawn.command.setpermission. - Dangerous Permissions: Some commands like
delcan affect multiple players or teams. Use caution when granting these permissions to prevent accidental or malicious changes. - Admin Permission: The
xspawn.adminpermission provides full access to all plugin features and commands. Only grant this to trusted server administrators to prevent unauthorized modifications.