Minecraft Wiki:Issues/Weekly 12w07a

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 weekly 12w07a) 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 ! Having a redstone clock at the new top of the world, attached to a dispenser spawning Creepers. Will crash the game with the "Saving Chunks" error. This is just how it happened to me, it could be any mob being spawned. Annoyances [A!][mp] I have a smp server, and the server is much more laggy then before. With one player online, first 8ms tick, now 40 ms! and if you play with redstone, over 60 ms! This is very annoing. Fixed/Skipped
 * spIt happens sometimes with any type of clock linked to anything, at any level (confirm)

Redstone/Pistons
Bugs Annoyances a The boat track doesn't work anymore. (may be a fix) Fixed/Skipped

Blocks
Bugs Annoyances Fixed/Skipped

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

Achievements
Bugs Annoyances Fixed/Skipped

Gameplay
Bugs Annoyances Fixed/Skipped

NPC/Animals
Bugs undefined mp When sheep tries to eat, it will constatnly head bang heavy metal style all the time. Reloging will solve this, but it will happen again with their next meal. Annoyances Fixed/Skipped

Mobs
Bugs Annoyances Fixed/Skipped

World generator
Bugs undefined In new generated Worlds Birch Trees do not spawn. (please confirm) --Galaxy_2Alex (Talk) Annoyances [A!][mp] on mp, the jungle looks like swamp or is snowy. in the desert you can see grass that is green and not dry. this is anoying Fixed/Skipped

Graphical/Lightning
Bugs Annoyances acr In creative mode everything is at full light level, even under the ground and in water. a You are able to see the sun at night when standing at a high Y-level.
 * I thought it's a feature? --Galaxy_2Alex (Talk)

a Your character turns invisible in third person/front view while standing on Y=256 or above. Fixed/Skipped

Sound
Bugs Annoyances Fixed/Skipped

Language
Bugs Annoyances