TickVisor reads Spark profiles, logs, crash reports, and diagnostic bundles, then turns noisy server data into grades, likely causes, top systems, and next steps your team can actually use.
Upload one real capture, read the report, apply one fix, then compare the next profile.
Spark profiles are best for performance triage. Logs, JSON, text files, crash reports, and zip bundles can support the investigation.
TickVisor groups raw Java method noise into readable systems like entity ticking, chunk I/O, event handlers, players, and mod-specific hotspots.
Use grade, likely causes, recommendations, report history, and comparison to confirm whether a fix improved the server.
Minecraft performance work gets messy when every change is a guess. TickVisor gives you a consistent report structure so you can test one fix, upload again, and see what changed.
Profile while players, machines, chunks, and entities are doing normal work.
Check the grade, top systems, likely causes, and recommended action.
Upload another profile and confirm if MSPT, TPS, and grade improved.
Start with the workflow closest to your problem, upload the right capture, then use the report to choose the next fix.
For owners who need a broader TPS, MSPT, logs, reports, and diagnostics workflow.
For teams starting with .sparkprofile exports and raw profiler captures.
For tracking lag causes, trying one fix, and comparing before/after captures.
Verified accounts can test the reporting flow before paying.
25 reports per calendar month for ongoing performance checks.
250 reports per calendar month for larger operations.