Minecraft Wiki:Issues

This page's purpose is to list all the bugs players have come across. Most of the single-player bugs also apply to multi-player.

Bugs and feature requests can now be logged at Getsatisfaction: Mojang.

General

 * If the FPS is too low, Minecraft will close without saving any chunks. The inventory, player position, momentum, and time will all be maintained, however, as these are stored in the level.dat and are constantly updated.
 * You are unable to directly swap items in your inventory if the two items are same. This is important if you would like to swap the same item type with two different durability values. This is a result of the way combining stacks works.
 * Sometimes you can see through everything; this randomly happens on all games on all platforms. Toggling the fog distance will change everything back to normal (Default key is F).
 * Occasionally, picked up items will not appear in the inventory.
 * If you die while viewing your inventory, your character will fall out of the box and will be rotated sideways. The player's skin will also be reverted to default after a few moments.
 * Sometimes, the game may reset the seed that the map generates from. This is a result of tweaks of the seed and terrain generation code that are regular parts of the game's updates.
 * The addition of naturally generated sandstone has 'fixed' the floating sand by providing support.
 * Sneaking does not prevent the player from falling off of Stone Slabs, Cacti and Soul Sand. Sneaking only prevents falling off of Soul Sand and Cacti if the ledge height is more than 1.
 * Sneaking prevents movement from Soul Sand or Cacti to any other block.
 * If you are sneaking when you exit the game, when you reload the game you fall into the block below you, and onto the block below it instead.
 * The red glow featured at sunset and sunrise is normally a gradient. Pulling up the player's inventory will cause the gradient to solidify along a sharp boundary.
 * If you hold the left mouse button down while holding a item, then open your inventory, still holding the left mouse button, and then close your inventory, as long as you don't release the left mouse button, you are able to break blocks without the swinging item animation.
 * Occasionally, when saving the game and reloading, you will fall through the block you were standing on. This can be prevented by jumping as soon as the game loads.
 * A bug exists where the game may refuse to remember custom controls after updating (not to a specific version - just updating in general). This is caused by one of the values in Minecraft's "options.txt" file being unset, usually the "lastServer" field - attempting to connect to any multi-player server address (valid or otherwise) typically resolves the problem.
 * Occasionally, some chunks of the map do not update with the day/night cycle, as seen here. Also, even in caves or closed environments the player can still see lighting bugs, (i.e. An area has full light and it has a small spot of full darkness next to it. When the spot is edited, it changes to normal.) These glitches are fairly common and can cause multiple problems. Usually staring in the general direction of the chunk for a moment will fix this.
 * If you enter Fullscreen mode, then exit it, mouse clicks will no longer work for game dialogs (game menu, inventory etc.). However, mining and using items still work. Pressing Esc, waiting for the game to save and restarting the client or re-entering fullscreen to save and quit resolves this problem. Here is a topic on Minecraft Forums related to this bug.
 * If you place four blocks so that they can stop the flow of water then place water or lava into it you can put a cactus piece into it.
 * If you hit a movement key and at the same time open inventory or click that movement key will become "stuck". Pressing and releasing the same movement key again will stop you again.
 * If you disconnect from a server while a message is displayed, and then load a single player world, the text will appear in SSP as shown here.
 * When Java crashes, your work sometimes cannot be saved and you may have a new respawn point.
 * Sometimes mobs within a certain area will stop moving, and entering the area will cause the player to become rooted to the spot and often vibrate wildly. Many animations, such as digging and health recovery will be broken, and mobs that the player hits will constantly loop the damage animation without dying.  It is not possible to catch fire.
 * If the player adjusts their system clock one hour forward, the game will run abnormally fast, allowing quick movement and mining. Changing the time back, exiting the game, setting the time forward again, and re-entering the game will allow you to change the system clock properly. Note that the inverse of this is not true--setting the time backwards will not slow down the game.
 * The openAL32.dll and openAL64.dll that come with Minecraft do not work properly. This sometimes causes Minecraft to crash when players turn sound on in the options menu. On Windows machines, deleting Minecraft's openAL files usually solves the problem, because Minecraft will then automatically use Windows operating system's copy of the openAL dll, which works properly.
 * When trying to open Minecraft on an external monitor, Minecraft may crash.
 * Selection bounding box breaks ATI card's Anti-aliasing.

