SuccessChanges

Summary

  1. If Entity is added to chunk, look up the chunk if current isnt set (commit: e674d3a) (details)
  2. Always move Entity to its new Chunk even if unloaded (commit: c6d6773) (details)
  3. Always process chunk registration after moving (commit: f35324d) (details)
Commit e674d3a00f651dc0947ebb1393de072a71960baf by aikar
If Entity is added to chunk, look up the chunk if current isnt set
Hopefully will (f)ix #1280...
I'm suspicious that Citizens isn't calling things in the same order and
causes the current chunk to not be set, which then bugs removals. Though
this doesn't make any sense to me, so this likely won't fix it...
But if the isAddedToChunk is true, we really should be returning a chunk
anyways if its loaded.
(commit: e674d3a)
The file was modifiedSpigot-Server-Patches/0059-Change-implementation-of-tile-entity-removal-list.patch (diff)
The file was modifiedSpigot-Server-Patches/0006-Store-reference-to-current-Chunk-for-Entity-and-Bloc.patch (diff)
Commit c6d6773678486fc24ec0a784b37da9fc904bca61 by aikar
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.
(commit: c6d6773)
The file was modifiedSpigot-Server-Patches/0157-Chunk-registration-fixes.patch (diff)
Commit f35324dbed150269aeb30e0b06366e72336d68e2 by aikar
Always process chunk registration after moving
This will help guarantee that entities are always in the chunk that they
are currently located at.
Should hopefully also fix Citizens triggering the "Saved to wrong chunk"
message
(commit: f35324d)
The file was addedSpigot-Server-Patches/0344-Always-process-chunk-registration-after-moving.patch