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

Movement is still hit or miss #34

Open

cyberkitsune opened this issue Jul 16, 2015 · 0 comments

Labels

Milestone

v0.2.0 - Sechuran...

Member

cyberkitsune commented Jul 16, 2015

When it works, it works well.
But sometimes, certain clients don't get the movement data all the time.

We still may be handling the movement packet wrong? Maybe we need to send an identifier more often than not?

cyberkitsune added this to the v0.2.0 - Sechuran Fox milestone

cyberkitsune added bug packets labels

PolarisTeam locked and limited conversation to collaborators

PolarisTeam unlocked this conversation

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