In the video shown, i was attempting to break a block with both soul speed 3 on my boots and a speed 2 beacon in range. I was targeting the already broken block, but the highlight was appearing on a different, unbroken block. When attempting to continuously break the block, it allowed me to as if I was targeting the highlighted block, but behaved as if i was targeting the empty space instead.
NOTE: I have not tested if this effect is directional.
Steps to reproduce:
1) equip boots with soul speed 3
2) give yourself the Speed 2 status effect.
3) attempt to break a block
Expected outcome:
The targeted block is highlighted and broken
Observed outcome:
A differently block is highlighted, but the game attempts to break the space that is being targeted.
Attachments
Comments 5
I’ve seen it happen here and there, but I Haven’t tried to intentionally reproduce it in 1.17. I’ll check and let you know.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Interesting. I could not reproduce so far, unfortunately... Is this still an issue in the latest version?