Performance Optimization

ArenaLite is lightweight by design. Follow these tips to keep your FFA smooth when player counts rise.

Storage Choices

YAML (default)

Small/medium servers

Zero configuration, stored in plugins/ArenaLite/playerdata/

MySQL

Shared or high-population servers

Async read/write through Bukkit scheduler. Ensure database server is nearby.

Arena Regeneration

  • Regeneration works out-of-the-box via built-in snapshot restore
  • FAWE is optional but improves performance on large regions
  • Keep selections as tight as possible—larger regions mean longer snapshots
  • Tune regen.blocks-per-tick in config.yml to balance TPS vs. speed (default: 500)
  • Adjust arenas.default-regen-interval based on server TPS

Build & PvP Overrides

  • ArenaLite registers high-priority listeners to ensure your build settings override other plugins
  • If you want another plugin to control building, disable in config.yml (arenas.default-build-enabled)
  • Use /ffasetup build to toggle per-arena build settings

Join & Cleanup Buffs

Join protection and anti-cleanup effects use standard potion effects and invulnerability. They are configurable because:

  • Join protection and anti-cleanup effects use standard potion effects and invulnerability
  • Disabling them saves a few scheduler tasks
  • Lowering durations reduces interference with other combat plugins

Monitoring Checklist

  • Watch console for warnings during arena regen (FAWE load messages, snapshot restore progress)
  • Track database latency if using MySQL—slow connections show as delayed stat updates
  • Use /ffasetup list periodically to verify arena state

General Advice

  • Keep backups of arenas.yml and kits.yml before major edits
  • Use /ffa reload sparingly on busy servers—it writes kits/arenas synchronously
  • Remove unused arenas with /ffasetup delete <arena> to keep configuration lean