- Mar 26, 2003
- 1,389
- 123
- 289
lol trust me it's tricky (the delphi code is super super complicated in these areas)If that was the case, no one would be able to walk through, there would be no repel/dash bug and there would be no push back because they wouldn't start to walk and get canceled. (if the server confirms before movement).
Also why do you attempt to walk when disconnected?
some cases where you got pushback turned out to be situations where client and server couldnt agree on what spot was vacant, someone moved on the spot while you where moving, ....
the repel/dash bug is caused by how delphi mir clients deal with coords being out of sync. if your client somehow gets confused on what spot you're on: it try's to force-move you to the correct spot (does this without telling/showing you): stuff like dash overrides this.
dont ask me on every detail (it's been months and even with code infront of me, i wouldnt be able to fully comprehend every choice without investigation
i'm 200% sure the files originaly waited for server confirmation before moving, not sure on what else it waited etc tho (could be it just did quick checks to confirm cant remember)
