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.
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,
Hey @merhawie,
Are you calling client.join() after the onOpen signal, as described here? https://github.com/gamestdio/colyseus.js#react-native-compatibility
@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.
@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.
@endel So, I got this working by calling gameServer.matchMaker.create("game", {}); after registering (I only do this on the second process).
It seems that the you are only subscribing to presence when the room is created. There is no knowledge that a registered handler is registered within presence. So, I have manually created the room on startup.
This probably is not the best way, but it works for now while you can think about how we would want to solve for making the other game servers aware that a room is registered but not yet created.
A colyseus + DB with authentication would be the ideal example IMO
something like the existing tic tac toe example with a simple user creation (DB) and login (authentication) would be enough
and it would be all someone needs to make a complete multiplayer game experience
@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.
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
