Core concepts
How a virtual spawner is stored, typed, and how it generates loot.
Three ideas explain almost everything EliteSpawner does. Read this page once and the rest of the configuration will make sense.
The block is only an anchor
A spawner placed by EliteSpawner is an ordinary SPAWNER or DROPPER block with no special block-entity behavior of its own. Everything that makes it a spawner lives in the plugin's database, keyed by the block's location:
Type
Which spawner definition it uses.
Stack size
How many spawners are merged into this one block.
Storage
The items and experience it has generated so far.
Owner
Who placed it, and who they've trusted with access.
Breaking the block through EliteSpawner removes that record with it. The block itself never carries any of this data.
Types are names, not vanilla identities
Every spawner has a type: a named entry in mob_spawners.yml (for SPAWNER blocks) or item_spawners.yml (for DROPPER blocks).
The name is independent of the underlying mob or material. zombie and elite_zombie can both represent ZOMBIE with completely different loot, experience and drop chance, and you can define as many variants of the same mob as you like.
Rebalancing is safe
Placed spawners reference their type by name. Change the loot or experience of a type, run /esp reload, and every spawner of that type already in the world uses the new values.
Generation is virtual
Vanilla spawning is cancelled before an entity exists. In simplified terms, each generation cycle works like this:
Rolls its loot table. Each entry is checked against its own chance, and amounts are picked from their configured range.
Applies multipliers. Stack size, progression, prestige, traits, enrichment and any active boosts are factored in.
Writes to storage. Items and experience go straight into the spawner's virtual storage, up to its capacity.
No entity spawns, no item lands on the ground, and no chunk has to simulate any of it.
Storage limits apply
If storage is full, a cycle can generate less than it rolled. /esp debug reports when this happens, see Commands.
When spawners run
How often spawners are allowed to generate depends on the activation mode set in config.yml:
| Mode | Spawners generate |
|---|---|
| Near a player | Only while a player is close by |
| Anyone online | While at least one player is online anywhere |
| Always | Regardless of whether anyone is online |
Last updated on