受信任客户端
一款轻量级的反作弊/客户端扫描模组,在玩家加入服务器时显示其已安装的模组。
工作原理
当客户端连接到服务器时,客户端需要响应服务器发送的特定数据包。如果客户端未能响应,则被视为未运行该模组,并会被断开连接,同时收到提示安装 Trusted Clients 模组的消息。
当安装了该模组的客户端尝试加入时,它将被提示向服务器发送已安装模组的列表,随后服务器将检查这些模组是否与服务器管理员配置的服务器设置兼容。如果客户端存在被禁止的模组,它将被断开连接,并收到移除相关模组的消息;如果客户端没有任何被标记的模组,则可以正常加入。
我需要做什么?
该模组完全可通过位于 SERVER_ROOT/config/trustedclients/main.json 的配置文件进行配置。具体操作取决于您的需求:
我只希望允许某些模组
将 mode 设置为 "WHITELIST",并将您希望允许的客户端模组添加到 modList 中。服务器上已存在的模组会自动被允许。
我希望允许除某些模组之外的所有模组
将 mode 设置为 "BLACKLIST",并将您希望禁用的客户端模组添加进去。服务器上已存在的模组无法被列入黑名单。
我(作为服务器管理员)需要其他玩家不应使用的模组
使用上述任一方法,并在配置文件的 bypass 列表中将自己的用户名添加进去。这将使您能够绕过整个检查系统。
旧版文档
旧版本 (Forge 1.20.1)
(原名)EasyAntiCheat
一款轻量级、简单却功能强大的 Forge 反作弊工具,为服务器管理员提供对客户端已安装模组和资源包的监管能力。
⚠️ 免责声明
此模组并非旨在抵御熟练的黑客攻击。相反,它是一种基本的应对措施,主要针对脚本小子及类似的低级威胁。其设计目标是简单易用,并不能完全消除服务器上的黑客风险。
工作原理
该模组通过客户端在连接时向服务器发送已安装模组和资源包的列表来工作。服务器随后会记录所有安装在客户端但未安装在服务器上的模组和资源包。如果功能已启用并通过配置文件正确配置,当服务器所有者不认可的模组出现时,它还会采取自动行动。
它的用途是什么?
其主要目的是通过日志机制让服务器操作员快速识别不需要的模组。但由于这仅在小规模服务器上有效(因为需要人工监督),因此还具备白名单/黑名单功能,以自动化识别广泛传播/已知模组或协助操作员。
配置
配置文件位于 ./config/ezac-common.toml。所有选项均有注释说明,因此您可以轻松修改它们以满足需求。
下方是一个示例配置,使用了 WHITELIST(白名单)mode,这意味着只有 mods 数组中的模组才被允许在服务器上运行。由于 mods 为空,所有仅存在于客户端的模组都会被标记,这意味着任何不在服务器上但存在于客户端上的模组都会被标记。服务器上允许的资源包定义在 resourcePacks 列表中。在此示例中,只有名为 "TotallyLegitResourcePack.zip" 的资源包才被允许在服务器上运行。action 设置为 RESTRICT,这意味着只要客户端安装了被标记的模组,玩家将无法加入,但在移除这些模组后可以再次加入。
["Server Configuration"]
# 应添加到黑名单或白名单中的所有模组列表。
mods = []
# 应添加到黑名单或白名单中的所有资源包列表。
resourcePacks = ["TotallyLegitResourcePack.zip"]
# 列表中的模组应如何处理?
# BLACKLIST 将标记客户端列表中所有的模组。
# WHITELIST 将标记客户端列表中不包含的所有模组。
#Allowed Values: BLACKLIST, WHITELIST
mode = "WHITELIST"
# 当玩家使用被标记的模组时,应采取什么措施?
# NOTIFY 将在控制台记录被标记的模组(并向操作员发送消息)。
# RESTRICT 与 NOTIFY 相同,但会额外拒绝每次使用被标记模组加入的玩家。
# BAN 也与 NOTIFY 相同,但比 RESTRICT 更严厉,它将封禁玩家,一旦他们使用被标记的模组加入,除非获得操作员赦免,否则永远无法再次加入。
# 这仅在选择的模式为 BLACKLIST 或 WHITELIST 时生效。
#Allowed Values: NOTIFY, RESTRICT, BAN
action = "RESTRICT"
Trusted Clients
A lightweight anti-cheat/client-scanning mod which shows client installed mods on the server when a player joins.
How does it work?
When a client connects to the server, the client needs to respond to a certain packet sent by the server. If the client fails to respond, it is deemed as not running the mod and will get disconnected with a message stating that they should install the Trusted Clients mod.
When the client tries to join with the mod installed, it will then get prompted to send a list of mods installed on the client to the server and the server will consequently check whether the mods are compatible with the server configuration set in place by the server admins. If the client has disallowed mods, it will get disconnected with a message on what mods to remove, if the client has no flagged mods, they will be able to join just normally.
What do I have to do?
The mod is fully configurable via the config file located at SERVER_ROOT/config/trustedclients/main.json. From here it depends on what you want:
I want to only allow certain mods
Set the mode to "WHITELIST" and add all client-side mods that you want to allow to the modList. Mods that are already on the server are automatically allowed.
I want to allow all mods except for some
Set the mode to "BLACKLIST" and add all client-side mods that you want to disable. Mods that are already on the server can't be blacklisted.
I (as the server admin) need mods that other players shouldn't use
Use any of the methods described above and add your Username to the bypass list in the config. This will let you bypass the entire check system.
Legacy documentation
Old Version (Forge 1.20.1)
(formerly) EasyAntiCheat
A lightweight and simple, yet powerful AntiCheat tool for Forge, providing server admins with oversight of client-installed mods and resource packs.
⚠️ Disclaimer
This mod isn't intended to act as a defense against skilled hackers. Rather, it's a basic countermeasure aimed at script kiddies and similar low-level threats. It's designed to be simple and not to eliminate the risk of hackers on your server.
How does it work?
This mod works by the client sending the server a list of installed mods and resource packs upon connection. The server will then log all mods and resource packs, that are installed on the client but not on the server. If the functionality is enabled and properly configured via the config, it will also take automatic action when a mod isn't appreciated by the server owners.
What is its purpose?
Its primary purpose is the quick identification of unwanted mods by the server operators through the logging mechanism, but as this is only efficient on small servers, as it needs human oversight, there is also a whitelisting/blacklisting functionality to automate the identification of widespread/known mods or assist the operators.
Configuration
The config file can be found in ./config/ezac-common.toml. All options are described by comments, so you can modify them yourself easily to meet your needs.
Down below, you can find an example config, that uses the WHITELIST mode, which means that only mods in the mods array will be allowed on the server. As mods is left empty though, all client-only mods will be flagged, which means that every mod, that's not on the server, but on the client will be flagged. Allowed resource packs on the server are defined in the resourcePacks list. In this example, only resource packs named "TotallyLegitResourcePack.zip" are allowed on the server. The action is set to RESTRICT which means, that as long as flagged mods are installed on the client, the player won't be able to join, but can join again, after removing said mods.
["Server Configuration"]
# A list of all mods that should be added to either the blacklist or whitelist.
mods = []
# A list of all resource packs that should be added to either the blacklist or whitelist.
resourcePacks = ["TotallyLegitResourcePack.zip"]
# How should the mods in the list be treated?
# BLACKLIST will flag all mods of the client that are in the list.
# WHITELIST will flag all mods of the client that aren't in the list.
#Allowed Values: BLACKLIST, WHITELIST
mode = "WHITELIST"
# What should be done, when a player uses a flagged mod?
# NOTIFY will log the flagged mods in the console (and send a message to the operators).
# RESTRICT will do the same as NOTIFY, but will additionally deny the player everytime they join with a flagged mod.
# BAN will also do the same as NOTIFY, but is a bit harsher than RESTRICT and will ban the player, so once they joined with a flagged mod, they will never be able to join again, until they are pardoned by an operator.
# This will only work, when the mode selected is either BLACKLIST or WHITELIST.
#Allowed Values: NOTIFY, RESTRICT, BAN
action = "RESTRICT"
下载 Trusted Clients
下载 Trusted Clients
下载 Trusted Clients
下载 Trusted Clients
下载 Trusted Clients
下载 Trusted Clients
下载 Trusted Clients
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Trusted Clients
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Trusted Clients
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Trusted Clients
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
- 移植到 26.3
- 自定义列表/集合网络实现,因为之前使用的实现已被移除
- 修复了一个 bug,由于玩家的用户名提取不正确,导致
bypass功能无法正常工作
关于这个资源的讨论、问题反馈与使用心得
还没有讨论,来发第一帖吧
你是这个资源的作者?登录后可认领此资源。
相似资源
模组
显示你正在注视的方块的信息。(适用于 Minecraft 1.16+ 的 Hwyla/Waila 分支)
模组
使用 JavaScript 编辑配方、添加自定义物品、编写世界事件!
模组
查看物品与配方
模组
在游戏画面角落显示附近世界地形、玩家、生物和实体的地图。可创建路径点,帮助你找到标记过的位置。
模组
AE2:一款流行的自动化与存储模组
模组
那是什么?一个 Waila/Hwyla 的分支。
评论 0
登录后参与评分
还没有评论,来抢沙发吧