Known bugs/Version 12w21a
| Read the instructions! You'd better read the instructions before posting an issue or modifying this page, lest raptors from the depths of the intertubes attack you and devour your liver. Also, spellcheck and the talk page are your friends, as are research, diligence, and Jeb.
|
| Current versions | |
|---|---|
| Full release 1.2.5 |
Weekly release 12w21a |
| Previous versions | |
|---|---|
|
Full releases
|
Weekly releases
Pre-releases
|
Contents |
[edit] Instructions & Page Organisation
[edit] Bug Reporting
This page is for bugs that:
- Are found in the version of the game specified in the article's title.
- 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.
- 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:
{{cr|your crash report here}}
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:
- Always prepend it with one or more issue labels.
- Sign your report with --~~~~ so that we know who reported the bug.
- Leave a blank line between each bug report.
- 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.
[edit] Commenting
When commenting on bug reports:
- Prepend your comment point with an indented bullet point using the code ":*".
- Place the comment directly below the bug report without leaving a blank line between them.
- Sign the comment with --~~~~. 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.
[edit] 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 ( [!!] > [!] > [X] ). 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 {{subst:Known bugs}}. Any changes made to this header should also be made to this template.
[edit] 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:
- [!!] = {{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. 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 [A] [SP] [MP] [Su] [Cr] .)
Optional labels can be added after mandatory labels.
Labels for indicating that an issue happens only in a particular game mode:
- [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:
In addition, [?] = {{bl|?}} 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: {{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}}.
Further information is available at Classifying bugs.
[edit] Crashing/System
Bugs
[!!] / [A!]
When downloading the snapshot, it svaed itself as a zip file, and not a .jar. It didn't allow me to put it in .minecraft/bin, so I couldn't play the snapshot.
[!!]
when I trie to load a world I see myself spawning in a black world and I keep falling down. nothing gets generated. when I do this in creative mode I can hover and even after waiting a fiew minutes still nothing has generated. when I just installed the snapshot the worlds worked. now they don't.
This happened to me too, but it hasn't crashed yet. 72.209.199.2 21:29, 24 May 2012 (UTC)
| Crash Report |
|---|
{{{1}}}
|
[!!] When loading a world created in 12w21a sometimes it's very laggy (FPS drops down from 100 to 10 or less), other times it doesn't show any (or almost any) chunks and I start falling into the Void, other times it just crashes.
| Crash Report |
|---|
Time: 24/05/12 22.02 Description: Unexpected error java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$KeyIterator.next(HashMap.java:828) at aql.a(SourceFile:30) at fr.a(SourceFile:25) at ach.c(SourceFile:746) at aco.c(SourceFile:500) at ach.a(SourceFile:738) at ho.b(SourceFile:132) at ho.a(SourceFile:69) at akp.a(SourceFile:21) at ajk.<init>(SourceFile:72) at net.minecraft.client.Minecraft.a(SourceFile:1377) at px.c(SourceFile:142) at px.a(SourceFile:120) at aag.a(SourceFile:64) at aag.e(SourceFile:112) at aag.h(SourceFile:100) at net.minecraft.client.Minecraft.k(SourceFile:1134) at net.minecraft.client.Minecraft.D(SourceFile:577) at net.minecraft.client.Minecraft.run(SourceFile:525) at java.lang.Thread.run(Thread.java:680) Relevant Details: - Minecraft Version: 12w21a - Operating System: Mac OS X (i386) version 10.7.4 - Java Version: 1.6.0_31, Apple Inc. - Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Apple Inc. - Memory: 481030784 bytes (458 MB) / 580517888 bytes (553 MB) up to 1067057152 bytes (1017 MB) - LWJGL: 2.4.2 - OpenGL: ATI Radeon HD 6750M OpenGL Engine GL version 2.1 ATI-7.18.18, ATI Technologies Inc. |
It happens less than once every 10 tries, tested on SSP Creative and Survival, both with Normal and Large Biomes generation. The glitchy world can load smoothly afterward and doesn't seem corrupted. Never happened before 12w21a.--Wedhro 21:05, 24 May 2012 (UTC)
[!!]
Crash when pressing save and quit to title --Shikamaru123 14:23, 24 May 2012 (UTC)
| Crash Report |
|---|
Time: 5/24/12 7:13 AM Description: Unexpected error java.lang.NullPointerException at nv.a(SourceFile:41) at aag.a(SourceFile:64) at aag.e(SourceFile:112) at aag.h(SourceFile:100) at net.minecraft.client.Minecraft.k(SourceFile:1134) at net.minecraft.client.Minecraft.D(SourceFile:577) at net.minecraft.client.Minecraft.run(SourceFile:525) at java.lang.Thread.run(Thread.java:679) Relevant Details: - Minecraft Version: 12w21a - Operating System: Linux (i386) version 2.6.38-15-generic - Java Version: 1.6.0_22, Sun Microsystems Inc. - Java VM Version: OpenJDK Client VM (mixed mode, sharing), Sun Microsystems Inc. - Memory: 216211696 bytes (206 MB) / 367689728 bytes (350 MB) up to 508887040 bytes (485 MB) - LWJGL: 2.8.3 - OpenGL: Gallium 0.4 on ATI R350 GL version 2.1 Mesa 7.10.2, X.Org R300 Project |
Annoyances
[A]
The server file is still required. --Sejsel 13:23, 24 May 2012 (UTC)
- Annoyance, Downgraded --71.251.115.135 21:05, 24 May 2012 (UTC)
- Workaround: Create an empty file in .minecraft/server called minecraft_server.jar, and it will work fine. The real server jar file works too. --Frogging101 15:12, 24 May 2012 (UTC)
Fixed/Skipped
[edit] Gameplay
Bugs
[!] Deleting region-files, causes a crash of the Map like this [1]. Normally the game will regenerate the terrain with the informations of the level.dat and the Seed. But here the whole map crashes.--Locoloco 15:24, 24 May 2012 (UTC)
[!] Going to the End results in the player being kicked for moving too quickly. (This may be related to players in the End spawning in specific coordinates.) When you reload you are in a completely empty End (other than the dragon). I don't know whether this happens when going through a portal in a stronghold, because I got there by using /give 119. TorchicBlaziken 21:02, 24 May 2012 (UTC)
[!] Saving the world can cause an "Exception in server tick loop" that will cause the game to not be able to communicate with the server (to load or interact with worlds) for a length of time after the bug occurs. Restarting Minecraft will not fix the bug but connecting to a multiplayer server(or just trying to) seems to fix it. Anything that causes the single player server to stop properly should fix it. How to reproduce: Toggle "Advanced OpenGL" and then "Save and Quit to Title" while the world is still being redrawn, load any world and the world will only load a few chunks or Minecraft will crash. ----Nagrom_17
(I don't know why the crash report isn't showing, you can see it if you click Edit)
- Fixed the crash report for you. --Shikamaru123 19:35, 24 May 2012 (UTC)
| Crash Report |
|---|
Time: 5/24/12 1:49 PM Description: Exception in server tick loop java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$KeyIterator.next(Unknown Source) at aql.a(SourceFile:87) at ox.n(SourceFile:363) at ox.m(SourceFile:327) at ox.run(SourceFile:279) at dd.run(SourceFile:447) Relevant Details: - Minecraft Version: 12w21a - Operating System: Windows 7 (amd64) version 6.1 - Java Version: 1.7.0_02, Oracle Corporation - Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation - Memory: 318532328 bytes (303 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB) - Player Count: 1 / 0; [fq['Nagrom_17'/1479, l='Testing New- Can delete', x=-32.65, y=87.33, z=1123.13]] - World Testing New- Can delete Entities: 0 total; [] - World Testing New- Can delete Players: 0 total; [] - World Testing New- Can delete Chunk Stats: ServerChunkCache: 0 Drop: 0 |
[X] Villager trading does not work properly when the Emerald price is not placed in one go. Screenshots. HexatonicFantasm 13:08, 24 May 2012 (UTC)
- I'm able to repro. Upgrading to major bug.--Nathan2055 16:20, 24 May 2012 (UTC)
- Not a major bug. Does not render game unplayable, and there's a simple workaround; pay the full emerald price in one go.--Simons Mith 17:31, 24 May 2012 (UTC)
[X] When being offered a stack of an item by a villager, right-clicking the stack will only give you half the stack but will still take all the emeralds, most likely because the game is trying to split the stack.
[X] The trading system only checks how much of an item you are offering the first time you put the stack in. For example, adding three emeralds to the trading UI one-by-one for an item worth 3 emeralds will not allow you to buy the item, but adding all three emeralds at once will.
[X] Many villages in sand biomes are completely glitched, as shown in this video.
- This has happened with all the villages since 1.8 multiplayer not just desert ones. <MCKMan> 15:12, 24 May 2012 (UTC)
- That happend one time with 12w19a for me. I simply restart Minecraft and that failure was gone.
[X] Cannot reliably place water from buckets, seems to happen mostly around spawn. The placed water simply vanishes and right-clicking nearly anywhere in the area refills the bucket. However, other effects of placing the water (such as farmland being irrigated, or lava turning into obsidian) are not visible. Happens in both 12w19 and 12w21.
Annoyances
[X] I beat "The End" on creative mode without going to "The Nether" first and it appears that the "End Poem" text is doubled over itself. Screenshot I don't know if this is limited to not going to "The Nether" first.
[A!] The golem recipes do not care whether the blocks are freestanding or part of a larger structure, so structures made of iron or snow blocks can be griefed by Endermen placing down pumpkins. TorchicBlaziken 01:11, 22 May 2012 (UTC)
[A] Sandstone Stairs are not craftable. --Kumasasa 21:59, 24 May 2012 (UTC)
Fixed/Skipped
[edit] Blocks
Bugs
[X] Emerald ore is red, it has not been changed to green. This can confuse new members. Wcb98 14:26, 24 May 2012 (UTC)
- Mojang is already aware of this. Expect a fix in 12w21b or 12w22a. <MCKMan> 15:13, 24 May 2012 (UTC)
- Not a major bug, downgrading. Read the Classifying_bugs guidelines --Simons Mith 17:36, 24 May 2012 (UTC)
[X] Placing a dispenser makes a block below sand
- Not a major bug , downgrading. Read the Classifying_bugs guidelines --Simons Mith 17:36, 24 May 2012 (UTC)
[X] Book on Enchanting table isn't opening
- Not a major bug, downgrading. Read the Classifying_bugs guidelines --Simons Mith 17:36, 24 May 2012 (UTC)
[X] Placing a sand or gravel block ONE block ABOVE snow (NOT a snow block, but the thin snow,) will cause the sand to be supported by the snow, rather than falling. Placing it directly on the snow works properly, as does placing the sand TWO blocks above the snow.
[X] [Cr]
I was in a shallow cave, not far from spawn. When placing torches on about 4 blocks, they changed from stone to dirt. I took these pictures: http://imgur.com/a/z95IY --Blazonfox 22:44, 24 May 2012 (UTC)
Annoyances
[A] Pressure plates function on top of fences. They should be reverted to the way they were in Beta 1.8 and not work on top of fences. Because they work on top of fences the tables in villages make annoying sounds. TorchicBlaziken 21:28, 24 May 2012 (UTC)
Fixed/Skipped
[edit] Items
Bugs
[X] Emeralds are called "Diamond" in the inventory screen. *
- Doesn't seem to happen on everyones game. Mine are called emeralds.
- I have this problem too.
- I have the same problem here as well. Maybe it is to do with the language setting?
- Yes, it has to do with the language setting. It's a bug in English:UK for sure, works fine in English:US. Not sure about other languages --16:54, 24 May 2012 (UTC)
- Only happens with other languages then English (US) because in the code for the languages Diamonds were called as "item.emerald.name" and jeb_ fixed that now for all languages. So the language files need to be updated.
[X] When eating food you will eat it twice. TorchicBlaziken 21:21, 24 May 2012 (UTC)
- I saw this is 12w19a, but only sometimes. Most likely to trigger if you eat then move immediately afterwards; it's as if the 'moving' keypress, if timed right, continues to register as an 'eat' command. Result is you eat two of an item rather than the one you intended. If you stop, eat, wait for a moment to digest, then move, the problem doesn't trigger. --Simons Mith 21:41, 24 May 2012 (UTC)
[X] Emeralds works like an entity ghost, they can pass trough blocks when dropped.
Annoyances
Fixed/Skipped
[edit] World Generator
Bugs
[!] Just as in most of the prior snapshots, there are massive chunk errors like the one on the Mojang site posted by Jeb the week where there was no snapshot. I am mostly playing in "large biomes" mode and therefore this is also known for "flat worlds", this may be especially connected to this. There is one in each generated world for sure, the question is not if but just where. (Java, drivers & co. are up to date and i really know what i am doing; also this was not the case before 1.2.5 or the snapshots after it).
[X] Just like abandoned mineshafts were before the floors were implemented, strongholds generate weirdly when they cross a ravine. The seed -623160645725253637 is a good example of this with a stronghold in a hole close to spawn which crosses an underground ravine. TorchicBlaziken 22:00, 4 May 2012 (UTC)
Annoyances
[A] Small house in Desert Villages can contain floor made from dirt --Sejsel 13:27, 24 May 2012 (UTC)
- May be intended: The inhabitant of that house is quite poor and cannot afford more than a dirt floor. --80.134.16.213 15:41, 24 May 2012 (UTC)
- Poor? The inhabitant wants to give me many emeralds just for toilet paper! --Sejsel 16:12, 24 May 2012 (UTC)
- Yes, the inhabitant is really poor: He cannot wipe his back with emeralds, so that's a cool win-win-deal... --Kumasasa 18:23, 24 May 2012 (UTC)
- I think the point is that they should be made with sand instead, to fit the aesthetic theme. I agree that they should be made with sand instead. TorchicBlaziken 20:58, 24 May 2012 (UTC)
[A] Takes a really long time to load chunks, which either causes or is the cause of lag. Probably both. Not sure if this is just my computer being slow, but it's annoying
[A] Pyramids at edges of chunks may be invisible. Placing a block where the pyramid should be shows the correct block and does not use up the placed block.
- Brought down to [A] as exiting and reloading made the entire pyramid visible. Occurs with villages as well. --Zomborger 19:59, 24 May 2012 (UTC)zomborger
Fixed/Skipped
[edit] Mobs/NPCs/Animals
Bugs
[X] Notch forgot to code it so that the air meter goes down when mobs, including the player, are submerged in lava. This is an oversight and should be fixed. TorchicBlaziken 21:23, 24 May 2012 (UTC)
[X] All the cats that have been tamed become ocelots.
- Please label your bugs properly... Added the [X] tag. <MCKMan> 16:02, 24 May 2012 (UTC)
[X] [?] Villagers are unable to locate Desert Village houses in night --Sejsel 13:32, 24 May 2012 (UTC)
- Cannot reproduce. Are the doors reachable or two blocks in the air or blocked ? --Kumasasa 22:17, 24 May 2012 (UTC)
[X] Classic bug, but boat glitches through block when being pushed by current.(client side)
[X] When using the Villager trade system, you have to add the right amount of (whatever material) all at once, you can't add 50 then right click (to half them,) to get the desired result of 25 (for example.) Nor can you pick up a stack and manually right click to drop materials into the villager one by one.
[X] Only farmer villagers spawn naturally and other villagers can be only spawned from spawner egg or when the villagers mate. --84.0.149.137 18:51, 24 May 2012 (UTC)
- Reload your world, the other types of villagers will have their correct skins. This is still a bug, though, it's just that the bug is actually that they sometimes won't render as the correct type. TorchicBlaziken 21:00, 24 May 2012 (UTC)
[X] [?] The sheep are always white but they drop other wool colours.
- Cannot reproduce. At least natural spawned sheep are white, gray and brown and drop their colour when killed. Downgraded to annoyance. --Kumasasa 22:15, 24 May 2012 (UTC)
- If the original report is true then it is a genuine bug, so you should leave the OP's classification alone. Marking a bug with Template:? to indicate that it's questionable in some way is helpful, but misclassifying a bug as an annoyance isn't.
I see reports of villagers not displaying the correct skins and tamed cats appearing as ocelots, so it is credible that coloured sheep (which kind of have custom skins too) could have the same problem. Reloading tends to cure the glitch for villagers and ocelots, may work here too. --Simons Mith 22:30, 24 May 2012 (UTC)
- If the original report is true then it is a genuine bug, so you should leave the OP's classification alone. Marking a bug with Template:? to indicate that it's questionable in some way is helpful, but misclassifying a bug as an annoyance isn't.
Annoyances
[A!] Cats and wolves do not have AI that prevents them from walking into cacti.
Fixed/Skipped
[edit] Graphical/Lighting
Bugs
[X] When a torch is at the top of a 1x1 vertical shaft, the space it occupies will be dark. TorchicBlaziken 21:13, 24 May 2012 (UTC)
[X] Lighting on transparent blocks or on block not exposed to sunlight in "Sandy" Village is broken. --Sejsel 13:25, 24 May 2012 (UTC)
- You are just describing a lighting bug that happens everywhere not just "Sandy" villages. <MCKMan> 16:06, 24 May 2012 (UTC)
[X] Upside-down slabs have buggy lighting when there are blocks above them. - Mustek 16:47, 24 May 2012 (UTC)
- Corrected to minor bug. Also, a bug that's well-known to Mojang by now, I'm sure. --Simons Mith 17:34, 24 May 2012 (UTC)
[X] Mobs that have different skins sometimes only render as the first skin. This happens with villagers and ocelots. TorchicBlaziken 21:03, 24 May 2012 (UTC)
Annoyances
[A] Stars aren't white. I wouldn't have mentioned this niggle at all, save that jeb already went to the trouble of making them 'more realistic' (specifically, smaller and brighter) in response to Twitter feedback. So I'd like to mention that a further refinement would be to make their colours vary too. --Simons Mith 21:12, 24 May 2012 (UTC)
Fixed/Skipped
[edit] Menus
Bugs
Annoyances
Fixed/Skipped
[edit] In-Game Interfaces/HUD
Bugs
[X] Right-clicking on a NPC with a Ender pearl will open the trading GUI, but will throw the ender pearl in the same time. It might hurt the villager. --Azenet 15:08, 24 May 2012 (UTC)
- Seems to be a genral right clicking bug: Right clicking with a bow on a NPC will shoot the NPC (and trigger the Golems), right clicking with rotten flesh will eat the flesh (and poison the player)... Upgraded to bug. --Kumasasa 18:26, 24 May 2012 (UTC)
[X] Villagers will trade with people who have attacked villagers. TorchicBlaziken 21:31, 24 May 2012 (UTC)
[X] While trading with a Villager, if the Villager dies, the trading menu stays open and it's still possible to trade with them. --Doopz479 21:58, 24 May 2012 (UTC)
Annoyances
[A] Pressing tab in singleplayer draws a black line instead of the online players list -- bmanrules
- Please use the proper tags. <MCKMan> 16:05, 24 May 2012 (UTC)
Fixed/Skipped
[edit] Language/Text Files
Bugs
[!!] The Game still crashes if you go to "controls" in EspaƱol (Mexico). This bug has existed since languages were first implemented.
[X] Generating chunks, Saving chunks and Loading world texts are not present when creating/loading/exiting a save file.--Mega9man 18:10, 24 May 2012 (UTC)
- This is a serious bug that I'm getting as well. I'm going to up this to major. --Nathan2055 16:22, 24 May 2012 (UTC)
- Why does it class as a major bug? Please explain, otherwise you should leave the original poster's classification alone. --Simons Mith 18:22, 24 May 2012 (UTC)
Annoyances
[A] The chat settings section of the options menu doesn't have an ellipsis like all the other sections. TorchicBlaziken 21:25, 24 May 2012 (UTC)
- C'mon. --Kumasasa 22:21, 24 May 2012 (UTC)