Skip to main content

๐Ÿ”ง Z-Craft Admin Commands: Complete Staff Reference

Essential command reference for Z-Craft staff and administrators. This comprehensive guide covers all moderation, server management, and administrative commands used to maintain a safe and fair gaming environment.
Command Access: Requires appropriate permission levels โ€ข All commands logged โ€ข Use responsibly
Important: Admin commands should only be used by authorized staff. All actions are logged and monitored. Misuse may result in administrative action.

๐Ÿ‘‘ Permission Levels & Access Control

Staff Hierarchy

Command Categories

  • ๐ŸŽฏ Moderation - Player discipline and chat control
  • ๐Ÿงญ Teleportation - Movement and location management
  • ๐Ÿ’ฐ Economy - Currency and shop administration
  • ๐ŸŒ Server - Performance and system management
  • ๐Ÿ“Š Information - Player data and statistics
  • ๐Ÿ›ก๏ธ Security - Protection and anti-cheat tools

๐ŸŽฏ Player Moderation Commands

Warning & Communication Control

Disciplinary Actions

Ban Management & Information

Duration Formats

Time Units for Temporary Actions:
  • 30s - 30 seconds
  • 5m - 5 minutes
  • 2h - 2 hours
  • 7d - 7 days
  • 1w - 1 week
  • 30d - 30 days
  • 1M - 1 month

๐ŸŒ Server Management & Performance

System Monitoring

Server Control

World & Environment

๐Ÿ’ฐ Economy & Currency Management

Player Currency Control

Shop Administration

Economy Monitoring

๐Ÿ“Š Information & Investigation Tools

Player Information

Logging & Investigation

๐Ÿ›ก๏ธ Protection & Security

Claim Management

Security Controls

๐Ÿ”ง Advanced Administration

Plugin Management

Configuration Management

Database Operations

๐Ÿ› Debugging & Troubleshooting

Performance Debugging

Player Monitoring

๐Ÿ“‹ Command Usage Guidelines

Best Practices

Always Include Reasons:
  • Provide clear, specific reasons for disciplinary actions
  • Document evidence and context
  • Use consistent formatting
Communication Standards:
  • Be professional and respectful in all interactions
  • Explain actions clearly to affected players
  • Use appropriate communication channels
Documentation Requirements:
  • Log all significant actions
  • Include timestamps and context
  • Maintain detailed records for appeals

Common Command Patterns

Moderation Workflow:
  1. /warn Player1 First offense warning
  2. /mute Player1 30m Continued violation
  3. /kick Player1 Final warning
  4. /tempban Player1 1d Pattern of violations
Investigation Process:
  1. /playerinfo Player1 - Basic information
  2. /logs chat Player1 1h - Recent activity
  3. /seen Player1 - Login patterns
  4. /stats Player1 - Behavior analysis

โš ๏ธ Critical Commands & Safety

Dangerous Operations

These commands can cause data loss or server instability. Use extreme caution:
  • /economy reset - Irreversible balance reset
  • /db restore - Overwrites current data
  • /stop - Immediate server shutdown
  • /money set - Economy impact
Always:
  • Create backups before major operations
  • Test commands in a development environment first
  • Have rollback procedures ready
  • Notify other administrators of major changes

โ“ Command Troubleshooting

Common Issues

Command Not Working:
  • Check your permission level with /rank
  • Verify command syntax
  • Ensure target player is online
  • Check for plugin conflicts
Permission Errors:
  • Contact higher-level staff for access
  • Verify youโ€™re in the correct group
  • Check if command is enabled in config
Unexpected Results:
  • Review command logs
  • Check for conflicting plugins
  • Verify target exists
  • Test with simpler parameters

Getting Help

Internal Resources:
  • /help - Basic command list
  • /adminhelp - Staff command reference
  • Discord #staff channel for assistance
External Support:
  • Plugin documentation
  • Server administration forums
  • Professional Minecraft hosting support

Remember: With great power comes great responsibility. Use these commands to maintain a fair, safe, and enjoyable environment for all Z-Craft players. All administrative actions are logged and subject to review. ๐Ÿ›ก๏ธโš”๏ธ๐Ÿ’š โœ… Best Practices:
  • Log all administrative actions
  • Use /warn before /mute
  • Check logs before banning
  • Communicate with team
  • Document decisions
  • Review appeals fairly

Need help with commands? Ask in staff-help channel! ๐Ÿ’š