Arrows

 * Arrows that hit doors can float if the door changes its state.
 * They also appear to collide with fences, portals, and sugar cane. Arrowsugarcane.pngArrowportal.png
 * Arrows that have not hit a mob become unobtainable if you die or save and quit then begin playing before retrieving them.

Beds

 * Sneaking does not prevent you from falling off beds, however the player can't walk directly on them as one would stairs.
 * While sleeping, particles (torches, furnaces, etc.) do not "adjust" to face you, some of them may look flat or even be invisible.
 * Sneaking while sleeping can produce some interesting and varying results, from not being able to see limbs to being able to see yourself and toggle between sneaking and not sneaking.
 * If placing a bed on an outside facing one block thick wall, Mobs can sometimes spawn on or near the bed with you sleeping in it. This causes you to wake up during the night in danger of being killed by a hostile mob.
 * If you try to activate a bed you are standing on it will not work giving the error message "You can only sleep at night".
 * If you try to activate a bed when you are too far away it will not work giving the error message "You can only sleep at night".
 * Beds placed in fully enclosed (on both sides and with only one space above) areas can cause you to wake up inside a wall, killing you and potentially destroying your items.
 * Beds cannot be placed on snow.

Boats

 * Boats will collide with a snow layer as if it is a full block when placed on land.
 * If you manage to stand on your boat while it is under water, the boat will be unable to move. The boat will still retain horizontal movement, though, and will often slide out from underneath you.
 * If you go under a water stream your boat will accelerate and rise upwards. This is an error in the programming of how boats float.
 * If you save and reload while in a boat, you will no longer be in the boat.
 * You can, although slowly, move in your boat on land.
 * Pressing F5 whilst in a boat will show your leg/foot armor protruding from the bottom of the boat, even though your character is sitting. The leg armor will also fail to properly adjust to still be around the player's legs and will still be going straight down as if the player was standing still.
 * If you place a boat on the ground and drop sand onto it, the sand will repeat the falling animation on the top of the boat and you will be able to pass through it. Reloading the world will properly place the sand, but the boat may be dark as if it's in an area with no light.
 * Exiting a boat will make the player to fall through it. This could be fixed by implementing code that would place the player one block higher than the boat when it's exited.

Cactus

 * Cactus also has a South/West rule for applying damage. Placing a block above a single cactus piece prevents you from stepping on the cactus and prevents you from taking damage by pushing against the south or west sides of the cactus. The north and east sides of the cactus can still hurt you.
 * If there is snow, fire, water, or lava on a block, then a cactus can be placed on top of that block violating the usual rules for placing cactus. When the cactus grows it will recognize that it is improperly planted and uproot itself leaving two loose cactus blocks.
 * Cacti cannot be placed next to a portal.

Chests

 * A chest may always be placed on top of a block that has snow, fire, water, or lava on it allowing you to create triple (or larger) chests. Naturally the interface for these over-sized chests is buggy (as shown here).

Dispensers

 * Unlike chests, when a dispenser is destroyed, the items inside are gone forever. Notch stated that this is a bug on Twitter.

Doors

 * If you place a door next to a Cactus it will break and drop them both, but the door will drop two doors instead of one as shown Here. This can be reproduced indefinitely.
 * If a door is placed level with the cactus it will break the cactus and the bottom part of the door, leaving a un-collectible but breakable window.
 * 'Double doors' do not open simultaneously as one might expect them to when activated with redstone.

Fences

 * Occasionally placed fences will become invisible under certain conditions: Divide a chunk up into 16-block-high segments, for each of these segments that does NOT contain a block, any fences within will be invisible.

Fire

 * Fire has a South/West rule for applying damage. Placing a block directly above a fire prevents you from stepping into the fire and also makes it impossible to damage yourself by pressing against the block from the south or west sides. The north and east sides of the fire can still hurt you.
 * It is possible to have "Invisible Fire", fire that is dark and unlit.
 * A forest fire can cause strange patches of light to be left after all the fire has burnt out.

