Minecraft Wiki:Issues/Weekly 12w17a

Bug Reporting
This page is for bugs that:
 * 1) Are found in the version of the game specified in the article's title.
 * 2) Are found in an unmodified 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.
 * 3) Are reproducible to a certain extent. Please provide a short description on how to reproduce your bug along with system specs if required.

You can read Classifying Bugs for further information on what you should and shouldn't add to this page.

Bug reports should be as concise as possible without anecdotal waffle or your own opinions. We want to keep a clean, easy-to-read list of bugs for the developers to check through. This is not a place to express gameplay ideas or improvements.

Please include your system specs, where appropriate, and instructions on how to reproduce the bug. If the bug caused the game to crash or freeze, there may be a file beginning with the word "crash" in your .minecraft directory containing the crash report. If not, you can follow these instructions to obtain a crash report. Once you have the report, wrap it in the following template:

If you are unsure of an issue, it's good practice to post about it on the |talk page to see whether others can reproduce it.

When adding your bug report:
 * 1) Always prepend it with one or more issue labels.
 * 2) Sign your report with  ~  so that we know who reported the bug.
 * 3) Leave a blank line between each bug report.
 * 4) Do not place bullet points before issue labels. They are reserved for use with comments.

Once you've added a bug report, please keep track of it. Others may post comments underneath your report requesting clarification or more information.

Bug reports that do not provide enough useful information or contain too much opinionated or anecdotal waffle may be subject to removal.

Commenting
When commenting on bug reports:
 * 1) Prepend your comment point with an indented bullet point using the code ":*".
 * 2) Place the comment directly below the bug report without leaving a blank line between them.
 * 3) sign the comment with Mattrition 11:21, 26 April 2012 (UTC) . This is a deliberate exception to the usual wiki conventions; normally you should only add signatures to content on talk pages.

Please don't let debates about whether something is or is not a bug get out of hand. Similarly, don't clog bug reports with discussions of workarounds or possible fixes. If a bug or annoyance exceeds 10-12 lines of follow-up comments, move the entire follow-up discussion to the talk page and link to the discussion under the original bug.

Page Moderation
Please do not spontaneously delete a bug report unless it is blatant nonsense submitted an unregistered user. Try to contact the submitter by user-talk first and tell them about your concerns. Almost all active submitters will be co-operative. Always assume good faith.

You may also leave a comment explaining why you feel the bug should be removed, allowing time for others to weigh in on the decision or for the original poster to give additional information. Where possible, removal of a bug should be a group decision, not a decision made by a single individual.

