User:Mattrition/new known bugs template

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. Please provide a short description on how to reproduce your bug along with system specs if required.

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. Gameplay ideas should be left to the developers.

Things you should include in the report are your system specs where appropriate, and instructions on how to reproduce the bug. If the bug caused the game crash or freeze in any way, you can follow these instructions to obtain a crash report and wrap it in the following template:

If you're 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) always prepend it with an issue label.
 * 2) sign your report with ~ so that we know who reported the bug.
 * 3) Leave a blank line between each bug report.

Do not place bullet points before issue labels; these are reserved for comments.

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

Commenting
Use bullet points for commenting on bug reports, placing the comment directly below the bug report without a blank line between them.

When commenting on a bug or annoyance, please sign your remarks 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 or annoyance get out of hand. Similarly, don't clog bug reports with discussions of workarounds or possible fixes. If ever a bug or annoyance ends up with more than about 10-12 lines of follow-up comments, please move the entire follow-up discussion to the talk page and put in a cross-reference to the discussion under the original bug.

Page Moderation
Please do not spontaneously delete an issue report or comment unless it is patent nonsense submitted by someone who has not logged in. Try to contact the submitter by user-talk first and tell them about your concerns. Almost all genuine, 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: redstone issues go in the Redstone section, problems with mobs go into the Mobs section, and so on. List crash bugs !! first, then major bugs !, then minor ones undefined. Annoyances go into the Annoyances subsection, with major ones A! before minor ones A. Issues that have been 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. Any changes made to this header should also be made to 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  = 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.
 * ? =  ?  = Potential issue that you are unsure of or that the community (on the discussion page) believes requires further vetting. Note: 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. When you apply this label to an issue, place it after the issue's existing labels; do not remove those labels.

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.)

Labels for indicating that an issue happens only in a particular game mode: (These labels cannot stand alone; you must use them in addition to, not instead of, the ones listed above.)
 * sp =  sp  = Single-player.
 * mp =  mp  = 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

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>.