Block breaking is not canceled when losing focus of a block

Can't confirm in 1.8.3. Are you still experiencing the issue?

I'm still not experiencing this bug. Are you sure there aren't some other conditions causing it?

Can confirm for 1.8.6
Some other things I found:

• This bug only happens if you are only just able to reach the block when you start to break it - I found I had to be at least 4 1/3 blocks away from the block I was breaking.

• If you move back into this range between 4 1/3 blocks and the limit, you can continue to break the block.

• Once the glitch has happened, holding down left click while moving in and out of range will allow the block to be mined in stages provided the player does not mine any other block in that time. Left click does not have to be held down all the time, just when coming into range

The most pressing exploit of this is mining trees while jumping. When you jump, you are in block-breaking range of what is sometimes the topmost tree block and if you hold left click then occasionally after a handful of jumps you will partly mine the block. I assumed it was server lag when this happened to me but apparently not.

Confirmed. You must be at the extreme edge of the block-breaking range for this bug to occur. The easiest way to replicate this bug is to place a block 6 blocks above you, and jump at it while holding the mine button. The outstanding mining progress will reset itself after a few seconds if left alone.

Please don't fix. It's not so much a bug, as more a good feature. I've been using it since 1.8 came out, and it really helps with that last block I forgot in the ceiling. Make it a feature, don't call it a bug 🙂

You have got to be kidding. Just because the bug is slightly useful in some situations doesn't mean it should stay in the game. It's clearly not how mining is supposed to work.

Wow.. That came out way more aggressive than I hope you meant it.
I, and a lot of others, think this bug is a great thing in the game.
It helps with simple mining of that one last block, it resets after a few seconds, and is generally not in the way of anything.
If you don't want to use that "feature", fine. If you do: 1.8 ftw 🙂

PS: If you mine in real life (not that Minecraft should simulate real life), you have the same effect, so please.. I was actually a little disappointed at Minecraft the first time I played it, cause of the lack of that function. It seemed obvious that the block should be half-broken, so I could decide if I wanted to mine it all the way through, or if I thought I would lose it in lava etc. so I could leave it to regenerate.
Like obsidian.. just soo long to mine a block, and if you slip a little with the mouse: Start over again..

Sorry if that came out rather rude, I was just shocked that someone would want that.

If you were arguing that blocks should stay partly broken when you stop mining them, then I would agree with you. But you are arguing that blocks should stay partly broken when you stop mining them, as long as you are at the exact right distance from them. This makes no sense.

Though I agree that this bug can be very useful when mining that last tree block, ever since non instant mining was implemented in Minecraft, the block had to be focused on the whole time. This bug breaks one of the game's most fundamental rules, no part mining.

I see your points about the exact distance and about the fundamental rules of the game, so I put myself in a more neutral state towards this issue. Thanks for clearing stuff up for me 🙂
Man.. Did I just have a valid conversation with someone on the internet?

I know right

The description seems to be incorrect in 15w43c.
For me these are the steps to reproduce (unless this is a different ticket, since there are way to many on a seemingly slightly different issue):
-start mining a block
-move your mouse so that it does not focus on any block, but don't release the break button
-move your mouse on the block again and release the button when it is not yet broken
-the cracks should now go away but they actually don't
Maybe the description etc. should be updated?

Done.

Confirmed for 15w44a and 15w44b

Relates to MC-73786, MC-8472, MC-62124, MC-8472 & MC-19676.
Add these related issues to each other too, if they don't already have them. Also, add MC-54587 & MC-70359 to the related issues I just mentioned.

Please be reasonable. This is not related to MC-1. Let me know if you update your list.

Actually, why doesn't it? Because that's with Zombies and this is with players?

This bug came into existence way after MC-1 was fixed, they are only related in that they affect block cracks. I don't think it's helpful to list any remotely related issue as related.

@@unknown Ah, of course, I hadn't seen it was fixed.

@unknown: Updated the list. You could've just added the related issues that you actually thought was related 🙂

Done.

Confirmed for 15w45a

