Skip to content
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.

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

Fast travel (using a mouse) can lead to unpredictable navigation #52

Open
Gaffen opened this issue May 2, 2018 · 4 comments
Open

Fast travel (using a mouse) can lead to unpredictable navigation #52

Gaffen opened this issue May 2, 2018 · 4 comments
Labels

Comments

@Gaffen
Copy link
Collaborator

Gaffen commented May 2, 2018

If you travel quickly between rooms using the mouse to click on location names, after clicking one or two in succession the app will randomly 'teleport' your character to a previously visited location after a couple of seconds.

This is likely to do with the server state syncing.

@MatejJan MatejJan added the bug label May 4, 2018
@MatejJan
Copy link
Member

MatejJan commented May 6, 2018

@Gaffen What's the chance you had two browser tabs with the game open? So far I've discovered that definitely causes what you're experiencing. It's probably another reason, just want to eliminate this possibility.

@Gaffen
Copy link
Collaborator Author

Gaffen commented May 8, 2018

@MatejJan Hmm, I'm not sure - I'm not able to recreate it anymore, with or without a second tab open

@MatejJan
Copy link
Member

MatejJan commented May 8, 2018

Hmm, it might also be that it happens just when the server is overloaded and game states aren't immediately being saved to the database and there are different race conditions due to that. The whole saving/updating of game state isn't the most robust system in these kinds of instances. Def needs an upgrade at some point.

@Gaffen
Copy link
Collaborator Author

Gaffen commented May 16, 2018

@MatejJan after our discussion the other day I think this bug was probably caused by long term usage of the site in a separate tab. I'm sure it will still be useful to solve this bug at some point, but I feel like it's a symptom more than it's a bug in and of itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants