Minecraft Wiki:Issues/Weekly 12w15a

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

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 undefined. 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  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. 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)
 * !! =  !!  = 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 </tt> = 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>.

Bugs
!! Resizing the GUI in the options menu will cause the game to crash.

Bugs
! 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: 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); }        }

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

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