Wikis / MythicSeasons / Troubleshooting / Skills Not Firing

Skills Not Firing

Use this checklist when a season skill, a pack skill, or a MythicSeasons condition or mechanic does nothing. Stop at the first check that fails.

Checklist

1. MythicMobs was there when MythicSeasons started

  • Good: the start line Integrations active: lists MythicMobs.
  • Bad: Integrations not installed: lists MythicMobs. Install it and restart the server.
  • Bad: MythicSeasons could not start: <error>, see Troubleshooting.

2. MythicMobs has loaded the skill

You edited Run
A file in plugins/MythicMobs/packs/MythicSeasons, or a skill file of your own /mm reload
A season file, including its skill-triggers /ms reload
  • After /mm reload, a condition or mechanic name that neither plugin knows prints an error block with Failed to load custom condition <name> or Failed to load custom mechanic <name>, the file and the line.
  • If /mm test cast <skill> works, check steps 4 and 5, otherwise steps 3 and 6.

3. The names are right

Condition and mechanic names are not case sensitive, skill names are.

  • seasonfrozen tests the state setfreezing sets. isfrozen (aliases freezing and isfreezing) is the MythicMobs condition for vanilla freezing.
  • The MythicMobs conditions raining, sunny, snowing and thundering (and their aliases) follow the MythicSeasons weather only on MythicMobs builds with the component provider API. Other builds warn at start: This MythicMobs build has no component provider API (<reason>); its built-in weather conditions and mechanics will keep using server weather. The atmosphere condition always follows it.
  • On builds with that API, the weather mechanic and effect:thunderlevel on a player silently do nothing where the simulation runs.
  • atmosphereweather, atmospherewind and atmosphereprofile (alias atmoprofile) read the weather as conditions and apply it as mechanics. atmoswind is only a condition alias, atmowind only a mechanic alias.

All names are on Conditions and Mechanics.

4. The season lists the skill

Open plugins/MythicSeasons/seasons/<season>.yml.

skill-triggers:
  player-tick:
    - MS_ColdFreezing
  player-tick-particles:
    - MS_NightSparks
  • The keys are player-tick, player-tick-particles, world-tick, season-start, season-end and the eight atmosphere- keys on Triggers. A misspelled key is ignored silently.
  • Each key is a YAML list. player-tick: MS_ColdFreezing is not read.
  • The name must match the skill exactly, case included. An unknown name prints Skill trigger references unknown MythicMobs skill: <name> once per name until the next restart.
  • A cast error prints Failed to cast skill '<name>': <message> once per skill.
  • The lists run only in worlds in that season, and only while at least one player is in the world.
  • season-end (from the old season) and season-start (from the new one, a tick later) do not run for a season restored at server start, or when another plugin cancels the change.
  • Skills run every performance.skill-trigger-interval ticks (5 as shipped). A change needs a restart.
  • Players who ran /toggleseasonparticles skip the player-tick-particles skills and lines that check <mythicseasons.particles>.

5. The caster and the targets

Trigger Caster
player-tick, player-tick-particles and the atmosphere- triggers The player the trigger is about. Use @Self
world-tick, season-start and season-end The first player in the world's player list, so @Self reaches only that player. Use @PlayersInWorld or another targeter
  • No trigger entity is set, so @Trigger selects nothing and a skill with TriggerConditions: does not run.
  • @PlayersInWorld leaves out the caster unless it sets targetself=true, so in a world with one player it finds nobody. Write @PlayersInWorld{targetself=true}.
  • MythicMobs leaves creative and spectator players out of a mechanic's targets, except with @Self, unless the mechanic sets targetcreative=true.
  • modifytemp, blockheat, setfreezing, sethealing, setrsburn, atmosphereweather and atmospherewind accept only players and fail with an invalid target on other entities.

6. The conditions

Conditions: and an inline ?condition test the caster, TargetConditions: each target and TriggerConditions: the trigger entity. See Conditions.

When MythicMobs loads the skill, these lines name a missing or unreadable attribute, and the condition never matches:

