Hi @hardik_sl,

You may modify the requestJoin method to allow creating the room regardless of the param create is being passed as true or not. I've made this example to demonstrate that clients may have control to create or join into rooms. By omitting the requestJoin method, it will always return true.

Hi @zpr, welcome!

I think the problem you're facing is exactly what @Nebri just asked about in the Gitter channel.

You're probably facing the famous this problem in JavaScript. When referencing the function directly on setSimulationInterval you will lose the this reference.

You can call it like this instead:

this.setSimulationInterval(() => this.tick())

or

this.setSimulationInterval(this.tick.bind(this))

Hi @amit-gshe, welcome!

Have you tried this.emit('dispose')? It should work as you expect!

Hi @holyxiaoxin, it looks like this.broadcast() would be better on this case. Then the message is broadcasted instantly. You can retrieve the message using the room.onMessage signal from the client-side.

Hey @gabrieltong, welcome!

I'd suggest sending the private data you're not synching directly to the only client that should've access to it. I'm using exactly like this on a game I'm currently working on:

Server-side:

this.send(client, ['cards', privateCards]);

Client-side:

room.onMessage.add(function(message) {
  let [type, data] = message;

  if (type === "cards") {
    console.log("your cards are:", data);
  }
});

@jalu's suggestion is handy, but if the user spends some time in the developer console he might retrieve the hands of the other players in order to cheat in the game.

The screenshot looks awesome, @Tyrus-Shan, congrats!

I've tried to play but there aren't many users for match-making yet, I suppose. I'd suggest adding bots to allow users to play by themselves while people are still discovering this game.

Hey @dpastorini, that's not possible. You can do it by storing the data you'd like to retrieve in the presence (e.g. this.presence.hset("roomxyz", "key", "value")), and then retrieving it in the other room (this.presence.hget("roomxyz", "key")).

I wouldn't recommend doing this, though. It's likely that you'll face some issue when the data is not available anymore, in case the room gets disposed, for example.

Hi @dpastorini, sorry the delay to answer. I've just published some docs for Presence here: http://colyseus.io/docs/api-presence/

Just be careful when using Presence methods manually to avoid memory leaks. It's common to set values there and forget to clean them up.

That's amazing @halilbilgin, thanks a lot for sharing! I've added your game to the showcase section on the website. Best of luck with your project!

I'd love to hear more about your experience in the client-side, since the Unity client is not so easy to use in comparison to JavaScript, due to the insane amount of typecasting necessary on C#.

client.close() does not trigger anything in client

It's likely that this one can be fixed. Unfortunately, the Unity client lacks some good care.

Hi @halilbilgin, which error are you seeing, and during which callback? (onJoin, onMessage, onLeave?)

Do you have a stack trace?

It makes sense avoiding a total server crash, but the error messages should be still easy to catch somehow during development.

Cheers