Template:Issues organization

Bug Reporting
This page is for bugs that:
 * 1) Are found in the version of the game specified in the article's title.
 * 2) Are found in an unmodified Minecraft game. If you think a bug you have found in a modded version is not the result of the mods you have added, please be sure to reproduce it in an unmodded game before posting it here.
 * 3) Are reproducible to a certain extent. Please provide a short description on how to reproduce your bug along with system specs if required.

You can read Classifying bugs for further information on what you should and shouldn't add to this page.

Bug reports should be as concise as possible without anecdotal waffle or your own opinions. We want to keep a clean, easy-to-read list of bugs for the developers to check through. This is not a place to express gameplay ideas or improvements.

Please include your system specs, where appropriate, and instructions on how to reproduce the bug. If the bug caused the game to crash or freeze, there may be a file beginning with the word "crash" in your .minecraft directory containing the crash report. If not, you can follow these instructions to obtain a crash report. Once you have the report, wrap it in the following template:

If you are unsure of an issue, it's good practice to post about it on the |talk page to see whether others can reproduce it.

When adding your bug report:
 * 1) Read through the list of known bugs first to check that your bug has not already been submitted. If it has, add any extra information as a comment to the current submission.
 * 2) Always prepend it with one or more issue labels.
 * 3) Sign your report with  --~  so that we know who reported the bug.
 * 4) Leave a blank line between each bug report.
 * 5) Do not place bullet points before issue labels. They are reserved for use with comments.

Once you've added a bug report, please keep track of it. Others may post comments underneath your report requesting clarification or more information.

Bug reports that do not provide enough useful information or contain too much opinionated or anecdotal waffle may be subject to removal.

Commenting
When commenting on bug reports:
 * 1) Prepend your comment point with an indented bullet point using the code ":*".
 * 2) Place the comment directly below the bug report without leaving a blank line between them.
 * 3) Sign the comment with  --~ . This is a deliberate exception to the usual wiki conventions; normally you should only add signatures to content on talk pages.

Please don't let debates about whether something is or is not a bug get out of hand. Similarly, don't clog bug reports with discussions of workarounds or possible fixes. If a bug or annoyance exceeds 10-12 lines of follow-up comments, move the entire follow-up discussion to the talk page and link to the discussion under the original bug.

Page Moderation
Please do not spontaneously delete a bug report unless it is blatant nonsense submitted by an unregistered user. Try to contact the submitter by user-talk first and tell them about your concerns. Almost all active submitters will be co-operative. Always assume good faith.

You may also leave a comment explaining why you feel the bug should be removed, allowing time for others to weigh in on the decision or for the original poster to give additional information. Where possible, removal of a bug should be a group decision, not a decision made by a single individual.

Please make sure issues are given the correct category, type, and priority: issues with blocks go in the Blocks section, issues with mobs go into the Mobs section, and so on. List bugs in order of importance ( !! > ! > undefined). Annoyances go into the Annoyances subsection, with major ones A! before minor ones A. Issues that Mojang have marked as fixed or skipped are moved to the Fixed/Skipped section. Issues that Mojang cannot reproduce should be left in their original place.

If a new version of Minecraft is released, create that page with. Changes to this header should be made by editing this template.

Issue Labels
Use issue labels to indicate the importance and nature of a bug.

Mandatory issue labels come first, and must be one of the following:
 * !! =  !!  = Critical bug that can crash a Minecraft client or server.
 * ! =  !  = Major bug. Use this tag sparingly; if there is consensus your bug is not major, it will be downgraded.
 * a! =  a!  = Major annoyance. Think very carefully before flagging an annoyance as major.  Is it really more important than most minor bugs?  Use this tag sparingly; if there is consensus your annoyance is not major, it will be downgraded.
 * undefined =  undefined  = Minor bug.
 * a =  a </tt> = Annoyance. Note that this is not the same as feature requests, which is not what this page is for. Remember, leave gameplay ideas/solutions up to the developers.

Please also determine which game mode(s) your issue appears in, and flag it with the appropriate label(s) if any. (Also, note that if, for example, a minor annoyance appears in both single-player and multiplayer, and in both creative and survival modes, you should label it as a, not aspmpsucr.)

Optional labels can be added after mandatory labels.

Labels for indicating that an issue happens only in a particular game mode:
 * sp =  sp </tt> = Single-player.
 * mp =  mp </tt> = Multiplayer.
 * su =  su </tt> = Survival mode.
 * cr =  cr </tt> = Creative mode.

Labels for indicating that an issue is restricted to a particular OS:
 * =  </tt> = Mac OS X
 * =  </tt> = Windows
 * =  </tt> = GNU/Linux

In addition, ? =  ? </tt> can be added to tag an issue that you are unsure of or that the community (on the discussion page) believes requires further vetting. Do not use this label to indicate this-is-not-a-bug. Instead, replace the issue's current label with a or a!. Furthermore, it is inappropriate to use this to flag something you disagree with. Instead, express your opinion in a comment.

Labels that Mojang (not you!) uses: (Please place these tags in front of existing issue labels. Do not remove the existing labels.)
 * f = Issue for which a fix will appear in the next update.
 * n = Not a bug; intended behavior. By definition, this label is inapplicable to annoyances. Annoyances are not bugs.
 * s = Issue that will not be fixed in the next update.
 * u = Issue that Mojang has tested but was unable to reproduce.

To produce these labels, use the following code:  </tt>c </tt> where c is the code of the label you wish to use. (e.g., a for annoyances, etc.)

The default issue type is minor bug; you can produce this label with the shorthand  undefined </tt>.

Further information is available at Classifying bugs.