Skip to content

3. Commands

Jump to bottom
Vincenzo Reina edited this page May 15, 2025 · 4 revisions

ServerPulse Commands and Permissions

This guide covers all available commands and permissions for ServerPulse across all supported platforms: Bukkit/Paper, Velocity, and Fabric.

Commands

Bukkit/Paper Commands

Command Description Permission
/serverpulse status Check connection status with InfluxDB serverpulse.status
/serverpulse reload Reload plugin configuration serverpulse.reload

Platform-Specific Permission Systems

Bukkit/Paper Permission System

Permissions work with any permission plugin compatible with Bukkit/Paper, including:

  • LuckPerms
  • PermissionsEx
  • GroupManager

Operators (players with op status) automatically have all permissions.

Velocity Permission System

Permissions work with Velocity's built-in permission system or any compatible permission plugin like:

  • LuckPerms for Velocity

Fabric Permission System

Fabric uses the Fabric Permissions API (included with ServerPulse). This is compatible with:

  • LuckPerms (when used with the Fabric Permissions API adapter)
  • Default server operator system (level 2+)

Permission Examples

LuckPerms Example (works across all platforms)

To give a group access to check status:

/lp group admin permission set serverpulse.status true

To give a specific player reload permission:

/lp user username permission set serverpulse.reload true

Command Usage Examples

Checking Status

Bukkit/Paper and Fabric:

/serverpulse status

Response:

[ServerPulse] Connected to InfluxDB.

Velocity:

/spv status

Response:

[ServerPulse] Connected to InfluxDB.

Reloading Configuration

Bukkit/Paper and Fabric:

/serverpulse reload

Response:

[ServerPulse] Configuration reloaded.

Velocity:

/spv reload

Response:

[ServerPulse] Configuration reloaded.

Console Commands

All commands can be run from the server console without permission restrictions.

Command Aliases

  • In Velocity, you can use /spv as a short form of /serverpulsevelocity
  • Bukkit/Paper and Fabric do not have command aliases by default

Troubleshooting Permissions

If you experience permission issues:

  1. Ensure the user has the correct permission node
  2. For Fabric servers, make sure Fabric Permissions API is properly loaded
  3. Check if your permission plugin is loading correctly
  4. Verify the user has the correct permission group assignments
  5. For Bukkit/Paper, ensure the plugin is correctly registered in the permission system

Upcoming Command Features

Future releases may include additional commands such as:

  • Real-time metrics display in chat
  • On-demand metric collection
  • Dashboard access links
Clone this wiki locally