Every source I've been able to locate suggests that the delay in ticks feature added to command blocks is meant to be a delay in redstone ticks (1/10th of a second), but in reality the delay is in game ticks (1/20th of a second).
To reproduce, place an impulse block with
tell @a start
follow with a chain with a delay in ticks value of 300
tell @a end
Use a stopwatch to record the time between the start and end messages. You'll find that the time elapsed is 15 seconds, when it should be 30.
Comments 4
Only if it actually is working as intended. I'm not asking for a feature, I'm pointing out that an existing feature does not work the way the patch notes say it is supposed to.
Thank you for your report!
However, this issue has been temporarily resolved as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
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.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
This is a feature, should be closed as working as intended.