administrators

Hi @LukeWood, welcome!

You'd be better off setting a filter for matchmaking, and use joinOrCreate() normally.

First, you need to define your room, with the "code" filter (you can use any identifier, I'm using "code" just for the sake of this explanation).

The filterBy() below means that the available list of rooms is going to be filtered accourding to the options provided by the client. (See the docs)

gameServer
  .define("match", MyMatch)
  .filterBy(["code"]);

Then, you can have an "code" provided by the client-side, and provide it to .joinOrCreate("match", { code: "ABCD" }).

There are many ways to achieve that - you may need a service to make sure these ids are unique, or you can just generate long enough ids in the client-side and hope they won't collide.

Hope this helps, cheers!

Hi @boygiandi, this error is likely to be coming from your application. If you're using TypeScript, the compiler should be able to warn you where the issue is.

This could be happening if you have if (yourConstant = x) instead of if (yourConstant == x) for example.

Hi @BlueBang, you should be able to call .toJSON() on your root Schema instance. Does that help?

@Zielak have been working on one for quite some time 👀 https://github.com/Zielak/cardsGame

Hi @gkanwar, the way I usually approach it is by unit testing the structures that will be inside your Room implementation. I usually do not do end-to-end testing with real WebSocket connections.

For a card game I've been working on, I manually trigger a @colyseus/command (or other patterns of your choice) to manipulate the state, and then perform some assertions on the mutated state.

Both server-side and client-side of Colyseus have been evolving, and by doing end-to-end testing it's likely that you'll need to re-do a lot in order to upgrade to a newer version. (version 0.13 is coming soon!)

Hope this helps, cheers!

Hi @boygiandi, what do you mean? Each Room creates a WebSocket connection, by leaving that Room, you're disconnecting that WebSocket.

On previous versions of Colyseus (0.9.x and below) the Client also had a WebSocket connection, this is no longer the case on recent versions. Match-making happens via HTTP requests.

Hope this helps, cheers!

Hi @meetsreekanth, filters are experimental right now, but it should work for the use-case you've just described.

I think the order of your parameters is not correct, the filter callback type looks like this:

export type FilterCallback<
    T extends Schema = any,
    V = any,
    R extends Schema = any
> = (this: T, client: Client, value: V, root?: R) => boolean;

It's also important not to use arrow functions on filters, so this should work:

@filter(function (this: PlayerTurn, client: Client, value: ArraySchema<Card>, root?: GameState) {
  return // ??
})

Hope this helps, cheers!

Hi @boygiandi, not the gameServer, but you can access the matchMaker via:

import { matchMaker } from "colyseus"

Hi @codestitch, to allow the client to reconnect to the room he was previously connected with, you'd need to use allowReconnection(): https://docs.colyseus.io/server/room/#allowreconnection-client-seconds

Hi @BlueBang, this lacks documentation indeed.

I assume you're talking about the JavaScript client (colyseus.js). Here's how you can remove the listener:

var callback = (message) => {/* ... */}

// attach listener
room.onMessage(callback);

// remove listener
room.onMessage.remove(callback);

Cheers!