Closed riddle closed 9 years ago
If you implement this, please reuse the existing system I used. It already has a worker pool where you can submit your worker instance and it will take care that it gets executed and not too many blocks get changed while executing it
Where is that worker thing you speak of?
This is not a big issue with Growth but can be baad for Decay. Basically the # of block updates happening at the same time can overpower main thread for up to a second, lagging players. I’d see this benefiting from a queue-like approach like narrowtux did with abandoning claims and removing water in Core.