Migrating from another plugin

AtlasSpawner can take spawners over from five other spawner plugins. It only ever reads from them, never writes into or deletes from them directly — each spawner is read, the other plugin is asked to release it, and only then is it written here, in that order, so a spawner is never briefly held by both.

Sources

Plugin	What is converted
MineableSpawners	Items only (the mob a spawner item names). Works even after the plugin is removed.
SpawnerMeta	Type, upgrade levels, stack, and owner, from both blocks and items. Can name every spawner it holds, loaded or not.
UpgradeableSpawners	Type and upgrade levels. No stack or owner — its own API has neither. Only sees loaded chunks.
VirtualSpawner	Type, stack, experience, and store contents. No upgrade levels — it has none. Only sees loaded chunks.
AxSpawners	Type, its single level axis (mapped onto amount), stack, owner, and store contents. Can name every spawner it holds.

A level above what your spawners.yml allows for that type is brought down to the type’s own max-level, and the console says so once per type — raise max-level before the rest of the world loads if you want to keep what was bought.

Preview, then confirm

/atlasspawner migrate <plugin>
/atlasspawner migrate <plugin> confirm

Without confirm, this is a dry run: nothing is taken, nothing is released, and the command reports how many spawners it found. With confirm, it takes every one it found, releasing each one from the other plugin as it goes.

Caution

/atlasspawner migrate <plugin> confirm cannot be undone. Back up your world and both plugins’ data before you run it.

The migrate branch is only shown at all when a supported plugin is installed alongside AtlasSpawner.

migrate.on-chunk-load

migrate:
  on-chunk-load: false

SpawnerMeta and AxSpawners keep every spawner they hold in memory, so /atlasspawner migrate <plugin> confirm alone takes all of them regardless of this setting.

UpgradeableSpawners and VirtualSpawner key their own storage by chunk: their spawners only exist for them while that chunk is loaded, so /atlasspawner migrate only ever sees what happens to be loaded at the moment you run it. Turning on-chunk-load on hands over any spawner still held by one of those two plugins as its chunk loads — each read, released, and written in the same step — which is the only way to finish a migration from a plugin that cannot name its own spawners up front.

Turn on-chunk-load back off once the old plugin’s jar is removed; nothing else reads this setting.