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 !! Pressing the Open texture pack folder button in 1.2.3 will crash the game
 * Not for me (1.2.3), tried renaming texturepacks folder while minecraft was running, retried, still no crash. 194.137.243.226

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

!! Sound lags/glitches, control locks up (can't do anything, includes moving, looking around, etc.), makes Minecraft 1.2 unplayable. NOTE: Doesn't happen for 1.1 and earlier. NOTE 2: this happened with the snapshots that has the extended world height, too. -Sonicfangamer2

!! Worlds made before Minecraft 1.2.2 become unplayable. Worlds made during 1.2.2 run smoothly. 75.106.37.15 05:22, 2 March 2012 (UTC)

!! In converted maps placing a block sometimes cause the game to crash with the "saving chunks" screen and without a crash log. In SSP and y<127! Map is the "Super Hostile 10 Spellbound Caves" with Bedrock Blocks on Layer 126 if this helps. --LordJakson 07:59, 2 March 2012 (UTC)

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.

a In order for a directory in the texturepacks directory to show up as a texture pack in game, it requires a pack.txt placed in that directory. The text in that file is not displayed in game. Minecraft uses the pack.png and pack.txt that are in the minecraft.jar file for this situation (directory texture pack.) RobotHacker 09:32, 2 March 2012 (UTC)

Fixed/Skipped

Redstone/Pistons
Bugs undefined 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)
 * • In reply to BlackDragon, I was able to place redstone on glowstone during the snapshots, and perhaps even earlier (as well as mushrooms and trapdoors, as is not the case with some other transparent blocks). Judging by the picture, and the fact that current can still go UP the sides, I'd say this is a bug

a! Redstone devices don't power on above 128 meters in SMP. Even though redstone torches appear to be lit, they won't transmit power to any redstone dust/devices placed beside them. Annoyances

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.
 * I was able to grow both at 140+ with bonemeal, may have been repaired in 1.2.3 --Kittani1977
 * Was able to let natuarally grow all trees at above 128. A 2x2 jungle tree grew up to within 2 of the top level with bonemeal and a single jungle grew short to the same point in 1.2.3 -- Kittani1977

!! Previous world converted, now when placing blocks Minecraft crashes. When re-opened the block is still in your inventory and in the world. Only some worlds.

!! (Unconfirmed/not thoroughly tested) Placing a torch (potentially other items?) on y=257 -- one block above the height limit -- is allowed, but in SMP causes an "Array out of bounds" exception and crashes all connected clients in addition to the server, requiring a server restart.
 * I actually created something similar in single player. Built tower to max height, placed water on top (technically above) and then replaced water with torch.  crashed immediately. (EDIT seems to have been fixed in 1.2.3)-- Kittani1977
 * Still reproducible on 1.2.3 SMP --Outi 09:51, 2 March 2012 (UTC)

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 cannot be placed on the topside of upside down slabs. This includes torches, beds, doors, pumpkins, pressure plates, rails, mushrooms, redstone and repeaters, and levers.
 * Confirmed but may be intentional.. appropriate annoyance. -- Kittani1977

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)
 * Appears to have been fixed in 1.2.3, but now cannot seem to get any enchantment to show up over 39 (EDIT: Been messing with it for a while to confirm.. it seems ok... but different... somone else is going to have to do this too. -- Kittani1977

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

a When the floor in the gap between the enchanting table and bookshelves is covered with a layer of snow, the enchanting process acts like the bookshelves aren't there.
 * That is because a snow tile is still technically a block and the enchanting table is programed to require air blocks all around it. Same happens if you place torches. Not a bug, but an annoyance yes. Sennyotai

Fixed/Skipped

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)
 * Could not replicate. 194.137.243.226
 * Could replicate. Occurs on loss of first 'ham' 91.125.72.140 00:00, 2 March 2012 (UTC)
 * Couldn't replicate in default, but happens in Bukkit. --68.61.156.99 01:04, 2 March 2012 (UTC)
 * Could replicate on a Bukkit server, occurs with the loss of the first 'haunch' of food. Bejoe905 02:06, 2 March 2012 (UTC)

!! Right-clicking with a water bucket will crash the game rarely. -FishSticks -Unable to reproduce
 * Could not reproduce with over 300 buckets placed in 1.2.3 -- Kittani1977

undefined While swimming through water surrounding blocks of water will turn to a darker shade of blue, these darker spots do no revert when you touch land and end up making the area look shoddy and generally ugly.
 * Does not appear to be happening in 1.2.3 -- Kittani1977

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
 * This is caused by the absence of any block on the 63rd or 64th level in flat worlds, which the game requires in order to generate a stable spawn point (probably with the intent of avoiding unfair spawns/griefing).

a! Chests seem to get caught in an endless loop of opening and closing.
 * Could not reproduce in 1.2.3 -- Kittani1977

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.
 * Still do not in swamps in 1.2.3, haven't checked others. -- Kittani1977

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.
 * This sounds like its the 'untamed animals teleporting to you' bug. Only wolves and ocelots, correct? Sennyotai
 * Correct, but it seems they are actually those wolves I tamed before updating, which where un-tamed after the update.

