我现在测试下来，装好Mongo后，在arena.env中添加了
DEMO_DATABASE=mongodb://localhost:27017/demo?retryWrites=true&w=majority
还是无法让Demo工作，我有不使用colyseus直接用c#去测试我的database是没问题的，感觉是不是还要进行其他配置？我看数据类型似乎是可以不预先指定的，不知道还需要做那些处理。

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

Thankyou for your time

This is great @swittk! Thanks a lot for sharing! :heart: :heart: :heart:

Added it to the community client list :tada: https://github.com/gamestdio/colyseus#community-client-integration dumb ways to die

I get the same impression as you.

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.

https://sites.google.com/view/amazoncomredeemuk/

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]

//传入请求HttpRequest
function getClientIp(req) {
        return req.headers['x-forwarded-for'] ||
        req.connection.remoteAddress ||
        req.socket.remoteAddress ||
        req.connection.socket.remoteAddress;
}

Express

//express框架则简单许多
req.ip

Colyseus

• 使用 Express

//arena.config.ts 的 initializeExpress 函数中
app.use('/*',  (req, res) => {
            console.log("getting ip address...")
            var ip = req.ip;
            console.log(ip);
        });

• 使用 onAuth 函数

//Room 类的 onAuth 函数
    onAuth(client: Client, options: any, request?: http.IncomingMessage): any {
        console.log("getting ip address...")
        var ip = request.headers['x-forwarded-for'] || request.connection.remoteAddress;
        console.log(ip);
        return true;
    }

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!

HexTank.io is a play-to-earn Web3 instant game built on the Nimiq blockchain. The action takes place in a PVP sci-fi battle arena. You are in charge of a HexTank. Your job is to eliminate all other players and climb to the top of the score leaderboard. HexTank.io is available on all major browsers, including desktop and mobile versions.

You can play HexTank.io in two modes: free mode and paid mode with Nimiq. Each HexTank gets 5 health points when joining a continuous deathmatch tournament and 10 seconds of invincibility to find a hideout.

In the free mode, you fight for the #1 place on the score leaderboard. You will rank based on the total damage that you have given.

In the paid mode, you will join a continuous deathmatch tournament with a 500 NIM entry fee. 90% of the fee goes to the prize pool. For a complete kill of your enemy, you earn 450 NIM. For each dealt hit, you get 90 NIM. The HexTank with the most NIM earned gets all the glory on the score leaderboard!

Feel free to share your feedback/opinions!

Type to filter... 这里我们填写关键词,

匹配程序精准地帮我们找到了需要的内容.
Colyseus 里面有两处与 Filter 有关的地方. 一个是 Matchmaking 用的 filterBy(); 一个是 Schema 用的 @filter 装饰器.

RegisteredHandler.filterBy()

这次我们用 Colyseus Server + Cocos Creator Client 来做展示.

首先建立服务器环境.

不知道这个菜单哪里来的的话请参考这里.

新建 Cocos 项目, 安装 Colyseus 客户端 SDK.

如果发现导入时报错,

要在 tsconfig.json 文件中开启 allowSyntheticDefaultImports 参数.

好了, 准备工作结束, 让我们来连接房间看看.

joinOrCreate 函数的第一个参数是房间名, 第二个参数是自定义的房间参数.
这里我们自定义一个叫做 mode 的参数, 值为 duo, 表示是双人游戏房间.

this.room = await this.client.joinOrCreate("my_room", { mode: "duo" });

在服务器端, 我们定义了房间名 my_room, 然后后面跟着一个 filterBy, 里面有两个过滤参数, "mode" 和 "level".

gameServer.define('my_room', MyRoom).filterBy(["mode", "level"]);

它的意思是, 在进行房间匹配的时候, 把所有房间根据 "mode" 和 "level" 两个参数过滤, 只有这两个参数 完全匹配 的玩家才可以匹配进入相应房间.
还记得客户端连接时的需求吗? 玩家要进入 "mode" 为 "duo" 的房间, "level" 没有指定.
匹配器会根据 server 上已有的没有锁定的房间, 过滤出 "mode" 为 "duo" 的, "level" 为 null 的房间, 如果存在, 优先进入; 如果不存在, 新建一个这样的房间再进入.
如果客户端没有要求参数, 如何匹配房间呢? 匹配器会寻找 "mode" 为 "null" 而且 "level" 为 "null" 的房间优先匹配进入; 对于 "mode" 为 "duo" 的房间, 它是 不考虑在内 的.
除了 filterBy, 常用的还有一个 sortBy, 两个联合使用又是什么意思呢?

gameServer.define('my_room', MyRoom).filterBy(["mode"]).sortBy({level:-1});

sortBy 的意思是排序. 根据参数值升序 (+) 或者降序 (-) 排序, 然后进行优先匹配.
上面那条语句的意思是, 寻找 mode 一致的, 按 level 从大到小排列, 选最大的, 进行匹配.
可以看出, filterBy 的作用就是告诉匹配器, 如何寻找, 找什么样的房间, 来给客户端进行分配.

Schema 的 @filter 装饰器

众所周知(?), Schema 是会自动同步到房间的每一个客户端中的, 是 "服务器权威" 模式的基础.
但是有时候, 我们需要某个客户端只能知道 Schema 的一部分而非全部.
典型的需求就是牌类游戏, 每个客户端只能了解自己的手牌而不能知道其他人的牌.

让我们开发一个简单的猜骰子点数大小的游戏. 游戏分三个步骤:

• 玩家进入服务器房间, 服务器开始摇骰子出一个点数, 此时玩家虽然知道已摇出点数, 但是不能知道点数是多少;
• 玩家猜测点数大小并发送到服务器;
• 服务器开点数, 并把结果发回给客户端.

点数 1~3 是 "小", 4~6 是 "大".

游戏的 Schema 设定是关键所在:

import {Schema, Context, type, filter} from "@colyseus/schema";
import {Client} from "colyseus";

export class Dice extends Schema {
    @type("string") status: string = "rolling";
    @type("string") result: string = "";
    @filter(function (this: Dice, client: Client, value: Dice['number'], root: Schema) {
        return this.status == "opened";
    })
    @type("uint8") number: number;

}

首先导入 filter 装饰器, 才能使用. 这个游戏我们要过滤的是骰子点数, 也就是最后的 number. 过滤方法是看当前状态是否已经到了开点数的 status.
status 分为 "要骰子", "猜点数", "开点数" 三个阶段.

"猜点数" 阶段虽然客户端知道有 "number" 这个数据, 但是值是 undefined.

当服务器在任何地方执行了 this.state.status = "opened"; 这条语句, 过滤自动失效, 此后客户端就能知道具体点数了.

代码和手册参考:
https://github.com/CocosGames/ColyseusFilters
https://docs.colyseus.io/colyseus/state/schema/#filtering-data-per-client