@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 @ahtashamabbasse, not sure if this was already replied on Discord, I'll post here anyway! you can listen to your hand structure using something like this: room.Listen("hands/:index/:attribute", this.OnHandChange); // ... void OnHandChange(DataChange change) { Debug.Log(change.path["index"]); Debug.Log(change.path["attribute"]); Debug.Log("has changed to"); Debug.Log(change.value); } The callback will be called for each attribute you have on each item in your array. Here's the logs I've got from this:

There's a big discussion about this here: https://github.com/colyseus/colyseus/issues/59 To summarize: in the current state of the framework, you'd be better off sending data manually to each client (thorugh room's send method), and not use the state for the world. Hopefully this will be improved eventually when colyseus/schema gets stable!

wow, that's insane @doorbash 👏👏👏 thanks a lot for sharing!

@deadwind88 I think I can help with this. You need to create an onMessage handler on your client side. Refer to this https://docs.colyseus.io/client-room/#onmessage so lets say your server code is working fine, in the client, you'd need to extract that message. ex: onMessage(…) { if (message.action === "request_dule") {…} }

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 !!!

Thank you! Apologies if I thought it was colyseus related. Its probably that but I wont be able to test for a while (computer crashed and fails to start, less than a year old, still under warranty) And that's why unit tests should always be used. Could have caught the error. I come from a compiled background so still getting used to debugging JS

use ws:// or wss://

Aah interesting I'm also wondering about this thing but don't know about forever package. Hope so it will solve my problem too while deploying the game I'm working on multiplayer puzzle game in JS. And noticed that whenever server is crashed need to spin it again.

You will not be able to easily restart game loops and etc after the server restarts. The best you can do is persist the relevant state to the DB and load it when the room is created again.

You can start working from it Sample Project easily just modify it as per your requirements.

Hi @DenisNP, welcome. This is not available at the current state of the framework. The only encoding option the framework provides today is a binary-diff using fossil-delta. The diff transferred to all clients consists in diff of the msgpack-encoded version of the previous state with the current one. A custom state encoding would be necessary to allow this behaviour.

I do not have a solution strictly speaking to counter the problem in a "clean" way, only a way to circumvent the problem by adding a condition that would remove an element of the dictionary if it already exists

Hi @Oviol, this sounds really good, sorry the delay to reply here. Would you mind creating a pull-request in the colyseus-unity3d project with this update? Cheers!

Hi @donghung, have you tried replacing the file mentioned by the author? (https://github.com/deniszykov/msgpack-unity3d/issues/21#issuecomment-451642818) I don't have Unity3D installed right now. Let me know if it works for you!

Awesome, feel free to share what you are doing here on the forums or the Discord chat! Not many people are using the Haxe client yet! Good luck with your project!

@endel thank you, i will try this.