Minecraft Wiki:Issues/1.2.3

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.3) 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
 * I cannot reproduce this in 1.2.3 vanilla on Windows Vista Home Premium: freshly downloaded and installed, I login and click texture packs and click button "Open texture packs folder" and the expected Windows explorer folder opens. Please give the detailed error message and check your antivirus software in case that is the cause. -Aurelius 15:28, 2 March 2012 (UTC)
 * Can you please pastebin the error it gives you? Or does the game just close with no error? Dinnerbone 15:55, 2 March 2012 (UTC)

undefined mp Setting server build limit to 64 will disallow creation of new blocks above 64, but does not prevent loading/generating blocks beyond 64. 194.137.243.226
 * But I think this is good, allows creating areas which are prohibited from modification. 194.137.243.226

Annoyances a Neither 1.2.3 nor 1.2.2 accept command line arguments that previous versions accepted. I first determined this changed when the minecraft.jar launcher changed from 1.1 to 1.2.2, while the launcher for 1.2.3 is unchanged from 1.2.2. See Stand alone client (change). Please note this is not related to the environment variable JAVA_OPTIONS. -Aurelius 15:22, 2 March 2012 (UTC)

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)
 * (1.2.3 cmp,smp) I was able to place torch there, but no crash. 194.137.243.226

Crafting/Enchanting/Brewing/Interface
Bugs undefined The first character of every enchantment label is missing. For example, "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
 * Could get roughly level 25 ench at max with 32 bookcases. Then added roof and floor bookcases, total 82 bookcases. After could get level 48 ench. Then removed back to 32 bookcases. Still could get level 48 ench. Rebuilt 32 bookcases + table, still could get level 48 ench. (did this in cmp) 194.137.243.226

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

x mp Naturally generated leaves no longer decay in 1.2.3 tested in vanilla SMP
 * All naturally generated tree leave types decayed. (oak, large oak, birch, pine, jungle tree, 2x2 jungle tree, jungle undergrowth tree) (tested in cmp) Did this occur at 1.2.3 generated world or converted world? 194.137.243.226

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

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

undefined If you log out while sitting in a boat, you fall out of the boat when you log back in. 82.69.54.207

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 Ocelots only spawn on easy or above difficulty only (Even though they are suppose to be peaceful mobs and don't harm you) Confirm?
 * I believe this due they spawned by mob generator. Read about that on weekly bug pages. (not tested) 194.137.243.226

undefined When standing you stand in a portal with a block behind you creepers sometimes won't attack you.

Annoyances a Iron Golems do not kill slimes. Slimes are annoying in superflat worlds and should be killed.

World generator
Bugs

undefined (1.2.3) Chunk generation error, chunk seems flipped. Seed "bug" location 41x,-381z. 194.137.243.226
 * Added picture Zicxynum 15:57, 2 March 2012 (UTC)
 * Unable to reproduce, running vanilla 1.2.3, using seed "bug" at exact location. Check for mods.

Graphical/Lightning
Bugs

undefined At times a texture will be stretched so that one of the corners is not on the actual block. Stretching may occur to a point far from the block. Observed on versions 1.1, 1.2.2 and 1.2.3

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)