Summary:
Running "/tick freeze" then "/tick sprint N" will advance the game by N+1 ticks.
Steps to reproduce:
Build a tall scaffolding pillar.
Run "/tick freeze".
Break the bottom scaffolding.
Run "/tick sprint N".
Expected result:
N scaffolding break.
Observed result:
N+1 scaffolding break.
Impact:
In case it’s not clear that "/tick sprint" should be accurate to a single tick, I’d like to point out that this is a maddening bug when trying to measure redstone timing. I’d also argue that accepting a tick-precise sprint duration is a reason for actual behavior to also be tick-precise.
Tested in:
1.20.4 and snapshot 24w05b
Attachments
Comments 5
Can confirm in 24w09a, using a different methodology. I put down a repeating command block to output '/say tick' every game tick, and then sprinted the game. This was done to avoid any possible block behavior with scaffolding.
Thank you for your report!
After consideration, the issue is being closed as Working as Intended.
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 – The official Minecraft feedback site
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Please attach a video of this happening.