Hello, each colyseus server will try to get it's ip address from process.env.SELF_HOSTNAME before falling back to internal-ip. In some rare cases it appears internal-ip isn't working, so an easy fix is to set the SELF_HOSTNAME env variable for each server.

ooohhh, I overlooked that when looking at the dispatcher typing. Thank you!

SOLVED! I had "module": "ES6" in tsconfig.json. Changed to "module": "commonjs", and now can find the colyseus.js module. Colyseus is great but configuration files are a nightmare!

Hello @daimonkor I'm using also Colyseus Client on Android, this unofficial portage to Java: https://github.com/doorbash/colyseus-java I've seen you are using Kotlin, did you make your own version from doorbash's library? I'm interested in your Kotlin lib :) Thanks

@endel thanks for quick reply, but keys of map are different. For player I use sessionId and nanoid for bot key.

onMessage returns function that remove listner: var removeListner = room.onMessage("powerup", (message) => { console.log("message received from server"); console.log(message); }); removeListner();

I had a client-side problem. I wasn't passing the property at all.

Did it work?

Clone of https://discuss.colyseus.io/topic/345/is-it-possible-to-run-joinorcreatebyid/2

Thank you, @endel. I will publish another quick question as a new thread if you don't mind.

@endel I even upgraded to latest 0.13 version but still get issues I do know the await reconnection function does fire but something after that blows up. I am using pm2 with a reverse proxy by the way & over SSL

@endel Thank you, I am aware of this. As I understand @colyseus/schema doesn't support multiple classes, right?

For whoever may read this: check the state with room.onStateChange, not right away you are connecting to the room.