Skip to Content
Permissions System

Permissions System

VanguardRanks uses a comprehensive permission system to control access to various features. This guide explains all available permissions and how to set them up.

Basic Permissions

GUI Permissions

  • vanguardranks.gui

    • Allows players to open the rank GUI for themselves
    • Default: op
  • vanguardranks.gui.other

    • Allows players to open the rank GUI for other players
    • Default: op
  • vanguardranks.gui.set

    • Allows players to set ranks through the GUI for themselves
    • Default: op
  • vanguardranks.gui.set.other

    • Allows players to set ranks through the GUI for other players
    • Default: op

Rank Management Permissions

  • vanguardranks.up

    • Allows players to rank themselves up
    • Default: op
  • vanguardranks.up.other

    • Allows players to rank up other players
    • Default: op
  • vanguardranks.list

    • Allows players to view the list of available ranks
    • Default: op

Administrative Permissions

  • vanguardranks.reload

    • Allows reloading of configuration files
    • Default: op
  • vanguardranks.save

    • Allows forcing a save of player data
    • Default: op
  • vanguardranks.version

    • Allows checking plugin version
    • Default: op
  • vanguardranks.help

    • Allows viewing help information
    • Default: op

Setting Up Permissions

Using LuckPerms

  1. Add permission to a group:
/lp group <group> permission set vanguardranks.gui true
  1. Add permission to a player:
/lp user <player> permission set vanguardranks.gui true

Using Other Permission Plugins

VanguardRanks is compatible with any permission plugin that implements Bukkit’s permission system. Common alternatives include:

  • PermissionsEx
  • GroupManager
  • UltraPermissions

Best Practices

  1. Hierarchical Setup

    • Create different permission groups for different staff ranks
    • Use inheritance to build upon lower-ranked permissions
  2. Security Considerations

    • Carefully control access to .other permissions
    • Regularly audit who has administrative permissions
    • Use temporary permissions for temporary staff
  3. Permission Organization

    • Group similar permissions together
    • Document which groups have which permissions
    • Maintain a permissions hierarchy document

Common Issues

  1. Permission Denied Messages

    • Verify the player has the correct permission node
    • Check for typos in permission nodes
    • Ensure the permission plugin is working correctly
  2. Inheritance Problems

    • Check group inheritance chains
    • Verify permission priorities
    • Look for conflicting permissions

Testing Permissions

  1. Use /lp user <player> info to view current permissions
  2. Test commands with different permission levels
  3. Verify GUI access works as expected
  4. Check rank-up functionality with different permissions
Last updated on