Explain a RoseStacker placeholder count that differs from nearby mobs

A scoreboard placeholder may report a plugin-wide value rather than the visible entities around one player. Identify its scope before treating a different count as missing mobs.
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 exact PlaceholderAPI placeholder and the scoreboard or menu that renders it. Consult the installed RoseStacker placeholder reference for its meaning and dependencies.
Compare the value with documented RoseStacker statistics at the same timestamp. Note loaded worlds and chunks, because a local visual count may cover a much smaller area.
On staging, add one known disposable stack and refresh the display through its supported workflow. Observe which counters change and whether the displayed value is cached.
Test the placeholder directly through the documented PlaceholderAPI inspection route for your installed release, then compare the scoreboard result. This separates provider output from formatting or caching.
Verify the result
The value should match its documented scope and update when the corresponding underlying statistic changes. The display should label that scope clearly rather than implying a local head count.
If the result differs
If direct expansion is correct but the scoreboard is stale, inspect its update interval and cache. If the placeholder remains literal, check expansion availability and syntax before editing stack data.
Keep a recovery path
Restore the previous display expression if the new label or placeholder is incorrect. Keep the actual stack configuration and stored entities untouched; this investigation concerns a reported metric rather than missing world content.
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.