Documentation

Config

File locations, defaults, and behavior for PlayerBatch configuration, saved kits, and saved combat presets.

Main Config File#

PlayerBatch writes its main runtime config to:

text
config/playerbatch.properties

The current source defines these keys:

  • maxSummonCount
  • maxSpawnsPerTick
  • debugEnabled

Defaults#

Based on the current code:

  • maxSummonCount = 256
  • maxSpawnsPerTick = 4
  • debugEnabled = false

Behavior#

The config is loaded on initialization and sanitized before use:

  • maxSummonCount is clamped to a minimum of 1
  • maxSpawnsPerTick is clamped to a minimum of 1
  • invalid numeric values fall back to the built-in defaults

These values can also be changed live with commands and are saved back automatically.

Saved Kits#

PlayerBatch stores saved loadouts in:

text
config/playerbatch-kits.properties

Kits are keyed by normalized names and preserve saved equipment and inventory state for reuse with:

text
/pb kit save <name>
/pb kit load <name>
/pb kit self <name>

Saved Combat Presets#

Combat preset definitions are stored in:

text
config/playerbatch-combat-presets.properties

These records preserve:

  • preset name
  • default count
  • raw combat option string

Typical Admin Workflow#

text
/pb limit 512
/pb spawnspertick 8
/pb debug on

Then confirm the resulting values in the playerbatch.properties file if you want a file-level audit trail.

When to raise spawns per tick

Raise maxSpawnsPerTick when your server can comfortably absorb more spawning work per tick. If you are tuning for stability on shared or lower-headroom environments, keep this lower and let the queue spread the load.