So you've heard about the Minecraft Bug Tracker and you'd like to help out by reporting in game bugs? Well, this guide will cover important tips so that your bug reports will be as useful and helpful to the Minecraft team as possible. We'll also outline common mistakes that make bug reports not as useful as they could be and how to avoid them, with clear examples.
Note: we only accept bug reports for unmodified game clients.
Search the site before you report a bug! "But I don't have time to report this, I want to get back to my game!"
This is very important: to save yourself (and us) time and effort, try searching the site first to see if your bug has already been reported. If you are unable to locate your bug, and it looks like it hasn't been reported already, you can come back and submit a bug report when you do have time.
Searching before creating a bug will keep the number of duplicate reports to a minimum and is the best way to help us get to your issue. The fewer bugs we have to go through and mark as duplicates, the faster we'll get to your bug!
Tips for Searching: As you can see below, when you use generic keywords, you might get lots of responses. Be as specific as possible with your keywords/descriptions to make sure you find any bugs related to your problem.
"Help! It's broken!"
When reporting a bug it is very important that you be as specific as possible. We know we already said that, we're just reminding you because it's important.
Try to avoid saying things like "My game is broken!" because this doesn't tell us anything. Instead, try to keep the following questions in mind:
What's broken? (e.g. "Squids are dropping apples, not ink sacs like they should be.")
The summary or title of the report should tell us what the problem is at a glance. Saying "Help!!!" or "I found a bug!!" will likely result in your bug report being closed, as it's not enough info for us to help you.. Instead, be specific (see, we're serious about this) and tell us exactly what the problem is.
Explain to us what is actually broken in the description of your report. Be as detailed as possible here, even if you think it's not important. Think about the question "what is actually broken?" and tell us all about it!
What were you doing when it broke?
Knowing what actually broke is only one part of the issue. Telling us what you were doing when the thing broke will help us to figure out what caused the bug. If you can figure out and tell us, step by step, how you managed to cause the bug, you'll earn our everlasting gratitude.
Example of a Rock Star Bug Report:
I was trying to gather ink sacs so I could make some black wool for my chessboard and when I killed a squid, it dropped apples instead. A chessboard is pretty useless without black tiles...
What I expected to happen was...:
When I killed a squid, it should have dropped an ink sac.
What actually happened was...:
Instead, it dropped an apple.
Steps to Reproduce:
- Find a squid (though we all know how difficult they are to find when you *actually* want to find one).
- Kill the squid.
- Notice that it drops apples instead of ink sacs. How am I supposed to get black dye now?
What version of Minecraft are you running? (e.g. "Minecraft 1.4")
Even if your bug report is really well written, knowing what version of Minecraft you're running is very important. We might have already fixed the bug in another version and we need to know what version we should run when trying to recreate your bug. When you start up Minecraft, you'll be able to see what version you are using.
Other useful information
The more information you can share, the better! If you know what version of Java you are using and what operating system you are using (Windows 7, Windows 10, OSX, for example), let us know in the "Environment" area of the page.
"This is broken and this is broken, and this..."
We know you're eager to get all of your bugs fixed, but if you stuff them all in one bug report, chances are they'll get lost or it will just make things more confusing. Make one bug report per bug, that way you can be as specific and detailed as possible and we can focus on one bug at a time.
"I've discovered a dupe or a security issue!"
If you've discovered an exploit or a security issue, please create a Private report that only yourself and Mojang will be able to see. Follow the same guidelines above, but make sure to set the bug report to Private when you create it.
Still need more help writing a bug report? Take a look at this example here of a bug report that makes us happy. Now that you know how to write awesome bug reports for us, help us improve Minecraft by reporting bugs you find (after you have made sure it hasn't been reported already)!