I'm currently working on a Node.js - Unity game that utilizes sockets for user connection to the game. I've encountered an issue where the connection seems to be constantly reconnecting and disconnecting in a loop within Unity. However, when I tested it using a web browser, I did not experience this problem.
Another observation is that I initially used port 3011 without any issues, but after switching to port 3012, things are not working correctly. Initially, I suspected that changing ports could be the cause of the problem, but further investigation proved otherwise.
My Node.js version is v6.11.0, utilizing both port 3011 and 3012. The socket version being used for the server-side in Node.js is 2.0.3.
I would greatly appreciate any help with this issue. Below is a snippet of the sample code:
io.on('connection', function(socket)
{
console.log('User connected');
socket.on('disconnect', function(reason){
console.log('User disconnected',reason);
});
});
socket.on('joinroom', function(roomId)
{
console.log('player joined room: ' + roomId);
socket.join("room_"+roomId);
});
http.listen(3012, function(){
console.log('Started nodejs server');
initRoomActivity();
});
The issue appears as follows:
player joined room: XXXX
User disconnected client namespace disconnect
User connected
player joined room: XXXX
User disconnected client namespace disconnect
User connected
player joined room: XXXX
In the above example, "XXXX" represents the same room, while "client namespace disconnect" is listed as the reason for disconnection.