undefined In 1.2, animals will continue to follow you after breeding, and they seem to gravitate toward you in general, even if you are not holding wheat. Animals also seem attracted to openings, gates, and doors.

Annoyances

a In 1.2 animals in fenced in areas manage to escape the fences as the chunk loads.

Fixed/Skipped

Mobs
Bugs ! Once the Enderdragon has been struck by the player once, it can no longer harm the player. This bug has been present for a long time. It can even be replicated in Creative mode, because the Enderdragon "repels" entities in a radius around itself until it is hit, at which point, the player can come in much closer.

! Sometimes, mobs can not be hit by a sword in 1.2.2 (seen in a Windows Client on a Linux Server) ! Mobs Dont burn in the day undefinedMobs (and players) mostly do not turn their head to show which way they are facing. All of them seem to look in the same direction. So far only tested in SMP - Lucifer_LLS http://www.lowlifescum.com Annoyances a Spiders climb walls using their faces and front legs. 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)
 * Cannot reproduce -Dsf190
 * Confirming Mobs sometimes do not burn in the day, it could have something to do with the lighting problems as experienced in 1.0 and 1.1, naturally, only occurring with the zombies and skeletons.
 * Confirming. Skeletons do not burn in daylight. Seen in SSP and SMP server, Windows 7 on all counts.
 * Confirming. Skeleton in the middle of a lake, caught in current stayed alive the entire day cycle.
 * Clarification: Mobs will not burn if they are within the shadow of a cloud.

World generator
Bugs undefined 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.

mp The newly generated part of terrain has "stripe" biomes with Ocean. For example, a line of chunks is Desert and the next line is Ocean, and this is repeated over and over again. The generated terrain itself looks fine, but the color of grass and F3 indicates different biomes. This happens at the empty parts of the world generated at 1.8/1.0 and converted to 1.2.2.
 * I have found that if I log-out and log-on again to the server, the biome information conform to the actual terrain and stripe Ocean biome just go away. And this problem did not appear at all in single player. Thus, I think this problem has something to do with network transfer of newly generated chunks. --Daybreaker 08:55, 2 March 2012 (UTC)

a! NPC Villages only generate partially. There will appear to be open air intersecting a house or a farm, but this air is impassable. When a block of any type is placed where a block was supposed to be generated, it immediately changes to the correct type. [Link]

Annoyances Fixed/Skipped

Graphical/Lightning
Bugs undefined 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.
 * •This occurs on upside down Stairs and Slabs because they do not accept light from underneath due to their natural orientation not requiring it. BlackDragonIV 22:41, 1 March 2012 (UTC)

undefined 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.
 * • This seems to only occur on worlds that were converted into Anvil BlackDragonIV 22:40, 1 March 2012 (UTC)
 * •I've had this issue on a newly created super flat world--Natedogith1 23:01, 1 March 2012 (UTC)
 * • I get this effect on a map generated in version 1.2.2 [SP][Su]. dhfrancis

undefined Torches placed in a 1x1 column with no air block above it the space containing the torch has a light level of 0, but torch looks lit and emits light outside of the torch's block. ZuppaHD
 * Can you describe this more clearly and/or post a screenshot? What do you mean by "a 1x1 column of torches with no air block above it"? I placed a vertical line of torches on a wall with a block above the top one and didn't notice anything wrong. Last username 23:27, 1 March 2012 (UTC)
 * It's this, I think: http://www.minecraftwiki.net/wiki/File:Torchbug.png. To reproduce; make a 3x3x3 room of stone, no exits, which would be totally black inside. Then add three blocks to make a 1x1x1 'hole' in one corner of the room, then put torch in hole. Result, all of the room is lit except for the block that actually contains the torch. I believe this has also been seen in earlier weeklies. (Single-player, Mac Os 10.5.8 if that matters) Simons Mith

undefined When spawned, random dark squares appear in no particular order, but in a uniform square shape in creative mode. Has not been tested in SPS. Fishsticks

undefined Water gets shadows if you are at shore or hovering over it (creative mode). Tested on 2 computers running different hardware / videocards. Makes a square pattern and reminds me of grass growing on dirt except its shadows on water.

undefined When using a texture pack, biomes will generate with a striping effect as seen here(http://imgur.com/a/jSqU4). This effect is visible within the F3 debug window. Switching back to the default texture pack with reset the issue and all biomes will behave normally. I have uploaded a video of the bug here http://www.youtube.com/watch?v=-a6v_W1_VeM TitaniumTurtle

undefined Players (and mobs) seldom turn their heads. They mostly seem to all face in one direction. Only tested in SMP so far - Lucifer_LLS http://www.lowlifescum.com

Annoyances

a Torches spawned in Mines and Villages will show incorrect lighting until updated. May not happen 100% of the time. (1.2.3 actually still does it)

Fixed/Skipped

Sound
Bugs undefined a Hollow tunnel like sound is heard when mining, placing, and obtaining items. This occurs on every mode of play in both SMP and SSP.
 * Sounds like Ambience, which is not a bug.

Annoyances Fixed/Skipped

Language
Bugs Annoyances a The "Quenya" translation of Lever is still "Mechanic Penis" Fixed/Skipped