Minecraft Wiki:Issues/Weekly 12w15a

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

This page is for bugs that occur in the client or server of an unmodded Minecraft game. If you think a bug you have found in a modded version is not the result of the mods you have added, please be sure to reproduce it in an unmodded game before posting it here.

When reporting or commenting on a bug or annoyance, please sign your remarks with ~~~~. This is a deliberate exception to the usual wiki conventions; normally you should only add signatures to content on talk pages.

Please do not spontaneously delete an issue report or comment unless it is patent nonsense submitted by someone who has not logged in. Try to contact the submitter by user-talk first and tell them about your concerns. Almost all genuine, active submitters will be co-operative. 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 [A] [SP] [MP] [Su] [Cr] .)

Please make sure issues are given the correct category, type, and priority: redstone issues go in the Redstone section, problems with mobs go into the Mobs section, and so on. List crash bugs [!!] first, then major bugs [!] , then minor ones [X] . Annoyances go into the Annoyances subsection, with major ones [A!] before minor ones [A] . Issues that have been marked as fixed or skipped are moved to the Fixed/Skipped section. Issues that Mojang cannot reproduce should be left 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.

If a new version of Minecraft is released, create that page with {{subst:Known bugs}}. Any changes made to this header should also be made to this template.

Note: Please don't let debates about whether something is or is not a bug or annoyance get out of hand. Similarly, don't clog bug reports with discussions of workarounds or possible fixes. If ever a bug or annoyance ends up with more than about 10-12 lines of follow-up comments, please move the entire follow-up discussion to the talk page and put in a cross-reference to the discussion under the original bug.

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

[!!] Resizing the GUI in the options menu will cause the game to crash.
[!!] Having a minecart dispense from a dispenser onto powered rail causes the game to crash.

Gameplay

Bugs

[!] [MP] Eating food in multiplayer takes significantly longer than normal, up to over a minute. (eating animation time + additional duration due to lag) Singleplayer is uneffected by this. For some reason this is not happening when the player is in water.

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

[A] [MP] The "/" key for opening the chat box in multiplayer is still not working properly in some keyboard layouts such as Portuguese Brazilian, where it is triggered by the ";" key.

Mobs

Bugs

[X] Entities can breathe in lava. This is probably not intended behavior and most likely an oversight. This can be fixed by adding this code to onEntityUpdate in EntityLiving:

Code Sample

if (isEntityAlive() && isInsideOfMaterial(Material.lava) && !canBreatheUnderwater() && !activePotionsMap.containsKey(Integer.valueOf(Potion.waterBreathing.id))) { setAir(decreaseAirSupply(getAir())); if (getAir() == -20) { setAir(0); for (int i = 0; i < 8; i++) { float f = rand.nextFloat() - rand.nextFloat(); float f1 = rand.nextFloat() - rand.nextFloat(); float f2 = rand.nextFloat() - rand.nextFloat(); worldObj.spawnParticle("bubble", posX + (double)f, posY + (double)f1, posZ + (double)f2, motionX, motionY, motionZ); } attackEntityFrom(DamageSource.drown, 2); } }

• whilst its probably a bug, its not one that will affect a great deal in the game, so I've downgraded it to minor --Mattrition 15:51, 13 April 2012 (UTC)

[X] When a Spider Jockey climbs up a wall, it can suffocate the Skeleton in the ceiling. TorchicBlaziken 23:08, 12 April 2012 (UTC)

[X] [SP] [Cr] When multiple types of Spawn Eggs are placed inside a dispenser, furnace, or chest and the container is destroyed, or when multiple spawn eggs are dropped by the player, some of the spawn eggs will become invisible and change type. If for example if 1 each of squid, zombie, slime, and blaze spawn eggs are dropped, the player might receive back 2 squid eggs and a 2 blaze eggs.

Annoyances

[A] [Cr] When dropping multiple spawn eggs the coloured dots on the eggs will not correctly align with the egg dropped. (Floating on their own)

[A] [MP] [Cr] When multiple types of spawn eggs are dropped near each other, by the player, or from destroying a chest, dispenser, or furnace containing eggs, some will become invisible. They can still be picked up, but are just transparent.

[A] When using mob-eggs to spawn mobs in creative mode, any mob that doesn't have a 'baby' mode will not display.

• What difficulty were you playing on? NetherrackCreeper (talk) 13:01, 13 April 2012 (UTC)

Blocks

Bugs

[!] [Cr] Pick block still picks technical blocks for some items, for example:

• Signs
• Redstone Wire

Tell me if you find any more :) NetherrackCreeper (talk) 12:33, 13 April 2012 (UTC)

Multiplayer-related

Bugs

[!] Several sound instances do not play:

• Chicken egg laying sounds.
• Pressure plate, lever, button sounds.
• Mob/Other Player stepping sounds.
• Other Player mining sounds (the sounds playing before the mining is finished - see Obsidian or Bedrock for examples).
• Fishing rod sounds (reeling should not make a sound).
• Cave sounds (or at least, they are not synchronized between players).
• Slime and Magma Cube sounds.
• Hoe breaking sounds.
• Armor breaking sounds.

[!] A few graphical elements are missing:

• Fishing rod "line".
• Fishing rod "line" in held item. It shouldn't appear when the line is casted.
• Other Player breaking animations.
• Magma Cube animations.

[!] Mining takes longer in multiplayer than in singleplayer. This is caused by a click-mining 'fix' that was added in Beta 1.3 and is not needed.

[!] Slimes and Magma Cubes randomly warp up and down when they have a ceiling above them.

[!] Knockback and damage screen calculation is often wrong in multiplayer, actually dealing knockback when it shouldn't (like drowning or being on fire).

[!] Hitting mobs is harder in multiplayer because of lag. It is also much easier for monsters to hit players. Perhaps a delay before attacking (based on lag) should be added...

[X] Player movement is not smoothed enough (the client does this) in fairly or very laggy conditions.

[X] Arrows "warp up" when shot on walls. They also disappear and become impossible to collect when shot on ceilings.

[X] The anti-spam does not really prevent spam.

• I can type 4-5 messages a second as non-op and I do not get kicked. Calinou - talk × contribs » 23:43, 24 February 2012 (UTC)

[X] Arrow shooting is buggy and sometimes "resets" the charging progress.

[X] Not able to breed chickens and only able to breed some cows and sheep.

[X] The 3 second invincibility on reconnection can be exploited to be invulnerable to falls/lava/PvP/...

[X] Having trouble making dogs change from sitting position.

Annoyances

[A] Instead of saying "Outdated Server!" when going on a 1.1 server, it says:" Internal Exception: java.net.SocketException:Connection reset"

[A] When connecting to an outdated server/client, protocol version/game version should be shown.