Furnaces

 * When destroying a Furnace, unlike Chests, anything inside the Furnace will be permanently destroyed.
 * If you access a furnace and press the jump key, sneak key or a movement key, your character will act as though that key is still being held even after exiting the furnace's interface. This can be fixed by pressing the same key after leaving the furnace's interface.
 * Furnaces emit light even if its face side is blocked. This is because the block itself emits the light, and it could be fixed by making the block in front of it emit light instead.

Glass

 * Glass placed in the same block as an item entity will not displace said item.

Grass

 * Grass does not grow under signs nor fences.

Gravel or Sand

 * Gravel or sand will not fall down if a torch is placed between the time a block underneath is destroyed and before the sand/gravel begins to fall. Example
 * Gravel or sand will accumulate into resources if a torch is place between the time a block underneath is destroyed and during the time the sand/gravel is falling to fill in the spot. Example
 * Gravel or sand will not fall down if snow is underneath it.
 * If you break a block below gravel or sand and are walking into gravel or sand, you will literally walk into the gravel or sand.
 * If you allow sand or gravel to fall on you, after moving around it is possible to be in such a position that you will not suffocate and you will be able to see through the sand or gravel and any blocks connected to the sand or gravel. This can reveal caverns.
 * If you place a sand or gravel block then quit the game before it starts falling, upon reload, it will float. If a nearby block updates, it will fall.
 * When sand or gravel is generated above a cave (or any opening), it will float until a space by it is modified in any way.

Lava
Example
 * Sometimes lava won't cause damage.
 * If the player moves into a corner to their southwest of which lava is on the other side, the player will be damaged(see South/West rule). This same bug can also incinerate items and other entities.

N  =^= W +== E  ++= S = is a block + is lava ^ is the player

Levers

 * Levers can be placed on the bottom of a block, as long as there is an open space, and a block horizontal to the open space. The lever will act as if placed on the horizontal block, but looks glitched, as shown [[Media:Brokenlever.png|here]].
 * Placing a lever on snow will produce a similar effect.

Minecarts

 * When spawning mine carts on a small track, they will gain momentum from colliding with each other.
 * Because of this, it is possible to gain neverending speed for a mine cart. This could be used to travel fairly quickly along far distances.
 * Riding a minecart at the top of the map makes the player invisible until you leave the cart or ride downwards.
 * Sometimes moving minecarts disappear completely.
 * Riding a minecart into a Nether portal causes the game to crash and kills the player.
 * Removing a minecart while riding in it will cause the player to go through the ground.
 * Minecarts can go off tracks or crash through the ground if their momentum is too high.
 * Placing a minecart behind a wall of lava or water and right clicking the minecart behind the lava/water makes the player to enter the minecart without touching the lava/water. This trick can be used as a "teleport" or a secret entrance.
 * When exiting a minecart, if there is only a single block free above the track, the player will take some damage.
 * If you start sneaking right after destroying a minecart, you may crash and get buried, but there is also a chance you will get multiple minecart drops.
 * Placing a detector rail adjacent to a normal minecart rail crashes the game.

Mobs

 * If a mob is riding a minecart and 2 or more mine carts get stuck in each other, after destroying or moving the carts away from the other carts the mobs will be invisible.
 * When up close to a Zombie Pigman, the inventory GUI will become much brighter. This could be interpreted as a "hint" towards future trading/interaction with some mobs.
 * If you are above a Ghast's height and are standing still, Ghasts will shoot fireballs over your head, without damaging you.
 * Ghasts will shoot at the camera in 3rd person view.
 * Squids can spawn in unintended locations, such as from cavern springs or even in The Nether(if water is hacked in). This is more common in multiplayer.
 * Mobs can move briefly before map data is loaded when signing out and loading the world, usually resulting in the mobs getting stuck.
 * In The Nether, Ghasts spawn on peaceful, but they would not to do anything. A ghast will disappear soon after appearing.
 * Tamed Wolves will attack you if you shoot yourself with an arrow. This can be achieved by looking straight up, shooting an arrow, and moving forward a small bit to compensate for a small amount of curve.
 * If a wolf is tamed when it's attacking an another mob, it may still attack it when on sitting animation.

Paintings

 * Paintings have no player or object collision(players, mobs, and entities can pass through them, and non-solid blocks can share the same position a multi-pane painting is in).
 * Paintings can be placed inside snow.

