-
Notifications
You must be signed in to change notification settings - Fork 219
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
Client keeps getting "undefined" socket.io #194
Comments
@Flavius256 I think you migrated your fork to socket.io as well. May be do you have some useful information about this? Thank you! |
Of course I do ;) The main issue is that socket.io and BQ are not properly 'merged' together, so some packets of type undefined or null get sent, that causes all the monsters and group entities to disappear.. I won't keep the temporary fix for myself, so here's what I've done to prevent this until I find out what packets are being undefined.
|
@Flavius256 thank you! now, /status displays I'm using node Again, thank you for your fix. I'll test it some time and then I'll let you know if I found something else. |
Each object in the array [2, 0, 0, 0, 0] is the world with its players. It should never be completely empty unless there are 0 worlds. [0] for 0 players, [2] for two players in a single world. |
Then it's my fault. I configured server/config.json for a single world, but I forgot that. 😅 |
c3a960b
I noticed you are using v1.4 in your heroku server, and I noticed 1.4 is not using socket.io; so maybe there are some issues with socket.io migration?
The text was updated successfully, but these errors were encountered: