Commands Permissions

Commands & Permissions Mastery

A complete list of commands and permissions to manage your BeaconPlus server.

---

1. Administrative Commands (/beaconplus)

The main command is /beaconplus (aliased as /bp). Accessing these requires the beaconplus.admin permission or OP.

Core Management

• /bp reload:
  • What it does: Reloads all .yml configurations, effect files (/effects), and language files. It also forcefully shuts down all active beacon tasks and restarts them using the new data.
  • Proactive Note: Use this after editing any YAML file. Note that "Restarting tasks" might cause a split-second delay in effect application as the world is re-scanned.
• /bp help:
  • What it does: Displays an interactive list of all available subcommands.

Troubleshooting & Diagnostics

• /bp debug:
  • What it does: Toggles local debug mode for the player. While active, you will see internal log messages in your chat (e.g., scan results, power calculations).
• /bp info:
  • What it does: Target the beacon you're looking at. It will print the beacon's Internal ID, Location, Power level, and all currently active effects.

Override Controls (Experimental)

These commands allow you to bypass standard pyramid logic temporarily.

• /bp overrideRange <value>: Sets a hard-coded range for the beacon you are looking at.
• /bp overridePower <value>: Forcefully sets the power level (ignoring the blocks in the pyramid).
• /bp overrideClosedState <true|false>: Can be used to "Lock" a beacon's menu from being opened by anyone.

Utility & Data

• /bp give <player> [amount]: Gives the specialized BeaconPlus item to a player.
• /bp migrate: Manually triggers the storage migration sequence (see the Storage Guide for precautions).

---

2. Player Commands (/beacon)

• /beacon:
  • What it does: Opens a GUI for the player listing all beacons they have placed in the world.
  • Requirements: Enable Beacon Tracking must be set to true in beacon.yml.
  • Utility: Players can see the distance, world, and generic status of their beacons from anywhere.

---

3. Comprehensive Permission Lexicon

BeaconPlus uses a hierarchy-based permission system.

Administrative Permissions

• beaconplus.*: Grant all plugin permissions.
• beaconplus.admin: Permission to use the admin command /beaconplus.
• beaconplus.command.reload: Permission to reload the plugin.
• beaconplus.command.give: Permission to use the give command.
• beaconplus.command.debug: Permission to use the debug toggle.

Operational Permissions (Default Nodes)

These control standard player interactions. Note that these can be overridden in beacon.yml -> Permissions.

• beaconplus.place: Permission to place a beacon.
• beaconplus.break: Permission to break a beacon.
• beaconplus.craft: Permission to craft a beacon (requires the recipe to be enabled).
• beaconplus.open: Permission to open the main beacon dashboard.
• beaconplus.open.settings: Permission to open the settings menu.
• beaconplus.open.language: Permission to open the language selection menu.
• beaconplus.upgrade: Permission to purchase an upgrade.

---

4. Proactive Permission Strategy

Recommended Default Group (Common Players)

We recommend granting the following nodes to your default player group:

• beaconplus.place
• beaconplus.break
• beaconplus.open
• beaconplus.upgrade

Recommended VIP Group

If you have a VIP rank, you might want to give them exclusive access to certain effects using the HAS_PERMISSION condition in the Effect Files.

• Proactive Logic: Give VIPs the beaconplus.effect.fly permission node, and then in flying.yml, add a condition that checks for that node. This is much more efficient than using separate beacon items!

Inheritance Note

Most permission plugins (LuckPerms, EssentialsGroupManager) allow for inheritance. If you grant beaconplus.admin, the player will implicitly have access to all sub-nodes like beaconplus.command.reload unless explicitly negated.