Having some issue with channel.onDisconnect()

[HuntingtonJ]

Currently working on a multiplayer game (go figure), and for while wasn't having issues with disconnects so not sure if a recent update change things.

Setup:

• 3 node based servers running on amazon ec2 (EDIT: problem does not occur locally)
• 1 server provides a nuxt website
• 1 server hosts the game client
• 1 server manages game server instances through pm2

The basic flow I've implemented is:

1. Server is booted up and waits for a user(=channel) to connect.
2. On the server io.onConnect(), I setup all the basic events, including user.onDisconnect()
3. Server sends a 'ready' event to the connected user
4. User and Server perform a handshake to give the user a unique Id
5. With normal operation, User sends inputs updates and server sends state updates

My issue at the moment is with the user.onDisconnect() event on the server. When I have multiple users connected, and then disconnect one by closing the browser tab, the server io seems to die as evidenced by the connected clients channel.onDisconnect() event firing. The expected behavior is when the server user.onDisconnect() is fired (which it does), it would then send a 'removePlayer' event to the remaining connections (which does not occur, never seen by the other users).

So to summarize, users can connect to the server and play (so server and clients do communicate) but when a user disconnects, the server io instance dies(?) and stop communicating.

Server io

Client boot scene

Client game scene (in create function)

[yandeu]

There was a recent update/fix in onDisconnect().

Can you please open a new issue a provide a small sample project?

I will have a closer look in mid January.

[Zenchess]

I have the same issue when I use the express server as https for the game. Everything works fine but if a player disconnects everyone gets disconnected. It does not happen when using just a local server without express.

[yandeu]

@Zenchess Can you please tell me if the issue goes away if you downgrade geckos to v2.1.4.

[Zenchess]

I apologize, I'm pretty sure I had it set up wrong. It works now, at least with the latest code and I think 2.1.0 as well.