Awesome @halome, it's looking good! Another option would be MatterJS: https://github.com/liabru/matter-js Good luck with your project! Don't hesitate if you need any help with Colyseus here!

Hey @rscata, I've just released a new version (colyseus@0.8.13, see release) which adds the isNew parameter on requestJoin. With this version you'd be able to achieve the same result by having this implementation: // ... maxClients = 4; requestJoin (options, isNew) { return (options.create && isNew) || this.clients.length > 0; } // ...

@endel said in colyseus.js: server error: registeredHandler.klass is not a constructor: Or by exporting the room usin I'll try it the week end and come back to you later. Thx for the help so far.

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,

Hey @merhawie, Are you calling client.join() after the onOpen signal, as described here? https://github.com/gamestdio/colyseus.js#react-native-compatibility

That's great to hear @visgotti, thanks a lot ❤️❤️❤️

@umen we have 3 servers now (each droplet of DigitanOcean 1 vCPUs 1GB / 25GB Disk), each server can keep about 500-600 users, but it's depends on logic of your server.

@endel I was looking at this in a tired state, but im pretty sure i had fully updated client and server. Ill double check what i was seeing and if i still have an error I'll open an issue on the github. Thanks for the response.

@Алексей-Андронов the clock only works if you set up the simulation interval. I guess that's not intuitive, I'll fix this on version 0.9.0 too.

@Carlos-Montesino, i've tried your endpoint (wss://carmenproject.herokuapp.com) but it is not working properly. the "please wait" text is not destroyed. it seems that it is cannot join any room.

Thanks :smile:

@endel So, I got this working by calling gameServer.matchMaker.create("game", {}); after registering (I only do this on the second process). It seems that the you are only subscribing to presence when the room is created. There is no knowledge that a registered handler is registered within presence. So, I have manually created the room on startup. This probably is not the best way, but it works for now while you can think about how we would want to solve for making the other game servers aware that a room is registered but not yet created.

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

@endel Yay !! thats work Thanks.

Client debugging ... Leaving both current and joining room with just one room.leave() call .... HTML5 works well, Windows is doing well most of the time, but Mac and Android are having troubles in leaving and joining. I suspect that Windows problems are caused by the same issue, but couldn't steadily reproduce that. It is the same HaXe client-code due to being a HaXe extension. There are only differences in Player Name gathering on HTML versus native. Didn't test iOS/Linux. What I think is happening is that room.leave() is done twice on Mac/Android?!? What can be the cause of this?! HTML5 debug: Colyseus.hx:156: JoinRoom to joinID: BWNT-kGd0 Calling Room Leave with room.id: NRL_w4txR Colyseus.hx:421: leavecounter: 1 room.onLeave RoomID: NRL_w4txR Session ID: XqE4dF-s6 Colyseus.hx:275: (Client: )p6_HgFPtE join room to JoinID : BWNT-kGd0 Good: Colyseus.hx:304: joinRoom : joinCounter: 2 Joined Room BWNT-kGd0 sessionID : VXeeGm4oI Debug Mac: Colyseus.hx:156: JoinRoom to joinID: z40eavIgr Calling Room Leave with room.id: Ge_RICPir Colyseus.hx:421: leavecounter: 1 room.onLeave RoomID: Ge_RICPir Session ID: f2c1YeU3i Colyseus.hx:275: (Client: )9EoXglrY9 join room to JoinID : z40eavIgr Colyseus.hx:421: leavecounter: 2 room.onLeave RoomID: z40eavIgr Session ID: null Never reached joinRoom!! And it does TWO leave rooms !!! The output on server side is the same (of course not the IDs and names ...) HTML5 Request join : this.roomId: NRL_w4txR options.Type: undefined PlayerName: APlayer3642 OldMax: 1 Number of clients in room: 1 the room id is : NRL_w4txR Request join : this.roomId: NRL_w4txR options.Type: undefined PlayerName: APlayer7523 OldMax: 100 Request join : this.roomId: NRL_w4txR options.Type: undefined PlayerName: APlayer7523 OldMax: 100 StateHandlerRoom created! { PlayerName: 'APlayer7523', RoomName: 'Room5672', requestId: 2, clientId: '3VTAK8HPh', lobby: { rooms: [] } } Request join : this.roomId: BWNT-kGd0 options.Type: undefined PlayerName: APlayer7523 OldMax: 1 Number of clients in room: 1 the room id is : BWNT-kGd0 Number of clients in room: 0 the room id is : NRL_w4txR Dispose StateHandlerRoom : remove room.id : NRL_w4txR Request join : this.roomId: BWNT-kGd0 options.Type: JOIN PlayerName: APlayer3642 OldMax: 100 Number of clients in room: 2 the room id is : BWNT-kGd0 Number of clients in room: 1 the room id is : BWNT-kGd0 MAC: Request join : this.roomId: Ge_RICPir options.Type: undefined PlayerName: APlayer7255 OldMax: 1 Number of clients in room: 1 the room id is : Ge_RICPir Request join : this.roomId: Ge_RICPir options.Type: undefined PlayerName: Player5710 OldMax: 100 Request join : this.roomId: Ge_RICPir options.Type: undefined PlayerName: Player5710 OldMax: 100 StateHandlerRoom created! { PlayerName: 'Player5710', RoomName: 'Room1021', requestId: 4, clientId: 'vJGYZCiJ5', lobby: { rooms: [] } } Request join : this.roomId: z40eavIgr options.Type: undefined PlayerName: Player5710 OldMax: 1 Number of clients in room: 1 the room id is : z40eavIgr Number of clients in room: 0 the room id is : Ge_RICPir Dispose StateHandlerRoom : remove room.id : Ge_RICPir Request join : this.roomId: z40eavIgr options.Type: JOIN PlayerName: APlayer7255 OldMax: 100 Number of clients in room: 2 the room id is : z40eavIgr Number of clients in room: 1 the room id is : z40eavIgr I even used a timer to call join after the leave so that it does it 5 or 10 seconds later. As soon as I do the join the leave call is executed !!!

@lezanardi function setEnumerable(object) { let private = {}; for (let key in object) { Object.defineProperty(private, key, { value: object[key], enumerable: false, writable: true }); } return private; } Will return the passed object with all the items non-enumerable.

I have no idea if we do not have access to "getAvailableRooms". If we did then you could simply have the client make that call every few seconds or minutes to get a fresh list.

Hi Guys Feel free to give and feedback if you tried and played the game :).

@wenish looks really awesome, thanks for sharing! Did you do the artwork yourself? :o (On the Login / Sign Up screen) I'll definitely consider using it at one point.

Hi @endel thank you for the quick response. will keep track of the issues.