Portals

 * Placing a boat in the portal and entering it will cause the game to crash.
 * Similarly, riding a minecart or a pig into a Nether portal will cause the game to crash.
 * Being killed in the Nether will cause a portal to be generated near your relative location on Earth, as though you had teleported back from the location at which you died normally.Can someone confirm this?
 * Dying while in the Nether will also ignore a changed spawn point (via sleeping).
 * Opening the inventory then crafting while in a portal will destroy the item you are crafting and make the loading screen text turn gray, will add an identically gray "shadow" beneath the text, and will prevent the loading bar from filling. Everything will load as normal, though.
 * If the game is closed while entering The Nether, you will be sent to your spawn point on earth without held items, as if you were killed. However, it ignores a when the player's spawnpoint is changed via sleeping.

Sapling

 * If snow, fire, water, or lava are over a block, a sapling may be placed on that block even if it is not a dirt block. After a short time the sapling will recognize that it is illegally planted and uproot itself.
 * If a sapling grows into a tree next to a wall that would not to let leaves grow over it, the leaves will grow through the wall.

Sign

 * Placing a sign on top of a block at the maximum height removes the item from your inventory without creating a sign.

Sugar Cane



 * If a block is covered in snow, fire, water, or lava, sugar cane can be placed on that block violating the usual placement rules for sugar cane. When the sugar cane grows it will recognize that it is illegally planted and uproot itself leaving two loose sugar cane blocks.
 * Bugs in the terrain generation code can cause Sugar Cane to float.

Snow

 * As of the Halloween Update (Alpha 1.2.0), snow will not fall, meaning that once it's destroyed, it will not come back(falling snow will return in Beta 1.5, however).
 * The snow falling animation is absent, but if you have chunks from a world that was originally a snow world (pre-biomes) than snow will still accumulate on those tiles even though there is no longer any snow fall animation.
 * Utilizing snow, one can place saplings, cacti, and sugarcane on any block. However, the cacti and sugarcane will break when they first grow, and the sapling will uproot itself after a while.
 * In snow biomes, water and lava lakes can generate below the snow and leave some of the snow floating.
 * Beds cannot be placed on snow.

Stairs

 * Stairs let light pass through.
 * Stairs, along with fences, can sometimes become invisible. Water may be the cause of the bug.

Slabs

 * When firing arrows at the opposite corner of the slab, your arrows may clip through and hit the block behind it.
 * Wooden slabs can currently only be properly collected with a pickaxe instead of an axe. This may be caused because all 4 slabs use the same data value.
 * Different types of slabs cannot be placed together.
 * When walking with 50-100% of your body over a slab, whilst being at the high of another block, the walking sound effect for the slab type will play, rather than the one which you are actually on.



Water

 * It is possible for multiple water currents to crash against each other and create an inescapable rip-tide. Not only will this rip tide hold you in one place, it will also throw you from a boat if you are sailing it.
 * Under certain circumstances, underwater players can breathe, and see through the water. An example is shown here.
 * Like lava, when water is touching the same corner as you it has a possibility of colliding with you, allowing you to float upwards.
 * Numerous strange objects will prevent the flow of water such as signs, sugar cane, doors, fences and half-blocks.
 * Water sometimes doesn't flow into newly generated areas.

Workbench

 * If you access a workbench and press the jump key, sneak key or a movement key, your character will act as though that key is still being held even after exiting the workbench's interface. This can be fixed by pressing the same key after leaving the workbench's interface.

