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 :)

Alright! Considering how much behind the v3 was getting I've decided to do a beta release for v4! This version is available on NPM: https://www.npmjs.com/package/reldens And the installation is easier than before: https://github.com/damian-pastorini/reldens/wiki/New-v4.0.0-beta.6-Installation For that matter I've created an Skeleton repository: https://github.com/damian-pastorini/reldens-skeleton The dev server was updated as well http://dev.reldens.com And between all the huge refactor now you will find: Almost everything now works based in events, so this will allow you implement a lot of customizations without need to rewrite almost anything. In any case there are still some configuration files and the idea of having a "game-theme" was implemented, so you could easily use the skeleton theme for start. At the same time a lot more stuff is now configurable just by changing some values in the database. Maps animations were implemented (in the skeleton example you can see the river moving). Objects with animations are also available in both public (broadcast), and private (for single client). For example: the doors will open > the player will change the room > but for the other users that are seeing the door open, a few seconds later the door will be closed. A basic NPC was implemented. NPC's are used like another object type that will just respond on specific actions. In the skeleton example you can click on the NPC (the guy with the hat) and it will show a message. Targets System was implemented, you can click on any player or NPC, and the target will be selected. With targets, short distance attacks are now available, if you are close enough to a player and click on it, then you can click on the action button or press the space bar to attack (for now we only have that action). Related to attacks, the stats are now affected, atk and def are (for now) simple compared to validate the attack, and when the attack success (for now always since the atk and the def are the same for all the players), the HP will be reduced. And for last! Now we have the Game-Over event when a player that die will be kicked out! Sorry, that was the quickest thing I was able to come up with. In terms of roadmap, issues and progress tracking I've started to complete the project board with all the tasks: https://github.com/damian-pastorini/reldens/projects/2 Hope you like all the new improvements, I'll keep adding new stuff and fixing the parts that can be improved. Best, Damian

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.

Ok, I will try to mix with WebRTC. Twilio is not free. ;-) Thank a lot !

Also, if you’re creating separate files to keep your code lean, I created a class with a static variable pointing to the room. In the onCreate event of Room, I assign the static room property. Then I can import that class from any file and use the room methods.

it seams remove @type("number") to some variable makes it private over the network