Skip to main content

Commands

Complete reference for all SigmaTools commands, including usage, arguments, permissions, and examples.

Command Overview

SigmaTools provides a single main command /sigmatools (aliases: /st, /sigmatool) with several subcommands for administration and debugging.

Main Command

/sigmatools

Permission: sigmatools.admin (default: op)
Aliases: /st, /sigmatool
Description: Main command for SigmaTools administration

Usage:

/sigmatools [subcommand] [arguments]

Subcommands:

  • give - Give tools to players
  • bind - Bind custom items to tools
  • reload - Reload configuration
  • debug - Debug commands

Give Command

/sigmatools give <tool> <player>

Permission: sigmatools.admin (default: op)
Description: Give a SigmaTools item to a player

Arguments:

  • <tool> - Tool type: pickaxe, axe, bucket, or hoe
  • <player> - Target player name (must be online)

Examples:

# Give pickaxe to yourself
/sigmatools give pickaxe YourName

# Give axe to another player
/sigmatools give axe PlayerName

# Give bucket tool
/sigmatools give bucket PlayerName

# Give hoe tool
/sigmatools give hoe PlayerName

Expected Output:

[SigmaTools] ✅ Successfully gave pickaxe to PlayerName!

Error Messages:

  • §cUsage: /sigmatools give <tool> <player> - Missing arguments
  • §cInvalid tool type: <tool> - Invalid tool name
  • §cPlayer not found: <player> - Player not online
  • §cFailed to give tool to <player> - Tool creation failed

Tab Completion:

  • First argument: pickaxe, axe, bucket, hoe
  • Second argument: List of online players

Bind Command

/sigmatools bind <tool>

Permission: sigmatools.admin (default: op)
Description: Bind a custom item to a tool type using a GUI

Arguments:

  • <tool> - Tool type: pickaxe, axe, bucket, or hoe

Examples:

# Bind a custom pickaxe item
/sigmatools bind pickaxe

# Bind a custom axe item
/sigmatools bind axe

Behavior:

  • Opens a GUI showing items from your inventory
  • Valid items are highlighted in green
  • Invalid items are highlighted in red
  • Click an item to bind it to the tool
  • Supports both vanilla items and ItemsAdder custom items

What Gets Bound:

  • The item's material type (for vanilla items)
  • ItemsAdder custom item ID (for ItemsAdder items)
  • Binding is saved to config.yml automatically

Configuration: After binding, the config will contain:

tools:
pickaxe:
bound-item:
type: "vanilla" # or "itemsadder"
material: "IRON_PICKAXE"
# itemsadder-id: "namespace:id" # if ItemsAdder item

Expected Output:

Successfully bound item to pickaxe!

Error Messages:

  • §cUsage: /sigmatools bind <tool> - Missing arguments
  • §cInvalid tool type: <tool> - Invalid tool name
  • §cInvalid item! You must select a <tool>. - Selected invalid item type
  • §cFailed to bind item. Check console for errors. - Binding failed

Tab Completion:

  • First argument: pickaxe, axe, bucket, hoe

Notes:

  • Only admins can use this command
  • Bound items replace the default item-material setting
  • ItemsAdder items are automatically detected if ItemsAdder is installed
  • Bound items must match the tool type (pickaxe for pickaxe tool, etc.)

Reload Command

/sigmatools reload

Permission: sigmatools.admin (default: op)
Description: Reload all plugin configuration files

Usage:

/sigmatools reload

What Gets Reloaded:

  • config.yml - Main configuration
  • messages.yml - Message templates
  • All manager settings (cooldown, durability, economy, etc.)
  • Tool configurations

Examples:

# Reload after editing config.yml
/sigmatools reload

Expected Output:

[SigmaTools] ✅ Configuration reloaded successfully!

Error Messages:

  • §c❌ Failed to reload configuration! - Configuration error (check server logs)

Notes:

  • Reloading is safe and doesn't affect active operations
  • Changes take effect immediately
  • Invalid configuration may cause errors (check logs)

Debug Commands

/sigmatools debug <subcommand>

Permission: sigmatools.admin (default: op)
Description: Debug and diagnostic commands

Debug Info

Command: /sigmatools debug info