Mac OSX

 * On some Mac OS X Systems, the World Select screen will not appear at all, making the game unplayable on those Mac systems.
 * In other cases, the Mojang AB logo will appear green and the title screen and the game in dark areas will appear red.
 * In dark areas some sides of tile blocks will not render making a see through cave and grass and trees in daylight will appear purple, anything in darkness will also not render properly. The sound and music will also be weird. This has only been proved with non-Intel chip Mac.
 * on some Mac OS X systems, when the player is done and ( X'es out of the window ) the computer will take HOURS to close, the mouse will be able to move, but the windows and anything else will not be available until it closes. And when it does, the top bar on the screen will become black, and hard to see, so, either way, you will have to shut down, or keep the window open forever.

Rain

 * During rain, rain can fall through glass and possibly other transparent blocks

General

 * When entering a server, the player may fall into an endless void and eventually disconnect. This is caused by a large amount of server lag and there is no effective workaround.
 * If a player has respawned, he can place blocks on the block he is currently standing on. This will not decrease the block count in his inventory, effectively cloning blocks. This bug only occurs with non-opped players.
 * Full server world saves do not reliably save the entire world. This can be proven on a single person private server with whitelisting enabled when attempting to do a full server save via:
 * 1) Disabling incremental level saving with 'save-off' on on Minecraft console.
 * 2) Forcing a full save to disk with 'save-all' on on Minecraft console.
 * 3) Archiving and saving the archived world with 'tar -xvzf save.tg world' on shell in secondary system console.
 * 4) Turning back on incremental level saving by doing a 'save-on' on Minecraft console.
 * Enormous, cuboid areas (usually one or two chunks) of unfinished map open in random places. Caves, minerals, water, magma and mobs are visible when a Player peers into one of these voids. These areas cannot be walked on, causing a "[user] moved wrongly!" message to appear in the Server; however, players can ride minecarts through them with relative ease. If the void appears in the middle of water, Players can "float" over the void using a boat. Placing a torch next to one of these "void holes", dumping lava or water nearby, or disconnecting and reconnecting to the server will make the land inside of them reappear. These have become significantly less common since the 1.3 update.
 * When you sneak (in third person), your character's feet are "in" the ground.

Arrows

 * Arrows shot onto a wall cause the arrow to create a flickering wobbling repeat of the arrows movement. This happens mainly on glass.
 * Fired arrows will appear to come out backwards at first, then continue on a regular trajectory.
 * Many arrows fired appear glitched and stay in mid air, going back and forth, even if they hit a mob or another player.

Beds

 * Sometimes when a player is sleeping and other player walks on that sleeping player the sleeping player will fall through the bed and the floor.
 * Trying to get into bed while sneaking disconnects the player(Illegal Stance).
 * If someone uses their bed in SMP, other players may get disconnected(Unrecognizable Packet ID: 17).

