mojira.dev
MC-271230

Block Breaking animation starts too early

In recent versions the first frame of the block breaking animations appears the moment that block is touched, no matter how durable, instead of appearing after the block is ~7% broken like it used to before.

Environment

Ubuntu 22 Openjdk21

Linked issues

Attachments

Comments 4

Thank you for your report!
However, this issue is Working as Intended.

The report you have submitted is working as intended: this was previously a bug that has been fixed in 1.20, see MC-35078.

Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.

Full Version History – Snapshot Version History – Feature Requests and Suggestions

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

I dont think it was fixed correctly. The problem was that the animation wasnt divided into enough frames. This just moved the bug to the beginning of the animation. so instead of missing the last its now missing the first where the block isnt yet damaged

That's not true. The first frame is destroy_stage_0, which is now shown immediately. There's no frame before that.

Before the fix of MC-35078, destroy_stage_9 was never shown; this was a simple off-by-one error.

This is the intended behaviour by the developers; if you think otherwise, feel free to provide feedback on The Minecraft Feedback Site or the Minecraft Feedback Discord server.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

But why would it be shown immediately if the animation shows damage to the block? there should be an extra frame for destroy_stage_9 rather than offsetting the whole thing. Before stage 9 was shown at 100% broken instead of ~91% so there was no chance to see it. Now stage 0 shows at 0% instead of ~8%. You can see it because time moves forwards but it shows no progress. The same amount of information is displayed.

migrated

(Unassigned)

Unconfirmed

1.20.5

Retrieved