The Mojang Bug Tracker is the place where all bugs in Minecraft and all other games created by Mojang Studios are reported, documented, and tracked. Please read this guide to understand how you can help us squash bugs!
For additional tips and policies, please read the full bug tracker guidelines and our FAQ. If you need additional help with reporting a bug or have questions about the bug tracker, feel free to ask other players in the community by visiting our official Minecraft Discord, or through the player run pages linked here.
Before you create a bug report…
First, make sure that your issue is really a bug. A bug is when a game function does not behave as intended. Issues with payments, accounts, technical support issues, and features you’d like to be added are not bugs and are not handled on the bug tracker.
Also note that we do not accept any bug reports about older versions of Minecraft or modified game clients.
If you’re sure you’ve found a bug, search for an existing report. Only one report will be kept open for each existing bug. That report is the one where your input will count.
In case you have trouble using the bug tracker’s search function, we have a few tips for how to perform searches in the full bug tracker guidelines.
You may find reports matching your issue that are already resolved. If the resolution is “Duplicate”, follow the link to the parent bug report where the issue is tracked. For other resolutions, you can take a look at our FAQ to find out what they mean.
If you find that your issue has already been reported by someone else, you may add new information to the existing report by giving it a vote, or adding a comment or attachment. A vote is how you can tell us that you are affected by the bug and want it to be fixed. Comments and attachments are for sharing more detailed information about the bug and its impact. If you want to discuss the bug, please do so outside of the bug tracker.
How to write helpful bug reports
When you’re sure you’ve found a new bug, it’s time to create a new bug report. The most important parts of the report are the summary and description. The summary should say what the bug is as briefly as possible. The summary is how most people will find the report, so think carefully about how to phrase it so that the report can be found as easily as possible.
The description should include:
- Steps to reproduce the bug (i.e., what you need to do in the game to get the bug to happen)
- What you expect to happen when you follow those steps
- What actually happens when you follow those steps
- Any further information you can give about the bug, such as explaining any attachments you’re including, when the bug started to happen, how you’ve tested the bug, messages shown (e.g. error messages), and how the bug impacts gameplay.
For an example template that you can simply copy and paste, please refer to the full bug tracker guidelines.
Also fill out the other fields such as version, platform, game mode, etc., and make sure you select the right project for your bug (the projects are explained in the bug tracker guidelines).
A few more pointers:
- Do not share personal information or account information on the bug tracker.
- Bug reports must be in English. You may use an online translator to help you.
- A bug report may only describe a single bug.
- Look out for incoming comments and reply to them if they ask you a question.
Here are some well-written bug reports that you can take a look at as an example: