Best Practices

Server Software

• Paper - recommended for best performance
• Purpur - good alternative, additional optimizations
• Spigot - minimum requirement, works but less optimized
• Java 17 minimum, Java 21 recommended

Performance Tuning by Server Size

Setting	Small (under 20 players)	Medium (20-50)	Large (50+)
general.global-concurrent-cap	25	50	100
general.max-global-queue-size	500	1000	2000
general.max-player-queue-size	50	100	150
tools.pickaxe.per-tick-limit	15	20	25
tools.pickaxe.max-blocks-per-use	50	80	100

Economy Examples

economy:
  enabled: true
  currency: "vault"
  costs:
    pickaxe: 5.0
    axe: 3.0
    bucket: 1.0
    hoe: 2.0
  rewards:
    pickaxe: 0.5
    axe: 0.3
    bucket: 0.1
    hoe: 0.2

Set economy.enabled: false to disable entirely.

Protection Integration

general:
  lands-integration: true
  worldguard-integration: true
  griefprevention-integration: true

tools:
  pickaxe:
    check-protection: true  # recommended: always enable

World Limiting

tools:
  pickaxe:
    worlds:
      - world
      - world_nether
      - world_the_end

Use the worlds list per tool to restrict where it functions (e.g. higher max-blocks-per-use/per-tick-limit for a dedicated resource world; consider disabling economy in creative worlds).

Monitoring

debug:
  enabled: true
  operations: true
  performance: true
  log-to-file: true

• Check queue/op load: /sigmatools debug queue, /sigmatools debug ops
• Check integration status: /sigmatools debug info
• File log: logs/sigmatools-debug.log
• Back up plugins/SigmaTools/config.yml and messages.yml regularly

See Also

• Configuration
• Troubleshooting
• FAQ