Frequently Asked Questions
Short answers to the questions that come up most. Anything else lands in the issue tracker.
Answers
No. Statistics are read asynchronously on a background thread pool, and the embedded HTTP server runs its own executor, so API requests never touch the main server thread. A 30-second statistic cache means repeated polls hit memory, not the Bukkit API.
You can confirm live behavior any time: /statfyr status shows the async worker state, and /api/health reports the executor's active threads.
Yes. For players currently online, stats are read live from the Bukkit Statistic API. For offline players, statfyr parses the vanilla world/stats/<uuid>.json files, so leaderboards and lookups include everyone who has ever played.
Names are resolved the same way in both cases: a UUID always works, and an exact current name works for any player the server has seen before.
Paper, Spigot, Purpur, and compatible forks running 1.16.5 through 1.21.x. The plugin compiles against the Paper 1.16.5 API and uses only stable Bukkit API surface.
Still stuck?
Bug reports, feature ideas, and questions each have a template in the issue chooser. For anything sensitive, see the contact channel in SECURITY.md.
Before filing, it helps to capture one failing request with debug mode on:
# plugins/statfyr/config.yml
debug: true