Commands & Permissions Reference
Complete command reference, permission nodes, and staff workflows for MinerTrack.
🎮 Command Overview
| Command | Aliases | Description | Permission |
|---|---|---|---|
/mtrack help |
/mtrack, /minertrack |
Show help menu | minertrack.help |
/mtrack reload |
/mtrack rl |
Reload all configuration files | minertrack.reload |
/mtrack verbose |
/mtrack v |
Toggle verbose mode (real-time alerts) | minertrack.verbose |
/mtrack check <player> |
/mtrack c |
View player's violation history | minertrack.check |
/mtrack reset <player> |
/mtrack rs |
Reset player's violation level to 0 | minertrack.reset |
/mtrack kick <player> <reason> |
/mtrack k |
Kick player with custom reason | minertrack.kick |
/mtrack notify <message> |
/mtrack n |
Send custom alert to staff | minertrack.sendnotify |
/mtrack update |
/mtrack up |
Check for plugin updates | minertrack.checkupdate |
/mtrack logs <file.log> [page] |
/mtrack log |
View MinerTrack log files | minertrack.logs |
Root Permission:
minertrack.use— Required for any/mtracksubcommand (default: op)
📋 Detailed Command Reference
/mtrack help
Usage: /mtrack help
Permission: minertrack.help
Description: Displays all available commands with descriptions.
Output Example:
----[MinerTrack Help]-----------
/mtrack reload - Reload plugin's configuration file
/mtrack notify <message> - Send alerts to staff
/mtrack verbose - Toggle Detailed Mode
/mtrack check <player> - Check player's violation history
/mtrack reset <player> - Reset player's violation record
/mtrack help - Get plugin's help
/mtrack update - Check for plugin updates
/mtrack kick <player> <reason> - Kick player with reason
/mtrack logs <log name.log> - View a MinerTrack log file
/mtrack reload
Usage: /mtrack reload
Permission: minertrack.reload
Description: Reloads config.yml, language.yml, and all Configuration/*.yml files.
Console Output:
[MinerTrack] Configuration and Language reloaded successfully.
What Reloads:
- ✅ Global settings (
config.yml) - ✅ Messages (
language.yml) - ✅ World profiles (
Configuration/*.yml) - ✅ Discord webhook settings
What Doesn't Reload:
- ❌ Plugin JAR (requires restart)
- ❌ Java version changes
- ❌ Newly added world dimensions (auto-loaded on dimension access)
/mtrack verbose
Usage: /mtrack verbose
Permission: minertrack.verbose
Description: Toggles verbose mode. When enabled, you receive real-time notifications
whenever any player's violation level changes.
Toggle On:
[MinerTrack] Verbose Mode Enabled!
Toggle Off:
[MinerTrack] Verbose Mode Disabled!
Verbose Notification Format (from language.yml):
Notch failed X-Ray check VL:3(+1) Block:diamond_orex3(Veinx1) World: world Pos: X123 Y-45 Z67
Use Case: Staff monitoring — enable during peak hours to catch X-rayers in real-time.
/mtrack check <player>
Usage: /mtrack check <player>
Permission: minertrack.check
Description: Shows the target player's current violation level and history.
Output Example:
Notch's violation level is 3.
Console/Offline Player: Works with offline player names (uses UUID lookup).
/mtrack reset <player>
Usage: /mtrack reset <player>
Permission: minertrack.reset
Description: Resets the target player's violation level to 0 and clears path history.
Output Example:
Successfully reset Notch's violation record.
When to Use:
- False positive confirmed
- Player appeal accepted
- Testing configuration changes
- New player joining (clean slate)
/mtrack kick <player> <reason>
Usage: /mtrack kick <player> <reason>
Permission: minertrack.kick
Description: Kicks the player with a formatted X-Ray kick message.
Example:
/mtrack kick Notch "X-Ray detected - VL 5"
Kick Message (from language.yml kick-format):
Notch kicked out of the server for allegedly using X-Ray! (X-Ray detected - VL 5)
Features:
- Lightning strike effect (configurable:
kick_strike_lightning: true) - Broadcast to all players (configurable:
kick-broadcast: true) - Logs to MinerTrack log files
/mtrack notify <message>
Usage: /mtrack notify <message>
Permission: minertrack.sendnotify
Description: Sends a custom message to all players with `minertrack.notify` permission.
Example:
/mtrack notify "Staff: Please check Notch at X:123 Y:45 Z:67"
Received By: All online players with minertrack.notify permission.
Use Case: Staff coordination without Discord/voice chat.
/mtrack update
Usage: /mtrack update
Permission: minertrack.checkupdate
Description: Manually checks for plugin updates on configured channel (stable/beta/alpha).
Output Examples:
New stable version 2.5.0 now available!
You are using the latest version.
Failed to check for updates.
Auto-Check: Runs on server startup if check_update: true in config.yml.
/mtrack logs <file.log> [page]
Usage: /mtrack logs <log name.log> [page]
Permission: minertrack.logs
Description: Views MinerTrack detection log files with pagination.
Examples:
/mtrack logs 2024-01-15.log
/mtrack logs 2024-01-15.log 2
Log Format (from language.yml log-format):
2024-01-15 14:30:22 | Notch failed X-Ray check VL:3(+1) Block:diamond_orex3(Veinx1) World: world Pos: X123 Y-45 Z67
Pagination: 10 lines per page (configurable: log-viewer-lines-per-page: 10)
Navigation:
---- MinerTrack Logs (1/3) ----
2024-01-15 14:30:22 | Notch failed X-Ray check...
2024-01-15 14:31:05 | Steve failed X-Ray check...
...
Use /mtrack logs 2024-01-15.log 2 to view next page.
🔐 Permission Nodes
Permission Hierarchy
minertrack.use # Root - required for ALL commands (default: op)
├── minertrack.help # /mtrack help
├── minertrack.reload # /mtrack reload
├── minertrack.verbose # /mtrack verbose
├── minertrack.check # /mtrack check
├── minertrack.reset # /mtrack reset
├── minertrack.kick # /mtrack kick
├── minertrack.sendnotify # /mtrack notify
├── minertrack.checkupdate # /mtrack update
├── minertrack.logs # /mtrack logs
└── minertrack.notify # Receive verbose/notify messages
Default Permission Assignments
| Permission | Default | Recommended For |
|---|---|---|
minertrack.use |
OP | All staff |
minertrack.help |
OP | All staff |
minertrack.reload |
OP | Admins only |
minertrack.verbose |
OP | Senior staff, moderators |
minertrack.check |
OP | Moderators, admins |
minertrack.reset |
OP | Admins only |
minertrack.kick |
OP | Admins only |
minertrack.sendnotify |
OP | Senior staff |
minertrack.checkupdate |
OP | Admins |
minertrack.logs |
OP | Admins, investigators |
minertrack.notify |
OP | All staff (receive alerts) |
minertrack.bypass |
OP | Trusted players only — bypasses detection entirely |
LuckPerms / PermissionEx Examples
LuckPerms (Recommended):
# Full admin access
/lp group admin permission set minertrack.* true
# Moderator: check, verbose, notify, logs
/lp group moderator permission set minertrack.use true
/lp group moderator permission set minertrack.check true
/lp group moderator permission set minertrack.verbose true
/lp group moderator permission set minertrack.notify true
/lp group moderator permission set minertrack.logs true
/lp group moderator permission set minertrack.sendnotify true
# Helper: only receive alerts
/lp group helper permission set minertrack.use true
/lp group helper permission set minertrack.notify true
# Trusted player: bypass detection (USE SPARINGLY)
/lp user TrustedPlayer permission set minertrack.bypass true
PermissionEx:
groups:
admin:
permissions:
- minertrack.*
moderator:
permissions:
- minertrack.use
- minertrack.check
- minertrack.verbose
- minertrack.notify
- minertrack.logs
- minertrack.sendnotify
helper:
permissions:
- minertrack.use
- minertrack.notify
trusted:
permissions:
- minertrack.bypass
⚠️ Critical: minertrack.bypass
What It Does
- Completely disables X-Ray detection for the player
- Player can mine any ore, any pattern, without VL increase
- Does not affect other players' detection
When to Grant
- ✅ Server owner / head admin (for testing)
- ✅ Content creators / streamers (with monitoring)
- ❌ Regular staff / moderators
- ❌ Donors / VIP players
- ❌ Anyone you don't fully trust
Force Monitoring Everyone
Set in config.yml:
disable_bypass_permission: true
This ignores minertrack.bypass — even ops and bypass holders are monitored.
Recommendation: Keep
disable_bypass_permission: falsebut never giveminertrack.bypassto regular staff. Only server owners for testing.
👮 Staff Workflows
Daily Monitoring Routine
# 1. Enable verbose mode at shift start
/mtrack verbose
# 2. Monitor chat for alerts like:
# [MinerTrack] Notch failed X-Ray check VL:3(+1) Block:diamond_orex3...
# 3. Investigate suspicious players
/mtrack check Notch
# 4. If confirmed X-Ray:
/mtrack kick Notch "X-Ray detected - VL 5"
# 5. If false positive:
/mtrack reset Notch
# 6. Disable verbose at shift end
/mtrack verbose
Investigation Checklist
| Step | Action | Command |
|---|---|---|
| 1 | Check current VL | /mtrack check <player> |
| 2 | View recent logs | /mtrack logs <date>.log |
| 3 | Check mining pattern | Look for: direct paths, no caves, rare ores only |
| 4 | Compare to baseline | Normal players: VL 0-1, occasional 2 |
| 5 | Take action | Kick / Reset / Monitor longer |
Discord Webhook Integration
Staff with minertrack.notify receive in-game alerts AND Discord webhooks fire when VL ≥ vl-required (default: 4).
Webhook Payload Includes:
- Player name, UUID, current VL
- Ore type, count, vein count
- World, coordinates
- Timestamp
🖥️ Console Usage
All commands work from server console (prefix with mtrack):
# Console examples
mtrack help
mtrack reload
mtrack verbose
mtrack check Notch
mtrack reset Notch
mtrack kick Notch "X-Ray"
mtrack notify "Console alert: Check Notch"
mtrack update
mtrack logs 2024-01-15.log
Console Permissions: Console has all permissions by default.
📝 Command Aliases
| Primary | Aliases |
|---|---|
/mtrack |
/minertrack, /mt |
reload |
rl |
verbose |
v |
check |
c |
reset |
rs |
kick |
k |
notify |
n |
update |
up |
logs |
log |
🔗 Related Pages
- Installation — Initial setup
- Configuration — Configuring detection, webhooks, messages
- Troubleshooting — Command issues, permission problems
- FAQ — Common command questions