The Mojang Studios Bug Tracker is the place where all bugs in Minecraft and other games in the Minecraft family are reported, documented, and tracked.
You can help us squash bugs! To report bugs properly and for additional tips and policies, start by reading the 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 social channels, or through the player-run pages.
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, we do not accept any bug reports about older versions of Minecraft, modified game clients, or any third-party software.
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 see our FAQ.
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. Each vote tells us how many players 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 Constructive Bug Reports
When you’re sure you’ve found a new bug, you may 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.
The description should include:
- Steps to reproduce the bug (e.g., what you need to do in the game to get the bug to occur).
- What you expect to happen when you follow those steps.
- What actually happens when you follow those steps.
- Any further information about the bug, such as explaining any attachments you’re including, when the bug first occurred, how you’ve tested the bug, messages displayed (e.g., error messages), and how the bug impacts gameplay.
For an example template that you can copy and paste for your own use, see 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).
IMPORTANT Do not share personal information or account information in the bug tracker. The bug tracker is not a place to receive tech support or account support. NEVER post personal information, contact information, or Transaction IDs there. 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 if needed.
- A bug report must only describe a single bug.
- Watch for incoming comments and reply to them if they ask you a question.
Here are some well-written bug reports that you can look at as an example:
Thanks for helping us squash the bugs!