asofold c5e1f6ba2b [BLEEDING][BREAKING] Player move set back: cancel event + schedule TP. ... Because Spigot changed to fire the teleport following an altered move end point with TeleportCause.PLUGIN, we have to alter set back handling, so we can ensure to keep TeleportCause.UNKNOWN for setting back players. Instead of altering the move end point, the event is just cancelled, and a teleport is scheduled (with a dedicated TickTask method). Uncancelled moving events mean removing scheduled teleports. [BLEEDING] * Comparably simple change - more places and special cases may still be uncovered. [BREAKING] * Plugins that may rely on the exact sequence of things within NCP, as it used to be. Random * Change "set-back" to "set back" everywhere for simplicity, and to obfuscate the actual code changes. * Set backs are now going through MovingListener.onCancelledMove instead of MovingListener.onMoveMonitorNotCancelled. * Illegal move handling would still use event.setTo.		2017-04-02 15:01:23 +02:00
..
src	[BLEEDING][BREAKING] Player move set back: cancel event + schedule TP.	2017-04-02 15:01:23 +02:00
pom.xml	[BLEEDING] Use 1.9 API to detect actually using elytra.	2016-03-23 22:35:09 +01:00