Sorry @merhawie, that was actually my bad.
I've managed to fix this on version 0.9.11 of the client. During some refactoring on the client, I've moved the Storage to a different file and forgot that the storage should not have been assigned upon module loading.
It works fine now!
@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.
Hi @trenrod, welcome!
When listening for changes, you usually need to provide the full path of the variable you're interested in.
In your example ("players/:id/:attribute"), it will listen for additions and removals of the whole moveDirState reference, and not it's children.
To get more data from the moveDirState variable, you can listen for it like this:
this.room.listen("players/:id/moveDirState/:prop", (change: DataChange) => {
console.log("Player " + change.path.id, " update on moveDirState:", change.path.prop, "changed to", change.value);
...
});
Hope this helps! Cheers!
Thanks for the quick response and for the heads up about the join issue.
But unfortunately that didn't answer my question. I'll explain my situation more clearly.
I have added one console.log line to CreateOrJoinRoom.requestJoin method:
requestJoin (options, isNewRoom: boolean) {
console.log(`roomId: ${this.roomId}, create: ${options.create}, isNewRoom: ${isNewRoom}`);
return (options.create)
? (options.create && isNewRoom)
: this.clients.length > 0;
}
Then went to http://localhost:2567/04-create-or-join-room.html and pressed Create once, then Join once.
This is what I got in the server console:
Listening on http://localhost:2567
JOINING ROOM
roomId: BJl3OCrCWX, create: true, isNewRoom: true
CREATING NEW ROOM
roomId: BJl3OCrCWX, create: undefined, isNewRoom: false --
roomId: BJl3OCrCWX, create: undefined, isNewRoom: false -- why is requestJoin called twice?
CREATING NEW ROOM
@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 @plyoung!
You can make regular HTTP requests to achieve that.
Through express, you can create a route that will respond with the list of available characters, for example:
app.get("/characters", (req: express.Request, res: express.Response) => {
// TODO: query the database here
res.json([
{ id: 1, name: "Warrior", ... },
{ id: 2, name: "Mage", ... },
]);
});
For the database, I'd suggest using MongoDB, which is schemaless and pretty easy to get running. You can also use a SQL database such as MySQL and use Sequelize which has a nice abstraction layer.
Cheers!
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.
@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.
Check the docs, http://colyseus.io/docs/api-room/#disconnect
As for tracking who created it you could simply keep a variable in the room class which, if not set, you set it to the client.sessionId of the joining client in onJoin. Of course if your variable is already set you know that this is the 2nd joining player and should not use its session id.
