Measure RoseStacker changes with stack statistics instead of labels
A larger stack label does not by itself prove that fewer server entities are active. Compare the plugin statistics with a controlled test population before tuning a whole farm.
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
- Record the installed RoseStacker version and the type of stacking under review. Save the relevant configuration and keep other farms unchanged during the measurement window.
- In game, use the documented
/rs statscommand to record the available stack statistics. Note the time and whether the test chunks are loaded so later results are comparable. - Introduce a small known number of expendable test entities or items on staging. Observe merging and record statistics again, using the same loaded area and player position.
- Change one relevant stacking rule, then repeat the same test population. Compare actual server timing evidence as well as the plugin counters before calling the result a performance improvement.
Verify the result
The counters should explain how the known population is represented after stacking. The test should distinguish a display change from a reduction in active entity processing.
If the result differs
If counts jump unexpectedly, inspect chunk loading and other nearby farms before changing limits. If labels differ but statistics do not, investigate presentation settings separately from stack formation.
Keep a recovery path
Restore the previous rule if the comparison is inconclusive. Remove only the deliberately created test population through normal supported interactions; avoid global clear commands that could destroy other players mobs or items.
References and related help
Check the maintainer reference: RoseStacker documentation, RoseStacker documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.