Power sources keep a list of things they are powering and recalulate this list whenever they recieve a certain type of update to a block they're powering. This is done for performance reasons and makes redstone dust and redstone in general way less laggy than java for the most part.
However, they calculate this list around 10x slower on a block update than they do when the chunk they're in is first loaded. I don't see why this should be the case. It shouldn't be that much slower. It should be faster actually.
As well as this, it recalculates everything it's powering, instead of only checking the section that got the update.
It needs to be way less laggy than it currently is, because the current behaviour allows for some really compact lag machines, such as this one, which can bring a server to it's knees in under half a subchunk of space.
I'll send a test world soon.
Comments 4
If you replace the target blocks with jukeboxes or observers you should be able to test it in 1.14. You could also do a platform of redstone blocks with dust on top (31x31) and update that, which is probably the easiest way.
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 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.
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
Is this new to 1.16.0.61, or can you reproduce it in earlier betas or 1.14.60?