Hello everyone! I'm back on the project and v4.0.0-beta.7 is about to be released! https://github.com/damian-pastorini/reldens/pull/51 What's included in this beta? Issues fixed! 5 issues were reported and the 5 were fixed https://github.com/damian-pastorini/reldens/issues Battle mode is been implemented, you will be able to start a battle and set a battle time-off which will be considered after the last player attack (still incomplete since there are none rules for what happens on this mode, but it's already available to setup any). PvP with (for now), short distance attack was implemented using the battle mode. A new "Forest" map was included with some enemies. PvE is still in progress but will be available with the beta.7 release. A path finder was implemented (though it still can be improved, it's working for a start point), now you can click on the scene and the player will move to that point. With this implementation enemies will also go after you. Health bar is now visible for the current player. Some new animations are been implemented and others were fixed: hit player and die. All dependencies were updated: Colyseus 0.12.x, Phaser, etc. Here's a small video to show you the progress!

It would be nice if video training about scaling is added

Hi @enishi , how do you handle the 3d on the server side? I don't have a clue about Unity, just been curious about it.

Pass Player.prototype to filter() in Javascript. There is no need to modify code.

Hopped on a chat in discord with @endel. Definitely a stand up guy! I really appreciate his help and this library is working exactly as advertised. He discovered that my real problem was due to referencing some of properties in the rooms' state in messages that I was sending to clients. For example, earlier you can see how I am sending ShortDeckWagerStateChanged. That message has properties that references properties in my state which is wrong. From what I understand this will run the schema encoding logic and leave my state altered. If I really wanted to do that then Schema has a clone() method on it but I didn't investigate doing that.

@endel I am also looking at using Godot for a new project. So a Godot integration would be nice.

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!

Awesome, thanks :)

Hi @endel, thanks for your quick answer. I understand why I was struggling now ! With your fix, I still can't deliver my messages to all clients. For now I did this on async for testing purposes, but it's really ugly and unreliable if (this.hasReachedMaxClients()) { setTimeout(async () => { for (let sessionId in this.clients) { this.send(this.clients[sessionId], { message: "Hello world!" }); } } }, 1000); If you have a better way, I'll take it ! Have a nice day !

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.