Minecraft Wiki:Issues/1.2 Preview

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. Finally, please determine which game mode(s) your issue appears in, and flag it with the appropriate label(s). (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.)

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, however, are to remain in their original place.

Please sign all issue reports and comments by typing   (three tildes; tilde may be found above  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)
 * !! =  !!  = 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.
 * ? =  ?  = 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 =  sp  = 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

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

Crashing/System
Bugs !! spcr Created a single column of Glowstone up to 256, and got a "saving chunks" crash, logged back in and it kept crashing, shortened the render distance and still crashed.--Sxerks 17:51, 29 February 2012 (UTC)
 * Confirmed. Error message: http://i1098.photobucket.com/albums/g368/j1k3bucket/mcerror.jpg --J1k3

!! When you go to options and click on controls the game crash.

Annoyances a In the video settings menu when cycling/clicking through the gui scale option, clouds will be toggled on/off. Fixed/Skipped

Redstone/Pistons
Bugs undefined (Found in Survival SinglePlayer) Piston heads frequently fail to push the player. The same occurs with items. Annoyances Fixed/Skipped

Blocks
Bugs undefinedcrsp When breaking the top half of a wooden door in Singleplayer Creative, the door drops as an item, when you break the bottom half though, it doesn't drop as an item. 90.231.9.197 18:30, 29 February 2012 (UTC)

Annoyances a In 1.2, you added the ability to place torches on top of upside down stairs. However, one cannot place a torch on a upside down half slab, though this makes no real sense. Note that one can place a torch on a double-slab block, and the upside down half slab is at the same level as it is. -otto4242

Fixed/Skipped

Crafting/Enchanting/Brewing/Interface
Bugs Annoyances

a! The enchanting system has always, and continues to be frustratingly unfair. sometimes producing Efficiency III when a level 50 enchant is used. Considering you need to kill NINE HUNDRED AND TWENTY FIVE zombies/creepers etc, to get to Level 50, users are naturally in consensus that, to quote Yahtzee Croshaw, the ratio of difficulty to find versus actual usefulness is completely arbitrary. While we respect the mystique Mojang have tried to create about enchanting, the numbers need serious review. Kizzycocoa
 * important discussion do not comment at this page

Fixed/Skipped

Achievements
Bugs Annoyances Fixed/Skipped

Gameplay
Bugs Annoyances Fixed/Skipped

NPC/Animals
Bugs Annoyances Fixed/Skipped

Mobs
Bugs Annoyances Fixed/Skipped

World generator
Bugs ! Again, Birches and pines spawn rate is very low. --Galaxy_2Alex (Talk)

! spoffline. There is definitely something broken in the biome code since the map heigh is extended at 256. In the normal forest there are no birch trees (I can't find one in about 10 maps in creative) and the trees are all the same height (no big trees). The swamps are broken too, the trees mostly stand in the water, so no mushrooms can spawn. I also couldn't find a pine tree forest. In some snow taigas there were isolated pine trees. The biome generation is not as it was before the extension of height.

Some examples for normal tree forest with same trees and no birches. 6203567990940513874 x:-239  z:256

6562840201062392468 x:9  z:-233

--reptile311 Annoyances Fixed/Skipped

Graphical/Lightning
Bugs

undefined Mining clay from directly above does not show mining damage texture (cracks) as you're mining it. As seen here: http://imageshack.us/photo/my-images/109/cracks.png/ EsOne

Annoyances

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

Fixed/Skipped

Sound
Bugs Annoyances Fixed/Skipped

Language
Bugs Annoyances Fixed/Skipped