Description: Show general plugin information

Output:

=== SigmaTools Debug Info ===
Plugin Version: 1.0.3
Enabled Tools: 4
Lands Integration: true
WorldGuard Integration: true

Debug Queue

Command: /sigmatools debug queue

Description: Show operation queue information

Output:

=== Queue Information ===
Global Operations: 5
Global Concurrent Cap: 50

Debug Operations

Command: /sigmatools debug ops

Description: Show performance operation information

Output:

=== Operations Information ===
Per-Tick Limit: 20
Your Operations: 2

Note: Only shows your operations if run by a player

Debug Status

Command: /sigmatools debug status

Description: Show debug system status

Output:

=== SigmaTools Debug Status ===
Master Debug: Enabled
Categories:
- Protection: Enabled
- Performance: Disabled
- Operations: Enabled
- Cooldown: Disabled
- Durability: Disabled
- Integration: Enabled
Settings:
- Timestamps: Enabled
- Thread Info: Disabled
- File Logging: Enabled

Debug Toggle

Command: /sigmatools debug toggle <category|all> [on|off]

Description: Enable or disable debug logging categories

Arguments:

  • <category> - Category name or all for master toggle
  • [on|off] - Enable or disable (default: on)

Categories:

  • protection - Protection plugin integration
  • performance - Performance monitoring
  • operations - Tool operations
  • cooldown - Cooldown system
  • durability - Durability system
  • integration - Plugin integrations
  • all - Master debug toggle

Examples:

# Enable all debug logging
/sigmatools debug toggle all on

# Disable all debug logging
/sigmatools debug toggle all off

# Enable protection debugging
/sigmatools debug toggle protection on

# Disable performance debugging
/sigmatools debug toggle performance off

Expected Output:

[SigmaTools] Debug logging enabled for all categories
[SigmaTools] Debug logging enabled for protection
[SigmaTools] Debug logging disabled for performance

Error Messages:

  • §cUsage: /sigmatools debug toggle <category|all> [on|off] - Invalid arguments
  • §cInvalid category. Valid categories: protection, performance, operations, cooldown, durability, integration - Invalid category

Notes:

  • Changes are saved to config.yml immediately
  • Debug manager is reloaded automatically
  • File logging requires debug.log-to-file: true in config

Command Aliases

All commands support these aliases:

  • /sigmatools/st or /sigmatool
  • /st give/sigmatools give
  • /st reload/sigmatools reload
  • /st debug/sigmatools debug

Tab Completion

Tab completion is available for all commands:

Main command:

  • give, bind, reload, debug

Give command:

  • First argument: pickaxe, axe, bucket, hoe
  • Second argument: Online player names

Bind command:

  • First argument: pickaxe, axe, bucket, hoe

Debug command:

  • First argument: info, queue, ops, toggle, status
  • Second argument (toggle): all, protection, performance, operations, cooldown, durability, integration
  • Third argument (toggle): on, off

Permission Requirements

CommandPermissionDefault
/sigmatoolssigmatools.adminop
/sigmatools givesigmatools.adminop
/sigmatools bindsigmatools.adminop
/sigmatools reloadsigmatools.adminop
/sigmatools debugsigmatools.adminop

Common Usage Patterns

Daily Administration

# Check plugin status
/sigmatools debug status

# Give tools to new players
/sigmatools give pickaxe NewPlayer
/sigmatools give axe NewPlayer

# Bind custom items to tools
/sigmatools bind pickaxe
/sigmatools bind axe

# Reload after config changes
/sigmatools reload

Troubleshooting

# Enable all debug logging
/sigmatools debug toggle all on

# Check queue status
/sigmatools debug queue

# Check operations
/sigmatools debug ops

# Disable debug when done
/sigmatools debug toggle all off

Bulk Tool Distribution

# Give tools to multiple players (run multiple times)
/sigmatools give pickaxe Player1
/sigmatools give pickaxe Player2
/sigmatools give pickaxe Player3

Error Handling

All commands provide clear error messages:

  • Permission denied: §cYou don't have permission to use this tool!
  • Invalid arguments: Usage message with correct syntax
  • Player not found: §cPlayer not found: <name>
  • Configuration errors: Check server logs for details

Next Steps