Awesome @halome, it's looking good! Another option would be MatterJS: https://github.com/liabru/matter-js

Good luck with your project! Don't hesitate if you need any help with Colyseus here!

Hey @rscata, I've just released a new version (colyseus@0.8.13, see release) which adds the isNew parameter on requestJoin. With this version you'd be able to achieve the same result by having this implementation:

// ... maxClients = 4; requestJoin (options, isNew) { return (options.create && isNew) || this.clients.length > 0; } // ...

@endel said in colyseus.js: server error: registeredHandler.klass is not a constructor:

Or by exporting the room usin

I'll try it the week end and come back to you later.
Thx for the help so far.

@umen we have 3 servers now (each droplet of DigitanOcean 1 vCPUs 1GB / 25GB Disk), each server can keep about 500-600 users, but it's depends on logic of your server.

@endel I was looking at this in a tired state, but im pretty sure i had fully updated client and server. Ill double check what i was seeing and if i still have an error I'll open an issue on the github. Thanks for the response.

@Алексей-Андронов the clock only works if you set up the simulation interval.

I guess that's not intuitive, I'll fix this on version 0.9.0 too.

@Carlos-Montesino, i've tried your endpoint (wss://carmenproject.herokuapp.com) but it is not working properly.
the "please wait" text is not destroyed. it seems that it is cannot join any room.

Thanks

@lezanardi

function setEnumerable(object) { let private = {}; for (let key in object) { Object.defineProperty(private, key, { value: object[key], enumerable: false, writable: true }); } return private; }

Will return the passed object with all the items non-enumerable.

I have no idea if we do not have access to "getAvailableRooms". If we did then you could simply have the client make that call every few seconds or minutes to get a fresh list.

Hi @endel thank you for the quick response. will keep track of the issues.

But things like updating player movement wouldn't need to be that reliable. I understand that things like interpolation could be used but it's still going to make something like an FPS too glitchy.

@rscata I meant 1000 per server.

I recommend checking the matchmaking docs to understand how the room instantiation works: http://colyseus.io/docs/concept-matchmaking/

You can follow the links from there and hopefully you'll be ready to code your own solution!
Cheers

@Burjee-Bataa this should do:

var room = client.join("room_name"); // ... room.leave();

@talothman I had a similar issue. I realized that the client is trying to instantiate the player twice. Add this to the top of your OnPlayerChange in the "add" opratin:

if (players.ContainsKey(changePathId)) { return; }

@endel thank you very much

Hi @endel ! Thank so much!

@rscata alright! One thing that is not intuitive in this version is that you can only see the error messages and stack traces if you turn on DEBUG=colyseus:errors

DEBUG=colyseus:errors npm start

oh, I see.. Use "in" rather than "of".
It looks much better now. Thanks.

@endel thanks!