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
Seems it doesent happen anymore (I updated the Server to 1.4.4)
Ill test it a little longer, but thanx for trying!
L. Bergerot
added a comment - - edited Seems it doesent happen anymore (I updated the Server to 1.4.4)
Ill test it a little longer, but thanx for trying!
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.
Tom Lee
added a comment - 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.
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)
L. Bergerot
added a comment - 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)
Tom Lee
added a comment - Why is this a bug? This is intended behavior.
Unassigned
L. Bergerot
Votes:
0Vote for this issue
Watchers:
1Start watching this issue
Created:
Updated:
Resolved:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
Yeah, never happend anymore on 1.4.4! Thx