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!

hi @deadwind88, welcome!

yes, clients can join multiple rooms. each room connection has its own websocket connection.

you'd need exchange messages between client and server during the Lobby room.

• sending messages from client to server
• onMessage in the client-side
• onMessage in the server-side

once your custom "handshake" between two clients has established on Lobby handler, you can send a "dule code" to the two players, and make the players join the same "dule" session.

client.join("dule", { code: "bothPlayersShouldJoinThisCode" });

on Dule room handler, you should only allow clients with the same dule code do join toguether:

maxClients = 2;

onInit (options) {
  this.code = options.code;
}

// on dule room handler
requestJoin(options) {
  return this.code === options.code;
}

I haven't tested the code, you can play around and modify as you see fit! Hope this helps, cheers!

hey @KG204, welcome!

this is an error from your room handler, apparently the error is here: https://github.com/KG204/ff/blob/master/src/questionretriever.js#L13

url is not defined on this scope, you should use this.url I think

cheers!

Hi @Tobi4s1337, welcome!

That's an interesting use-case. I think the major challenge is listening and triggering CS:GO events. I've googled about this and found a project that may help you with that, not sure how to use it, though:

• overwolf: http://developers.overwolf.com/
• CS:GO game events http://developers.overwolf.com/documentation/sdk/overwolf/games/events/csgo/
• their SDK: https://github.com/overwolf/game-events-sdk
• sample events consumer (dunno how to run this) https://github.com/overwolf/events-consumer

I imagine this is not possible through a web browser, but maybe it can be achieved through Electron.

Not sure if CS:GO allow external applications to perform actions, such as creating the server and stuff.

Cheers, good luck!

hey @kukuts, after restarting is not easily done.

hey @mdotedot, not exactly sure what you're planning to build, but to persist the data across server reboots you can use the RedisPresence alternative. The LocalPresence really doesn't persist any data. Cheers!