1. Docs
  2. /
  3. BanManager
  4. /
  5. Configuration
  6. /
  7. schedules.yml

schedules.yml

Controls how often data is synced between the database and Minecraft server to punish players across multiple servers. If you are updating punishments directly via the database, ensure you update the timestamps of the relevant punishments to correctly sync back to the Minecraft server.

PlatformLocation
CraftBukkit/Spigot/Paper/plugins/BanManager/schedules.yml
BungeeCord/plugins/BanManager/schedules.yml
Sponge/config/banmanager/schedules.yml
Velocity/plugins/BanManager/schedules.yml
  • scheduler
    • expiresCheck - The number of seconds the server will check for expired punishments
    • playerBans - The number of seconds the server will check for for player bans changes
    • playerMutes - The number of seconds the server will check for player mutes changes
    • playerWarnings - The number of seconds the server will check for player warnings changes
    • ipBans - The number of seconds the server will check for ip bans changes
    • ipRangeBans - The number of seconds the server will check for ip range changes bans
    • rollbacks - The number of seconds the server will check for /bmrollback uses
    • nameBans - The number of seconds the server will check for name bans changes
    • externalPlayerBans - The number of seconds the server will check for global player ban changes; disabled if global database not enabled
    • externalPlayerMutes - The number of seconds the server will check for global player mute changes; disabled if global database not enabled
    • externalPlayerNotes - The number of seconds the server will check for global player note changes; disabled if global database not enabled
    • externalIpBans - The number of seconds the server will check for global player ip changes; disabled if global database not enabled
    • saveLastChecked - The number of seconds the server will update lastChecked values in this file
  • lastChecked - Represents the timestamps of when the server last checked for data changes, do not change these values

Example

scheduler:
  expiresCheck: 30
  playerBans: 30
  playerMutes: 30
  playerWarnings: 30
  ipBans: 30
  ipRangeBans: 30
  rollbacks: 30
  nameBans: 30
  externalPlayerBans: 120
  externalPlayerMutes: 120
  externalPlayerNotes: 120
  externalIpBans: 120
  saveLastChecked: 60

About

  • by James Mortemore © 2012 - 2024