schedule.yml

# ============================================================
#  RoodyEvents · schedule.yml · when events start by themselves
#  Also in the menu: /events admin → Schedule. After editing the file: /events reload
#  /events pause stops the schedule until /events resume. /events next shows what comes.
# ============================================================

# false = no event starts by itself (they can still be started with /events start).
enabled: true

# Every how long one event of the rotation starts (the events with auto: true and enabled).
# 0 = no rotation, only the fixed times below. Examples: 30m, 1h, 1h30m.
every: 45m

# How the next one is picked: random (by each event's weight) or order (one after another).
# It is picked ahead, so /events and %roodyevents_next% show what comes.
pick: random

# With fewer players online that turn is skipped. When the next event asks for more players
# (its min-players) than are online, another one that can start takes its turn.
min-players: 1

# An automatic event does not start while this many events are running: the rotation waits
# until they end (and a minute more). A fixed time is skipped.
max-running: 1

# Seconds before an automatic (or delayed) event when the countdown is announced.
countdown: [300, 60, 30, 10, 5, 4, 3, 2, 1]

# Fixed times: "HH:mm", "HH:mm <event>" or "<days> HH:mm [event]" (days: mon, tue, wed, thu,
# fri, sat, sun, several with commas). Without an event, one of the rotation is picked.
# Examples: "20:00 supply-drop", "sat,sun 18:30 forgotten-king", "12:00"
times: []

# Time zone of the fixed times (Europe/Madrid, America/New_York...). Empty = the server's.
time-zone: ""