# Verify spawner-stack quantity before changing farm output

A spawner display and its represented quantity need to be understood before adjusting farm yield. Test one known stack rather than changing every spawner multiplier at once.

## Check the installed content

RoseStacker stores behaviour for stacked mobs, dropped items, spawners and blocks. A stack label is not a reliable inventory of every underlying entity or item. Test one feature at a time with expendable objects before changing rules that affect existing farms.

## Work through the change

1. Record the RoseStacker version, spawner type and known starting quantity. Save the relevant configuration and a small staging-world checkpoint containing the test location.
2. Create a disposable test setup through the supported normal placement workflow. Record the represented quantity using the plugin display or supported inspection method for your release.
3. Observe several spawning cycles with ordinary activation conditions satisfied. Keep entity caps, nearby mobs and player distance comparable, and count actual spawned output.
4. Test the documented normal add or remove interaction with a small quantity. Recheck represented spawners and output before making any farm-yield adjustment.

## Verify the result

The setup should account for its starting spawner quantity and maintain it through normal interactions. Output measurements should be consistent enough to separate activation limits from stacking behaviour.

## If the result differs

If output stops, inspect Minecraft activation conditions and nearby entity limits before increasing stack output. If quantity differs, examine placement and break permissions or integrations rather than compensating with another spawner.

## Keep a recovery path

Restore the staging-world checkpoint and previous configuration if quantity becomes uncertain. Do not break production spawner stacks or issue replacement items during diagnosis; both can complicate accounting and recovery.

## References and related help

Check the maintainer reference: [RoseStacker documentation](https://wiki.rosewooddev.io/RoseStacker/introduction/), [RoseStacker documentation](https://wiki.rosewooddev.io/RoseStacker/getting-started/).

Before changing live data, read [how to keep a completed recovery copy](https://help.cloudexa-hosting.com/books/game-hosting/page/back-up-game-files-before-making-changes). For startup errors, use [the log collection guide](https://help.cloudexa-hosting.com/books/game-hosting/page/find-minecraft-logs-and-send-useful-troubleshooting-details).