Topics created by cmdt.ed

OK, I'll look into doing that. I don't have much experience with redis, promises, async and even javascript but I'll see what I can do. Thanks.

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

I have no idea about that.