Commands & Permissions

Complete reference for all commands and permissions in ClearLaggEnhanced.

Command Overview

All commands use the base command /lagg with the following aliases:

  • /clearlagg
  • /clearlag
  • /cl
  • /cle

Example: /lagg help or /cl help or /cle help

Commands

Help Command

/lagg help

Description: Displays the help menu with all available commands.

Permission: CLE.help

Default: All players

Usage:

  • Shows command list with descriptions
  • Color-coded based on player permissions
  • Displays plugin version and author

Clear Command

/lagg clear

Description: Manually clears entities immediately without waiting for the automatic timer.

Permission: CLE.clear

Default: Operators only

Usage:

  • Clears all entities not protected by whitelist
  • Respects protection settings (named, tamed, etc.)
  • Displays entity count and execution time
  • Broadcasts to all players

Console Example:

[12:34:56 INFO]: [ClearLaggEnhanced] Cleared 1,247 entities in 23ms

Next Command

/lagg next

Description: Shows the time remaining until the next automatic entity clear.

Permission: CLE.next

Default: All players

Usage:

  • Displays countdown in minutes and seconds
  • Updates in real-time
  • Helps players prepare for entity clearing

Example Output:

Next automatic clear in 4 minutes and 32 seconds

TPS Command

/lagg tps

Description: Displays current server TPS (Ticks Per Second) with detailed statistics.

Permission: CLE.tps

Default: Operators only

Usage:

  • Shows current TPS (color-coded)
  • Displays 1-minute, 5-minute, and 15-minute averages
  • Green = healthy (19+), Yellow = moderate (15-19), Red = poor (<15)

Example Output:

Server TPS: 19.85 (Excellent)
1m avg: 19.72
5m avg: 19.65
15m avg: 19.58

RAM Command

/lagg ram

Description: Displays detailed memory usage information.

Permission: CLE.ram

Default: Operators only

Usage:

  • Shows used memory in MB
  • Shows maximum allocated memory
  • Displays usage percentage
  • Shows available memory

Example Output:

Memory Usage
Used: 2,048 MB / 4,096 MB (50.0%)
Free: 2,048 MB

Chunk Finder Command

/lagg chunkfinder

Description: Scans nearby chunks and identifies those with high entity counts.

Permission: CLE.chunkfinder

Default: Operators only

Usage:

  • Scans chunks within configured radius
  • Lists top laggy chunks by entity count
  • Shows distance from your position
  • Helps identify problem areas

Example Output:

Laggy Chunks Near You:
1. Chunk [X:156, Z:893] - 87 entities (12 blocks away)
2. Chunk [X:157, Z:894] - 64 entities (28 blocks away)
3. Chunk [X:155, Z:892] - 52 entities (16 blocks away)

Configuration:

chunk-finder:
  radius: 10                  # Scan radius in chunks
  entity-threshold: 50        # Minimum entities to be "laggy"

Admin Command

/lagg admin

Description: Opens the interactive admin GUI (in-game only).

Permission: CLE.admin

Default: Operators only

Usage:

  • Visual overview of all modules
  • Toggle modules on/off
  • View performance statistics
  • Access module-specific GUIs
  • Must be executed by a player (not console)

GUI Features:

  • Module Status: See which modules are enabled
  • Performance Stats: Live TPS and memory usage
  • Quick Actions: Fast access to common tasks
  • Module Configuration: Click to open module GUIs

Reload Command

/lagg reload

Description: Reloads all configuration files and restarts enabled modules.

Permission: CLE.reload

Default: Operators only

Usage:

  • Reloads config.yml and messages.yml
  • Reloads all module configurations
  • Restarts enabled modules
  • Preserves player data and statistics
  • Does NOT reload database connections

Example Output:

ClearLaggEnhanced configuration reloaded successfully!

Warning:

  • Do NOT use /reload to reload the server
  • Always use /lagg reload to reload just this plugin
  • Database connections are not reloaded (requires full restart)

Permissions

Permission Nodes

Permission Description Default Commands
CLE.* All ClearLaggEnhanced permissions OP All commands
CLE.help Access to help command True /lagg help
CLE.clear Access to manual entity clearing OP /lagg clear
CLE.next Access to next clear timer True /lagg next
CLE.tps Access to TPS monitoring OP /lagg tps
CLE.ram Access to memory information OP /lagg ram
CLE.chunkfinder Access to laggy chunk finder OP /lagg chunkfinder
CLE.admin Access to admin GUI OP /lagg admin
CLE.reload Access to configuration reload OP /lagg reload

Permission Groups

For regular players:

permissions:
  - CLE.help
  - CLE.next

This allows players to see when entities will clear and access help.

For moderators:

permissions:
  - CLE.help
  - CLE.next
  - CLE.clear
  - CLE.tps

Adds ability to manually clear entities and check TPS.

For administrators:

permissions:
  - CLE.*

Full access to all features.

Permission Plugin Examples

LuckPerms

/lp group default permission set CLE.help true
/lp group default permission set CLE.next true
/lp group mod permission set CLE.clear true
/lp group mod permission set CLE.tps true
/lp group admin permission set CLE.* true

PermissionsEx

groups:
  default:
    permissions:
      - CLE.help
      - CLE.next
  moderator:
    permissions:
      - CLE.clear
      - CLE.tps
  admin:
    permissions:
      - CLE.*

GroupManager

groups:
  Default:
    permissions:
      - CLE.help
      - CLE.next
  Moderator:
    permissions:
      - CLE.clear
      - CLE.tps
  Admin:
    permissions:
      - CLE.*

Command Tips

Console Usage

All commands can be executed from the console without permissions:

lagg clear
lagg tps
lagg reload

Exception: /lagg admin requires a player (cannot be run from console).

Tab Completion

All commands support tab completion:

/lagg <TAB>     → Shows all subcommands
/lagg c<TAB>    → Completes to "clear"
/lagg ch<TAB>   → Completes to "chunkfinder"

Command Aliases

Use shorter aliases for faster typing:

/cl help        → Same as /lagg help
/cle tps        → Same as /lagg tps
/clearlag next  → Same as /lagg next

Troubleshooting Commands

Command not found

  • Verify plugin is enabled: /plugins
  • Check console for errors
  • Ensure proper installation

No permission

  • Check permission configuration
  • Verify operator status: /op <player>
  • Test with console (always has permission)

Command works in console but not in-game

  • Check permission plugin configuration
  • Verify permission nodes are set correctly
  • Confirm player has the specific permission

Next Steps