New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Warp Bug #112

Open

vilarion opened this issue Jun 22, 2020 · 0 comments

Assignees

Labels

bug

Member

vilarion commented Jun 22, 2020 •

edited

I have now logged the warp bug in the server.

[0x10] <-- requests to move north with NORMALMOVE
[0xDF] --> moves to (359, 875, 0) with NORMALMOVE
[0xBD] --> was moved to (359, 878, 1)
[0x10] <-- requests to move northwest with NORMALMOVE
[0xDF] --> moves to (358, 877, 1) with NORMALMOVE

The client asks for two moves
First one is onto a warp, which gets handled and sent back
Second one is just away from the warp destination
It also gets handled and sent back
That is where the client freezes up

This cannot be reproduced on demand, you have to walk on warps until you get the freeze.

The text was updated successfully, but these errors were encountered:

vilarion added the bug label

vilarion pinned this issue

voidowl-rl self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment