Crashing on connecting due to holding a bugged item

This article relates to a client crash that is caused by holding a bugged item in the player's hand. The client will crash as soon as the item is either placed in the active slot on the hotbar, or the item is first placed in the hotbar and then selected. When the client tries to render the item in the player's hand, it fails and crashes. When the player tries to re-join, the server remembers which hotbar slot was active and so the client will crash upon joining. The specific cause of the crash can vary so the intital lines of a stack trace in a crash report cannot be relied upon to identify the problem. However, the following lines (or similar) may appear near the top of the stack trace:

at net.minecraft.entity.player.EntityPlayer.func_70620_b(
at net.minecraft.client.entity.EntityPlayerSP.localGetItemIcon(
at api.player.client.ClientPlayerAPI.getItemIcon(
at net.minecraft.client.entity.EntityPlayerSP.func_70620_b(
at net.minecraft.client.renderer.ItemRenderer.renderItem(
at net.minecraft.client.renderer.ItemRenderer.func_78440_a(

Fix 1:

The game will save current item slot and inventory into your player's save file located in:


You can find out a player's UUID at this website:

This file is in the NBT format and can be edited using the NBTExplorer tool:

You can remove the inventory item from this file as follows:

  • Download and run NBTExplorer
  • Download the .dat from your server: FTP Access to Download and Upload files
  • Rename the .dat on your server to .dat.backup (in case you make a mistake)
  • Open the .dat file: Open>File...
  • Scroll down and look for the 'SelectedItemSlot' entry: Make a note of the value
  • Now find the 'Inventory' node and expand it
  • Expand each node in 'Inventory' until you find the one with a 'Slot' value that matches the 'SelectedItemSlot'
  • Highlight that node by left clicking it. Delete it by pressing the delete key or clicking the red 'X' icon
  • Save the changes: Click the save icon
  • Close NBTExplorer
  • Upload the .dat back to the server

Fix 2:

A quick option is to delete or rename the .dat file. This will wipe that player's progress and inventory.

  • 10 Users Found This Useful

Was this answer helpful?

 Print this Article

Also Read

"Internal Exception: java.lang.IlegalArgumentException: Parameter 'directory' is not a directory"

When you connect to a server you will be immediately disconnected and get the following error:...

"Failed to Login: Bad Login" error

Description When you connect to a Minecraft Server, your Minecraft client sends data about your...

'Outdated Server' when trying to connect

What to do if a new version of Minecraft is available and the players on your server have updated...

How To Connect to a MC:PE (Minecraft : Pocket Edition) Server

This article describes how to connect to a remote server using Minecraft : Pocket Edition. You...

Failed to connect to the server Outdated Server!

The "Failed to connect to the server Outdated Server!" message means your Minecraft client...