Minecraft Wiki:Issues/1.2.2

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.2) 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 [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, 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! =  = 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 =  = Minor bug.
 * 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 =  = Single-player.
 * mp =  = Multiplayer.
 * su =  = Survival mode.
 * cr =  = Creative mode.

Labels for indicating that an issue is restricted to a particular OS:
 * =  = Mac OS X
 * =  = Windows
 * =  = 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:  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  undefined .

Crashing/System
Bugs ! Minecraft is lagging heavily after playing for a few minutes. 0 FPS for 2-4 seconds with >1 sec delay between them. (SP, Normal/Far view distance) -- L.K.

Annoyances a 1.2.2 no longer accepts command line arguments that previous versions accepted. Is this intentional or an oversight? See Stand alone client (change). -Aurelius 16:23, 1 March 2012 (UTC)
 * Use the  environment variable instead.

Fixed/Skipped

Redstone/Pistons
Bugs Annoyances a! Redstone current will not travel down the side of a glowstone block. Fixed/Skipped

Blocks
Bugs undefined you can't grow birch and pine trees over 128 block high. oak and jungle tree grow just fine with both versions available.

Annoyances Fixed/Skipped

Crafting/Enchanting/Brewing/Interface
Bugs undefined The first character of enchantment labels are missing. ie "lame I" instead of "Flame I"
 * Grammar corrected for clarity. CaMoreno3 19:21, 1 March 2012 (UTC)

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 Fixed/Skipped
 * important discussion do not comment at this page

Achievements
Bugs Annoyances Fixed/Skipped

Gameplay
Bugs a!mpOnce the food bar is no longer full, it immediately empties.
 * Grammar corrected for clarity. CaMoreno3 19:21, 1 March 2012 (UTC)

Annoyances Fixed/Skipped

NPC/Animals
Bugs undefined In 1.2.2 Snow golems do not place snow on the ground when wandering around at all.
 * Clarification: They do not place snow in plains, swamps or mushroom biomes. It's still unintended, and should be fixed.

undefined In 1.2.2 mobs will spawn when walking around or landing after flying.Like a pack of about 6-8 wolves or 2 ocelots for no reason will spawn right in front of you or around you which can be annoying when building.

Annoyances Fixed/Skipped

Mobs
Bugs ! Sometimes, mobs can not be hit by a sword in 1.2.2 (seen in a Windows Client on a Linux Server) Annoyances Fixed/Skipped
 * Confirming, this was in 1.2 prereleases and 1.1 as well. This wastes tool durability, very annoying. Seen on a windows client SSP and a windows client on windows server (SMP)

World generator
Bugs A building with blocks at 127 at conversion time from the old format to Anvil will suffer severe block placing/removing lag and crashes in this chunk. Removing blocks at the top layer before converting will avoid the issue in the new map. Tested on a very old map, blocks were not placeable at this height in 1.1, only removable.

Annoyances Fixed/Skipped

Graphical/Lightning
Bugs Lighting on blocks will not render correctly when on the underside of a large structure. They become either black or they are completely lit up. Going next to the blocks renders some of the light, but it is in patches. Annoyances Fixed/Skipped

Sound
Bugs Annoyances Fixed/Skipped

Language
Bugs Annoyances Fixed/Skipped