Minecraft Wiki:Issues/Weekly 12w05a

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 12w05a) 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, not  .)

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! =  = 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 =  = Minor bug.
 * 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 =  = Single-player.
 * mp =  = Multiplayer.
 * su =  = Survival mode.
 * cr =  = Creative mode.

Labels for indicating that an issue is restricted to a particular OS:
 * =  = Mac OS X
 * =  = Windows
 * =  = 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: 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.

Crashing/System
Bugs !! When a minecart falls into the void, it doesn't get destroyed unlike other items and therefore will be never deleted from the memory or world file. this is a huge memory leak that can easily cause chrashing when few hundred minecarts fell down after a while ( this can happen quite easily as they NEVER despawn=> it just fills up over time!) Tested it with MCedit: even 1km below bedrock they still fall down.

Annoyances Fixed/Skipped

Redstone/Pistons
Bugs undefined 2 Pistons facing each other, fired with a rapid pulser with a 1 block space and another sticky piston between them, makes the middle sticky piston to be "rideble" Picture: http://desmond.imageshack.us/Himg192/scaled.php?server=192&filename=20120202212659.png&res=medium (bartselen)

undefined Standing middle of block that piston pushes, makes you fall through pushed block. (tested on sp) 188.238.156.140

undefined If you use piston to break redstone signal that powers another piston, signal goes away but piston does not retrac. (tested on sp) 188.238.156.140

undefined Standing on downwards pointing piston, while it retracts, makes you fall through. Also possible to walk through retracting piston. (tested on sp) 188.238.156.140

undefined This kind of 1-2 tick clock gets jammed after save/load sometimes. (tested on sp) 188.238.156.140 r>r r<r further instructions and statistics on [edit] 188.238.156.140

Annoyances Fixed/Skipped

Blocks
Bugs x The bug where vines are replaced when a block is placed in the same space was not actually fixed even though it was marked as fixed by Jeb in the 12w04a bugs page. Annoyances

a Jungle trees that are 2x2 blocks wide, are actually 4 separate trees, since each individual wood block has bark around it.

Fixed/Skipped

Crafting/Enchanting/Brewing/Interface
Bugs ! In survival, Shift-click crafting doesn't take all the resources you use into account. Example: Shift-click Crafting 4 signs will give you two.

Expanding on that: When shift-clicking to craft: Crafting something a few times at once (8 furnaces from 64 cobblestone, for example), will only give you half of what you should get. Leftover resource stacks will be lowered by 1 if you craft an uneven amount of times. This is caused by the materials accidentally being removed twice from the crafting table in the code.

Annoyances a Armor gauge never fills up unless you are using diamond armor. It never decreases when the armor degrades, no matter what type. You have to manually check your armor level via inventory.
 * That's normal behavior. It's to show how much armor power you have. How close it is to breaking is the damage bar, found in the inventory. --Nathan2055 19:33, 2 February 2012 (UTC)
 * It used to be like in the bug report for quite a long time. The new armor bar style is confusing. --Sejsel 19:46, 2 February 2012 (UTC)
 * Specifically, the behavior was changed in Beta 1.9 pre1; see Armor. —kpreid 20:49, 2 February 2012 (UTC)

Fixed/Skipped

Achievements
Bugs Annoyances Fixed/Skipped

Gameplay
Bugs

undefined When crafting with shift-clicking i get less than i should. I used 8 planks to craft sticks and only got 12 instead of 16. i used 16 sticks and 16 coal and only got 32 torches. Only happened since i got the weekly snapshot today. I was using the inventory crafting grid for reference. --Stewb83 16:27, 2 February 2012 (UTC)
 * Please delete this, its already reported in correct place. 188.238.156.140

Annoyances

a Saplings in swamp biomes will not grow swamp trees.
 * Swamp trees are normal trees. Also this belongs to blocks. 188.238.156.140

a Pasting text into Minecraft only works with Ctrl-V and not Command-V, which is the Mac command for pasting.

Fixed/Skipped

NPC/Animals
Bugs undefinedVillagers go in and out of houses repeatedly at night.

undefinedVillagers can get stuck trying to open a door that is unreachable.

undefinedIf a villager is exiting a house while another is entering it, they will get stuck.

undefinedAt night, if a villager fails to detect a house, it will stand still and do nothing.

undefinedIf two villagers are attempting to exit or enter the same door, they will get stuck.

undefinedVillagers barely move their heads anymore.

undefinedCats only sit if your right click with an item in hand. Thecatlover1996 18:13, 2 February 2012 (UTC)

undefinedPushing A tamed cat in the Sit stance and pushing it off a cliff will cause the cat not to take any fall damage.

Annoyances Fixed/Skipped

Mobs
Bugs Creepers explode if they are killed while hissing.

undefined you can't let sit or stand-up a cat without have a item in your hand. --Joppiesaus 18:05, 2 February 2012 (UTC)

Creepers and skeletons no longer strafe

Annoyances a If you "sit" your cat and go on a journey away from where they are sitting, they will appear near you, away from where you sat them, and still in the sitting position. I had to "un-sit" my cats and let them follow me home, to get them back. This seems to happen during combat with hostile mobs.

Fixed/Skipped

World generator
Bugs undefined Jungle trees can be generated floating above water. Thecatlover1996 16:04, 2 February 2012 (UTC)

undefined When placing 4x4 pastern of Jungle Tree Saplings, when using bone meal it can create another large jungle tree on top of it. alaskafish22:22, 2 February 2010 (GMT+2)

Annoyances Fixed/Skipped --Joppiesaus 18:24, 2 February 2012 (UTC)

Graphical/Lightning
Bugs undefinedEggs have their pattern disconnected when dropped. Thecatlover1996 18:13, 2 February 2012 (UTC) Annoyances Fixed/Skipped

Sound
Bugs undefinedRain sometimes makes no sound. Thecatlover1996 18:13, 2 February 2012 (UTC) Annoyances a Fire Charge make no sound like flint and steel. --Joppiesaus 18:24, 2 February 2012 (UTC)

a Cats and ocelots make no sound. --Joppiesaus 18:24, 2 February 2012 (UTC)

a Lava has a very unnatural sound. (Trenix 20:47, 2 February 2012 (UTC))

a NPC Villagers don't make sound. This is something Jeb and Jon planned to add sometime in the near future.

Fixed/Skipped

Language
Bugs Annoyances Fixed/Skipped