Bug Report Guidelines

Making Your Report Easy to Act On

A report that follows the format above is a good start, but a few extra habits make the difference between a thread that gets fixed quickly and one that sits unanswered. Most people who read bug reports on a community forum are volunteers working on server files, emulators or tools in their spare time, so the less guessing they have to do, the better.

Search before you post

Check the existing threads in the forums and the notes attached to the relevant download in Releases. If someone has already reported the same problem, add your details to that thread instead of opening a new one. A second confirmation with a different setup is often more useful than a duplicate topic.

Isolate the problem

Try to reproduce the bug on a clean setup: a fresh copy of the release, default configuration and no extra plugins or custom scripts. If it only appears after you add a particular mod or edit a config file, say so clearly. That single detail can save hours of debugging.

Write steps someone else can follow

• Number each step and keep it to one action.
• Note exact versions of the client, server build, database engine and runtime you are using.
• Say how often it happens: every time, occasionally, or only once.
• Copy error messages as text rather than retyping them, and trim long logs to the lines around the failure.

Protect your own setup

Before sharing logs, config files or screenshots, remove passwords, database credentials, IP addresses and license keys. Never post a full server package that contains private data.

Follow up

Stay subscribed to your thread and answer questions from developers. If you find a workaround or the fix works, post an update so others with the same issue benefit. Keep discussion civil and on topic, in line with the forum rules; a patient, detailed report is far more likely to get attention than an impatient bump.