Managed Spawners

Every spawner a player places becomes a managed spawner, tracked in XCore's shared database with its owner UUID / name, spawned type, stack count, location and placement date.

Owner tracking — each managed spawner remembers who placed it
Break protection — with owner-only-break, only the owner (or a player with xspawners.bypass) can break or mutate it
Egg-change block — block-egg-change prevents swapping the spawned type with a spawn egg
Silk-touch for naturals — silk-touch-for-natural requires a Silk Touch pickaxe to break naturally-generated spawners

A managed flag and the stack count are written to the block's persistent data container, so XSpawners still recognizes the spawner after a server reload or chunk reload.

Stacking

Stacking lets a single block represent many spawners. It is enabled by default (stacking.enabled) and is the defining feature of XSpawners.

Place on top — placing a same-type spawner over an existing one adds to the stack instead of creating a second block
Shift + right-click — holding a spawner item of the same type and shift-right-clicking the stack merges it in without consuming a block
Merge-radius — when merge-radius is greater than 0, placing within N blocks of a same-owner, same-type stack merges into it (great for dense farms)
Stack cap — max-stack caps how high a stack can go (default 1000)
Spawn-rate multiplier — with multiply-spawn-rate, the spawn count scales with the stack size
Nearby-entity cap — spawn-cap-per-stack caps mobs around the spawner to prevent lag (0 = unlimited)

Config key	Default	Description
`stacking.enabled`	`true`	Master toggle for the stacking system
`stacking.max-stack`	`1000`	Maximum spawners on a single block
`stacking.merge-radius`	`0`	Auto-merge radius in blocks (`0` = off)
`stacking.show-hologram`	`true`	Show the stack-count hologram (needs FancyHolograms)
`stacking.multiply-spawn-rate`	`true`	Scale spawn count with the stack
`stacking.spawn-cap-per-stack`	`32`	Nearby-entity cap per spawner (`0` = unlimited)