Console line Cause
weekday condition requires a day parameter (d=Monday), e.g. weekday{d=Monday,Friday} No d, day or weekday attribute
No valid days in weekday condition: <value> An empty list of days, for example only commas
month condition requires a month parameter (m=1), e.g. month{m=January} or month{m=1,6} No m or month attribute
No valid months in month condition: <value> An empty list of months
isEvent condition requires an event parameter (e=eventId), e.g. isEvent{e=christmas} No e or event attribute
No valid event IDs in isEvent condition: <value> An empty list of event ids
isDate condition requires a date parameter (d=DD-MM), e.g. isDate{d=25-12} No d or date attribute
Invalid date format in isDate condition: <value> (expected DD-MM) Not two parts separated by - or /
Invalid date numbers in isDate condition: <value> A part is not a number, for example a month name
subSeason condition requires a phase parameter (p=START), e.g. subSeason{p=EARLY,MIDDLE} No p or phase attribute
Invalid sub-season phase in subSeason condition: <NAME> A phase other than START, EARLY, MIDDLE, LATE or END, printed in capitals. The valid phases still match
No valid phases in subSeason condition: <value> No valid phase
Invalid <attribute>: <value>, for example Invalid atmospheretemp min: cold A number attribute of temperature, playertemperature, atmospheretemp, atmospherewind, seasonprogress or timerange is not a number. The condition stays false

These print nothing and never match:

  • A misspelled day, month, event or season name in weekday, month, isevent or season, and season without s= or season=.
  • weekday, month, isdate and seasonprogress while the calendar is off, and subseason while sub-seasons.enabled is false.
  • season, isdate, isevent, subseason, weekday, month, timerange and seasonprogress in the Nether and the End. Negated (season{s=winter} false, ?!season{s=winter}), they pass there.
  • atmosphere{raining=yes} while it rains: in atmosphere only true counts as true, and yes, on and 1 mean false.
  • cloudcover and atmosphereprofile while enabled is false in atmosphere.yml, and atmosphere{incloud=true} without the simulation.
  • In a MythicMobs spawner's Conditions:, any MythicSeasons condition except those eight: the spawner never spawns.

Only atmospheretemp, atmospherewind and cloudcover take a bare range argument, and only without spaces: atmospheretemp > 10 matches every value, atmospheretemp >=10 works. Inline ? conditions cannot take one (write ?atmospherewind{min=5}), and a bare 0 counts as none. Attributes such as atmospheretemp{min=10} avoid all this. See Range argument.

7. The temperature skills

  • enabled must be true in temperature.yml, or playertemp and temperature never match.
  • The system must be on for the world. /ms temperature toggle flips it and prints World temperature on or World temperature off. If it prints World temperature off, run it again.
  • Creative and spectator players are not updated, so playertemp reads an old value.
  • /toggletemperature hides only the readout and warnings.
  • 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. See Land Claims.
  • MS_TemperatureRecovery ends the frost at -4, the healing block at 34 and the burn mark below 50. A skill that sets these states at other numbers flickers on and off.
  • Armour, items, blocks, water and food need MS_TemperatureModifiers and MS_BlockHeat in the season, the action bar readout needs MS_TemperatureReadout and the chat warnings MS_TemperatureWarnings.

8. The weather triggers

The atmosphere- triggers never read the vanilla weather.

  • They need the simulation, a WorldGuard permanent-weather region or an add-on weather provider. Snow and cloud triggers need the simulation or a provider. See No Rain.
  • In a WorldGuard region with season-atmosphere set to deny, they see no rain, storm, snow or cloud unless a permanent-weather flag answers.
  • The world's season must list at least one atmosphere- key.
  • A player's first check only records the state, so joining in the rain fires no atmosphere-rain-start.
  • While the simulation has no weather for a player yet, for example right after a teleport, nothing fires for up to 30 seconds. Then the weather counts as clear, and the stop and exit lists of the active states fire.
  • atmosphere-rain-start also fires for snow, followed by atmosphere-snow-start.

9. The event signals

Calendar events send startEvent_<id> and endEvent_<id> to the world's active MythicMobs mobs.

  • Use the event file's lowercase id. Signals are case sensitive: startEvent_christmas works, startEvent_Christmas does not.
  • ~onSignal: reads only letters, digits, _ and -, so an id with other characters cannot be received by name.
  • Signals go out on a calendar day change and on /ms event start or /ms event stop. An event already running at server start or /ms reload sends none, and mobs that spawn later get none.
  • A daily event sends startEvent_<id> every day and endEvent_<id> only after /ms event stop.

See Triggers.

10. The pack on your server is old

Skill trigger references unknown MythicMobs skill: <name> can also mean your copy of the pack lacks a skill that a season lists. Pack files are never overwritten, so skills a newer version adds to a file you already have never arrive, and no warning says so. See Updating the Pack and Updating to the temperature skills.

Updated Nov 11, 2026