F A Q
Quick answers to common questions. If a feature does not work, start with Troubleshooting.
- Do I need MythicMobs?
- Which Minecraft versions and server software does it support?
- How do I start seasons in a world?
- Can each world have its own season?
- Does MythicSeasons change the blocks in my world?
- How long does a season last, and how do I change that?
- Why does the season I set with /ms set change back?
- How do I stop the seasons from changing by themselves?
- How do I add my own season?
- How do I turn on the weather simulation?
- Why do players see no rain or snow?
- Why does /weather clear not stop the rain?
- How much server load does the weather simulation cause?
- Why can't players see the volumetric clouds?
- Do players need a resource pack for the clouds?
- Why do some players or places show vanilla colours?
- What can players change for themselves, and who can use /ms?
- Should I use /ms reload or /mm reload, and what needs a restart?
- Why does my skill do nothing, for example with isfrozen?
- Why is a player's temperature not changing?
- How do I show the season, the date or the temperature in a scoreboard?
- Why do my event commands run more than once, or not at server start?
- Where does MythicSeasons save its data, and how do I reset it?
- Can servers share one weather?
Do I need MythicMobs?
No. Seasons, sub-seasons, the calendar, events, biome colours, client-side blocks, crop growth, the air temperature and the volumetric clouds run without it. Without it no season skill runs: players see no simulated rain, snow, wind or storm effects, and body temperature comes only from the air, /ms temperature changes and region settings, with no readout, warnings or effects. See Compatible Plugins.
Which Minecraft versions and server software does it support?
Paper, or a server built on Paper, on Minecraft 1.21 to 1.21.11 and 26.1 to 26.3, with Java 21 or newer. One jar covers them all. The volumetric clouds need 1.21.11 or newer. See Installation.
How do I start seasons in a world?
Run /ms set <season> in the world as an operator or with mythicseasons.admin. While no world has a season, the console says No world has seasons yet. Run /ms set <season> in a world to start one. To give overworld-type worlds a season on their own, set on-new-world-creation.default-season in config.yml to a season id. The Nether and the End cannot have seasons (No seasons in the Nether or the End). See Seasons.
Can each world have its own season?
Yes, each world has its own season and date. To move worlds together, list them under synced-worlds in calendar.yml or turn on sync-time-with-real-world. See Calendar.
Does MythicSeasons change the blocks in my world?
Biome colours, snow, ice, flowers and leaf litter are added only to the chunks sent to players. Some options change the world itself in worlds with a season: modify-daynight-length, modify-blocks (with freeze-in-winter, keep-natural-snow and prevent-moisture-change), a season's prevent-cauldron-fill, disable-berry-damage-for-entities (also in worlds without one) and modify-weather-cycle, see General Config.
With modify-daynight-length on, run /ms disable in every seasonal world before you remove the plugin, or the daylight cycle game rule stays off.
How long does a season last, and how do I change that?
With the shipped calendar.yml a day lasts 20 real minutes at 20 ticks per second, and a season (90 to 92 days) about 30 real hours. Change each month's days, day-length-in-min and night-length-in-min and the <season>-start dates, or follow real days with calendar-is-real-life-days or sync-time-with-real-world. See Calendar.
Why does the season I set with /ms set change back?
With automatic-season-cycling on, each world gets the season of its date, checked every second. /ms set moves the date only with the calendar and sub-seasons.enabled both on. Otherwise use /ms nextseason or /ms setdate, or turn automatic-season-cycling off.
A season missing from season-cycle or without an <id>-start line cannot stay either. With the calendar and sub-seasons on, /ms set prints Date unchanged, <id> has no usable length in calendar.yml for it. See Seasons Not Changing.
How do I stop the seasons from changing by themselves?
Set automatic-season-cycling: false in config.yml and run /ms reload. The date and events keep running, and only /ms set or /ms nextseason change the season. /ms pausetime stops a world's date too. See General Config.
How do I add my own season?
- Copy
plugins/MythicSeasons/seasons/example.yml, removeenabled: falseand set a lowercaseid. - Set
biome-color-indexto-1to keep the vanilla colours. - Add
<id>-start: <Month> <day>tocalendar.yml, with a month from itsmonthslist. - Add the id to
season-cycleinconfig.yml, in the order of the start dates. - Add a block for the id under
modifiers.season-base-temperatureintemperature.yml. - List
MS_Atmosphereand the temperature skills of the shipped seasons underskill-triggers.player-tick, see Packs. - Run
/ms reload, then/ms set <id>in a world.
Seasons has a complete example.
How do I turn on the weather simulation?
It is on by default and starts in a world when the world first gets a season. If it does not run, check enabled at the top of atmosphere.yml (then /ms reload), run /ms atmosphere toggle <world> in a world that was switched off, install MythicMobs for the pack skill MS_Atmosphere, and check that the world has a season. See Installation.
Why do players see no rain or snow?
Check enabled in atmosphere.yml, the world switch (/ms atmosphere toggle), the world's season, MythicMobs and its pack, MS_Atmosphere in custom seasons, and WorldGuard regions with season-atmosphere set to deny. Otherwise it may not be raining there: the weather is local, and rain needs cloud above the player. See No Rain.
Why does /weather clear not stop the rain?
Where the simulation runs, players see its weather, and /weather changes only the world's own weather. Use /ms weather clear, rain or storm around you, the atmosphereforce and atmosphereprofile mechanics, or a WorldGuard region with permanent-weather. On a MythicMobs build that supports it, the weather mechanic and effect:thunderlevel on players are refused there too, see Compatible Plugins.
How much server load does the weather simulation cause?
The cost follows the simulated weather cells around players, up to grid.max-cells (2000000 per world by default), and one player alone keeps about 2,000,000 busy with the shipped grid at the default cloud quality. Lower it with bigger cells (grid.cell-size), a lower grid.max-cells or physics.pressure-iterations, or a higher timing.step-period-ms (above 3000 ms that slows the weather at the shipped timing.time-acceleration). The cell size and the timing settings need a restart.
A step longer than half of timing.step-period-ms logs atmosphere sim step took <n> ms -- lower grid.max-cells or physics.pressure-iterations in atmosphere.yml. See Atmosphere.
Why can't players see the volumetric clouds?
They need Minecraft 1.21.11 or newer, enabled and clouds.enabled set to true in atmosphere.yml followed by a restart, a world switched on with /ms atmosphere toggle, a /cloudquality other than off and no WorldGuard region with season-clouds set to deny. /ms atmosphere info shows a Clouds: on line while they run, else Clouds: off (clouds.enabled) or Clouds: unavailable (needs 1.21.11+ and a restart). See No Clouds.
Do players need a resource pack for the clouds?
No, but without it clouds beyond a client's render distance fade into its fog. With clouds.shader-pack.enabled: true and the master enabled switch on, the plugin writes a pack that removes the fade, plugins/MythicSeasons/MythicSeasons-CloudFog.zip by default, and you deliver it to players yourself. See Shader Pack.
Why do some players or places show vanilla colours?
Usually a world without a season, a player who ran /toggleseasoncolors, biome files edited without a restart, a custom season whose biome-color-index is -1, a WorldGuard region or GriefPrevention claim that turns season effects off, or chunks sent before the change and not sent again. See Biome Colors.
What can players change for themselves, and who can use /ms?
| Command | Permission | What it does |
|---|---|---|
/ms getinfo [world] |
mythicseasons.getinfo |
Shows the world's season, date, time and events |
/toggleseasoncolors |
mythicseasons.toggleseasons |
Turns seasonal colours and client-side blocks on or off |
/toggleseasonparticles |
mythicseasons.toggleparticles |
Skips player-tick-particles skills and lines that check <mythicseasons.particles> |
/toggletemperature |
mythicseasons.toggletemperature |
Hides or shows the temperature readout and warnings |
/togglefahrenheit |
mythicseasons.togglefahrenheit |
Switches between Celsius and Fahrenheit |
/cloudquality <quality> |
mythicseasons.cloudquality |
Sets the cloud detail, off draws none |
/togglecloudlayer [layer] |
mythicseasons.togglecloudlayer |
Hides or shows a group of cloud layers |
Every player has these by default. Every /ms subcommand except help and getinfo needs mythicseasons.admin (operators have it by default), but /toggletemperature <player> needs mythicseasons.toggletemperature.others. See Commands and Permissions.
Should I use /ms reload or /mm reload, and what needs a restart?
| You changed | Run |
|---|---|
config.yml, calendar.yml, crops.yml, temperature.yml, atmosphere.yml, lang/, seasons/, events/, cloud-layers/, cloud-styles/ or atmosphere-profiles/ |
/ms reload |
A file in plugins/MythicMobs/packs/MythicSeasons |
/mm reload |
A biome file in biomes/, except its atmosphere block |
Restart |
performance.*, biome-display-name or optimized-custom-biomes in config.yml |
Restart |
clouds.enabled, grid.cell-size, grid.y-min, grid.y-max, timing.*, physics.solver-threads or shared-weather-group in atmosphere.yml |
Restart |
commands.yml or griefprevention.yml |
Restart |
foliage-transitions in a season file, or the shader part of a file in cloud-styles/ |
Restart |
/ms reload never resends chunks, and it prints Biome file changes need a restart every time. See Installation.
Why does my skill do nothing, for example with isfrozen?
isfrozen is the MythicMobs condition for vanilla freezing, and MythicMobs always runs its own condition for a name it knows. The MythicSeasons one is seasonfrozen. Names neither plugin knows log Failed to load custom condition <name> or Failed to load custom mechanic <name>. Pack skills need /mm reload, season trigger lists /ms reload. See Skills Not Firing.
Why is a player's temperature not changing?
Check that enabled is true in temperature.yml, that the world has the system on (/ms temperature toggle prints World temperature on or World temperature off), and that the season lists the pack's temperature skills (MS_BlockHeat, MS_TemperatureModifiers, MS_TemperatureReadout) under skill-triggers.player-tick. A world that on-new-world-creation.default-season gave its season while the server started begins with the system off. /toggletemperature hides only a player's readout and warnings. Creative and spectator players are not updated.
In a WorldGuard region or GriefPrevention claim that turns season effects off, the temperature moves toward a fixed 25, unless the region sets permanent-temperature or the claim a fixed temperature. It moves temperature-change-rate (0.2 by default) of the way to its target every temperature-update-interval ticks (40 by default). Simulated weather changes body temperature only through pack skills such as the optional MS_AtmosphereBodyTemp. See Temperature.
How do I show the season, the date or the temperature in a scoreboard?
Install PlaceholderAPI. The ms expansion is built in: %ms_season_display% (season name), %ms_day%, %ms_month_asname% and %ms_year% (date), %ms_time% (clock), %ms_temperature% (body temperature with unit) and %ms_biome% (biome at the player). See PlaceholderAPI for the rest.
%ms_season_display% keeps the MiniMessage tags of the season's display-name (<#B0E0E6>Winter). To compare seasons, use %ms_season%, the id (DISABLED in a world without a season).
Why do my event commands run more than once, or not at server start?
A line in commands.start or commands.stop runs once for every world whose date changes, so with several seasonal worlds or synced-worlds it runs once per world. Limit it with disabled-worlds in the event file or worlds-without-events in calendar.yml. An event already inside its dates at server start or /ms reload runs no start lines, though isevent is true. See Events.
Where does MythicSeasons save its data, and how do I reset it?
plugins/MythicSeasons/data.yml holds the worlds' seasons, dates, switches and paused time and the players' own settings. The plugin rewrites it from memory every performance.autosave-interval-minutes minutes (5 by default), on season changes and at shutdown, so edit it only while the server is stopped. To reset a world's weather on a server that simulates its own weather, stop the server and delete <world folder>/mythicseasons/atmosphere-v1-.... /ms disable removes a world's season and keeps its date. See Config.
Can servers share one weather?
Yes, with MythicProxy: one server of a group (shared-weather-group in atmosphere.yml) simulates each world's weather for all. By default servers whose MythicProxy names end in a dash and a number, such as survival-1 and survival-2, form the group survival. They share only with matching grid.cell-size, sky height range, timing.step-period-ms, timing.time-acceleration and world seed. See Shared Weather.