Hi @Enriqueto, a Godot client is on the radar but I think there aren't many users right now to justify the time put into it.

Are you already using Godot or just considering it for the future @Enriqueto?

Cheers!

Hi @kukuts, glad you're trying out the proxy. At the moment the proxy is going to distribute the load equally between available servers via round-robin. Currently, there is no fancy distribution based on CPU load, number of spawned rooms, or anything like that.

So a "new room" request can end up being forwarded to a node that's already quite busy. I believe the current node discovery structure can evolve for a more mature/fancy way of distribution in the future.

Cheers!

Hi @hlarcher,

Here's a modified version to work on v0.11:

// no assignment, as the return value is Promise
this.client.joinOrCreate('battle', {team}).then(room => {
    this.room = room; // here's the room instance!

    // on join has been successful already!
    this.onRoomJoin(team)
    // room.onJoin(() => this.onRoomJoin(team));

    room.onStateChange((state) => this.onRoomStateChange(state));
    room.onMessage((message) => this.onRoomMessage(message));
    room.onError(() => this.onRoomError());
    room.onLeave(() => this.onRoomLeave());
}).catch(e => {
    console.log('---> JOIN BATTLE FAILED!!!: ', e);
});

Hi @hlarcher, this error is most likely to happen when having a previous version of @colyseus/schema listed under your package-lock.json. Please remove your package-lock.json + node_modules, and run npm install again. It should get rid of this error. Cheers!

Hi @elberto, this is actually a bug in the server as of 0.11.x (related to #260). This is going to be fixed on 0.12.x next year.

For now, you can do this:

onJoin() {
    if (this.hasReachedMaxClients()) { 
        this.lock()
    }
}

Hope this helps! Cheers!

Hi @MamaCatDev,

I've just replied on the original GitHub issue from @gioragutt, saying this:

As of 0.11.4, it is possible to retrieve the metadata from the client-side by defining a custom RoomAvailable + Metadata types.

Example:

[Serializable]
class Metadata
{
	public string mode;
	public string name;
}

[Serializable]
class CustomRoomAvailable : RoomAvailable
{
	public Metadata metadata;
}

var roomsAvailable = await client.GetAvailableRooms<CustomRoomAvailable>(roomName);

for (var i = 0; i < roomsAvailable.Length; i++)
{
    // getting metadata
    Debug.Log("metadata.mode: " + roomsAvailable[i].metadata.mode);
    Debug.Log("metadata.name: " + roomsAvailable[i].metadata.name);
}

The metadata comes from a JSON response from the server. Unfortunately, the built-in JsonUtility from Unity has limitations regarding the usage of generic types, making it necessary to create a new type having its own hardcoded Metadata type defined on it. (here's the method to decode the JSON response)

If you think the API can be improved please don't hesitate to share your thoughts.

Hello everyone!

Me, @AnubisCode and his brother Stanislav (artist and animator) wanted to make a multiplayer game in a "game jam" style. Initially, we wanted the game to be super simple and finished within a month of work. We've got the first prototype in a few weeks, and it didn't meet our expectations. Then we decided to change the game entirely. In the end, we spent around 2 months (+3 months of pause) to make a quite polished version of it 😅

We're glad to finally announce the first playable version of PartyToons.io! The game is inspired by Mario Party, Pokemon Stadium Minigames, and such. We have 5 mini-games implemented so far:

Gameplay video:

Playable link: http://partytoons.io/

We're using Defold for the client-side :)

Feedback is very welcome! Also if you have any questions, let us know! 🤗

Well done @halftheopposite! 👏👏👏 Thanks a lot for sharing!

Version 0.11.14 is now using the internal ip instead of external. Can you check if it works for you now? Cheers!

Hi @nguyen991,

This pull-request recently introduced using public-ip to expose the address for the proxy: https://github.com/colyseus/colyseus/pull/264

Maybe we should use the internal-ip package instead of public-ip? Could you try this out? Cheers!