This repository has been archived by the owner on Sep 3, 2022. It is now read-only.
TeleportID implementation and usage #1366
Comments
lzardy
pushed a commit
that referenced
this issue
Mar 25, 2022
I wrote "progress" because I still have to use teleportation for collisions. Otherwise, collision avoidance comes into play and the minions go in different directions. They are already trying to do this, but in the *indev* branch they are teleported away every tick of the server. This also looks ugly, but I decided to keep this behavior. At least now, instead of recalculating the entire path, a collision only changes the zero point of the path. And this is usually enough, because the collision only throws the unit back a little.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the original league, packets only have a
TeleportIdif theHasTeleportIDfield is set. Also in the LS it is possible to create a visibility packet containingMovementDatawithout this field set. And in general, theuseTeleportIDparameter is used too often, instead of just two cases: teleportation and appearance in the field of view - because of this, the client fails to smooth the movementThe text was updated successfully, but these errors were encountered: