custom-events:
dated-events:
october-event-example:
enabled: false
name: "&6Spooky October"
display-event: true
times:
event-start:
date: 1/10
event-stop:
date: 1/11
commands:
start:
- "&aOctober has started, monsters are becoming stronger and stronger.."
- "/difficulty hard"
stop:
- "/difficulty normal"
weekly-events:
safe-sunday-example:
enabled: false
name: "&aSafe Sunday"
display-event: true
day: Sunday
commands:
start:
- "&6It is now &7Sunday %day%/%month%/%year%. &6Time for a break, dying isn't dangerous for the day"
- "/gamerule keepInventory true"
stop:
- "/gamerule keepInventory false"
daily-events:
daily-message-example:
enabled: false
commands:
- "&3Midnight has passed, &f%weekday%, %month_asname% %day%, year %year%&3 has started"
- "&3Current season: &f%season%"
This file allows you to create as many planned events as you want. These events can be daily, weekly or on specific dates. You can send messages to the player or run commands as the console (include a '/' before the command) when the event starts and stops. Possible placeholders in commands are %day%, %month%, %month_asname%, %year%, %weekday%, %season%, %world%. All external placeholders by PlaceHolderAPI are also supported.
The dates in dated events can be: dd/mm/yyyy or mm/dd/yyyy if American date format is enabled in the calendar.yml. Not including a year makes the event run every year (see october-event-example). You can also enter only a day ("date: 5"), this will make the event run every month between the specified days.
Active events can be viewed by the user through /season or the placeholder %rs_active_events%. This can be disabled separately for each event with "display-event". The "name" field will be used to display it. Colour codes can also be used.
Build-in events
Events.yml has a similar configuration as the custom-events.yml except that is has extra settings for build-in season events like Christmas, New year, Easter and Halloween. Here is the default file:
