Updating both server and client to 0.15 has done the job.

Thankyou for your time

Set up an email account to use for sending the error messages. You'll need to know the email address and password, as well as the SMTP server settings for the email provider.

In your application, catch any unhandled exceptions using a try-catch block. This will allow you to handle errors and take appropriate action, such as sending an email with the error details.

try
{
// Your code here
}
catch (Exception ex)
{
// Handle the error and send an email
}
In the catch block, create an email message with the error details, including the exception message, stack trace, and any other relevant information. You can use the System.Net.Mail namespace to create and send the email.

using System.Net;
using System.Net.Mail;

// Create the email message
MailMessage mail = new MailMessage();
mail.From = new MailAddress("your_email_address@example.com");
mail.To.Add("recipient_email_address@example.com");
mail.Subject = "Application Error";
mail.Body = "An error has occurred in your application:\n\n" + ex.Message + "\n\n" + ex.StackTrace;

// Set up the SMTP client
SmtpClient client = new SmtpClient();
client.Host = "smtp.example.com";
client.Port = 587;
client.UseDefaultCredentials = false;
client.Credentials = new NetworkCredential("your_email_address@example.com", "your_email_password");
client.EnableSsl = true;

// Send the email
client.Send(mail);
Make sure to test your error handling code thoroughly to ensure that it works as expected.
Note that sending emails for every error may not be practical, as it could generate a large number of emails. You may want to consider implementing a more sophisticated error logging and notification system that aggregates errors and sends periodic reports instead. I use this in my work on Chrome getprospect extension and it helps me a lot )

Thanks for your reply, actually i need information about @deprecated.

Live Version 1 :-

import { Schema, type, deprecated } from "@colyseus/schema";

class MyState extends Schema {
@type("string") myField: string;
}

LIVE VERSION 2 :-

import { Schema, type, deprecated } from "@colyseus/schema";

class MyState extends Schema {

}

How can achieve this in javascript.

This was reported months ago.

this is the code I have set on the client side
and This function is subscribe in "GameplayRoom.State.players.OnAdd += OnPlayerAdd;"

Is there any way to add POST to allowed methods with this configuration? Or may be it is better to move to self-hosted option?

https://discuss.colyseus.io/topic/847/服务器创建固定房间-不会销毁-不允许客户端创建房间等需求

We then setup listeners for the bot similar to how the actual client listens, like when a card is played then do something.

Generally we try to avoid treating the bot differently from an actual client which makes our workflow and loadtesting much easier as the game does not care what kind of client has joined + we can offload bots to a different process or server if needed.

We leave it up to the matchmaker if the game needs a bot then simply create one and join them to the room, to the player they look exactly the same as a real player. We also have special Bot rooms where the client might want to intentionally play against a bot, like in a campaign.

Here, we simply extend the base game and have the bot join as part of the joining logic, i.e, we create and join the bot once the player has joined the room.

If there is anything specific you would like me to expand on then I will try to get back to you.

Whenever a players x or y is updated i run this function which is inside the player class on the server.

It essentially loops through all the other players in the room, and compares their x and y coordinates to the 1 player who just moved. If the other_players.x is < (player.x-0.4) && other_players.x is < (player.x+0.4) that means they are touching in terms of x axis (my players are about 1 unit wide.

then if other_players.y is < (player.y-0.2) && other_players.y is > (player.y-0.5) that means my player is higher than them at about head level. You would have to play with the values depending on your character size

If both of these are true i run the function to kill them and send that message to all the connected clients where they can vanish the player. I also add them to an array with a timeout so that if they are in that array they cannot be killed again within 2 seconds

Hope this helps someone!

Im using sdk for unity webgl build
I want to remove remote players when they close tab from system browser or phone browser.
I saw the mmo-unity example and it works in that case
As im beginner I couldn't understand how its implemented

Thanks!

Error: room "SFuMjng78" not found
at new MatchMakeError (/var/www/Server/node_modules/colyseus.js/lib/Client.js:61:28)
at Client.<anonymous> (/var/www/Server/node_modules/colyseus.js/lib/Client.js:185:35)
at step (/var/www/Server/node_modules/colyseus.js/lib/Client.js:46:23)
at Object.next (/var/www/Server/node_modules/colyseus.js/lib/Client.js:27:53)
at fulfilled (/var/www/Server/node_modules/colyseus.js/lib/Client.js:18:58)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:94:5)
left y9BSgj4jF vp1ZqNWC8
left y9BSgj4jF uGzjwVgVa
left y9BSgj4jF 9fOJ5SdoC
left y9BSgj4jF Yvip_paAz
left y9BSgj4jF JaRwqtFrR
left y9BSgj4jF lYL3rY1cm
left y9BSgj4jF igZyCtr8n
left y9BSgj4jF VG_XLxXhd
2023-03-06T12:03:32: PM2 log: App name:Server id:1 disconnected
2023-03-06T12:03:32: PM2 log: App [Server:1] exited with code [1] via signal [SIGINT]

I am trying to avoid as much as possible data updates from the server. In my game, I'd like to mark a field "position" of game entities in a manual way, some like "entity.pos.sendUpdate()". Because I don't need every position all the time, because th client can calculate by itself, but I need them to be present. Also, a nice feature also would be you can set a "patchRate" for a specifics schemas: Some examples I can think of

@type("number", patchRate= 500)
"updates this number every 500ms, or when you call sendUpdate() manually in the next inmediate main path upddte, and when the client first synchronization"

@type("number", pathRate: 0)
"only update manually and in the first state sync"

Sorry if there are sintax error, take that as a pseudocode, since Im currentry in the smartphone.

There might be a way to do that with the current version of colyseus, but I wasn't able to find it.

My best try was, to set 2 position attributes, one marked as "type" and not the other, so I can schedule manually the synchronization, but it becomes a mess quickly.

Some examples for games that don't need every update from the position of the player I can think of: Old School Runescape / Rucoy online (the server sends the calculated path but not every change of the player position) (well, I am almost sure)

Thanks in advance!

The game we're developing on Colyseus and PlayCanvas runs within a corporate intranet. The players are facing issues after the corporate firewall cuts off the websocket connection after it sees say... 15 mins inactivity. For some reason, the clients have difficulty reconnecting when that happens.

Can I have some clarity on what the ping interval really means?
Assuming the default of 3 seconds for the ping interval:
Does it mean:
a) how often the server pings the client
b) how much time is tolerated for inactivity i.e. if the client don't make any calls to the server for a period of 3 seconds, it's considered inactive and it's given "retry" i.e. server gives the client another 3 more seconds, after which it is considered inactive.

In the context I described, I was thinking of doing a regular websocket "ping" to the Colyseus server every 30 seconds just to register some activity on the websocket. Do you guys think it's a good idea or it's really unnecessary?

Thanks for your tips/suggestions.

To resume the situation, I have a Schema (team) which contain an ArraySchema (players). When a user click on a button he will join the team and he will be added to the ArraySchema mentionned above to become a player.

When the user left the application, I added a function to splice the ArraySchema mentionned above at the exact index of that player. To make sure that the player is correctly removed from the ArraySchema, I added a console.log in the onRemove callback.

Now, when a new user logging and click on the button to join the team, the player index should be the current amount of player. However, the index of the player is always increasing even if I remove multiple items from the ArraySchema. Am I missing something? Thanks :)

Here's a little snippet to showcase the structure:

Thanks,
Mitch