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 weekly 12w08a) 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).[1] (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 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.
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
[!!] Minecraft never fully quits and disrupts all programs running and will require a hard computer reset on Mac OS X.
Annoyances
[A] The game is quite laggy when switching to another window and then reswitching to it Dexes TTP 23/02
I can't confirm this, maybe it's your computer --Galaxy_2Alex (Talk)
[!!] The game crashes if you type a seed for generating a new world
Can't confirm this bug on my platform, precise yours. Dexes TTP 23/02
Fixed/Skipped
.
Redstone/Pistons
Bugs
[X] Piston heads frequently fail to push the player.
Annoyances
Fixed/Skipped
Blocks
Bugs
Annoyances
Fixed/Skipped
Crafting/Enchanting/Brewing/Interface
Bugs
Annoyances
Fixed/Skipped
Achievements
Bugs
Annoyances
Fixed/Skipped
Gameplay
Bugs
[X][SMP] Flying over a pressure plate while not touching it is constantly activating/deactivating it. However, it doesn't do that when jumping over it (it doesn't activate it).
[X][Su][Cr] In Camera Mode [F5 Then F9]. Move around using the WASD Keys. There is no gravity and when you go back to Normal mode. You stick at the same Height. *Ruins Your World If you Try it !*
Annoyances
[A]Music Disc "where are we now" is still missing.
[A] Double doors mess up when switching to anvil media:lol.png
this was mentioned by jeb and is nothing serious, just fix them, they can't change it anymore and we have to live with this minor annoyance
To clarify what the above poster said: replace the incorrect door and things will be fine. Hardly even a minor annoyance unless you have a lot of old double doors.
This has been reported many times. I myself think this is a feature Yoshidude56 16:56, 23 February 2012 (UTC)
This indeed catches many people's eyes, and I'll say it again: if wolves are intended to change color because they're wet, why don't sheep? or wool blocks? We could go on and on about this... GhengopelALPHA
Annoyances
Fixed/Skipped
Mobs
Bugs
[X] Iron Golems can't get up a 1 block high step out of water.
[X] Sometimes Iron Golem texture is completely invisible.
I'm also getting this problem, playing vanilla w/o texture packs. I've checked the .jar, and the texture's definetely there in the Mob folder, but it's not being applied to the model. Same thing happens with a custom texture pack.TenhGrey 17:15, 23 February 2012 (UTC) File:Whitegolem.png
Golem Texture Glitch
[X] Zombies smash down doors on ANY difficulty.
[X] If you build a Iron golem in the ground you can push him through the adjancents blocks.
Annoyances
[?] Cave spiders can fight water currents in 1-high tunnels, bug or features?
Cave spiders are smaller than regular spiders, enabling them to get thru 1-high areas. Mob movement in water was also recently changed. Feature probably.
ok, that seems to break most of the spider transportation in traps. they fight the currents if they see the player, which is most of the time if the player stays in the "active zone" and move with the "new system"...
[A] Zombie pigmen attack iron golems individually when provoked, not in groups.
[X] Villager Golems can hit you through glass panes.
[X] Creatures don't spawn when using spawn eggs.
Don't forget to set difficulty on easy or higher to spawn hostile mobs.
[?] Iron Golems are way too slow to defend their village. They also dont see long enough.
Probably intentional considering their large health pools and respawn. Sight radius might be to prevent them wandering due to stray zombies that aren't threatening the village.
Fixed/Skipped
World generator
Bugs
[X][MP] Spawn location is still replaced by 0,50,0 when creating a new world.
[X] As in the last Snapshot, Birches and Pines do not spawn --Galaxy_2Alex (Talk)
= {{OS|OSX}} = Mac OS X
= {{OS|Win}} = Windows
= {{OS|Linux}} = GNU/Linux
Can't confirm this bug on my platform, precise yours. Dexes TTP 23/02
