The bug
If you start breaking a block in survival mode and switch to spectator mode, that block gains the ability to show the breaking animation.
How to reproduce
Go into survival mode
Start breaking a block, but do not finish
Let go of left click and switch to spectator mode
Attempt to break the same block
→ Notice the breaking animation and particles
Note: Blocks cannot be broken in this way, but in singleplayer you can see the animation. Not sure if others in SMP can see these particles.
Code analysis
Code analysis by @unknown can be found in this comment.
Related issues
is duplicated by
MC-55233
Mining a block in Creative, then changing to Spectator creates breaking particles
MC-70230
players in gamemode 2 can still have block-breaking animation
MC-206275
Spectator can produce mine particles
MC-215163
Spectators can produce client-side breaking particles without the animation
MC-215839
Spectators can create break particles
MC-225867
Mining block animation repeats when you change into spectator mode while breaking block
MC-228158
Spectators can continue breaking blocks
MC-236424
Breaking blocks is possible in spectator mode, but you can't destroy them.
MC-277231
creaking heart can be damaged by spectator players
relates to
Attachments
Comments
migrated
migrated
Is this still a concern in the current Minecraft version 14w11b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. - bot
migrated
Confirmed for 14w18b.
migrated
Confirmed for 14w19a.
migrated
Confirmed for 14w20a and b.
marcono1234
Confirmed for 14w21b
shufboyardee
Confirmed for 14w25b
shufboyardee
and for 26b.
shufboyardee
and 28b.. and 29b.. and 30c.. and 32a
migrated
By the way, thank you for keeping up on this so well, I haven't been able to keep on top of it lately. As far as I know, still a problem, client-side, although not an urgent one. It just may have other implications that i am unaware of, such as the client being unaware of restrictions accidentally.
shufboyardee
No problem! It sort of goes hand-in-hand with my bug MC-55233, so i always check both.
Confirmed for 14w33a.
Sonicwave
Confirmed for 1.8 and 1.8.1-pre2.
shufboyardee
and 1.8.1-pre4, and 1.8.2-pre4.
migrated
Also occurs in multiplayer, but other player can't see the animation.
shufboyardee
And 1.8.3, and 1.8.6 ... and 15w31b
migrated
Thanks for keeping tabs on this issue, as I've not been able to check on it for a while. An interesting little bug, hope it gets noticed.
shufboyardee
No problem at all.
Still in 15w33b.
migrated
When I found the bug, I did not require holding left click between gamemodes, simply having partially broken the block before the gamemode switch was enough. Is this no longer the case?
shufboyardee
Eric: It's still the case – if I understand you correctly: I always test for this bug by partially breaking a block, releasing, then switching gamemodes.
Still affects 15w35b.
migrated
Alright, then the edit was incorrect? I'll switch it back until notified otherwise.
shufboyardee
Still in 36c – Oh I didn't notice the edit! It looks good now anyway.
And still in 47a.
kumasasa
@@unknown: Please write "15w47a" instead of "47a" when mentioning affected versions, otherwise that may slip through some filters.
shufboyardee
Sure, thanks, I didn't know about such things. Confirmed in 15w50a.
migrated
Is it also confirmed for 1.8.9? I'm forgetting. Thank you once again for keeping me updated!
shufboyardee
You're welcome! Confirmed for 1.8.9, and snapshots through 16w04a.
migrated
If you want the bot to do it automatically, I think it requires a new comment. But I'm getting your edits just fine, and I like updating it, so either way works. Just FYI 🙂
migrated
@unknown no bots update the affected versions, mod do, and indeed a new comment would be much more noticable then a edited comment
migrated
Alright, thank you for the clarification. I just assumed "Filter" meant to catch update notifications, possibly for a bot. For some reason, I seem to remember a mod bot updating it for me, but the logs appear to show that I remember incorrectly there as well.
migrated
We have a bot to remove future versions from affected versions. The reason we want the whole snapshot version spelled out is so it's easier to parse quickly. The reason we want a new comment is so it shows up in the activity feed and not just in email inboxes.
migrated
Alright, thank you for clearing that up.
shufboyardee
Oh, I can do new comments if that's better. Confirmed in 16w05a.
shufboyardee
Affects 16w05b.
shufboyardee
Affects 16w06a and 16w07a.
shufboyardee
Affects 16w07b.
shufboyardee
Affects 1.9 Pre-release 1.
SunCat
Still in 1.9
shufboyardee
Affects 1.9.1 Pre-release 1.
shufboyardee
Please put a link in the description to Marcono1234's code analysis:
https://bugs.mojang.com/browse/MC-55233?focusedCommentId=301528&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-301528
Also, affects 1.9.4.
kumasasa
Where is the difference of this and MC-55233 (except the other starts with creative mode) ?
shufboyardee
Affects 16w20a. The only differences are the starting mode, and the way the breaking animation / particles look.
migrated
Confirmed for 1.13.1.
pulpetti
Affects 1.16.1 and 20w29a
Avoma
Can confirm in 20w48a.
Avoma
Can confirm in 20w51a.
Avoma
Can confirm in 21w03a.
Avoma
Can confirm in 21w05b.
Avoma
Can confirm in 21w06a.
Avoma
Can confirm in 21w11a.
Avoma
Can confirm in 21w17a.
Avoma
Can confirm in 1.17.1.
shufboyardee
Can confirm in 21w44a.
Avoma
Can confirm in 1.18.1.
Avoma
Can confirm in 1.18.2.
Avoma
Can confirm in 1.19.
Avoma
Can confirm in 1.19.2.
migrated
Can confirm in 1.19.3.
shufboyardee
can confirm in 1.20 Pre-release 1
B4dAtMC
this bug still exists in the newest snapshot, 25w04a