First off, you shouldn't do this. It's meant to be a state, which holds data. Not a lot more than that.
That said, if you really want to, you can add a @nonenumerable or @nosync attribute to the room variable. to make it not serialized.
Hi @DinhNguyen,
The requestJoin() method has a isNew as a second argument, you may check for it whenever requesting to join a room with a password.
Example:
requestJoin(options, isNew) {
if (options.password) {
// this forces to accept only if a room already exists
return this.password === options.password && !isNew;
} else {
// always dissallow joining without a password
// (you may want to change this)
return false;
}
}
I haven't tested this code, you may need to modify it slighly
hey @henrydavidzhu, you can always find the latest colyseus.js file here: https://github.com/colyseus/colyseus.js/tree/master/dist
colyseus.js: server error: no available handler for "1mnyb24wwjtwkdbld"
This error means you're trying to join a room handler named "1mnyb24wwjtwkdbld" that doesn't exist. You must register the room handler in the server.
gameServer.register("1mnyb24wwjtwkdbld", YourRoomHandler)
class YourRoomHandler extends Room {
// ...
}
I highly recommend you read the documentation:
https://docs.colyseus.io/server/api/
https://docs.colyseus.io/server/room/
@DinhNguyen and @rscata I think you both are looking for rejoin the game. Below snippet will solve your problem. For more details: Rejoin Link.
async onLeave (client, consented: boolean) {
// flag client as inactive for other users
this.state.players[client.sessionId].connected = false;
try {
if (consented) {
throw new Error("consented leave");
}
// allow disconnected client to rejoin into this room until 20 seconds
await this.allowReconnection(client, 20);
// client returned! let's re-activate it.
this.state.players[client.sessionId].connected = true;
} catch (e) {
// 20 seconds expired. let's remove the client.
delete this.state.players[client.sessionId];
}
}
Sorry to reply to an old post but this was the one that finally helped me understand how to use listen so I thought it might be helpful to clarify for other users who are as dense as I am.
The documentation for listen at https://docs.colyseus.io/client-state-synchronization/ is painfully terse and confusing especially in how it uses the colon (:). From my understanding, if you have something like the following as your state:
{foo: bar: {baz: 'somevalue'} }
then you can listen for baz via
room.listen('foo/bar/baz', ...)
or via something like
room.listen('foo/:wildcard_1/:wildcard-2', ...)
That is you can either use the exact path or use wildcards but the text after the colon has no special meaning. I kept thinking that the :id and :attribute wildcards in the docs had a special meaning.
Hope that helps others who got confused like me.
Thanks again.
Excellent! Thanks for the quick response.
I was confused on this so I'll summarize in case others come to this post in the future.
The @nosync decorator is needed because you might create an object foo that will be inside the state object and foo has properties bar and baz with bar being visible and baz being private. You would then use @nosync on baz since it is something inside the state that you want private. But for just other properties of the room but outside the state, those will not be synced.
Hi @cmdt-ed,
Can someone confirm that the mutation is NOT sent out anywhere?
Only the server can mutate the state, mutations in the client-side are going to be replaced in the next patch
Can someone confirm that future changes to the server room state still get synced to the client?
Yes
Any other things to be aware of if the client tries to "cheat" by messing with the client room state?
You usually don't send messages from the client to the server telling what the state is, but rather the action a client is taking to be validated in the server-side, and then mutate the state in the server
Cheers
Hi @endel
It WORKS! Thanks a lot!
I learned just now that there're several ways of packing js. And maybe umd is suitable for CommonJS mentioned by @parkcd. So please use this way for future pack : )
@usamasermad yes, you should ensure the Client connection is open before performing a ReJoin. If you're going to instantiate a new Client, make sure it has the same client.id as the one who initiated the first connection to the room (https://github.com/colyseus/colyseus-unity3d/blob/master/Assets/Plugins/Colyseus/Client.cs#L66)
