Issues 1.2 Preview


Full releases
Weekly releases

Organization of This Page & Instructions

Please do not spontaneously delete an issue report or comment, unless it is patent nonsense submitted by someone who has not logged in. If possible, contact the submitter by user-talk first and tell them about your concerns. They will almost certainly oblige. As always, assume good faith.

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. Make sure you`re testing the bug in the correct version (for this page, that`s 1.2 Preview) with no mods installed. Also, make sure to proofread your issue report before submitting it; unintelligible issue reports come off as inconsiderate and disrespectful. At long last, please determine which game mode(s) your issue appears in, and flag it with the appropriate label(s). (Also, note that if, for instance, a minor annoyance appears in both single-player and multiplayer, and in both creative and survival modes, you should label it as A , not A SP MP Su Cr .)

Be sure to sort issues by category, type, and priority: redstone issues go in the Redstone section, etc.; bugs go in the Bugs subsection, with major bugs listed before minor bugs, annoyances in the Annoyances subsection, with major ones before minor ones, and issues that Jeb has marked as fixed or skipped are moved to the Fixed/Skipped section. Issues that Jeb cannot reproduce, be that as it may, are to remain in their original place.

Please sign all issue reports and comments by typing ~~~ (three tildes; tilde may be found above Tab ⃢₆Ⅱ on USA keyboards, and to the right of @ on British keyboards).

There is no need to place bullet points before issue labels. Use bullet points only for comments. Be sure to leave a single totally blank line before each new issue (but not before comments), unless the issue appears directly beneath a header.


Issue Labels

Please mark your issue with one of these issue labels: (listed from highest priority to lowest)

  • !! = {{bl|!!}} = Critical bug that can crash a Minecraft client or server.
  • ! = {{bl|!}} = Major bug. Use this tag sparingly; if there is consensus your bug is not major, it will be downgraded.
  • A! = {{bl|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.
  • X = {{bl}} = Minor bug.
  • A = {{bl|a}} = Annoyance.
  • ? = {{bl|?}} = 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.

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 = {{bl|sp}} = Single-player.
  • MP = {{bl|mp}} = Multiplayer.
  • Su = {{bl|su}} = Survival mode.
  • Cr = {{bl|cr}} = Creative mode.

Labels for indicating that an issue is restricted to a particular OS:

  • = {{OS|OSX}} = Mac OS X
  • = {{OS|Win}} = Windows
  • = {{OS|Linux}} = 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: {{bl|c}} 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 {{bl}}.


!! Server is throwing error on connection:Failed to handle packet: java.lang.ArrayIndexOutOfBoundsException: 16

  • Deleting the player folder from the save folder will sometimes fix the problem.
  • Client side will say: Disconnected By Server, Internal Server Error.
  • Also happens when you die on the server.
  • No player can connect making the server useless.
  • Clinet must also be restarted after players folder is deleted, other wise the server will have to be restarted again.

! Several sound instances do not play:

! A few graphical elements are missing:

  • Fishing rod "line".
  • Fishing rod "line" in held item. It shouldn`t appear when the line is casted.
  • Other Player breaking animations.
  • Magma Cube animations.
  • Other player`s enchanted items don`t shimmer.

! Mining takes longer in multiplayer than in singleplayer. This is caused by a click-mining `fix` that was added in Beta 1.3 and is not needed.

! Slimes and Magma Cubes randomly warp up and down when they have a ceiling above them.

! Knockback and damage screen calculation is often wrong in multiplayer, actually dealing knockback when it shouldn`t (like drowning or being on fire).

! MP Huge Mushrooms planted with


A An old glitch, hoping jeb or dinnerbone will read and fix that⃂: when sneaking, if the player skin has a hat or head accesory, it will be offset one pixel up. Also, when looking down, the player head will pass through it, removing the front face.

A Using the new top-half slabs to create a ceiling causes the undersides of the ones on the inside to become completely black. ~~Minecrafterambesten

A In-game maps don`t show snow anymore. ~~spiderboy4