Minecraft Wiki
Advertisement
Read this 
Mojang has an official bug tracker and does not track bugs for any editions of Minecraft on this wiki. Please use the appropriate bug tracker to report and view current bug reports.

Java: bugs.mojang.com/browse/MC.
Bedrock: bugs.mojang.com/browse/MCPE.


For further info, see the issues notice page.
Do not delete this page, any issues currently being recorded are purely for archiving purposes.

Instructions & Page Organisation

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

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

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.[1] (Also, note that if, for example, a minor annoyance appears in both single-player and multiplayer, and also insurvival mode, you should label it as [A] , not [A] [SP] [MP] [Su] {.)

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.

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 4J Studios (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 a future 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 4J 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 [X] ; you can produce this label with the shorthand {{bl}}.

Further information is available at Classifying Bugs.

Crashes & Stability

Bugs

[!!] Game crashed on save and exit (frozen Xbox, "Exiting the game" screen) after after an extended (4-5 hrs) MP session. World was not successfully saved, when reloaded the world was back to the way it was before the MP session. --ArcaniX5696

  • To be honest, I hope I can't recreate this one... I have no idea what could help isolate the crash condition as the play session was too long to even start guessing... Is there anyway to do crash reports from the MCX360 version? --ArcaniX5696

[!!] Game crashes when trying to load a world, if you have dropped a iron block {9 iron crafting into block form} then save and exit. Tested on 3 separate worlds.

  • [?] The same happens if you create a cake. --Unsigned comment from 98.243.139.101
  • Disagree that the cake causes this. The 4-5 hour game session I lost due to a crash (listed in this section) was last successfully saved/loaded with a half-eaten cake placed on top of a furnace. --ArcaniX5696

[!] Game crashes whenever a player changes a filter to what might be Worldwide.

  • Assuming you refer to the leaderboards: when I was looking at them yesterday, I didn't crash when looking at the worldwide stats. Has anyone replicated this yet?
  • This happened to me the first time around, but after a console restart it worked. 70.160.166.80 22:32, 10 May 2012 (UTC)
  • My original post had the 'leaderboards' part in it. I would still keep this as a bug as it shouldn't crash at all. Pokeneon7 12:30 AM, 11 May 2012 (EST)
  • Is this a crash condition that should this be [!!] instead of [!]  ? (please cleanup this comment after addressing) --ArcaniX5696

[!] Game crashes whenever 2 (and/or possibly more) players finishing mining the same block.

  • Is this a crash condition that should this be [!!] instead of [!]  ? (please cleanup this comment after addressing) --ArcaniX5696

[!] Once you enter the nether, then go to leave the nether it causes the game, making the player restart the console --Jetty Z

  • Is this a crash condition that should this be [!!] instead of [!]  ? (please cleanup this comment after addressing) --ArcaniX5696

[!] Auto-Save system is completely non-functioning! --ArcaniX5696

  • Related to my crash log above, I recall seeing the Auto-Save icon appear consistently during my 4-5 hour play session, yet all off the changes were lost when the game crashed. --ArcaniX5696
  • Auto-Save only saves information related to your Xbox Live profile and player progress. The world must still be saved manually through the menu. The idiot who put the Captcha in forgot to include a submit button so I can't provide source links.--70.191.205.34 00:33, 12 May 2012 (UTC)

Game randomly exits the map for unknown reasons with a message saying a connection to the server was lost.

  • I'll assume you're talking about in an online session? I've had that happen to me a couple times.
  • Not an online session, but offline. I am then back to the last time I saved when I load the world again.
  • Well that bodes poorly. I removed the SP tag because it happens online as well, even when there aren't any network issues, so it must be something present in the game as a whole.
  • I have been getting the same problem as well. I will load up my map and play for awhile, then i will check the leader boards and i get a message saying the server connection was lost. I then reload my world and find that everything I had done before checking leader boards, was lost. This has happened twice now and both times it has bugged me immensely.--xGoDLiiKex
  • Same for me, i get disconnected from a "server" in SP. Happened heavily after having set a long redstone wire and made a long train line, on a part of the map.
  • Did you have the session set to online or not? It may be that you're actually connected to a server when the game is set to online, regardless of whether or not client players are present. --8bitlove2a03 02:04, 12 May 2012 (UTC)

[X] The game can crash if you change the leader board filters while the leader board is loading/refreshing.

Gameplay

Bugs

[X] Arrows can bounce off of the player without hurting them.

[X] Arrows can hurt the player without touching them.

[?] Pressing B while in bed will permanently delete the item you are holding, instead of dropping it.

  • Discussion on talk page questioning if this is a valid bug --ArcaniX5696

[MP] Game sometimes randomly says players have left the game even when they are still connected. So far I have manually disconnected/reconnected as soon as I as told the server had "dropped" me; will remain on server to see if any complications arise from the bug

[X] Sometimes drops that are sitting in a hole, then displaced by filling the hole with a solid block, will bounce up onto the top of the newly placed block (as they should) but cannot be picked up. So far, removing the newly placed block has let me pick the drop up. --8bitlove2a03 02:04, 12 May 2012 (UTC)

Annoyances

Manually saving after death without picking up dropped items from said death will delete those items from the world.

Coal (items?) can't be picked up if it is between 2 blocks, ie. the line in the middle.

  • How do you mean? Like, if it's on the line between two blocks of grass? I'm trying to replicate but getting nothing here. Were you doing it online? It may just be a phantom drop issue due to a hitch in the server; happens in the PC version too. --156.26.221.54 22:10, 10 May 2012 (UTC)

Map is not infinite

  • This was not a design choice. This is due to the hardware limitations of the Xbox 360, and from what I remember from interviews at GDC there's not much they can do about it. --70.169.103.206 05:23, 11 May 2012 (UTC)
  • If I remember correctly, infinitely generating maps were not released until 1.8. The 360 Edition is in 1.6. It is not a bug. The hardware limitations might restrict them later on. --Sciguymjm 04:02, 12 May 2012 (UTC)

[A] When you die and then respawn, the mobs who killed you is never stayed there if you are a bit far from that point.

[A] Your stats are sometime reset

Blocks & Fluids

Bugs

Pouring water from a bucket may cause it to either leave an extra water source, or leave no water source when pouring the water out.

Sometimes blocks will not be selected when looked at (No outline, can't mine them, etc.). Looking at another face of the block may select it, but looking back to the other face again still does not work. Occurs near the edge of the map (Could be due to world limit? Confusing, however, because some blocks can be broken but others can't)

Stone stairs (possibly wooden as well) sometimes glitch out and appear as a full cobblestone block.

  • I'm having this issue too. Two stairs next to each other are blinking between stair and cobblestone texture. They are still able to be walked on though. --156.26.221.154 22:15, 10 May 2012 (UTC)

[F] Sugar Canes are solid (You can't walk through them). (Wasn't this true on the PC and this isn't a bug?)

[?] Leaves often go unrendered for some people, causing trees to seem leafless, and people to walk into and bounce out of areas without a clue why. So far I've only encountered it while playing on others' worlds. Both the host and client players have been susceptible to the issue. Have had instance of both host and I being unable to see the leaves while another client could.

  • Have experienced this from both a client and a host perspective. The leaves can usually be seen from the host's side but can still be broken by the client's even if they cannot see them. --156.26.221.154 22:20, 10 May 2012 (UTC)

Farmland can revert back to dirt without being walked on.

  • Is the farmland irrigated, and are you sure there aren't mobs (or other players) walking across it while you aren't looking? Unirrigated farmland is intended to revert to dirt after a period of time.

Minecarts seem to have poor collision detection causing minecarts with furnaces to phase through other carts instead of pushing them, I cant narrow down exactly what is causing this but when my furnace cart tries to push another cart up a ramp it stops moving for a bit while the two carts seem to try and occupy the same square before the furnace cart goes through the regular cart and continues on up the ramp

Annoyances

You cannot place a sign and exit out of the text menu immediately, because it will leave the "awaiting authorization" on the sign. Instead, you have to edit at least one line of text.

[?] Signs sometimes go back to the "awaiting approval" temporary message for no apparent reason (I'v seen this on two occasions)

[A] Putting the word "Basic" on a sign caused "Censored, Censored, Censored, Censored" to appear on sign instead of entered text. --ArcaniX5696

Crafting, Inventory, and Interfaces

Bugs

[F] Crafting a Cake does not return the buckets.

When retrieving two or more stored leather from a chest, one disappears.

When interacting with a furnace, the interface freezes after closing out of the tutorial text.

When using the inventory, after the tutorial text pops up, I am unable to exit the inventory, and must go to the dashboard.

Mobs & Animals

Bugs

[X] [MP] Hostile Mobs will sometimes spawn inside enclosed *well* lit areas when sleeping in a bed. Torches surround my bed every two blocks on all sides, yet I woke up with a Skeleton Archer standing on the block immediately beside my bed. (I've only played MP so not sure if this is an issue in SP) --ArcaniX5696

Passive Mobs sometimes can't be damaged when they are standing in Tall Grass.

You can not ride a pig that has a saddle equipped.

Passive mobs, when attacked in tall grass, get stuck and can still be attacked.

Spiders will sometimes lose their ability to move when they are hit in tall grass.

I have had several instances in which mobs could not be damaged. Have had instances of being unable to kill a squid underwater (attacking with sword), a skeleton (attacking with fists), and a zombie (also with fists). --70.169.103.206 05:23, 11 May 2012 (UTC)

Pigs and spiders when they have a single block above them and are hit, will not move but just flash red and cannot be killed.

Chickens will sometimes open half of a wooden door, top or bottom, and enter your house. Really, this just happened to me.

[X] Hostile mobs that are unable to attack back while being attacked with a melee weapon will take no damage from hits. Example: A skeleton is behind a wall with only its feet exposed. You strike its feet. It turns red but is not knocked back and takes no damage.

[A] Hostile mobs can spawn in 2x1 empty spaces. Annoying if you accidentally left a small sliver of space between walls.

[X] Ghasts spawn in large numbers in the Nether, instead of rarely like in the PC version

Graphical & Lighting

Bugs

Lighting is often not smoothed on water blocks, so each block has obviously different light levels.

The minecart is flickering after getting pushed in the opposite side by a powered rails. Problem is solved by moving the camera.

Annoyances

There is quite heavy Mipmapping and low quality texture filtering, so blocks 10+ away from the player appear to have low resolution and tessellated textures. This can detract from the game experience.

I may be misremembering the old lighting system (considering how long it's been since Beta 1.6.6)but it seems like torches' slight is not as it was. When placed on a wall, the light seems to be very bright in a two block radius around the torch, and past that point drops off considerably. It may have been a temporary issue with newly-placed torches, as it seems to have improved after reloading the world

  • This seems to be common when playing as a client. When hosting I have not experienced any glitches with the lighting. --156.26.221.154 22:24, 10 May 2012 (UTC)
  • I agree that as a client, lighting is severely bugged. You all can work around this by spamming the breaking and replacing of a torch until it becomes bright. This should take anywhere from 5 to 15 seconds, but still requires a patch fix. 70.160.166.80 22:37, 10 May 2012 (UTC)

[A] Wooden pressure plates sometimes rise up a block. Not sure what caused it, but I placed two side-by-side and one of them rose up by a block into the air. Standing on it made it revert to its normal position.

[A] It seems that objects when dropped in a large amount (like dying with a full inventory) aren't all appearing at the same time, but progressivly after getting them, maybe a way to keep memory.

[A] Mobs seems to disapear when too far from the player.

  • Mobs are unrendered after existed for a certain ammount of time or if their distance to the player becomes too large. It's intentional. It prevents the world from overcrowding, and reduces memory usage since the game won't track entities in chunks on the other side of the map from the player.

GUI and Menus

Annoyances

Inventory, crafting, smelting, chest, and other pop-ups are too small to see in vertical and horizontal split screen. (moved from Bugs)


No confirmation when quitting without saving, but when you want to save, the game ask a permission.

Nether & Portals

Bugs

Nether portal generation bug: a player in the nether had his portal destroyed by Ghasts. A second player enters the (still lit) portal from the overworld, and instead of entering the nether through the existing gate a second portal was created in front of it and one space to the right. Not entirely broken, as both players left through this new portal and returned to the same portal in the overworld.

[!] Saving in the Nether, exiting the game without saving, and reloading the previous save game will cause the player to be stuck above the bedrock in the Nether. No blocks can be placed, and the player cannot jump off the edge of the map, so there is no way to get back. May be an online only glitch.

Worlds and World Generation

Annoyances

Worlds can't be renamed.

References

Advertisement