Thanks endel for the response.
The AI agent is built by multiple teams and the goal of this exercise would be to make the different agents compete against each other. So enforcing a language restriction on different teams is not an option. Further the standard implementations of the AI/ML libraries are more easily found in python than in Javascript. For the same reasons I am trying to separate the clients and the game server implementation.
If anyone has this issue and you are trying to use multiple join / left rooms like I was doing, make sure to always be joined in one room.
In my case I was leaving one room before join the next one, so I moved the oldroom.leave() action inside the newroom.onJoin() and now everything works fine.
Note, this was happening randomly at the beginning until I overloaded the room onInit with data, then I got the issue all the time because the second room was delayed on load.
Best,
[SOLVED]
Thanks @endel but as i am making card game i need to have options for client to choose whether to create a room ( private table ) or join the room ( if there is no room available then auto create room with)
Hi @holyxiaoxin, it looks like this.broadcast() would be better on this case. Then the message is broadcasted instantly. You can retrieve the message using the room.onMessage signal from the client-side.
Hi @endel thanks for you quick reply, as you said... yeah.. too many issues already LOL
I'll go for the database option to persist the data between room changes, I'm working on it now, the idea is to save the player progress > leave the room > join the new room > re-authenticate the user with the data in the session and reload the progress.
I though it will be too expensive in terms of server response time, but keep a room or persist too much information in the presence could end up been even more expensive than just hit the DB to get the data.
Best,
Thanks for answers and recommendations. My aim was to avoid crashs due to the bugs I haven't discovered yet, or any undefined action client made that could make the whole server(all the other rooms) crash.
As an answer to @endel, errors that I have come across so far was thrown from timeout callback functions so putting try catch to onJoin might not help :) .
