Spottedleaf 25e0cbdae4 Rework some parts of the player chunk loader ... Change overview: - Rework limiting - Remove mid tick updates - Introduce consistency checks The old limiting logic used an intervalled counter, but did not account for possible slight changes in mid tick invoke rate as it relied heavily on mid-tick logic. Due to the removal of mid tick updates, it is now important that the logic functions correctly no matter what rate it is invoked at. The new logic directly tracks the last update time and allocates an amount based proportional on the rate targetted, which makes the logic call rate independent. The removal of mid tick updates is done to eliminate recursive call risk, and to additionally reduce the lock pressure on the chunk system by grouping chunk loads onto one part of the tick rather than spreading it out. The limiting rework should ensure that this does not negatively affect rates, but it will decrease the perceived smoothness of chunk generation/loading at low rates. Introduce more consistency checks such as correct tick thread and ticking-after-removal checks. Also, perform checks during the player chunk loader tick to avoid updating potentially removed players during the tick. The checks are primarily made to try to hunt down a bug that is causing the player chunk loader to double send a chunk to a player.		2023-04-10 17:51:21 -07:00
..
api	fix: fix build number check in version fetcher (#16)	2023-03-30 14:13:55 -07:00
server	Rework some parts of the player chunk loader	2023-04-10 17:51:21 -07:00