Minecraft Wiki:Issues/Weekly 12w07b

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 12w07b) 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 x (F3) "Chunk Updates" info is still often equals to "FPS" info. This just can't be true. Annoyances Fixed/Skipped

Redstone/Pistons
Bugs Annoyances a The Boat track system (30m/s) from the last diamond stuff does not work. Fixed/Skipped

Blocks
Bugs x I don't think it's normal that mini trees in the jungle have jungle wood + normal leaves.


 * Why not jungle wood + jungle leaves (or normal wood + normal leaves) ?

x When torch is placed over tall grass, tall grass is destroyed.
 * Same is true for blocks (comfirm!)Skaruts 16:20, 15 February 2012 (UTC)
 * This is not a bug, this is intentional.

Annoyances Fixed/Skipped

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

Achievements
Bugs Annoyances Fixed/Skipped

Gameplay
Bugs undefined/a Directional keys will get "stuck" and you'll continue in the same direction untill pressed again Kit Ballard 16:17, 15 February 2012 (UTC)

Annoyances a Lilly Pads break boats Kit Ballard 15:48, 15 February 2012 (UTC)

Fixed/Skipped

NPC/Animals
Bugs Annoyances Fixed/Skipped

Mobs
Bugs Annoyances a Creeper "fuses" seems to be closer then usual. Took down a creeper a sword's reach when they used to attempt to blow up at that range Kit Ballard 16:02, 15 February 2012 (UTC)

Fixed/Skipped

aif a villager goes up a cactus they can't get down, take damage and die.

World generator
Bugs !although the nether has still a bedrock layer at 128, there's now air above, which means that there will spawn tons of zombie pigman and ghasts, but they are all unreachable unless you are in creative. this also means that there are a lot less monsters below, since the monsters above quickly fill up the mob cap. also sometimes mushrooms will grow on top.

! There are almost no trees in swamps, except on the water Skaruts 16:21, 15 February 2012 (UTC).

! Birch trees are not being generated. Skaruts 16:21, 15 February 2012 (UTC)
 * Wow, they wasn't kidding: http://img207.imageshack.us/img207/7523/28040658.jpg Kit Ballard 16:11, 15 February 2012 (UTC)

! Entering the End crated NO End Stone. http://img835.imageshack.us/img835/523/88907417.jpg Kit Ballard 16:36, 15 February 2012 (UTC)

! There are no caves generated in the world!


 * Mineshafts still generate luckly. Kit Ballard 16:21, 15 February 2012 (UTC)

Annoyances a! There are no trees generated in taiga biomes!

a Villages still tend to generate houses buried. Kit Ballard 16:27, 15 February 2012 (UTC) Fixed/Skipped
 * Villagers also spawn out side the buried house's door, covered by the ground. Found a group when I dug out the door. Kit Ballard 16:28, 15 February 2012 (UTC)

Graphical/Lightning

 * Water is much more clear.
 * Don't see how this is a problem. Kit Ballard 16:38, 15 February 2012 (UTC)


 * If Water is directly below an Ice Block, the Ice Block is a clear as glass.

Bugs ! The new redstone lamp causes extrem lag when switched and in sunlight/moonlight, but it works fine when you switch it in the complete dark or when there is only blocklight. If you don't believe me just build this small setup and switch the lever:


 * actually it's even worse: every block light update in sun light causes massive lag, just press F3 and place a glowstone and you'll see a big spike in the lagometer
 * According to the profiler, the lag is caused by "root.tick.level.tickPending.checkLight.top < too" --Barracuda 16:57, 15 February 2012 (UTC)

Annoyances a Snow isn't shown on the map!

a Text in the item screen overlaps item graphics http://img210.imageshack.us/img210/3937/11323001.jpg Kit Ballard 15:46, 15 February 2012 (UTC)

a Your Field of View changes when the player's head goes underwater. Although this might be deliberate, to show the different refractive index of water. Happens in single-player, on both creative and survival.

Fixed/Skipped

Sound
Bugs Annoyances Fixed/Skipped

Language
Bugs Annoyances Fixed/Skipped