Please make sure issues are given the correct category, type, and priority: issues with blocks go in the Blocks section, issues with mobs go into the Mobs section, and so on. List bugs in order of importance ( !! > ! > 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.

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.

Issue Labels
Use issue labels to indicate the importance and nature of a bug.

Mandatory issue labels come first, and must be one of the following:
 * !! =  !!  = 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. Note that this is not the same as feature requests, which is not what this page is for. Remember, leave gameplay ideas/solutions up to the developers.

Please also determine which game mode(s) your issue appears in, and flag it with the appropriate label(s) if any. (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.)

Optional labels can be added after mandatory labels.

Labels for indicating that an issue happens only in a particular game mode:
 * 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

In addition, ? =  ? </tt> can be added to tag an issue that you are unsure of or that the community (on the discussion page) believes requires further vetting. 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.

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

Further information is available at Classifying Bugs.

Crashing/System
Bugs

Annoyances

Fixed/Skipped

Gameplay
Bugs

Annoyances a cr In creative mode item selection screen, some blocks that can be useful are missing: Snow (the thin block of taiga and tundra biomes), the 3 Silverfish blocks (ID 97), End Portal Frame (ID 120) and the Dragon Egg (can be used as decoration without need to kill the Enderdragon. --89.21.192.211 19:15, 26 April 2012 (UTC)

a su When huge mushroom blocks are mined with Silk Touch, the damage value is always zero. TorchicBlaziken 20:19, 26 April 2012 (UTC)

a The first portal made in the overworld will spawn a portal in the nether as intended but subsequent portals WILL NOT. Any new portals made in the overworld will link to the first portal that Minecraft considered being the "closest" and will not spawn a portal regardless if it should have.

What that means is if you make a new portal in the nether, it WILL spawn new portal in the overworld in the appropriate coordinates. Also if you made a new portal in the nether with the appropriate coordinates to an existing portal in the overworld they will link up and function properly. (Example: I made a portal in my base that kept taking me to the communal portal exit in the nether. When I built a portal in the nether where my base's portal should have spawned, they link properly.)

This exists in single-player as well as multi-player with pure vanilla MC. Also this seems to have been present since 1.2.5, but not sure about earlier versions yet. -- KaizenNeko  ( T &#124; C )  20:51, 26 April 2012 (UTC)
 * This is intended behaviour, always has been. Lots of information here. Flagging this as annoyance. --Mattrition 21:07, 26 April 2012 (UTC)

Fixed/Skipped

Blocks
Bugs ! Redstone torch data-value/TileEntity (haven't decompiled to check what it uses, I think data-value) is not reset if the torch is destroyed and then replaced. This results in torhces burning out immediately if placed in a spot where it has previously burned out. Marked as major, as if this is related to TEs it may allow dupe bugs, although it probably isn't.--109.154.215.231 18:36, 26 April 2012 (UTC)
 * Corrected tag to mark as bug instead of annoyance. --Swampert rox 18:56, 26 April 2012 (UTC)

Fixed/Skipped f undefinedUpside-down slabs show as oak, no matter what type they are. Mustek 15:57, 26 April 2012 (UTC) Annoyances

Items
Bugs undefined Boats emit the blue spray water particles when moving on land. --Mattrition 17:09, 26 April 2012 (UTC)
 * Boats have always been placeable on land. This is intended. --Swampert rox 18:56, 26 April 2012 (UTC)
 * I stand corrected! And thinking about it, it makes sense to be able to place a boat on land and if you did, of course it would move slowly. The only thing that doesn't make sense is the water particles. --Mattrition 19:10, 26 April 2012 (UTC)
 * Updated your report --Moxxy 20:51, 26 April 2012 (UTC)

Annoyances

Fixed/Skipped

World Generator
Bugs

Annoyances

Fixed/Skipped

Mobs/NPCs/Animals
Bugs

Annoyances a When Mobs and players swim in water, their body will be shadowed when more than half of their body "dips" below the water line, possibly because they inherit the light level that the water block uses. This makes the body alternate between light and dark.--Mattrition 17:29, 26 April 2012 (UTC)

Fixed/Skipped

Graphical/Lighting
Bugs undefined mp When there is a thunderstorm in multiplayer the sky does not darken like in singleplayer.
 * Why is this flagged as "The community cannot reproduce"? Simply go on a server, wait for it to start thundering and you will see the sky will NOT turn darker, compared to single player. <font style="color:teal;text-decoration:underline;">heldplayer 15:57, 26 April 2012 (UTC)
 * That flag was there from the previous discussion, where clarification was needed on which visual effect is missing. I've cleared it up. --Mattrition 16:01, 26 April 2012 (UTC)

undefined mp When rain/snow starts on a server, then no starting animation is done. For reference, in single player downfall starts by slowly fading in. The same applies when weather stops. Annoyances

Fixed/Skipped

Menus
Bugs

Annoyances

Fixed/Skipped F undefined The volume sliders show no percentages. Mustek 15:50, 26 April 2012 (UTC)

In-Game Interfaces/HUD
Bugs

Annoyances

a When editing a book, adding text until the caret wraps on to the next line will cause the colour codes for the caret to become visible. -IPeer 17:51, 26 April 2012 (UTC)

a Either a bug or an annoyance, you cannot copy/paste into a book. Possibly if it is added, and you paste a large text into the book, it continues onto the next page(s) to enter in all the text in your clipboard. ~DaleK 18:14, 26 April 2012 (UTC)

a You can't change the cursor position while editing a book. <font style="color:teal;text-decoration:underline;">heldplayer 18:54, 26 April 2012 (UTC)
 * This is an omitted feature. And just FYI: you're not using the [?] label correctly. Have a read of the Issue Labels section at the top of the page.

Fixed/Skipped

Language/Text Files
Bugs/Errors

Annoyances a Oakwood, pinewood, and sprucewood are single words. Spelling them with a hyphen like they are in the names for the oak, pine, and spruce wooden slabs is improper for this reason. "Jungle-Wood" is fine because "junglewood" is not even a proper word. TorchicBlaziken 20:18, 26 April 2012 (UTC)
 * This is an extremely, extremely trivial annoyance. Not a bug--Moxxy 20:46, 26 April 2012 (UTC)

Fixed/Skipped