Pedro Paulo Monte Pagani
Pedro Paulo Monte Pagani
This is not exactly a bug. Currently that shows that you although generated the world, you did not tick fluids. this happens to every chunk that was never "visited" by...
BTW. I just implemented this on donut, on a custom dev-proxy and the main prod we have, our environment is big because we have many regions so our RTT matters...
Btw, just for "knowledge", i think this has an issue with force close loading terrain! not sure.
@valaphee did you by any chance see if this issue is a real problem on your side?
Do you by any chance have any socket buffer configuration or anything custom on the netty config?
 Here are some examples of the issue, which will lead to those regions that were locking the lock,to instead take 400ms lag spike each
I'm trying to help improve the software. but Since some people seem to care too much about every detail of the pattern, i'll close this.
> Why would you care about random users comments? If some "maintainer" closes an issue then OK, that's their business. Otherwise I don't see why you would want to close...
If this was to be added, what has to be reworked in general @Spottedleaf tryMarkTicking would probably become a region clock? how would this work in terms of the ReentrantAreaLock
I've been encountering the same behavior, and I also may have confirmed that the tasks still run, I am not sure as to why, or if it's exactly this, been...