7 Commits

Author	SHA1	Message	Date
Aikar	c6d6773678	Always move Entity to its new Chunk even if unloaded ... Vanilla logic here would allow us to remvoe an entity from its current chunk, and if it was going to move into an unloaded chunk, that entity would not be added to the unloaded chunk. This is bad because this will result in the entity being lost! In almost all cases, the chunk will be loaded, but in the event it wasn't, instead of losing the entity, load the chunk to add the entity to it.	2018-07-29 12:06:35 -04:00
Aikar	18c3716c49	Current Chunk for Entity and Block Entities, counts by entity type ... This enables us a fast reference to the entities current chunk instead of having to look it up by hashmap lookups. We also store counts by type to further enable other performance optimizations in later patches.	2018-07-04 03:58:56 -04:00
Zach Brown	272f130b5a	Update upstream CB/S	2017-06-18 20:37:08 -05:00
Shane Freeder	adab11a1f7	Update to 1.12-pre6	2017-05-31 22:12:46 -05:00
Zach Brown	c1d0b4b4c6	Update Paper to MC 1.12-pre5	2017-05-20 23:49:56 -05:00
Zach Brown	491286def4	Update to MC 1.12-pre2	2017-05-14 16:06:27 -05:00
Zach Brown	6c3faf6aa3	Update upstream B/CB/S	2017-05-04 18:08:52 -05:00

Renamed from Spigot-Server-Patches/0158-Chunk-registration-fixes.patch (Browse further)