Hi everyone,

A few months ago I've started my project using Colyseus and Phaser 3:
https://github.com/damian-pastorini/dwdgame

After hit a few walls and considering it was my first project it took me some time until I was able to get the physics working on the server to avoid cheating.
The way I get it done was using Phaser physics engine P2JS: https://github.com/schteppe/p2.js
Doing this I was able to avoid an overhead of modules and stuff required to run a headless Phaser.

Here I bring for you a small example of how to recreate a Tiledmap using P2JS:
https://github.com/damian-pastorini/p2js-tiledmap-demo

I'm still finishing the dwdgame version 1.2.6 in which this demo will be fully integrated.

Hope you like it, and please I would love to get any feedback!

If anyone has this issue and you are trying to use multiple join / left rooms like I was doing, make sure to always be joined in one room.
In my case I was leaving one room before join the next one, so I moved the oldroom.leave() action inside the newroom.onJoin() and now everything works fine.
Note, this was happening randomly at the beginning until I overloaded the room onInit with data, then I got the issue all the time because the second room was delayed on load.
Best,

Hi everyone,
From time to time and very random I'm getting:
colyseus.js: client left room before receiving session id.
It's really weird, everything works 8 or even 9 of 10 times, and suddenly... crashes...

I'm assigning the game client into a global variable:
window.gameClient = new Colyseus.Client(location.protocol.replace('http', 'ws')+host+(location.port ? ':'+location.port : ''));

And then on document ready, when the user submit the form I try to join the first room:
window.gameClient = new Colyseus.Client(location.protocol.replace('http', 'ws')+host+(location.port ? ':'+location.port : ''));

You can see the code here:
https://github.com/damian-pastorini/dwdgame/blob/dwdgame-master/client/client.js

Any ideas why it could be happening?

Thanks!

Yes, same here, even tried to open two browsers and even doing that wasn't able to access :(

Hi @endel thanks for you quick reply, as you said... yeah.. too many issues already LOL
I'll go for the database option to persist the data between room changes, I'm working on it now, the idea is to save the player progress > leave the room > join the new room > re-authenticate the user with the data in the session and reload the progress.
I though it will be too expensive in terms of server response time, but keep a room or persist too much information in the presence could end up been even more expensive than just hit the DB to get the data.
Best,

Hi @endel , one more question: let's say I'm on the Room1, and then I join Room2, is possible in the server side to access the data that's already in the Room1?
Because in the examples you have something like room.state.players[client.sessionId], so I would like to know if it's possible to access the data in first room from the second, maybe using super.allRooms[roomId] or something like that?

Thanks!

That's great!!! Thank you @endel ! :D
I'm still struggling on how to change rooms and keep using the same logged user data, and in between I broke my Phaser implementation, so I'll probably rollback my last changes and start again just by using the presence methods.
I'll keep you posted on how it goes and let you know as soon I get a working sample.
Thanks again!

Ok, I think I was able figure it part of how to do this by reading other posts...
For reference: https://discuss.colyseus.io/topic/149/using-multiple-rooms-to-support-one-large-map/10
There says to use room.presence functions for multiple rooms, so now I'm able to check if the user really left the first room before allow it to join the second with something like if(this.presence.keys[roomId+':'+client.id]), will this be ok?
There's none documentation about any of this, all I saw about presence there was related to the server and Redis, which I don't think it's the same, right?
Best,

For join/leave room procedure, I do it by sending message from client to server or vice versa first, then close the connection in both sides, which is not nice :/.

Yeah, exactly, I saw the client.leave and room.join on the client side, and the Room.close on server side, but I wasn't able to get for example a rooms list on server side from inside a room. Do you know if there's a way to do that? Or do you have any ideas on how to do it?

Best,

Hi @halilbilgin , thanks for your reply!

Well, I use a traditional way for that. I produce a token for each client when they first login to the server. Then, they use the token and their ID whenever they join to a new room. Following that, the server checks if ID&token pair exists in the DB.

That will be the same as use the user/password from the user object on the server side (which I don't share on the client) and hit again the DB. Even when that's is just a cheap query it will be still a query and a Promise to wait for information.

Another easy thing would be to have a global object in the server that is independent of any room, which keeps stores the credentials of the users. You can use such global objects to check if a user is already authenticated.

This is more like what I'm looking for, that's why I was thinking to use something like a "logged-users" room, as something global. That's why I was asking if Colyseus has something like this already implemented or if I will need to extend the Colyseus server class to make a custom implementation on my own (if this is the case it will be something that I would share later), but the way I see it, it could be something as part of Colyseus "core".

Also I didn't find any good join/leave rooms flow sample, so maybe I'm missing something?

Thanks!