Steps to Reproduce:
1. Build something using commandblocks that need to run with "Always Active & Repeat"
> Example: Commandblock with given sets: testfor @p[r=5] > comperator > redstone light
2. Use the structure block to clone stuff around the map
3. repeat step two for a random amount
Observed Results:
The Commandblocks with Always Active & Repeat are stuck on their last operation / result.
In the example: Ether: the lamp stays on or off regardless if "testfor @p[r=5]" is false / true.
The commandblock will say that a player is there even if its not the case and the other way around.
Expected Results:
The Commandblock should output the current result / operation.
In the Example: The lamp should go on off if in proximity of r5.
This Bug is very random and logging off / restarting the server e.t.c can also lead to described problem.
The error only appears for "Always Active" as repeat and need redstone seems to work after testing for days.
My current fix:
Building a redstone comperator clock fedding it into the commandblocks needed at Needs Redstone, Repeat
Attachments
Comments 6
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
Steps to Reproduce:
1. Build something using commandblocks that need to run with "Always Active & Repeat"
> Example: Commandblock with given sets: testfor @p[r=5] > comperator > redstone light
2. Use the structure block to clone stuff around the map
3. repeat step two for a random amount
Observed Results:
The Commandblocks with Always Active & Repeat are stuck on their last operation / result.
In the example: Ether: the lamp stays on or off regardless if "testfor @p[r=5]" is false / true.
The commandblock will say that a player is there even if its not the case and the other way around.
Expected Results:
The Commandblock should output the current result / operation.
In the Example: The lamp should go on off if in proximity of r5.
This Bug is very random and logging off / restarting the server e.t.c can also lead to described problem.
The error only appears for "Always Active" as repeat and need redstone seems to work after testing for days.
My current fix:
Building a redstone comperator clock fedding it into the commandblocks needed at Needs Redstone, Repeat
Changelog says:
Structure loading/saving no longer affects ticking blocks in nearby chunks
Well Issue is still here v1.16.100:
Video (proof): https://youtu.be/onZBYEqKhrU
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please add a comment or update the affected version field.
To make your bug report as effective as possible, please try and include the following 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.
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
I had the same issues! I have to move commandblocks over to the next chunk after using the first chunk for a few days. The command blocks do seem to function in a ticking area much longer tho