Crashes and bug reports
What the crash dump is, and how to write a report somebody can act on.
When the server hits something it cannot recover from, it writes a crash dump into
crashdumps/ and stops. The dump is the useful part: it holds the version, the PHP build, the
plugins that were loaded and the stack trace at the moment things fell apart.
Reading it yourself first
Open the newest file in crashdumps/ and look at two things: the trace, because if the top
frames name a plugin that is where to start, and the plugin list, because a crash with plugins
loaded may not happen without them.
Empty the plugins folder
Move everything out of plugins/ and restart.
Add them back in halves
If the crash is gone, put half the plugins back. Repeat until it returns.
Report to whoever owns it
Whichever plugin brings it back is the one to report to, and that is not here.
Reporting a server bug
If it crashes with no plugins loaded, it is a server bug. Open an issue on the tracker with:
| Include | Why |
|---|---|
| The crash dump, in full | Attached or pasted. Not a screenshot of it. |
| The server version | From version in the console. |
| The PHP build | Which binary, from where. |
| Steps to reproduce | The field people skip, and the reason issues go stale. |
| What you expected instead | Sometimes the bug is the expectation. |
A report without a reproduction is a note that something went wrong somewhere, once. It can rarely be fixed.
Bugs that are not crashes
Wrong block behaviour, an item that does nothing, a packet the client rejects. Same tracker, same rules, plus: say which Bedrock client version you tested with. Client behaviour changes between versions, and "broken" often means "the client changed and the server has not caught up".
Things that are not bugs
Getting help faster
Bring the dump
The Discord is the place for "is this a bug or am I holding it wrong". Bring the crash dump with you: the first reply will ask for it anyway.