Calendar

calendar.yml in plugins/MythicSeasons/ gives every world with a season a date, a weekday and a clock. The date decides when seasons change and events run. /ms reload reads the file again.

A file without an enabled line has the calendar off, although the shipped file has enabled: true.

General

• With the calendar off, events still start and stop on a date change from /ms setdate, /ms nextseason or a real midnight in synced mode, which also sets the season with automatic-season-cycling.
• With american-date-format: true, swap the numbers in the shipped event files, or christmas, easter and halloween are skipped with a warning.

Real time

• Synced mode needs twelve months in calendar order and seven weekdays starting with Monday.
• In synced mode a date set with /ms setdate is never read back, and /ms pausetime refuses worlds with a season. The day change runs at each real midnight while modify-daynight-length or modify-weather-cycle is on.
• /ms reload applies a new time zone, but going back to system needs a restart.

Clock

Week days

Worlds

• none is a placeholder and is ignored.
• A world moved forward to another world's date goes through a normal date change.
• With on-new-world-creation.sync-with-other-worlds in config.yml, worlds created or loaded after startup (not Nether or End) join synced-worlds and get the season of today's real date.
• Events still count as active in worlds-without-events worlds, unlike an event's own disabled-worlds. See Per-world control.

Season start dates

Every season in season-cycle of config.yml needs a line <season id>-start: <Month> <day>, custom seasons too. Write the month exactly as under months (case counts, spaces are fine), with no year.

• A season lasts until the day before the next start date, so the dates must follow the order of season-cycle. Do not give two seasons the same date. The day is not checked against the month length.
• A season without a start line is never reached.
• An unknown month name, a day that is not a whole number or a value without a space stops MythicSeasons from starting, or makes /ms reload fail.

Months

Dates are saved by month number. After you remove or reorder months, fix each world's date with /ms setdate: a saved month above the new count breaks that world's time handling.

The date

Each world with a season keeps its own date, saved in data.yml every performance.autosave-interval-minutes.

A world can get a season without a date, from on-new-world-creation or from /ms set with the calendar or sub-seasons off. Until /ms setdate, /ms nextseason, a restart or a counted day gives it one, it has no active event and, with modify-daynight-length on, its time stands still. While the calendar and sub-seasons are on, /ms set fails with an error there, so give it a date first. The first date is not a date change, so no event starts or stops.

How the date advances

• By default, one day each time the world clock passes 18000 (midnight). Setting the clock back from before 18000 (sleeping, /time set) counts a day too.
• With calendar-is-real-life-days, at each real midnight. In synced mode it is always the real date.
• /ms setdate, /ms nextseason and /ms set move it by command.
• In synced-worlds, a world that is behind takes the date of the one furthest ahead.

The year goes up after the last day of the last month. Years start at 0, or are the real year in synced mode.

What a date change does

• With automatic-season-cycling on, the world takes the season of the new date.
• Events start and stop as their schedule type says.
• Where temperature is on, the world picks a new base temperature.

With automatic-season-cycling on, the season follows the date within a second, so a season set by command flips back unless the date moved with it. /ms nextseason always moves the date, /ms set only while sub-seasons are on.

The clock

• While modify-daynight-length is on, the plugin runs the clock of every world with a season at the month's day and night lengths, with the daylight cycle game rule off. The minutes are real minutes only at 20 ticks per second.
• The clock text stretches with the month: sunrise reads about 07:48 in January and 04:12 in July.
• At night or in a storm, enough sleeping players (the players sleeping percentage game rule, rounded down, at least one) set the time to 0 and start clear weather for clear-weather-min-duration to clear-weather-max-duration of config.yml.
• /ms pausetime pauses a world's clock, in overworld-type worlds only. With a season and modify-daynight-length on, that also stops the date and sleeping and is saved. Elsewhere it switches the daylight cycle game rule.

Commands

All need mythicseasons.admin, except /ms getinfo (mythicseasons.getinfo, everyone). See Commands and Permissions for the rest.

/ms setdate works in any world. In a world without a season that has a stored date (for example after /ms disable), it gives the world the season of the new date while automatic-season-cycling is on.

Placeholders

Without a date or with the calendar off, the date placeholders show 0 for numbers and none for names. Full lists: Placeholders and PlaceholderAPI.

Console messages

Examples

sync-time-with-real-world: true
time-sync-timezone: 'Europe/London'
time:
  format: '$hours$:$minutes$'
  12-hour-clock:
    enabled: true
    add-am-pm: true

The sky and the date follow the clock in London, and the time placeholders read like 03:45 PM.

synced-worlds:
- world
- world_resource
worlds-without-events:
- world_resource

Both worlds share one clock and date, and events run their lines only in world.

months:
  Thaw: {days: 20, day-length-in-min: 10, night-length-in-min: 10}
  Highsun: {days: 20, day-length-in-min: 13, night-length-in-min: 7}
  Harvest: {days: 20, day-length-in-min: 10, night-length-in-min: 10}
  Frost: {days: 20, day-length-in-min: 7, night-length-in-min: 13}
spring-start: Thaw 1
summer-start: Highsun 1
fall-start: Harvest 1
winter-start: Frost 1

An 80-day year with one 20-day month per season. Event files for this calendar use month numbers 1 to 4.