Keep a MythicMobs spawn skill from duplicating its passengers

Applies to: MythicMobs; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

An encounter can accumulate extra riders when a passenger or mount action runs more than once. Check the lifecycle event that creates the attachment instead of clearing every nearby entity.

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

1. Write down which entity should own the attachment and when it should appear. Inspect the mob and its skills for more than one creation path.
2. Make a staging copy with a visible single attachment. Keep repeating timers and damage-triggered creation actions disabled while checking the initial spawn behaviour.
3. Test a fresh spawn, then the events that previously caused duplication, such as taking damage or entering a later encounter phase. Count attachments after each event.
4. Use the installed-release mechanics and trigger references to choose the lifecycle point intended for creation. Keep reattachment logic separate from creating a new companion entity.

Verify the result

A fresh encounter should create the planned number of attached entities. Repeated damage and phase checks should leave that count unchanged unless the design explicitly introduces another attachment.

If the result differs

If counts increase, find which skill line ran at that instant and trace nested skills. If a passenger disappears instead, check entity lifecycle and despawn rules rather than adding a repeated summon as a workaround.

Keep a recovery path

Put the prior definitions back on the test copy and remove its disposable entities. Keep the production encounter closed until the attachment count stays stable over a full run and an orderly server restart.

References and related help

Check the maintainer reference: MythicMobs documentation, MythicMobs documentation, MythicMobs documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.