Minecraft Wiki:Issues/1.2.2

Issues
Full releases 1.4.7 1.4.6 1.4.5 1.4.2 1.3.2 1.3.1 1.2.5 1.2.4 1.2.3 1.2.2 1.1 1.0.0 Beta 1.8.1 Beta 1.5 Pre-releases 1.4.6pre 1.4.5pre 1.4.4pre 1.4.3pre 1.4.2pre 1.4.1pre 1.4pre 1.3.1pre 1.3pre 1.2.5pre 1.2 Preview 1.0RC2 Beta 1.9pre6 Beta 1.9pre5 Beta 1.9pre4 Beta 1.9pre3 Beta 1.9pre2 Beta 1.9pre1 Beta 1.8pre2 Beta 1.8pre1	Weekly releases 13w02b 13w01b 13w01a 12w50b 12w50a 12w49a 12w42b 12w42a 12w41b 12w41a 12w40b 12w40a 12w39b 12w39a 12w38b 12w37a 12w36a 12w34b 12w34a 12w32a 12w30e 12w30d 12w30c 12w30b 12w30a 12w27a 12w26a 12w25a 12w24a 12w23b 12w23a 12w22a 12w21b 12w21a 12w19a 12w18a 12w17a 12w16a 12w15a 12w08a 12w07b 12w07a 12w06a 12w05b 12w05a 12w04a 12w03a 12w01a 11w50a 11w49a 11w48a 11w47a

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

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 JAVA_OPTIONS environment variable instead.

Redstone/Pistons

Bugs

File:Redstone on glowstone bug.png

[X] Redstone current will not travel down the side of a glowstone block.

What do you mean? Redstone current does not travel down the sides of blocks. Are you saying it will not travel Through the block, or that the Redstone Wire will not travel down the side of the block? Also please read the page, in no way is this a major issue as if glowstone doesn't work literally any other block apart from glass will work. --Moxxy 21:44, 1 March 2012 (UTC)

• This only occurs with Glowstone. Glowstone should be considered a transparent block, and thus you shouldn't even be able to place redstone wires on top of it. (May have been a change due to the ability to place redstone dust on top of redstone lamps, thus causing it to be logical that it could be placed on Glowstone Blocks.) BlackDragonIV 22:11, 1 March 2012 (UTC)

Blocks

Bugs

[X] you can't grow birch and pine trees over 128 block high. oak and jungle tree grow just fine with both versions available.

Annoyances

[A] Upside down stairs and slabs are generally difficult to work with since the only way to get one is to place the stair/slab on the underside of a block. If you place a slab on the side of an upside down slab, another upside down slab should be created instead of a normal slab. This will allow for faster upside down slab roof creation.

• For placement of upper slabs, being able to place upper/lower slabs based on targeting the upper/lower half of a block side would make things much easier.
• Alternatively a keyboard shortcut command (like holding a key down) to place the block in the upside down position in the normal block space would be likely easier, more extensable, and be able to allow for more up-side-down blocks going forward. Having to divide each block in half to determine targeting would be more difficult to implement without breaking or making difficult other block placement.
• A third option would be having upsidedown slabs as a completely different object which could be crafted simply by placing a single regular slab in the crafting menu to convert it to an inverted one. To convert it back, an inverted slab could become a regular one the same way.

[A] Many blocks/items (redstone, torches and doors for example) cannot be placed on the topside of upside down slabs.

Crafting/Enchanting/Brewing/Interface

Bugs

[X] 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

• important discussion do not comment at this page

Gameplay

Bugs

[A!] [MP] Once the food bar is no longer full, it immediately empties.

• Grammar corrected for clarity. CaMoreno3 19:21, 1 March 2012 (UTC)
• Could not replicate. 194.137.243.226

Annoyances

[A!] After dying in creative mode (by falling in the void), the player respawns on a random spot, not where he spawned when the world was created. (Tested on a superflat world) -Strobaal

NPC/Animals

Bugs

[X] 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.

[X] 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.

Mobs

Bugs

[!] Sometimes, mobs can not be hit by a sword in 1.2.2 (seen in a Windows Client on a Linux Server)

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

Fixed/Skipped

[!] zombies don't burn in sunlight anymore-JL

[!] Iron Golems are not generated at villages anymore-JL

World generator

Bugs

[X] 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.

Graphical/Lightning

Bugs

[X] 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.

[X] Mysterious shadows - zigzag lines and 'blobs' of shadow appear at random on map. Most noticeable on sand, water, and in superflat mode. The zigzags are about 16x16 blocks and on superflat can go on for hundreds of metres. Screenshot: http://www.minecraftwiki.net/wiki/File:Shadowbug.png 82.69.54.207 I did consider the possibility that it might be a cloud casting a shadow, but I can't seen any connection between the shape of the clouds and the shape of the shadows.