I found out a simpler way to reproduce (not that it isn't already simple). I added a GIF, breakfreeze.gif.

Update summary and description if you want.

@@unknown How did you do that?

@unknown: I hit in the air and then started mining the block. Should've been more clear.

@@unknown Ah, I see

Confirmed for 15w46a

Confirmed for 15w47a and 15w47c

Confirmed for 15w51b

Confirmed for 1.9-pre1 and 1.9-pre2

Still here up through 1.11.

Confirmed for 1.12 Pre-Release 5 (video title is inaccurate)

Confirmed in 17w43b

Confirmed for 1.12.2.

For more detailed info and videos see MC-125127

Confirmed for 1.13-pre5

Confirmed for 1.13.1.

Confirmed for 1.13.2, 1.14, 1.14.4, and snapshot 19w39a.

However, while click-off-drag-on-drag-off (i.e. this issue) creates cracks that can be furthered by the break-place-break-place action of instantly breakable blocks (i.e. MC-157404), the latter is irreproducible prior to version 1.14.4-pre6. It must be either these are related issues, or MC-157404 is a progression of this bug.

Good call. I was not aware that that part of the issue is only present in 1.14.4 and later. Thanks for your time testing that!

I've reopened MC-157404, it will be the ticket about that issue going forward.

Affects 1.15-pre1

i wrote about this too, glad im not the only one experiencing this issue

Still going in 1.15.2, continually seeing it when I mine piles of sand, and when I bonemeal-farm by holding bonemeal in my main hand and seeds in the off hand, hold the right click and left click when the crop is full. The dirt block below breaks pretty often. I have to compensate by putting obsidian behind the crop and pointing at just the right spot on the obsidian.

reproduced in 1.16-pre6

Affects 1.16-rc1

This could be intended to allow breaking of hard to reach blocks.

more than likely intended, iv had it happen on ps3 edition

Can confirm in 20w51a.

1.16.5 also

Can confirm in 21w03a.

Can confirm in 21w05b.

Can confirm in 21w06a.

Can confirm in 21w07a.

Can confirm in 21w11a.

Can confirm in 21w13a

Wait, this is in vannila too? i thought it only happened on hypixel

Can confirm in 21w18a

@unknown reports are only valid if they can be reproduced in a vanilla environment (without the use of mods, or occur whilst not play on a modified server).

Can confirm in 1.17.1.

this thing is still happening in 1.17, in my case i was afking in a sweeping edge killing chamber (a thing that puts minecarts in front of the player, who keeps hitting it and kills the mobs w/ sweeping 3), but i keep breaking the front dispenser, even hitting 1x per second w/ a sword

Can confirm in 21w44a.

Partly intentional. It makes it possible to break blocks that you can just reach when you jump. But I agree the code is not smart enough.

Can confirm in 1.18.

Can confirm in 1.18.1.

In 22w03a

Can confirm in 1.18.2 and 22w15a.

Can confirm in 1.19.

Can confirm in 1.19.3.

This also happens when you break down wood that's higher than the player range, this bug occurs when jumping and breaking

can confirm in 1.20 Pre-release 1.

This seems to now effect even non-instant mined blocks in 1.20. Break any block anywhere with any tool, and then place a block where you just broke one, and there will be a stage 1 breaking animation. This is super distracting and buggy-looking.

Сan confirm 23w44a.

Can confirm in 1.20.6 and 24w21b.

The main cause of this behavior is MC-255057 (continuing to destroy a block only cares if the block that was last targetted is the same as the current block, not if you were still destroying a block).

This was introduced in 14w29a (a 1.8 snapshot), which changed MultiPlayerGameMode.stopDestroyBlock from

public void resetBlockRemoving()
    {
        if (this.isHittingBlock)
        {
            this.netClientHandler.addToSendQueue(new C07PacketPlayerDigging(1, this.currentBlockX, this.currentBlockY, this.currentblockZ, -1));
        }

        this.isHittingBlock = false;
        this.curBlockDamageMP = 0.0F;
        this.mc.theWorld.destroyBlockInWorldPartially(this.mc.thePlayer.getEntityId(), this.currentBlockX, this.currentBlockY, this.currentblockZ, -1);
    }

to

public void resetBlockRemoving()
    {
        if (this.isHittingBlock)
        {
            this.netClientHandler.addToSendQueue(new C07PacketPlayerDigging(C07PacketPlayerDigging.Action.ABORT_DESTROY_BLOCK, this.currentBlock, EnumFacing.DOWN));
            this.isHittingBlock = false;
            this.curBlockDamageMP = 0.0F;
            this.mc.theWorld.sendBlockBreakProgress(this.mc.thePlayer.getEntityId(), this.currentBlock, -1);
        }
    }

i.e. prior to that version, if a block was no longer targetted, then the break progress would be reset to 0, making things mostly behave normally (though it still would fail to tell the server that it started breaking the block, and redstone ore wouldn't begin to glow in this case).

I'm not sure why this change was made. The only relevant issue fixed in 14w29a is MC-676, but I don't think this change was directly part of that fix. So perhaps it was an intentional change, but it wasn't included in the changelog and is implemented fairly awkwardly.