Compatible Plugins

MythicSeasons needs none of these plugins. Each one adds the features below.

A softdepend plugin loads before MythicSeasons, and a loadbefore plugin after it. Restart the server after you add or remove one of these plugins.

MythicMobs

MythicSeasons adds to MythicMobs:

• 24 conditions, such as season, playertemp and atmosphere
• 11 mechanics, such as modifytemp, blockheat and atmosphereforce
• 37 placeholders named <mythicseasons.*>
• skill-triggers in season files, for ticks, season changes and weather changes (see Triggers)
• the bundled pack of ready-made skills
• event signals and weather answers for built-in conditions and mechanics

Without MythicMobs there is no pack and no skill triggers: only the air sets a player's temperature, with no readout, warnings or effects, and players see no rain, snow, wind or storm effects.

Event signals

When an event starts or ends in a world, every active Mythic mob there receives the signal startEvent_<id> or endEvent_<id>, with the event file's id in lowercase.

Carolers:
  Type: villager
  Skills:
  - message{m="Merry Christmas!"} @PlayersInRadius{r=30} ~onSignal:startEvent_christmas

The signal name is case sensitive.

Weather conditions and mechanics built into MythicMobs

MythicSeasons answers MythicMobs' own weather conditions raining, israining, sunny, issunny, snowing, issnowing, thundering, stormy, isthundering and isstormy from its weather sources.

In a world with the atmosphere on (the master enabled in atmosphere.yml and the world switched on), it refuses the mechanics weather, and effect:thunderlevel when its target is a player.

Both need a MythicMobs build that lets plugins replace its built-in conditions and mechanics. Otherwise the console logs This MythicMobs build has no component provider API (<reason>); its built-in weather conditions and mechanics will keep using server weather. at startup.

MythicProxy

MythicProxy shares one weather per world between backend servers while the atmosphere is on. See Shared Weather.

• With the default shared-weather-group: auto in atmosphere.yml, a server whose MythicProxy name ends in a dash and a number joins the group named by the part before the dash (survival-1 joins survival). Servers with other names simulate their own weather.
• Servers share only when grid.cell-size, grid.y-min, the number of sky levels (from grid.y-min, grid.y-max and grid.cell-size.y), timing.step-period-ms, timing.time-acceleration and the world seed match. Servers that differ form separate groups.
• atmosphereforce and atmosphereprofile casts on any server of the group reach the shared weather.
• The weather is saved on the MythicProxy hub. A new map with another seed starts with fresh weather.
• /ms atmosphere info shows each world's shared weather status.

Console messages:

• MythicProxy is installed but its network API is unavailable (<reason>); the weather is not shared between servers
• Atmosphere is waiting for MythicProxy to name this server before the weather starts: logged every minute until it does. The weather waits until then.
• Lost the MythicProxy lease for the weather of <world>; it pauses here until the lease is renewed: the server lost contact with MythicProxy.
• MythicProxy was disabled; the shared weather stays paused until the next restart

PlaceholderAPI

MythicSeasons registers a built-in expansion ms (for example %ms_season%, all listed on PlaceholderAPI), so no /papi ecloud download is needed.

It also resolves PlaceholderAPI placeholders in the commands.start and commands.stop lists of an event file, but without a player, so placeholders that need one do not resolve there. Without PlaceholderAPI they stay as typed.

WorldGuard

With WorldGuard and WorldEdit installed, MythicSeasons adds ten region flags.

/rg flag spawn permanent-weather CLEAR
/rg flag spawn season-effects deny
/rg flag lodge permanent-season winter
/rg flag greenhouse permanent-temperature 22
/rg flag hotspring temperature-modifier 5

spawn stays dry without seasonal effects, lodge always shows winter, greenhouse stays at 22 degrees and hotspring adds 5.

How the flags are read:

• Every flag except season-atmosphere and season-clouds applies to a chunk only when the region contains the chunk's centre column at sea level height. A region whose height range leaves out the sea level never applies.
• season-atmosphere and season-clouds are read at the block where the player or mob is.
• Changes to the other flags reach body temperature, crops, weather, wind and hasseasons within about 5 seconds.
• Colours and client-side blocks only change on chunks sent after the flag changed: after a rejoin or a trip away from the area, at the world's next season or sub-season change, or when a skill resends the chunks around its caster with seasonpopulator{action=refresh;radius=6} @Self (see SeasonPopulator).
• Overlapping regions follow WorldGuard's region priority rules.
• permanent-temperature overrides every modifier, and also applies where season-effects is deny. temperature-modifier does not apply there.
• GriefPrevention outranks WorldGuard: when both fix the temperature of a chunk, the GriefPrevention value is used.

The colours and block rules of permanent-season follow the world's sub-season phase: in START or EARLY the colours blend with the season before it in season-cycle, in LATE or END with the season after it. The flag needs modify-biome-on-client: true in config.yml, and players who turned season colours off do not see it.

WorldGuard without WorldEdit logs You'll need WorldEdit installed on your server to use WorldGuard with MythicSeasons! and gets no flags.

WorldEdit

The WorldGuard support needs WorldEdit. MythicSeasons uses it for nothing else.

GriefPrevention

With GriefPrevention installed, MythicSeasons creates griefprevention.yml, which applies to chunks that contain claims. Changes need a restart. See Land Claims.

claimed-areas:
  seasons-enabled: false
  fixed-temperature:
    enabled: true
    value: 22

Claims show no seasonal effects and keep players at 22 degrees.

dynmap

To pause dynmap and BlueMap rendering in a season, set both:

pause-map-plugins-render-in-winter: true

pause-map-render: true

The first goes in config.yml (default false), the second in a season file (true in the shipped winter.yml, false in the other three seasons).

The pause starts when a world's season or sub-season changes, and ends when the world changes to a season with pause-map-render: false. With both plugins installed, only dynmap is used.

The pause is not saved: after a restart it comes back only at that world's next season or sub-season change.

For dynmap the pause is server-wide, on while any world is in a pausing season.

BlueMap

BlueMap uses the same settings as dynmap. MythicSeasons freezes every BlueMap map of a world in a pausing season, and unfreezes them when the season ends.

Multiverse-Core

Multiverse-Core only changes the load order, and its worlds behave like any other. on-new-world-creation in config.yml applies to the worlds it creates.

Saved values are restored at startup, only for worlds loaded by the first server tick. A world that a plugin loads later, Multiverse-Core included, is not restored.

Other plugins

• Custom biomes from other plugins go under includes in a file in the biomes folder, or use includes: ALL. See Biomes.
• Other plugins can add weather providers and cloud layer types, see Weather Providers and Cloud Layer Types.
• The cloud fog pack can be your server resource pack or be merged into yours, see Shader Pack.

MythicSeasons does not need ProtocolLib or PacketEvents, and does not check the version of these plugins.