Ban-Wave Configuration

Ban-wave scheduling is disabled by default. Review its queue and moderation policy before using the command.

What this file controls

Ban-wave scheduling is disabled by default, the schedule list starts empty, and the queue limit is 5,000 players.

The /fairplay banwave command requires fairplay.command.banwave. Queue changes are moderation decisions; follow your staff review and appeal policy before using them.

Stage a ban-wave change as a moderation decision

  1. Back up the generated banwave.yml and review its schedule and queue values.
  2. Confirm the operator has fairplay.command.banwave and consult the installed command usage for accepted subarguments.
  3. Route schedule and queue changes through your server’s review and appeal policy.
  4. Test the configured workflow with staff before using it for moderation.

Apply and verify changes

After editing a setting, use the reload command when that setting supports reload. If the change does not take effect, check the configuration troubleshooting guide for the setting’s restart requirements.

Browse all documentation