Frequently Asked Questions
What is a PocketMine-MP crashdump?
A crashdump is an automatically generated file that PocketMine-MP creates when the server crashes. It contains vital debugging information including the error message, a stack trace showing exactly where the crash occurred, server configuration details, loaded plugins, and PHP version info. Crashdumps are stored in the crashdumps/ folder inside your server directory.
How does this analyzer work?
The analyzer parses the crashdump text entirely in your browser — no data is ever sent to any server. It identifies the error type, extracts the stack trace, determines which plugin (if any) caused the crash, and provides human-readable suggestions for fixing the issue. It recognizes common error patterns like null method calls, class not found errors, type mismatches, and memory issues.
Which PocketMine-MP versions are supported?
This tool supports crashdumps from PocketMine-MP 3.x, 4.x, and 5.x (the latest version). The crashdump format is largely consistent across versions, so even older crashdumps should be analyzed correctly. It also works with forks like Altay, Genisys, and NukkitX if they follow a similar crashdump format.
Is my crashdump data private?
Yes. All analysis happens locally in your browser using JavaScript. Your crashdump content is never uploaded, stored, or transmitted anywhere. You can use this tool offline once the page has loaded.
My server crashed but there is no crashdump file, what do I do?
If PocketMine-MP didn't generate a crashdump, check your server console output or server.log for error messages. Crashes caused by out-of-memory errors or segmentation faults may not produce crashdumps. You can also try running the server with --debug.level=2 to get more verbose logging. Copy any error output you find and paste it here — the analyzer can often still extract useful information from partial logs.
How do I fix a plugin crash?
If the analyzer identifies a specific plugin as the crash cause: 1) Check if there's a newer version of the plugin available. 2) Temporarily remove the plugin to confirm it's the cause. 3) Report the crash to the plugin developer with the analyzed output. 4) If you wrote the plugin yourself, look at the specific file and line number mentioned in the stack trace to find and fix the bug.