Commands

Commands & Permissions

This page lists user-facing commands and administrative commands exposed by EndSectors and the Tools plugin. Command names and messages may be customized via message.json.

Player / basic commands

• /sector show
  • Description: Opens a GUI listing sectors and their status.
  • Usage: /sector show
• /sector where
  • Description: Shows the current sector (border and position).
  • Usage: /sector where
• /sector who
  • Description: Shows global online players list.
  • Usage: /sector who
• /sector execute
  • Description: Executes a command on all sectors (admin only).
  • Usage: /sector execute say Hello
• /sector reload
  • Description: Reloads the local configuration and updates borders.
  • Usage: /sector reload
• /sector border
  • Description: Force synchronization of sector borders across the network.
  • Usage: /sector border

Tools plugin (example)

• /spawn
  • Teleports player to spawn channel if available.
• /rtp
  • Random teleport inside the current sector or spawn channel.
• /home
  • Teleport to player home (tools plugin example).

Administrative & internal commands

• Commands invoked by Common or Proxy via NATS are not directly user-invokable; they require appropriate admin tools or direct NATS commands.
• Monitoring endpoints: Common exposes health/status endpoints (if available in your deployment); consult logs.

Permissions

• Use standard permission nodes (the plugin includes permission checks for admin-level commands).
• Suggested nodes:
  • endsectors.admin.* — full control
  • endsectors.command.show — open sector GUI
  • endsectors.command.execute — execute commands across sectors

Examples

• Grant a moderator the ability to open the sector GUI:
  • permissions: endsectors.command.show (configure in your permission plugin)

UI & placeholders

• Scoreboards and GUI texts use placeholders:
  • {sectorName}, {playerName}, {tps}, {onlineCount}, {ping}, etc.
• These placeholders are provider-agnostic; keep them unchanged in translations.

Command lifecycle

• Commands that cause network-wide changes (e.g., /sector execute) are broadcast via NATS to all sectors, which then act atomically or with controlled delay to avoid race conditions.
• Reload and border sync will validate Common connectivity before applying changes.

Next: See Troubleshooting & FAQ for debugging failed commands or registration issues.