Minecraft Wiki:Issues/1.2.5

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

undefined Cmd + Q still doesn't make Minecraft to quit. Tested on OSX 10.7.3 - Lion

undefined mp Labeled as Fixed on the 1.2.4 bugs page, still exists for me: After executing a command in the chat box, Minecraft will not exit the entry box thus the player is stuck in talking mode. Entering another command or text will, on a few occasions, give the opportunity to exit text mode. In most cases anyway, it will write another line beginning with a slash. This deprives the player from using command such as /tpa, /home or faction related command. This did not occur before 1.2.4.
 * Unable to reproduce this. Can you give us a screenshot of your Controls option screen ? --EvilSeph 17:08, 4 April 2012 (UTC)

! su Game crashes after 'saving chunks' whenever i walk in a certain direction. Annoyances

Fixed/Skipped

Minecarts/Boats
Bugs

undefined Getting into a boat with a water or lava bucket in hand causes the contents to be dumped if there is a selectable block on the other side of the boat. Cactose
 * Confirmed in 1.2.4, 1.2.5 prerelease, and a 1.2.4 world just updated today to 1.2.5 update. All 100% vanilla clients and worlds. Bucket empties when getting in or out of the boat if there is a selectable block within range behind the boat. Random seed used: debug. I copied Cactose's report above from Known bugs/Version 1.2.4 to Known bugs/Version 1.2.5. -Aurelius 15:59, 4 April 2012 (UTC)

Redstone/Pistons
Bugs Annoyances Fixed/Skipped

Blocks
Bugs Annoyances Fixed/Skipped

Crafting/Enchanting/Brewing/Interface
Bugs Annoyances Fixed/Skipped

Achievements
Bugs Annoyances Fixed/Skipped

Gameplay
Bugs x When the game searches for an existing portal (going from the Nether to the overworld), it doesn't seem to check above height 128. (Created a portal in the overworld at Y: 151, entered it, went back into the resulting portal in the nether, and ended up in a new portal at ground level)

x When you do "Pick Block" on Lapis Lazuli Ore you will get a Ink Sac. -joni97xXx Annoyances Fixed/Skipped

NPC/Animals
Bugs f When looking at an entity and doing "pick block", you get bedrock
 * According to this tweet, this is the case for all entities, not just pigs. And according to this tweet, it will be fixed "later". —Fenhl
 * This is a bug in single player only, as far as we know. --EvilSeph 16:05, 4 April 2012 (UTC)

! Nearby (100-200 blocks) dogs/cats teleport to you, even they are seated.
 * Specifically I've noticed that previously sitting cats and dogs teleport to you as soon as you get in range.


 * I tried reproduce the bug in a new world (generated in 1.2.4). No problem with this. Maybe a bug with converted worlds (pre 1.2.3).


 * Another case: (various users)


 * Confirmed that this happens in both single and multiplayer survival.


 * Confirm: seen by myself and a friend on two different servers running vanilla 1.2.4. Worlds are converted, cats and dogs where present and already tamed before conversion. Doesn't happen all the time: after upgrade, I've played a few hours without problems, all pets where sitting at home. Then suddenly all of them appeared at once while I was building a skyrail a few 100 blocks away from home. Maybe I crossed that distance for the first time since upgrade, but I'm not completely sure. They immediately started to push one another of the rail, causing all dogs to die from fall damage. Cats survived the fall and reapeared again and again, pushing me around, I barely escaped the same fate. I consider this a major bug, because uncontrollable tamed cats and dogs can easily cause the player to die, you either have to stop playing/building in dangerous areas, or you have to kill all your pet animals.


 * Untamed wolves and ocelots follow me and teleport.

Annoyances If you set animal on fire it will stay there and die. It does not "panic" like when you punch it. Fixed/Skipped

Mobs
Bugs Annoyances Fixed/Skipped

World generator
Bugs Annoyances Fixed/Skipped

Graphical/Lightning
Bugs Annoyances a! New lighting system severely drains FPS since 1.2. This problem persist in 1.2.5. Lighting changes in-game caused by lava, redstone lamps, redstone repeaters and/or pistons cause heavy FPS drops on low-mid range computers. This problem didn't exist in any version prior to 1.2. It looks as though there is now a lot of excess load on clients to calculate lighting changes, whereas pre 1.2 Minecraft forced the server to deal with lighting calculations. This essentially makes the nether and busy piston/redstone contraptions unplayable as the FPS lag is extreme. d3fin3d Fixed/Skipped

GUI
Bugs undefined When pasting a long link into the chat, if it wraps around to the next line, the link will be broken when clicked (it effectively gets cut off at the return point). Example - pasting: http://en.wikipedia.org/wiki/File:Countries_driving_on_the_left_or_right.svg into the chat displays as a long link covering two lines of chat. However, clicking the link returns the broken link: http://en.wikipedia.org/wiki/File:Countries_driving_on_t - d3fin3d Annoyances a In the multiplayer server list, descriptions of servers often overlap the player/slot count on the right of the interface. In 1.0, this issue also existed. In 1.1 - 1.2 the player/slot count was much better positioned: more to the right of the interface allowing for less overlap. In 1.2.4 the player/slot count has again returned to the center-right of the screen forcing many server descriptions to overlap the players/slots count. - d3fin3d

a In the multiplayer server list, long descriptions of servers don't 'wrap' around to the next line. Instead they continue on, even beyond the vertical scroll bar. - d3fin3d Fixed/Skipped

Sound
Bugs Annoyances amp The Sound for collecting experience orbs is extremely pitched higher than in SSP, and therefor sounds very tinny. Fixed/Skipped

Language
Bugs Annoyances Fixed/Skipped