When proxying the websocket connection, e.g. through nginx, the connection may be closed when there are no messages for longer than 60 seconds (by default). It makes sense to prevent this (even though configuring nginx is also a viable workaround for this problem), which also allows us to better keep track of which player is online.
When proxying the websocket connection, e.g. through nginx, the connection may be closed when there are no messages for longer than 60 seconds (by default). It makes sense to prevent this (even though configuring nginx is also a viable workaround for this problem), which also allows us to better keep track of which player is online.