Boats

 * Boats greatly increase server lag. Attempting to move in the boat invokes noticeable delays.
 * If you ride a boat over a chunk of water which did not load properly ( ex. the water is really there, but you can't see it and can see through the whole world ), the boat disappears.
 * When a Boat gets damaged (by a player), it does not shake.

Chests

 * Destroying a chest will spill its contents and every item in the chest will be duplicated. Only half of the items visible to the player can be picked up, so no items are gained nor lost in the process.
 * The disappearing seems to be caused by the same bug just in the opposite way. Instead of the server lagging behind the client and telling it that the item is still there the server will erroneously delete.

Dispensers

 * When a dispenser dispenses an item, there is no smoke puff and no sound is heard.

Doors

 * When attempting to stack doors, one will be deleted.
 * If you open and close a wooden door repetitively while jumping, you can catch yourself in the door and jump again. This can be used to reach places 1 block higher or to get on top of wooden doors overall.

Fences

 * Standing on top of fence posts triggers the anti-flying protection.

Fishing

 * Sometimes when fishing you won't get a fish when you right click to catch the fish. This is caused by latency issues.

Furnaces

 * Furnaces rotate when they are used. This seems to be influenced by the blocks placed around them.
 * Furnaces can stop smelting items during a severe lag.

Jukeboxes

 * The records duplicate if you eject the record before the song has finished. Only one record can be picked up however, the rest are client-side duplicates.

Ladders

 * Since the 1.4 update, if you log out on a ladder, upon relogging you will be teleported to the top of the ladder.

Minecarts

 * Engines consume coal but do not move under their own power, making them useless.
 * Minecarts that pass over pressure plates will sometimes not activate a redstone current, even though a "click" noise is heard.
 * A player will pass through the minecart, but when the player is passing through it counts as "pushing" the minecart.
 * Empty/Storage Minecarts start to behave strangely when they are too far away from the Player. They disappear completely, disappear until Players disconnect and reconnect, or suddenly stop on tracks despite having sufficient momentum.
 * Minecarts load before terrain sometimes causing them to be invisible until they are interacted with. Large transit systems and door water boosters are examples of when the issue occurs. (log out/in to reproduce).

Mobs, Hostile

 * Shooting animations (Ghast fireballs/opening mouth and eyes, Skeleton arrows) are not always visible.
 * Ghasts' fireballs occasionally do not explode, only lighting a small area on fire.
 * Sometimes mobs freeze in animation and can not be hit. They disappear after about 2 minutes.
 * Some users are reporting mobs will be invisible, but can still attack you. On update 11/24/2010 SMP health update post Notch explained that to see invisible mobs, players must set their difficulty to the server side difficulty or higher.
 * Upon death, all monsters around you will be frozen when you come back. you cannot kill them, or attack them, and they cannot attack you. You can however push them, touch them, and they will still make noises. Skeletons, and Zombies will catch fire, and it will flicker and not cause damage.
 * During severe lag, you can be killed by mobs or players without ever seeing them.
 * Hitting a mob a few times in a row before the mob receives the damage will cause the mob to receive the damage from only one hit, but the force of all of them, making them fly up and backwards a considerable distance.
 * Every mob will freeze, when the server is timed out.
 * When a mob dies, its corpse is still visible.
 * When slimes divide in SMP they often create many fake duplicates which are invulnerable, and inflict no damage. Disconnecting/Reconnecting causes these fake slimes to disappear. This bug does not occur in Survival (SP) mode.
 * When slimes divide, they can create larger slimes.
 * Slimes cannot be pushed.
 * Small slimes sometimes show a jumping animation that looks like rushing through the ground.
 * Mobs cannot be hit from underneath.

Mobs, Passive

 * Squids can fly upwards.
 * If a monster spawner is exposed to sunlight, the sprite shown inside the spawner block becomes a pig, and the spawner will spawn pigs on any nearby grass block. These pigs are glitched client-side pigs and cannot be interacted with.
 * Additionally, if torches are placed around the spawner, it will cease to spawn pigs. Also, the sprites inside the monster spawners may show always as pigs regardless of sunlight.

Paintings

 * When copying an SSP world onto an SMP server, paintings are removed in the transition.

Saddles

 * Saddles will return to the player's inventory if the pig de-spawns. This obviously demonstrates that saddles on pigs are not fully server-side.

Sand and Snow

 * Sand will not fall down if snow is underneath it.

Pumpkins

 * Pumpkins used as a helmet now display the carved face on the back instead of the front. Users wearing pumpkin helmets will still be able to see through the cut-outs but will appear in server to have a smooth pumpkin face and a Jack'o'Lantern grimace on the back of their head

Redstone Repeater

 * The particle colors for Delay/repeater blocks are the same of pumpkins.

TNT

 * TNT lit by one user cannot be seen by another, though its effects can.
 * Occasionally, a TNT block meant to drop will enter a repeating fall animation (but not actually fall) when lit. When the TNT finally explodes, it will explode at the position it was placed.
 * Occasionally, a TNT block can also explode twice, but this will not damage the environment twice.
 * If a lot of TNT is lit, some TNT may explode but leave behind an image of an exploding TNT block that is almost completely white, and will hover in mid-air. The ghost TNT will not disappear unless the player disconnects and reconnects.

Trees

 * Using bone meal to quick-grow trees will sometimes cause "floating" trees to grow with sapling still at the base. Removing the sapling or using more bone meal can cause the tree to grow into an enormous bundle of leaves with no log base. These leaves will now respawn immediately after being harvested. The only way to remove these glitched leaf blocks is to burn each block individually (fire will not spread for some reason) OR build an umbrella above it, the shadow seems to instantly vanquish the leaves. - This glitch is vastly more common when quick-growing trees under another trees foliage. Again, disconnecting and reconnecting will reset these "ghost trees."
 * Planting a sapling and waiting a bit will sometimes yield tree trunks with weird distributions of leaves, and in some cases, no leaves at all. Trees can also grow but be invisible, making it impossible to traverse a tree farm after a while. Rejoining the server appears to make invisible trees visible again and fire will swiftly cause phantom foliage to be made manifest. You can also place a torch to make the phantom foliage appear.
 * Leaves from trees will overwrite some blocks, such as a nearby fence.
 * Placing a torch on Leaves does not make the 'pop' sound for the item being placed.

Water

 * You may find yourself drowning despite having a full breath meter. This is caused by the client registering that the player has gotten air, but the server registers that the player is still underwater. This causes the non-synced breath meter.