Oh no! Something doesn't seem to be working properly on our server? We would like to know! By submitting a bug report, our development team can take a further look at what problems you or other players are facing. Please read through this article for more information on how to report bugs.

Creating Bug Reports

Does your bug happen randomly?

If your bug does not happen by following a set of actions they should be forwarded in the #team-help channel on our Discord server by clicking the "game errors" button.

In here you'll be asked for a /whereami output, you can receive this by typing /whereami right after the issue occurred. This will help us look into the behind the scene's of that specific game of why the bug happened.

https://cubecraftcdn.com/video-dist/1a17665c-b188-425f-b9bc-95f16881debe.webm

Reproducible bugs

Below are step-by-step instructions on how to create a report for bugs you can reproducible.

1. Go to the Bug Reports forum section on our website.
2. Depending on your platform click Java or Bedrock Bug Report.
3. Click CREATE A REPORT at the top right of the screen.
4. Fill out all the options shown in the form below, once you're done and click/tap on submit.
5. Tada, you're done! A team member will review your report as soon as possible.

After creating a report

Once your bug report has been submitted, we will try to check the report as quickly as possible. If you wish to add anything to the report you can do so by leaving a reply. By default your bug report will have the prefix open, it means that the report has not been checked yet. Below is more information about what our bug report thread prefixes mean!

• In review - This means that the report has been checked, but we need more clarification from you or someone within our team to forward or reproduce the bug. We will always reply to the thread if we need more information from you. If we don’t reply, that means we are discussing the report internally.
• Logged - This means that your report has been added to or is already in our internal bug tracking system, to be prioritised and looked at by a developer soon.
• Duplicate - This means that your report has already been reported. This prefix is applied in combination with Logged.
• Rejected - This means that your bug report has been rejected from being added to our internal tracking. You can find out why by opening the report.
• Intended - This means that the bug/behaviour you're reporting is intended and is not an issue. This prefix is applied in combination with rejected.
• Cannot reproduce - This means that the bug you're reporting cannot be reproduced on our side. This prefix is applied in combination with rejected.
• Inactive - This means that the bug report has gone inactive, as the reporter has stopped responding. This prefix is applied in combination with rejected
• Fixed - This means that the bug you're reporting has been fixed. Duplicate reports will also receive this prefix.

If you have any questions about the way your report was handled, you can message the team member by starting a conversation. To learn more about how to start a conversation please check out our Forum Guide Article!

Updated on: 08/07/2025