A colyseus + DB with authentication would be the ideal example IMO
something like the existing tic tac toe example with a simple user creation (DB) and login (authentication) would be enough
and it would be all someone needs to make a complete multiplayer game experience
OK! FINALLY FOUND THE ISSUE!
The short-temporal-fix:
1 - Open FF and go to about:config
2 - Look for network.websocket.max-connections
3 - Set the number as high as you like :P at some point you will probably hit the issue again.
The long-story:
Doing some research found the following: http://websocketstest.com/
In my case websockets in FF were mark as supported but every port seems to be closed and not a single connection was stablished. In CH everything is opened and working.
At this point I've realized that for sure it was something in the client and I've started to think in a weird case where FF is reaching a limit in the WebSocket connections. Didn't know this was possible....
Keep doing some research on the issue and found a post that says something like: "https:// to ws:// is disallowed by default on firefox", in the same thread says that could be fixed by going to firefox's about:config and toggling network.websocket.allowInsecureFromHTTPS but didn't worked for me.
So I've started to do some tests by changing the FF configurations, first tried by changing other configs like "network.websocket.delay-failed-reconnects" but didn't worked. And there it was! "network.websocket.max-connections" had a 200 value, so I've changed it to 201, and after refresh the App it finally worked. There are also other configurations there like "network.websocket.timeout.close", but I really don't want to change any of these to fix the issue (not even the max-connections value), because I don't think that's a fix but more of a hack to avoid the issue.
Now... the real issue seems to be that FF is keeping all the connections opened after you refresh the browser.
One thing to note is that even FF keep the "connection" as "active", the colyseus monitor show up how the user connects and disconnects.
An easy way to test this is by connecting to any app open the config in a new tab and set the connections limit to 2, then refresh the browser y after the second refresh you won't be able to connect anymore.
I'll be still digging on this to find a final fix but maybe is just something I'm setting in my app?
I'm using the very simple "state" case from the colyseus-examples.
@endel any clues?
Thanks in advance!
Hi @alexander-nortung, is it on colyseus-examples project? Make sure to run npm run bundle-colyseus-client to generate the colyseus.js file.
On a real scenario, it's recommended to import the client using webpack instead.
Cheers!
@endel Now I get it! Thanks so much for the help. I have enough to get started on my project.
Just curious though, why isn't an explicit create call supported? I see it being useful in scenarios where users can create their own game and share it with friends. The rooms can't really be locked when the game starts as the players might change devices during the course of the game. When there are many existing rooms, the creation of new rooms might become expensive. Is it a security concern for the clients to be able to create the rooms, or just not a common scenario?
Regards,
Madki
Ok, I found the answer myself thanks to this thread :
https://github.com/gamestdio/colyseus/issues/59#issuecomment-403288409
Currently, room.send() is the best method to achieve what I described.
Last one: one of the features in the 04-create-or-join-room.html example seems to be broken.
In the client I got: colyseus.js: server error: Failed to join invalid room "a-QUjQJmPs"
In the server:
CREATING NEW ROOM
Error: Failed to join invalid room "a-QUjQJmPs"
at MatchMaker.<anonymous> (/var/www/questworld/colyseus-examples/node_modules/colyseus/lib/MatchMaker.js:124:23)
at next (native)
at fulfilled (/var/www/questworld/colyseus-examples/node_modules/colyseus/lib/MatchMaker.js:4:58)
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
Best,
Hi @endel I already used client.Rejoin() to get reconnect back from client side, and I can successfully reconnect back to server with a new coroutine, just that after the reconnection, I couldn't recieve any update from server side but still can room.send() data to the server.
