MC-2447Cannot break block behind gravel, sand, dirt with Efficiency V Diamond-Pickaxe
While diggin, you will not be able to break stone when there is 2-3Blocks of Dirt, Sand, Gravel in front of it. It seems that the Efficiency V Pickaxe digs too fast and then the stone can not be broken. (Same effect as braking stuff at Spawn)
Reproduce:
-Place 2-3Blocks of Dirt with a block of stone at the End.
-Digg it with Efficiency V Diamond Pickaxe
Environment
Linux Server
All kind of Clients
Created Issue:
Cannot break block behind gravel, sand, dirt with Efficiency V Diamond-Pickaxe
While diggin, you will not be able to break stone when there is 2-3Blocks of Dirt, Sand, Gravel in front of it. It seems that the Efficiency V Pickaxe digs too fast and then the stone can not be broken. (Same effect as braking stuff at Spawn)
Environment
Linux Server
All kind of Clients
- Unresolved
- Open
- Public
- Unconfirmed
- Efficiency Pickaxe Unbreakable
- 1.4.3
While diggin, you will not be able to break stone when there is 2-3Blocks of Dirt, Sand, Gravel in front of it. It seems that the Efficiency V Pickaxe digs too fast and then the stone can not be broken. (Same effect as braking stuff at Spawn)
Reproduce:
-Place 2-3Blocks of Dirt with a block of stone at the End.
-Digg it with Efficiency V Diamond Pickaxe
Why is this a bug? This is intended behavior.
Try it, and you will see what I mean. A pickaxe is ment to break blocks until the player stops/it breaks/it hits Bedrock or the player dies (however)
Again, I see no signs of it being an issue. Unless when I'm reproducing it, I'm doing it wrong.
Are you saying that if I use an Efficiency V pickaxe on the line (3 dirts, 1 stone) and starting from the dirt side, I should be wiping all blocks out, but instead, there's a glitchy stone block left behind in the spot where I just wiped out the stone block?
EDIT: I'm using Windows 7, duh. I can't reproduce it on my side. Sorry.
Seems it doesent happen anymore (I updated the Server to 1.4.4)
Ill test it a little longer, but thanx for trying!
Are you saying this is fixed?
Yeah, never happend anymore on 1.4.4! Thx