aa52bf9e33
Mojang made some changes to priorities in 1.17 and it seems that these changes conflict with the changes made in this patch, which in some cases appears to cause excessive rescheduling of tasks. This, however, is not confirmed as such but seems to be the behavior that we're seeing to cause this issue, if mojang has adopted the changes we suggested, then a good chunk of this patch may be unneeded, but, this needs a much better look than I'm currently able to do |
||
|---|---|---|
| .. | ||
| No longer needed | ||
| 0009-Store-reference-to-current-Chunk-for-Entity-and-Bloc.patch | ||
| 0010-Store-counts-for-each-Entity-Block-Entity-Type.patch | ||
| 0351-Fix-issues-with-entity-loss-due-to-unloaded-chunks.patch | ||
| 0372-Reduce-sync-loads.patch | ||
| 0380-Optimise-random-block-ticking.patch | ||
| 0420-Ensure-Entity-is-never-double-registered.patch | ||
| 0436-Delay-unsafe-actions-until-after-entity-ticking-is-d.patch | ||
| 0438-Workaround-for-Client-Lag-Spikes-MC-162253.patch | ||
| 0488-Implement-Chunk-Priority-Urgency-System-for-Chunks.patch | ||
| 0626-Optimized-tick-ready-check.patch | ||
| 0698-Make-sure-to-remove-correct-TE-during-TE-tick.patch | ||
| state.txt | ||