Stop a MythicMobs timer skill from overwhelming an arena
A timer that summons entities or emits effects can multiply load during a long fight. Measure one mob first and set a deliberate event budget for the arena.
Check the installed content
MythicMobs separates mob definitions, skills, targeters and triggers. Keep the internal IDs stable while testing a behaviour change; changing a display name does not require replacing the mob ID. Use documentation for your installed MythicMobs release.
Work through the change
- Copy the affected mob to a staging definition with natural spawning disabled. Record the timer interval, actions per activation and number of mobs the arena normally allows.
- Estimate activations over one minute using the timer units documented for your release. Include nested skills and summoned mobs that can start their own timers.
- Increase the test interval or reduce actions per activation, changing one setting at a time. Avoid solving the problem by killing unrelated world entities.
- Run a timed encounter with one mob, then the planned maximum. Count surviving summons and compare server timing evidence with the same arena while the skill is disabled.
Verify the result
The number of skill actions should remain bounded over the complete fight, including periods when no player can finish it. Confirm that remaining summons have an intentional end or despawn path.
If the result differs
If load keeps rising after the caster dies, inspect skills on its summons and persistent scheduled actions. If the count grows only near several players, test target-dependent multiplication before increasing server resources.
Keep a recovery path
Restore the previous definition only if it is safe at the old arena capacity. Otherwise keep the encounter unavailable while you reduce its scope. Keep the world save before testing summoning changes.
References and related help
Check the maintainer reference: MythicMobs documentation, MythicMobs documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.