Okay, then I’ll wait. I ran ahead a little :) Thank you @endel for you work!

+1 for godot support

@endel Wait, you mean type string with value "123456" as a key of MapSchema is a number ??? Really @@ So what about "P123456" :-? is this string ?

@endel After upgrade to alpha, now the room.state return null, then I cant call back the onChange event :(

Found the issue. SSL was not the problem .Unity client is replacing the existing path in url when joining a room. Fixed it by adding existing path in CreateConnection method of Client.cs class UriBuilder uriBuilder = new UriBuilder(Endpoint.Uri) { Path = Endpoint.Path + path, //earlier it was just path Query = string.Join("&", list.ToArray()) };

It seem like not only colyseus server is affected: https://github.com/parse-community/parse-server/issues/6173 https://github.com/parse-community/parse-server/issues/6413 I created a bug for colyseus to handle this particular error in graceful way and keep clients connected: https://github.com/colyseus/colyseus/issues/364

@bluebang seems to. I have the same question, so I think now we must do something like that, but it could be complicated, if the game state will be too large

Working towards a beta release of the Colyseus Stencyl Extension. I had already Lock, TurnBased and Raw room-types. Most of the progress has been made with the Client-As-A-Server concept. I know that the best way to handle multiplayer is on the server-side. But many of the Stencyl users are not comfortable writing the server-side logic. Therefore I attempted for a Client-Server-Relay kind of thing. The collision and logic is handled on the client side with one of the clients acting as the server. On that client the real physics objects are hidden and only the data that is send to all players is displayed. These are the things that are currently made with the Client-As-A-Server approach: Left Window is a Windows executable Right Window is a web-page I hope to do some more beta-testing with other Stencyl users to gain more information about this approach.

I just asked if you can use Spanish. I attach this text if not: Thanks for the welcome !, and the question was to try to connect from gamemaker. Currently I made a very very basic server in Node but I would like to take advantage of something already made like Colyseus, which is a very good development, congratulations!

New beta released! https://www.reldens.com/beta-15-released

This solves the issue. Thank you!

Hi @kukuts, thanks for your availability for testing the alpha version. If you're using the JavaScript client (colyseus.js), you can try out the beta versions at: colyseus@0.14.0-alpha.5 (server) colyseus.js@0.14.0-alpha.4 (client) For short, you can install them using: npm install colyseus@alpha --save npm install colyseus.js@alpha --save Hopefully, ALL MapSchema issues should be gone now. There are some small API changes though, mostly regarding iterating through MapSchema values and/or its keys, and getting its length. Here's the upgrading guide so far: https://deploy-preview-45--colyseus-docs.netlify.app/migrating/0.14/

thanks for your answer!!

definitely nice game. i like the camera touch. and maybe you should let a lawyer look at your tos.

@endel And another problem, when A game and B game share the same schema, that would be a problem. gameA use PlayeInfo Schema in ARoomSchema and gameB use PlayerInfo too in BRoomSchema. That would be a situation, the PlayerInfo could only implement one specific context but not two.

@cooul Hi, i meat the same situation. that is because you just ctrl+c to terminate the node process. you should make some post method to trigger the graceful shutdown. this function will remove the room info from your redis.