Find which plugin is causing your lag.
You know the pattern. Your server starts lagging, you install Spark, and now you're reading stack traces trying to figure out which jar is responsible. Or you ask in Discord and someone tells you to "remove plugins until the lag stops."
There's a gap in the tooling. Spark assumes you can read Java. Plan tracks players, not plugins. Timings got removed from Paper. Astral fills the gap.
There's a gap in the tooling. Spark assumes you can read Java. Plan tracks players, not plugins. Timings got removed from Paper. Astral fills the gap.
In-game GUI
Browser dashboard
Setup
- Download
astral-profiler-1.0.0.jar - Drop it in your
plugins/folder - Restart your server
- Run
/astralin-game
The browser dashboard is opt-in. To enable, set
web.enabled: true in plugins/AstralProfiler/config.yml, restart, and run /astral web.Commands
/astral— open the GUI overview/astral help— list all commands/astral reset— clear collected samples/astral dump— print a summary of current issues/astral web— get a clickable URL to the browser dashboard
Permission:
astral.use (defaults to op).Compatibility
- Paper 1.21.x and above (primary target, tested against 1.21.4+)
- Spigot should work but is less tested
- Folia not yet supported — planned for v1.x
- Java 21+ required (Paper 1.20.5+ already requires this)
Honest limitations
- Folia compatibility is on the roadmap, not in v1
- Auto task profiling on Paper 1.21+ is disabled due to a JVM final-field restriction. Listeners and commands cover the same ground; the developer API still lets you profile tasks manually.
- Heap attribution is approximate — heap is global to the JVM, per-plugin growth is "since the plugin was loaded"
- TPS/MSPT readings need standalone Spark installed alongside (Paper's bundled Spark doesn't expose its API)
$19
One-time purchase. Lifetime updates.
One-time purchase. Lifetime updates.
Stop guessing which plugin is causing your lag.
Built by Visedev.
Built by Visedev.
