Tyron

No, it's not related to the inventory. The problem already appears in the main menu, before even getting into the game world. Plus that issue talks about mouse moving issues and not mouse clicking O_O

Why did you resolve the issue? It's still there!

I'm currently trying to fix up the furnace minecart for my mod Vintagecraft - I can confirm from simple tests that Thinkofdeaths solution fixes the problem of coal powered carts slowing down after going through a curve.

In that regard, thanks for the fix Thinkofdeath!

Did my previous comment just got deleted without any notice?

Anyhow, here a more informative comment about this issue: This one is in my opinion the most annoying bug in 1.7.x and causes unecessary lag, please fix this soon!
The issue is not just temporary, e.g. I've been having an arrow stuck in the ground in front of my house for the last 2 months now. I've restarted my server a couple of times inbetween so that did not fix it. (I'm using 1.7.4, was it perhaps fixed in 1.7.4 but broken arrows from 1.7.2 still persist or so?)

So I checked with my world save with some code. Just around my house, I'm finding over a hundred unique arrows stuck somewhere. I don't know why but all relevant arrow variables related to despawning are Zero, expect its coordinates. When I shoot new arrows, these seems to be ok though. I hope this can be of some help to someone.

One example:

found arrow with entityid 1493 (total found: 116)
motion: -0.0/0.0
arrowshake: 0
ticks in air 0
inground: 0
xtile: 56
ytile: 41
ztile: -375
life: 0
intile: 0
indata: 0

Variables printed with this (badly written) forgecode ('started' is set at FMLServerStartedEvent):

Hashtable<Integer, EntityArrow>arrows = new Hashtable<Integer, EntityArrow>();
    
    @SubscribeEvent 
    public void onEntityUpdate(EntityEvent event) {
    	if (!started) return;
    	
    	if (event.entity instanceof EntityArrow) {
    		EntityArrow arrow = (EntityArrow)event.entity;
    		
    		if ((!arrows.containsKey(arrow.getEntityId()) && arrow.posX != 0)) {
    			System.out.println("found arrow with entityid " + arrow.getEntityId() + " (total found: " + arrows.size() + ")");
	    		
    			arrows.put(arrow.getEntityId(), arrow);
    			
    			System.out.println("motion: " + arrow.motionX + "/" + arrow.motionZ);
    			System.out.println("arrowshake: " + arrow.arrowShake);	
                  
    			try {
    				Field field = EntityArrow.class.getDeclaredField("ticksInAir");
    				field.setAccessible(true);
        	    	int ticksinair = (Integer)field.get(arrow);
        	    	System.out.println("ticks in air " + ticksinair);
    			} catch (Exception e) {
    				System.out.println(e.getMessage());
    			}
    			
	    		NBTTagCompound nbttagcompound = new NBTTagCompound();
	            arrow.writeEntityToNBT(nbttagcompound);
	            
	            System.out.println("inground: " + nbttagcompound.getByte("inGround"));
	            System.out.println("xtile: " + nbttagcompound.getShort("xTile"));
	            System.out.println("ytile: " + nbttagcompound.getShort("yTile"));
	            System.out.println("ztile: " + nbttagcompound.getShort("zTile"));
	            
	            System.out.println("life: " + nbttagcompound.getShort("life"));
	            System.out.println("intile: " + nbttagcompound.getByte("inTile"));
	            System.out.println("indata: " + nbttagcompound.getByte("inData"));
    		}
    	}
    }

[Edit:]
I just broke the block beneath on of the never despawning arrows and it despawned! So looks pretty surely to me like 1.7.2 arrows saved to the world don't despawn in 1.7.4. - perhaps some missing nbt data?

That would be cool if this was fixed, then we could build a semi-automatic enchanted bow farm with skeleton spawners 😃

Very annoying bug indeed 😞
Please fix it Mojang.

That is a bad glitch in my opinion. You can forever repair your diamond tools at almost no cost. Enchanting damaged tools should at least retain the damage value.

That actually looks awesome and realistic for jungle biomes, in my humble opinion. I'd rather allow mushrooms to be placed on leaves than removing this feature. But that's such a minor thing that I would close this issue so mojang can concentrate on more relevant issues.

The fix is quite simple I think. The spawning Algo currently checks if the the block to spawn on is translucent, but instead it should check if the block has a bounding box where entities collide on.

Indeed. Not a bug in my eyes either.

^ Above comment. You can save your world e.g. the following way

• download NBTEdit

• open your player.dat

• increase ypos by 1 or 2 and save

> The achievements/tracking are just numbers. You can totally play without them. No gameplay elements depend on them.

The Achievements/Tracking IS a gameplay element. If this is not going to be fixed, Mojang might as well remove/disable the Achievements rather than people getting their work (trying to get all achievements) ruined after every update.