AntiSpoof - 高级客户端伪装检测
一款高级、可自定义的 Minecraft 插件,通过品牌分析和频道监控来检测客户端伪装行为
? 目录
? 主要功能
客户端品牌分析
- 品牌过滤:阻止/白名单特定客户端品牌(Fabric、Forge、Lunar Client 等)
- 模式匹配:使用正则表达式识别可疑的品牌模式
- Geyser 验证:检测假装为基岩版客户端的 Java 版玩家
频道监控
- 原版验证:标记声称使用原版但拥有插件频道的玩家
- 频道控制:将特定插件频道加入白名单或黑名单
- 严格匹配:针对特定客户端类型强制执行精确的频道要求
基岩版玩家集成
- Floodgate 集成:无缝支持 Floodgate API
- 前缀验证:通过用户名前缀识别基岩版玩家
- 特殊处理:为合法的基岩版用户配置豁免或忽略模式
高级检测
- 多种检查模式:自定义哪些检查处于活动状态及其严重程度
- 可配置的操作:为每种违规类型定义自定义惩罚命令
- 实时警报:在检测到可疑活动时通知工作人员
诊断工具
- 玩家检查:检查任何玩家的详细客户端信息
- 品牌分析:实时查看和验证客户端品牌
- 频道列表:检查任何玩家注册的插件频道
Discord 集成
- Webhook 支持:将警报发送到您的 Discord 服务器
- 可定制的嵌入:配置颜色、字段和格式
- 全面数据:包含玩家详情、违规原因等信息
PlaceholderAPI 支持
- 客户端信息:从其他插件访问玩家客户端详情
- 检测状态:检查玩家是否正在使用修改后的客户端
- 基岩版集成:验证基岩版玩家状态
丰富的彩色消息
? 下载选项
AntiSpoof 提供两个版本,以适应不同的服务器设置:
完整版(推荐大多数用户使用)
- 包含 PacketEvents 的一体化包
- 无需额外插件
- 简单的即插即用安装
- 文件较大但设置更简单
精简版(适用于高级设置)
- 需要外部安装 PacketEvents 2.7.1+
- 文件大小显著减小
- 防止重复的 PacketEvents 实例
- 非常适合已经使用依赖 PacketEvents 的插件的服务器
- 对于拥有多个基于 PacketEvents 的插件的服务器来说性能更好
两个版本的功能完全相同——唯一的区别是 PacketEvents 是包含在 JAR 文件中还是需要单独安装。
? AntiSpoof 能做什么
AntiSpoof 旨在捕获绝大多数未能正确伪装其客户端品牌或频道的作弊者:
1. 检测明显的伪装者
大多数 hacked 客户端(如 Wurst、Meteor、Impact、LiquidBounce 等)没有正确伪装其品牌或频道信息。它们的修改通常会留下 AntiSpoof 可以轻松检测到的明显迹象。
2. 执行仅限原版的策略
识别那些声称使用“原版”但已注册插件频道的玩家(这在真正的原版客户端中在技术上是不可可能的)。
3. 阻止或白名单特定客户端
使用强大的正则表达式模式来控制服务器上允许的确切客户端品牌和频道,从而对允许的修改进行细粒度控制。
4. 防范 Geyser 伪装
检测试图将自己伪装成基岩版玩家以绕过安全措施的 Java 版玩家。
5. 创建自定义安全策略
灵活的配置系统允许您根据服务器的具体需求定制插件,从极其严格(仅限原版)到更加宽松(允许某些模组)。
⚠️ AntiSpoof 不能做什么
由于 Minecraft 固有的局限性,AntiSpoof 无法检测以下事项:
1. 阻止复杂的伪装者
拥有自定义客户端的坚定作弊者可以伪装其客户端品牌和频道,以完美模仿原版客户端。然而,如此复杂的伪装极其罕见,且需要相当高的技术水平。
2. 检测 VPN 或小号
AntiSpoof 专注于客户端侧检测,不包含基于 IP 或账户的检查。对于这些保护,您需要额外的安全插件。
3. 替换完整的反作弊
AntiSpoof 旨在检测的游戏内作弊行为,如飞行外挂、杀戮光环或其他移动/战斗类作弊。它是对传统反作弊插件的补充,而非替代品。
4. 保证 100% 的保护
没有任何反作弊方案能够提供绝对的保护。AntiSpoof 是你安全体系中的一个强大层级,但与其他防护措施结合使用时效果最佳。
? 为什么 AntiSpoof 是最佳解决方案
尽管存在局限性,AntiSpoof 仍然是检测修改版客户端最有效的工具之一:
1. 拦截 95% 的伪装作弊者
绝大多数作弊者并不会使用复杂的伪装技术。AntiSpoof 可以轻松捕捉到这些玩家,以极低的误报率阻止大多数被篡改的客户端。
2. 高度可定制
每个服务器都有不同的需求。AntiSpoof 提供了广泛的配置选项,允许你根据具体需求精确调整插件,从非常严格到更加宽松的策略均可设置。
3. 专用用例
无论你是想完全阻止非原版客户端、实施特定的模组策略,还是仅仅防止 Geyser 伪装,AntiSpoof 都能通过针对性的检测方法为你提供保护。
4. 合理的期望
AntiSpoof 承认 Minecraft 本身的局限性,专注于切实可行的措施,而非做出不切实际的承诺。这种诚实和透明正是服务器管理员信赖它的原因。
5. 轻量且高效
AntiSpoof 在设计时充分考虑了性能影响,在提供强力保护的同时,对服务器资源的占用微乎其微。
? 设计理念
AntiSpoof 基于几个核心原则构建:
对客户端类型的细粒度控制
与传统黑名单/白名单方法不同,AntiSpoof 实现了一套复杂的按品牌(brand)配置的系统。这允许服务器管理员:
- 为特定客户端定义精确的检测标准
- 为不同类型的客户端设置自定义策略
- 针对不同违规行为制定定制化的响应措施
纵深防御
该插件使用多层检测方法来抓包不同类型的伪装行为:
- 客户端品牌验证
- 通道模式分析
- 通道注册监控
- Bedrock 端身份验证检查
这种多层方法确保了即使某一层检测被绕过,其他层仍可能捕捉到可疑活动。
安全性与可用性的平衡
AntiSpoof 在以下方面取得了谨慎的平衡:
- 用于捕获恶意客户端的强大安全措施
- 允许合法客户端修改的灵活性
- 面向服务器工作人员的清晰、可操作的警报
- 极低的误报率,避免困扰真正的玩家
透明的运行机制
该插件旨在提供清晰的可见性,让用户了解它正在检测什么以及原因:
- 全面的调试日志选项
- 面向工作人员的详细检查命令
- 明确的违规提示信息
- 用户友好的配置格式
这种透明度帮助管理员确切地了解插件的工作方式,并对其安全策略进行明智的调整。
? 安装
要求
- Java 21 或更高版本
- Spigot、Paper 或兼容分支 (1.20.4+)
- 安装插件所需的相应服务器权限
可选依赖项
- Floodgate(用于更好地检测 Bedrock 端玩家)
- PlaceholderAPI(用于其他插件中的占位符)
- ViaVersion/ViaBackwards(用于版本兼容性信息)
- PacketEvents 2.7.1+(仅 Lite 版本必需)
安装完整版
- 从 发布页面 下载最新的
antispoof-[version].jar
- 将 JAR 文件放入服务器的
plugins 文件夹中
- 重启服务器
- 通过生成的
plugins/AntiSpoof/config.yml 文件配置插件
- 使用
/antispoof reload 应用更改
安装 Lite 版本
- 首先,确保已安装 PacketEvents 2.7.1+:
- 从 发布页面 下载最新的
antispoof-lite-[version].jar
- 将 AntiSpoof Lite JAR 文件放入服务器的
plugins 文件夹中
- 重启服务器
- 通过生成的
plugins/AntiSpoof/config.yml 文件配置插件
- 使用
/antispoof reload 应用更改
? 命令与权限
命令参考
| 命令 |
描述 |
权限 |
/antispoof check [player] |
检查玩家是否在进行伪装(留空则检查所有在线玩家) |
antispoof.command |
/antispoof runcheck [player] |
重新分析玩家数据并再次运行检测检查 |
antispoof.admin |
/antispoof channels <player> |
查看玩家注册的插件通道 |
antispoof.command |
/antispoof brand <player> |
显示玩家的客户端品牌 |
antispoof.command |
/antispoof reload |
重新加载配置 |
antispoof.admin |
/antispoof blockedchannels |
显示当前的通道白名单/黑名单配置 |
antispoof.admin |
/antispoof blockedbrands |
显示当前的品牌白名单/黑名单配置 |
antispoof.admin |
/antispoof help |
显示包含所有命令的帮助信息 |
antispoof.command |
权限节点
| 权限 |
描述 |
默认值 |
antispoof.command |
访问基本 AntiSpoof 命令 |
op |
antispoof.admin |
访问管理命令,如重载配置 |
op |
antispoof.alerts |
检测到伪装时接收游戏内警报 |
op |
antispoof.bypass |
绕过所有伪装检查 |
false |
? PlaceholderAPI 集成
AntiSpoof 与 PlaceholderAPI 集成,为其他插件提供实用的占位符。这使得您可以在记分板插件、标签页列表插件、聊天格式插件等中显示客户端信息。
可用占位符
| 占位符 |
描述 |
示例输出 |
%antispoof_brand% |
显示玩家的客户端品牌 |
"vanilla", "fabric", "lunarclient:v1.8.9-10b0" |
%antispoof_channels% |
显示玩家已注册通道的逗号分隔列表 |
"minecraft:brand, fabric:registry/sync, fabric:screen-handler-api" |
%antispoof_channels_count% |
显示已注册通道的数量 |
"5" |
%antispoof_is_spoofing% |
返回是否检测到玩家正在伪装 |
"true" 或 "false" |
%antispoof_is_bedrock% |
返回是否检测到玩家为基岩版玩家 |
"true" 或 "false" |
使用示例
以下是一些如何使用这些占位符的示例:
聊天格式(配合聊天插件)
[%antispoof_brand%] %player_name%: %message%
欢迎消息(配合类似 essentials 的插件)
&a欢迎!&7您正在使用 &e%antispoof_brand%&7 以及 &e%antispoof_channels_count%&7 个插件通道。
自定义记分板
&6═════ &b服务器信息 &6═════
&7客户端: &e%antispoof_brand%
&7通道: &e%antispoof_channels_count%
&7基岩版: &e%antispoof_is_bedrock%
&6════════════════════
设置说明
- 确保您的服务器上已安装 PlaceholderAPI
- 无需额外设置 - AntiSpoof 会自动注册其占位符
- 在任何兼容 PlaceholderAPI 的插件中使用这些占位符
⚙️ 配置
配置文件 (config.yml) 包含大量注释,详细解释了每个选项。以下是主要部分的概述:
核心设置
- delay-in-seconds: 登录后的等待时间,之后才开始检查玩家(默认值: 1)
- debug: 启用详细日志记录以进行故障排除(默认值: false)
检测方法
- 原版伪装检测: 检测声称使用原版但通过插件通道进行通信的玩家
- 非原版检查: 可选地阻止所有非原版客户端(严格模式)
- 通道过滤: 使用正则表达式支持阻止或白名单特定插件通道
- 品牌过滤: 使用正则表达式支持阻止或白名单特定客户端品牌
- 基岩版处理: 对合法的基岩版玩家进行特殊处理
- Geyser 伪装检测: 识别假装是基岩版的 Java 版玩家
客户端品牌配置系统
client-brands 部分允许对不同客户端类型进行精细控制。每个品牌配置包括:
- 识别: 用于识别特定客户端品牌的正则表达式模式
- 标记/警报设置: 是否标记、发出警报或发送到 Discord
- 自定义消息: 针对该品牌的特定警报消息
- 惩罚控制: 是否惩罚以及运行哪些命令
- 必需通道: 该客户端合法实例必须存在的通道
- 特殊处理: 如针对修改版原版的严格检查等功能
品牌配置示例:
lunar:
enabled: true
values:
- "^lunarclient:v\\d+\\.\\d+\\.\\d+-\\d{4}$"
# 是否将玩家计为被 AntiSpoof 标记
flag: false
# 是否为此品牌发送游戏内警报
alert: true
# 是否为此品牌发送 Discord 警报
discord-alert: false
# 此品牌的自定义警报消息
alert-message: "&8[&eAntiSpoof&8] &7%player% 正在使用 &9Lunar Client &7版本: &b%brand%"
console-alert-message: "%player% 正在使用 Lunar Client: %brand%"
# 是否惩罚使用此品牌的玩家
punish: false
# 如果 punish 为 true,则执行的惩罚命令
punishments: []
# 此品牌合法存在所必需的通道
required-channels:
- "lunar.*" # 必须至少有一个 lunar 通道
# 如果没有通道则惩罚玩家?设置为 false 则仅发出警报。
required-channels-punish: false
required-channels-punishments:
- "kick %player% &c检测到 Lunar Client 伪装"
此系统允许您为每种客户端类型创建定制策略,而不是一刀切的方法。
操作配置
对于每种检测方法,您可以配置:
- 是否启用
- 自定义警报消息
- 违规是否触发惩罚
- 带有占位符的自定义惩罚命令
Discord 集成
- Webhook URL 和格式化选项
- 可定制的嵌入内容
- 警报过滤选项
config.yml 包含详尽的文档、示例和解释。如需完整示例,请参阅插件随附的默认配置。
? 工作原理
AntiSpoof 使用多种检测技术来识别试图绕过安全措施的客户端:
1. 客户端品牌分析
当玩家加入时,他们会发送一个包含客户端品牌的数据包(例如 "vanilla", "forge", "fabric")。AntiSpoof 捕获此信息并将其与您配置的白名单或黑名单进行比较。
2. 插件通道注册
修改版客户端会注册插件通道以与服务器通信。真正的原版客户端没有任何插件通道,因此任何声称是“vanilla”但注册了通道的客户端都是在伪装。
3. 模式匹配
复杂的正则表达式模式匹配使 AntiSpoof 能够识别特定的客户端类型或阻止某些模式,即使客户端试图伪装自己。
4. 基岩版身份验证
对于 Geyser/Floodgate 设置,AntiSpoof 通过 Floodgate API 或检查用户名前缀来验证基岩版玩家,防止 Java 版玩家假装成基岩版用户。
5. 动态检查
在初始注册后,AntiSpoof 继续监控通道注册情况,使其能够检测在会话后期尝试添加可疑通道的客户端。
? 故障排除
常见问题
玩家被错误标记
- 问题:合法玩家被标记为伪装者
- 解决方案:检查你的白名单/黑名单设置。你可能屏蔽了合法的客户端品牌。启用调试模式以查看是什么触发了标记。
未发送警报
- 问题:玩家在进行伪装,但没有出现警报
- 解决方案:确保工作人员拥有
antispoof.alerts 权限,并验证插件已正确启用。
Discord Webhook 无法工作
- 问题:警报未发送到 Discord
- 解决方案:检查你的 webhook URL,确保其格式正确,并验证
discord.enabled 设置已设置为 true。
性能担忧
- 问题:安装 AntiSpoof 后服务器卡顿
- 解决方案:该插件非常轻量,但可以尝试增加
delay-in-seconds 的值以分散检查时间,或禁用 debug 模式。
调试模式
在 config.yml 文件中启用调试模式,以获取关于检测到的品牌和通道的详细信息:
debug: true
这将把所有客户端品牌和通道注册记录到你的控制台,帮助你识别触发标记的原因,并相应地调整配置。
❓ 常见问题
一般问题
Q:我应该使用哪个版本——Full 还是 Lite?
A:为了简便起见,请使用 Full 版本。如果你已经有其他使用 PacketEvents 的插件以避免库重复,请使用 Lite 版本。
Q:AntiSpoof 如何处理 Bedrock 玩家?
A:当可用时使用 Floodgate API,否则回退到用户名前缀检查。你可以在配置中将模式设置为“EXEMPT”或“IGNORE”。
Q:什么是原版客户端?
A:在 Minecraft 术语中,原版客户端是 Mojang 提供的未经修改的游戏客户端,它报告“vanilla”作为其品牌,并且没有注册任何插件通道。
Q:AntiSpoof 能阻止所有作弊者吗?
A:不能,但根据你的设置,它可以阻止高达 95% 的作弊者。复杂的伪装很少见,需要自定义客户端。
Q:这与 ViaVersion 兼容吗?
A:是的!AntiSpoof 与 ViaVersion 完全兼容,甚至可以利用 ViaVersion 的信息来增强其检测能力。
Q:这会阻止所有修改过的客户端吗?
A:这取决于你的配置。你可以设置为阻止所有非原版客户端,或者你可以将特定的客户端品牌列入白名单以允许它们(例如 Lunar Client 或 Badlion)。
Q:这与传统的反作弊插件相比如何?
A:AntiSpoof 专注于客户端品牌和通道检测,这与移动/战斗作弊检测的方法不同。最好与传统反作弊插件配合使用,以实现全面保护。
Q:/antispoof runcheck 命令的作用是什么?
A:此命令重新分析现有玩家数据,并为一个玩家或所有在线玩家重新运行检测检查。当你更新了配置并希望在不让玩家重新加入的情况下根据新规则检查玩家时,这很有用。
技术问题
Q:玩家可以绕过这个插件吗?
A:拥有自定义客户端的高级黑客可能会绕过任何检测方法。然而,绝大多数作弊者不会走到那一步。
Q:AntiSpoof 是否与 Velocity/BungeeCord/Waterfall 兼容?
A:AntiSpoof 专为 Spigot/Paper 服务器设计。虽然在代理环境中可以工作,但它应该安装在后端服务器上,而不是代理本身。
Q:什么是插件通道?
A:插件通道是模组和插件用于在客户端和服务器之间交换数据的通信通道。大多数模组通过它们来实现其功能。
Q:我如何添加自定义正则表达式模式?
A:将你的模式添加到 blocked-brands 或 blocked-channels 下的 values 列表中。例如,要阻止所有 Fabric 模组,你可以添加 "(?i).*fabric.*"。
Q:对性能的影响有多大?
A:AntiSpoof 极其轻量。检查仅在玩家加入以及发送通道注册数据包时运行,而这些情况并不频繁。
? 支持与开发
获取帮助
- GitHub Issues:在我们的 Issue Tracker 上报告错误或建议功能
- Discord:在 Discord 上联系我以获得直接支持 (GigaZelensky)
贡献
欢迎贡献!若要贡献:
- Fork 仓库
- 创建功能分支 (
git checkout -b feature/amazing-feature)
- 提交更改 (
git commit -m 'Add some amazing feature')
- 推送到分支 (
git push origin feature/amazing-feature)
- 打开 Pull Request
开发指南
- 确保与 Java 21+ 兼容
- 遵循现有的代码风格和架构
- 为新功能添加适当的文档
- 尽可能保持向后兼容性
? 完整配置示例
# ___ __ _ _____ ____
# / | ____ / /_(_) ___/____ ____ ____ / __/
# / /| | / __ \/ __/ /\__ \/ __ \/ __ \/ __ \/ /_
# / ___ |/ / / / /_/ /___/ / /_/ / /_/ / /_/ / __/
# /_/ |_/_/ /_/\__/_//____/ .___/\____/\____/_/
# /_/
# Made by GigaZelensky
# ──────────────────────────────────────────────────────────
# AntiSpoof 配置
# ──────────────────────────────────────────────────────────
# 欢迎使用 AntiSpoof。此插件通过解析玩家发送的客户端信息,帮助服务器管理员检测和管理
# 客户端修改。
#
# ⚠️ 注意:虽然此插件增强了安全性,但并非万无一失。
# 技术高超的用户(具有讽刺意味的是)可以伪造其客户端详情以绕过检测。
#
# 默认情况下,插件仅验证声称使用
# 'vanilla'(原版)的玩家是否注册了插件频道,这在真正的
# 原版客户端中是不可能的。
# ──────────────────────────────────────────────────────────
# ⏳ 检查客户端伪装前的延迟时间(秒)。
# 设置为 0 可在玩家登录时立即进行检查(不可靠)。(默认值: 1)
delay-in-seconds: 1
# ️ 调试模式
# 如果启用,将在控制台记录玩家登录时的客户端频道和品牌详情。
debug: false
# ──────────────────────────────────────────────────────────
# 核心检测设置
# ──────────────────────────────────────────────────────────
# 原版伪装检测
# 检测玩家声称使用原版但实际上注册了插件频道的情况
vanillaspoof-check:
# 是否检查声称“vanilla”(原版)客户端的玩家是否有插件频道
enabled: true
# 是否为此类违规行为发送 Discord 警报
discord-alert: true
# 此特定违规行为的自定义警报消息
alert-message: "&8[&cAntiSpoof&8] &e%player% 被标记!&c带有插件频道的原版客户端"
console-alert-message: "%player% 被标记!带有插件频道的原版客户端"
# 如果检测到违规,是否惩罚玩家
punish: false
# 要执行的惩罚操作
# 可用占位符: %player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &c检测到原版伪装: %reason%"
# - "ban %player% &c检测到原版客户端伪装"
# 超级严格模式(不推荐)
# 阻止以下情况的玩家:
# - 没有“vanilla”(原版)客户端,或者
# - 注册了插件频道(表明使用了模组/插件)
# ⚠️ 这是一种极其严格的模式,可能会阻止合法玩家
non-vanilla-check:
# 是否启用此严格检查
enabled: false
# 是否为此类违规行为发送 Discord 警报
discord-alert: false
# 此特定违规行为的自定义警报消息
alert-message: "&8[&cAntiSpoof&8] &e%player% 被标记!&c检测到客户端修改"
console-alert-message: "%player% 被标记!检测到客户端修改"
# 如果检测到违规,是否惩罚玩家
punish: false
# 要执行的惩罚操作
# 可用占位符: %player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &c检测到非原版客户端及频道"
# - "tempban %player% 1h &c使用修改后的客户端"
# ──────────────────────────────────────────────────────────
# 无品牌检测设置
# ──────────────────────────────────────────────────────────
# 一些作弊客户端通过完全不发送客户端品牌来避免检测
# 此检查将标记未提供任何品牌信息就连接的玩家
no-brand-check:
# 是否标记未发送客户端品牌的玩家
enabled: true
# 是否为此类违规行为发送 Discord 警报
discord-alert: true
# 此特定违规行为的自定义警报消息
alert-message: "&8[&cAntiSpoof&8] &e%player% 被标记!&c未检测到客户端品牌"
console-alert-message: "%player% 被标记!未检测到客户端品牌"
# 如果检测到违规,是否惩罚玩家
punish: false
# 要执行的惩罚操作
# 可用占位符: %player%, %reason%
punishments:
- "kick %player% &c未检测到客户端品牌"
# - "ban %player% &c检测到可疑客户端(无品牌)"
# ──────────────────────────────────────────────────────────
# 频道检测设置
# ──────────────────────────────────────────────────────────
blocked-channels:
# 启用基于频道的检测
enabled: false
# 是否对被封禁频道的违规行为发送 Discord 警报
discord-alert: false
# ⚪ 白名单模式
# - FALSE: 封禁列出的频道。
# - SIMPLE: 仅允许至少拥有一个白名单频道的玩家。
# - STRICT: 仅允许完全匹配白名单且没有额外频道的玩家。
whitelist-mode: FALSE
# 要封禁/列入白名单的频道列表
values:
- "^fabric-screen-handler-api-v1:open_screen$"
# 在此处添加更多要封禁的频道
# - "another:blocked:channel"
# - "(?i).*litematica.*"
# - "(?i).*fabric.*"
# 此特定违规行为的自定义警报消息
alert-message: "&8[&cAntiSpoof&8] &e%player% 被标记!&c使用被封禁的频道: &f%channel%"
console-alert-message: "%player% 被标记!使用被封禁的频道: %channel%"
# 当玩家的插件频道被修改时发出警报
modifiedchannels:
enabled: true
# 是否对被修改的频道发送 Discord 警报
discord-alert: false
alert-message: "&8[&cAntiSpoof&8] &e%player% 修改了频道: &f%channel%"
console-alert-message: "%player% 修改了频道: %channel%"
# 如果检测到违规,是否惩罚玩家
punish: false
# 要执行的惩罚操作
# 可用占位符: %player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &c检测到被封禁的频道: %channel%"
# - "tempban %player% 1d &c使用被封禁的模组频道"
# ──────────────────────────────────────────────────────────
# 客户端品牌配置
# ──────────────────────────────────────────────────────────
# 此部分允许对不同类型的客户端进行细粒度控制。
# 每个品牌都可以拥有自己的检测模式、警报消息、
# 惩罚措施以及特殊豁免权。
client-brands:
# 客户端品牌系统的总开关
enabled: true
# 未明确配置的品牌的默认设置
default:
flag: true
alert: true
discord-alert: false
punish: false
# 如果未为特定品牌指定,则使用此默认警报消息
alert-message: "&8[&cAntiSpoof&8] &7%player% 正在使用未知客户端:&e%brand%"
console-alert-message: "%player% 正在使用未知客户端:%brand%"
# 品牌特定的配置
brands:
# Lunar Client 配置
lunar:
enabled: true
values:
- "^lunarclient:v\\d+\\.\\d+\\.\\d+-\\d{4}$"
# 是否将玩家标记为被 AntiSpoof 标记
flag: false
# 是否为该品牌发送游戏内警报
alert: true
# 是否为该品牌发送 Discord 警报
discord-alert: false
# 该品牌的自定义警报消息
alert-message: "&8[&eAntiSpoof&8] &7%player% 正在使用 &9Lunar Client &7版本:&b%brand%"
console-alert-message: "%player% 正在使用 Lunar Client:%brand%"
# 是否惩罚使用该品牌的玩家
punish: false
# 如果 punish 为 true,则执行以下惩罚命令
punishments: []
# 该品牌合法时必须存在的频道
required-channels:
- "lunar.*" # 必须至少有一个 lunar 频道
# 如果玩家没有这些频道,是否对其进行惩罚?设置为 false 则仅发出警报。
required-channels-punish: false
required-channels-punishments:
- "kick %player% &c检测到 Lunar Client 欺骗行为"
# Badlion Client 配置
badlion:
enabled: true
values:
- "^badlion.*"
- "^BLC.*"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% 正在使用 &b%brand%"
console-alert-message: "%player% 正在使用 Badlion Client:%brand%"
punish: false
punishments: []
required-channels: []
required-channels-punish: false
required-channels-punishments:
- "kick %player% &c检测到 Lunar Client 欺骗行为"
# Forge 配置
forge:
enabled: true
values:
- "^fml,forge.*"
- "^forge.*"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% 正在使用 &b%brand%"
console-alert-message: "%player% 正在使用 Forge:%brand%"
punish: false
punishments: []
required-channels:
- "(?i).*forge.*"
required-channels-punish: false
required-channels-punishments:
- "kick %player% &c检测到频道欺骗行为"
# Fabric 配置
fabric:
enabled: true
values:
- "^fabric$"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% 正在使用 &b%brand%"
console-alert-message: "%player% 正在使用 Fabric:%brand%"
punish: false
punishments: []
required-channels:
- "(?i).*fabric.*" # 匹配包含“fabric”的任何频道(不区分大小写)
required-channels-punish: false
required-channels-punishments:
- "kick %player% &c检测到频道欺骗行为"
# LabyMod 配置
labymod:
enabled: true
values:
- "^labymod.*"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% 正在使用 &b%brand%"
console-alert-message: "%player% 正在使用 %brand%"
punish: false
punishments: []
required-channels: []
required-channels-punish: false
required-channels-punishments:
- "kick %player% &c检测到频道欺骗行为"
# 作弊客户端配置
hacked:
enabled: true
values:
- "(?i).*wurst.*"
- "(?i).*impact.*"
- "(?i).*aristois.*"
- "(?i).*future.*"
- "(?i).*meteor.*"
- "(?i).*inertia.*"
- "(?i).*sigma.*"
- "(?i).*liquidbounce.*"
flag: true
alert: true
discord-alert: true
alert-message: "&8[&cAntiSpoof&8] &e%player% 正在使用 &c&l已知的作弊客户端:&f%brand%"
console-alert-message: "警报!%player% 正在使用已知的作弊客户端:%brand%"
punish: true
punishments:
- "kick %player% &c检测到作弊客户端:%brand%"
# - "ban %player% &c检测到使用作弊客户端"
# 原版客户端配置
vanilla:
enabled: true
values:
- "^vanilla$"
flag: false # 仅在玩家被捕获进行欺骗时才会标记
alert: false # 默认情况下不对原版客户端发出警报
discord-alert: false
alert-message: "&8[&cAntiSpoof&8] &7%player% 正在使用 &d%brand%"
console-alert-message: "%player% 正在使用 %brand%"
punish: false
punishments: []
# 原版客户端的特殊设置
# “strict-check” 如果客户端有任何插件频道,则进行标记(必须启用才能检测 VanillaSpoof)
# 您可以将此“strict-check”添加到任何客户端品牌,只有这样才能由前面的“vanillaspoof-check”进行处理
strict-check: true # 启用原版的严格检查(必须没有任何频道)
vanilla-variation: # 当客户端显示“Vanilla”或“vAnilla2”但不是“vanilla”时
enabled: true
values:
- "^(?!vanilla$).*?(?i)vanilla.*"
flag: true
alert: true
discord-alert: true
alert-message: "&8[&cAntiSpoof&8] &e%player% 正在使用虚假的原版客户端:&c%brand%"
console-alert-message: "%player% 正在使用虚假的原版客户端:%brand%"
punish: false
punishments: []
strict-check: true
blankbrand: # 当客户端发送空品牌频道时
enabled: true
values:
- "^$" # 匹配空/空白品牌的正则表达式
flag: true
alert: true
discord-alert: true
alert-message: "&8[&eAntiSpoof&8] &7%player% &eis using a blank brand"
console-alert-message: "%player% is using a blank brand"
punish: false
punishments: []
# ──────────────────────────────────────────────────────────
# Bedrock Handling Settings
# ──────────────────────────────────────────────────────────
bedrock-handling:
# 选择如何处理基岩版玩家。
# 选项:
# - "IGNORE": 完全忽略这些玩家;像处理普通玩家一样处理他们。
# - "EXEMPT": 处理他们,但如果未通过检查则不对其进行惩罚。
#
# 无论哪种方式,基岩版玩家都不会受到反欺骗处理的对待。
# 强烈建议使用 "EXEMPT" 模式,因为 "IGNORE" 很容易误判基岩版玩家。
mode: "EXEMPT"
# Geyser Spoofing Detection
# 检测声称客户端品牌包含 "geyser" 变体但未通过 Floodgate API 验证为基岩版玩家的玩家
geyser-spoof:
# 是否启用 Geyser 欺骗检测
enabled: true
# 是否向 Discord 发送有关 Geyser 欺骗违规的警报
discord-alert: true
# 此特定违规的自定义警报消息
alert-message: "&8[&cAntiSpoof&8] &e%player% flagged! &cGeyser client spoofing"
console-alert-message: "%player% flagged! Geyser client spoofing with brand: %brand%"
# 如果检测结果为阳性,是否惩罚玩家
punish: false
# 要执行的惩罚操作
# 可用占位符:%player%, %reason%, %brand%
punishments:
- "kick %player% &cGeyser client spoofing detected"
# - "ban %player% &cGeyser client spoofing"
# Check Player Prefix:
# 此选项通过验证前缀来检查玩家是否被识别为基岩版玩家。
# 启用后,系统将验证玩家的用户名或标识符是否以指定的前缀开头。
# 默认前缀为 ".",如果玩家的客户端品牌以任何形式包含 "geyser" 但不匹配
# 预期的前缀,他们将被标记。
prefix-check:
enabled: true
# 用于识别基岩版玩家的前缀。
prefix: "."
# ──────────────────────────────────────────────────────────
# Discord Webhook Settings
# ──────────────────────────────────────────────────────────
discord:
enabled: false
webhook: ""
embed-title: "**AntiSpoof Alert**"
embed-color: "#2AB7CA"
violation-content:
- "**Player**: %player%"
- "**Violations**:%violations%"
- "**Client Version**: %viaversion_version%" # 需要 Viaversion 和 PlaceholderAPI
- "**Brand**: %brand%"
- "**Channels**:"
- "%channel%" # 垂直通道列表
# 所有警报的全局设置(用作后备)
# 这些选项控制是否向 Discord 发送玩家加入的消息
# 即使他们没有触发任何违规
global-alerts:
# 当玩家带着品牌加入时,是否向 Discord 发送警报
join-brand-alerts: false
# 当玩家注册初始通道时,是否向 Discord 发送警报
initial-channels-alerts: false
# ──────────────────────────────────────────────────────────
# Update Checker Settings
# ──────────────────────────────────────────────────────────
# 服务器启动时从 GitHub 检查更新
update-checker:
# 是否在启动时检查更新
enabled: true
# 管理员加入时是否通知
notify-on-join: true
# ──────────────────────────────────────────────────────────
# Legacy Punishment Settings
# ──────────────────────────────────────────────────────────
# 遗留的全局惩罚系统(向后兼容)
# 如果特定检查设置了 'punish: true'
# 但没有定义自己的惩罚措施,将使用这些惩罚
# 可用占位符:%player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &cSuspicious client detected!"
# - "ban %player% &cClient spoofing detected"
# ──────────────────────────────────────────────────────────
# Legacy Alert Messages
# ──────────────────────────────────────────────────────────
# 遗留的全局警报系统(向后兼容)
# 如果启用了特定检查
# 但没有定义自己的警报,将使用这些消息
# 可用占位符:%player%, %reason%, %brand%, %channel%
# 定义了当检测到欺骗尝试时,向拥有 `antispoof.alerts` 权限的玩家发送的消息
messages:
# 向拥有 antispoof.alerts 权限的玩家显示的消息
alert: "&8[&cAntiSpoof&8] &e%player% flagged! &c%reason%"
# 记录到控制台的消息(不需要颜色代码)
console-alert: "%player% flagged! %reason%"
# 多条违规的消息
multiple-flags: "&8[&cAntiSpoof&8] &e%player% has multiple violations: &c%reasons%"
# 多条违规的控制台消息
console-multiple-flags: "%player% has multiple violations: %reasons%"
? License
AntiSpoof 根据 GNU General Public License v3.0 许可 - 详见 LICENSE 文件。
Copyright (C) 2025 GigaZelensky
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Made with ❤️ by GigaZelensky
⭐ Star us on GitHub if you find this plugin useful! ⭐
AntiSpoof - Advanced Client Spoof Detection
Advanced, customizable Minecraft plugin for detecting client spoofing through brand analysis and channel monitoring
? Table of Contents
? Key Features
Client Brand Analysis
- Brand Filtering: Block/whitelist specific client brands (Fabric, Forge, Lunar Client, etc.)
- Pattern Matching: Use regex to identify suspicious brand patterns
- Geyser Verification: Detect Java players pretending to be Bedrock clients
Channel Monitoring
- Vanilla Verification: Flag players claiming to use vanilla with plugin channels
- Channel Control: Whitelist or blacklist specific plugin channels
- Strict Matching: Enforce exact channel requirements for specific client types
Bedrock Player Integration
- Floodgate Integration: Seamless support for Floodgate API
- Prefix Verification: Identify Bedrock players by username prefix
- Special Handling: Configure exempt or ignore modes for legitimate Bedrock users
Advanced Detection
- Multiple Check Modes: Customize which checks are active and their severity
- Configurable Actions: Define custom punishment commands for each violation type
- Real-time Alerts: Notify staff when suspicious activity is detected
Diagnostic Tools
- Player Inspection: Check detailed client information of any player
- Brand Analysis: View and verify client brands in real-time
- Channel Listing: Inspect registered plugin channels for any player
Discord Integration
- Webhook Support: Send alerts to your Discord server
- Customizable Embeds: Configure colors, fields, and formatting
- Comprehensive Data: Include player details, violation reasons, and more
PlaceholderAPI Support
- Client Information: Access player client details from other plugins
- Detection Status: Check if players are using modified clients
- Bedrock Integration: Verify Bedrock player status
Rich Color Messaging
-
Hybrid formatting engine – one string can mix
- MiniMessage tags
<gradient:#ff7f00:#ffd700><bold>Hello</bold></gradient>
- Legacy
& color/style codes &aGreen &lBold
- Hex colours
&#FFAA00 or &x&F&F&A&A&0&0
-
Powered by the new MessageUtil.miniMessage() helper, so every configurable alert, Discord embed, or command output can use gradients, bold, italics, obfuscated text, etc.
? Download Options
AntiSpoof is available in two versions to suit different server setups:
Full Version (Recommended for most users)
- All-in-one package with PacketEvents included
- No additional plugins required
- Simple drop-in installation
- Larger file size but simpler setup
Lite Version (For advanced setups)
- Requires external PacketEvents 2.7.1+ installation
- Significantly smaller file size
- Prevents duplicate PacketEvents instances
- Ideal for servers already using plugins that depend on PacketEvents
- Better for performance on servers with multiple PacketEvents-based plugins
Both versions provide identical functionality - the only difference is whether PacketEvents is included in the JAR file or needs to be installed separately.
? What AntiSpoof Can Do
AntiSpoof is designed to catch the vast majority of cheaters who don't properly spoof their client brand or channels:
1. Detect Obvious Spoofers
Most hacked clients (like Wurst, Meteor, Impact, LiquidBounce, etc.) don't properly spoof their brand or channel information. Their modifications often leave telltale signs that AntiSpoof can easily detect.
2. Enforce Vanilla-Only Policies
Identify players who claim to be using "vanilla" but have registered plugin channels (which is technically impossible with a true vanilla client).
3. Block or Whitelist Specific Clients
Use powerful regex patterns to control exactly which client brands and channels are allowed on your server, giving you granular control over which modifications are permitted.
4. Protect Against Geyser Spoofing
Detect Java players who attempt to disguise themselves as Bedrock players to bypass security measures.
5. Create Custom Security Policies
The flexible configuration system allows you to tailor the plugin to your specific server's needs, from extremely strict (vanilla only) to more permissive (allowing certain mods).
⚠️ What AntiSpoof Cannot Do
Due to Minecraft's inherent limitations, there are some things that AntiSpoof cannot detect:
1. Stop Sophisticated Spoofers
A determined cheater with a custom client can spoof both their client brand and channels to perfectly mimic a vanilla client. However, such sophisticated spoofing is extremely rare and requires significant technical knowledge.
2. Detect VPNs or Alt Accounts
AntiSpoof focuses on client-side detection and does not include IP-based or account-based checks. For these protections, you would need additional security plugins.
3. Replace a Full Anti-Cheat
AntiSpoof is not designed to detect in-game cheats like fly hacks, kill aura, or other movement/combat hacks. It complements traditional anti-cheat plugins but does not replace them.
4. Guarantee 100% Protection
No anti-cheat solution can provide absolute protection. AntiSpoof is a powerful layer in your security stack but works best when combined with other protective measures.
? Why AntiSpoof is the Best Solution
Despite the limitations, AntiSpoof remains one of the most effective tools for detecting modified clients:
1. Catches 95% of Spoofing Cheaters
The vast majority of cheaters don't use sophisticated spoofing techniques. AntiSpoof catches these players easily, blocking most hacked clients with minimal false positives.
2. Highly Customizable
Every server has different needs. AntiSpoof's extensive configuration options allow you to tailor the plugin precisely to your requirements, from very strict to more permissive.
3. Specialized Use Cases
Whether you want to block non-vanilla clients entirely, enforce specific mod policies, or just protect against Geyser spoofing, AntiSpoof has you covered with targeted detection methods.
4. Realistic Expectations
AntiSpoof acknowledges Minecraft's limitations and focuses on what can be done effectively rather than making unrealistic promises. This honesty and transparency is why server owners trust it.
5. Lightweight & Efficient
Designed with performance in mind, AntiSpoof has minimal impact on your server's resources while providing robust protection.
? Design Philosophy
AntiSpoof was built with several core principles in mind:
Granular Control Over Client Types
Instead of a traditional blacklist/whitelist approach, AntiSpoof implements a sophisticated per-brand configuration system. This allows server administrators to:
- Define precise detection criteria for specific clients
- Set custom policies for different client types
- Craft tailored responses to various violations
Defense in Depth
The plugin uses multiple layers of detection to catch different types of spoofing:
- Client brand verification
- Channel pattern analysis
- Channel registration monitoring
- Bedrock authentication checks
This multi-layered approach ensures that even if one check is bypassed, others may still catch suspicious activity.
Balance Between Security and Usability
AntiSpoof strikes a careful balance between:
- Strong security measures to catch malicious clients
- Flexibility to allow legitimate client modifications
- Clear, actionable alerts for server staff
- Minimal false positives to avoid frustrating genuine players
Transparent Operation
The plugin is designed to provide clear visibility into what it's detecting and why:
- Comprehensive debug logging options
- Detailed check commands for staff
- Explicit violation messages
- User-friendly configuration format
This transparency helps administrators understand exactly how the plugin is working and make informed adjustments to their security policies.
? Installation
Requirements
- Java 21 or higher
- Spigot, Paper, or compatible fork (1.20.4+)
- Appropriate server permissions to install plugins
Optional Dependencies
- Floodgate (for better Bedrock player detection)
- PlaceholderAPI (for placeholders in other plugins)
- ViaVersion/ViaBackwards (for version compatibility information)
- PacketEvents 2.7.1+ (required for Lite version only)
Installing the Full Version
- Download the latest
antispoof-[version].jar from the releases page
- Place the JAR file in your server's
plugins folder
- Restart your server
- Configure the plugin via the generated
plugins/AntiSpoof/config.yml file
- Apply changes with
/antispoof reload
Installing the Lite Version
- First, ensure PacketEvents 2.7.1+ is installed:
- Download the latest
antispoof-lite-[version].jar from the releases page
- Place the AntiSpoof Lite JAR in your server's
plugins folder
- Restart your server
- Configure the plugin via the generated
plugins/AntiSpoof/config.yml file
- Apply changes with
/antispoof reload
? Commands & Permissions
Command Reference
| Command |
Description |
Permission |
/antispoof check [player] |
Check if a player is spoofing (empty for all online players) |
antispoof.command |
/antispoof runcheck [player] |
Re-analyze player data and run detection checks again |
antispoof.admin |
/antispoof channels <player> |
View a player's registered plugin channels |
antispoof.command |
/antispoof brand <player> |
Show a player's client brand |
antispoof.command |
/antispoof reload |
Reload the configuration |
antispoof.admin |
/antispoof blockedchannels |
Show current channel whitelist/blacklist configuration |
antispoof.admin |
/antispoof blockedbrands |
Show current brand whitelist/blacklist configuration |
antispoof.admin |
/antispoof help |
Display help message with all commands |
antispoof.command |
Permission Nodes
| Permission |
Description |
Default |
antispoof.command |
Access to basic AntiSpoof commands |
op |
antispoof.admin |
Access to administrative commands like reload |
op |
antispoof.alerts |
Receive in-game alerts when spoofing is detected |
op |
antispoof.bypass |
Bypass all spoofing checks |
false |
? PlaceholderAPI Integration
AntiSpoof integrates with PlaceholderAPI to provide useful placeholders for other plugins. This allows you to display client information on scoreboard plugins, tab list plugins, chat formatting plugins, and more.
Available Placeholders
| Placeholder |
Description |
Example Output |
%antispoof_brand% |
Shows the player's client brand |
"vanilla", "fabric", "lunarclient:v1.8.9-10b0" |
%antispoof_channels% |
Shows a comma-separated list of player's registered channels |
"minecraft:brand, fabric:registry/sync, fabric:screen-handler-api" |
%antispoof_channels_count% |
Shows the number of registered channels |
"5" |
%antispoof_is_spoofing% |
Returns whether the player is detected as spoofing |
"true" or "false" |
%antispoof_is_bedrock% |
Returns whether the player is detected as a Bedrock player |
"true" or "false" |
Usage Examples
Here are some examples of how you can use these placeholders:
Chat Format (with a chat plugin)
[%antispoof_brand%] %player_name%: %message%
Welcome Message (with an essentials-like plugin)
&aWelcome! &7You're using &e%antispoof_brand%&7 with &e%antispoof_channels_count%&7 plugin channels.
Custom Scoreboard
&6═════ &bServer Info &6═════
&7Client: &e%antispoof_brand%
&7Channels: &e%antispoof_channels_count%
&7Bedrock: &e%antispoof_is_bedrock%
&6════════════════════
Setup Instructions
- Ensure PlaceholderAPI is installed on your server
- No additional setup required - AntiSpoof registers its placeholders automatically
- Use the placeholders in any PlaceholderAPI-compatible plugin
⚙️ Configuration
The configuration file (config.yml) is extensively documented with comments explaining each option. Here's a breakdown of the key sections:
Core Settings
- delay-in-seconds: Time to wait after login before checking a player (default: 1)
- debug: Enable detailed logging for troubleshooting (default: false)
Detection Methods
- Vanilla Spoof Check: Detect players claiming to use vanilla with plugin channels
- Non-Vanilla Check: Optionally block all clients that aren't vanilla (strict mode)
- Channel Filtering: Block or whitelist specific plugin channels with regex support
- Brand Filtering: Block or whitelist specific client brands with regex support
- Bedrock Handling: Special processing for legitimate Bedrock players
- Geyser Spoof Detection: Identify Java players pretending to be Bedrock
Client Brands Configuration System
The client-brands section allows for sophisticated control over different client types. Each brand configuration includes:
- Identification: Regex patterns to identify specific client brands
- Flag/Alert Settings: Whether to flag, alert, or send to Discord
- Custom Messages: Brand-specific alert messages
- Punishment Controls: Whether to punish and what commands to run
- Required Channels: Channels that must be present for legitimate instances of the client
- Special Handling: Features like strict-check for modified vanilla clients
Example brand configuration:
lunar:
enabled: true
values:
- "^lunarclient:v\\d+\\.\\d+\\.\\d+-\\d{4}$"
# Whether to count the player as flagged by AntiSpoof
flag: false
# Whether to send in-game alerts for this brand
alert: true
# Whether to send Discord alerts for this brand
discord-alert: false
# Custom alert messages for this brand
alert-message: "&8[&eAntiSpoof&8] &7%player% is using &9Lunar Client &7version: &b%brand%"
console-alert-message: "%player% is using Lunar Client: %brand%"
# Whether to punish players using this brand
punish: false
# Punishment commands if punish is true
punishments: []
# Channels that must be present for this brand to be legitimate
required-channels:
- "lunar.*" # Must have at least one lunar channel
# Punish players if they do not have the channel(s)? Set to false to simply alert.
required-channels-punish: false
required-channels-punishments:
- "kick %player% &cLunar Client spoofing detected"
This system allows you to create tailored policies for each client type, rather than a one-size-fits-all approach.
Action Configuration
For each detection method, you can configure:
- Whether it's enabled
- Custom alert messages
- Whether violations trigger punishment
- Custom punishment commands with placeholders
Discord Integration
- Webhook URL and formatting options
- Customizable embed content
- Alert filtering options
The config.yml is thoroughly documented with examples and explanations. For a full example, refer to the default configuration included with the plugin.
? How It Works
AntiSpoof uses multiple detection techniques to identify clients attempting to bypass security measures:
1. Client Brand Analysis
When a player joins, they send their client brand as a packet (e.g., "vanilla", "forge", "fabric"). AntiSpoof captures this information and compares it against your configured whitelist or blacklist.
2. Plugin Channel Registration
Modified clients register plugin channels to communicate with the server. A true vanilla client has no plugin channels, so any client claiming to be "vanilla" but registering channels is spoofing.
3. Pattern Matching
Sophisticated regex pattern matching allows AntiSpoof to identify specific client types or block certain patterns, even when clients try to disguise themselves.
4. Bedrock Authentication
For Geyser/Floodgate setups, AntiSpoof verifies Bedrock players either through the Floodgate API or by checking username prefixes, preventing Java players from pretending to be Bedrock users.
5. Dynamic Checks
After initial registration, AntiSpoof continues to monitor channel registrations, allowing it to detect clients that attempt to add suspicious channels later in the session.
? Troubleshooting
Common Issues
Players Being Falsely Flagged
- Issue: Legitimate players are being flagged as spoofers
- Solution: Check your whitelist/blacklist settings. You may have blocked legitimate client brands. Enable debug mode to see what's triggering the flags.
No Alerts Being Sent
- Issue: Players are spoofing but no alerts are appearing
- Solution: Make sure staff have the
antispoof.alerts permission and verify the plugin is properly enabled.
Discord Webhook Not Working
- Issue: Alerts aren't being sent to Discord
- Solution: Check your webhook URL, ensure it's correctly formatted, and verify that the
discord.enabled setting is set to true.
Performance Concerns
- Issue: Server lag after installing AntiSpoof
- Solution: The plugin is very lightweight, but try increasing the
delay-in-seconds value to spread out checks or disable the debug mode.
Debug Mode
Enable debug mode in the config.yml file to get detailed information about detected brands and channels:
debug: true
This will log all client brands and channel registrations to your console, helping you identify what's triggering flags and adjust your configuration accordingly.
❓ Frequently Asked Questions
General Questions
Q: Which version should I use - Full or Lite?
A: Use the Full version for simplicity. Use the Lite version if you already have other plugins that use PacketEvents to avoid library duplication.
Q: How does AntiSpoof handle Bedrock players?
A: It uses Floodgate API when available and falls back to username prefix checking. You can set the mode to "EXEMPT" or "IGNORE" in the config.
Q: What's considered a vanilla client?
A: In Minecraft terms, a vanilla client is the unmodified game client from Mojang, which reports "vanilla" as its brand and has zero registered plugin channels.
Q: Can AntiSpoof stop all cheaters?
A: No, but it can stop up to 95% of them depending on your setup. Sophisticated spoofing is rare and requires custom clients.
Q: Does this work with ViaVersion?
A: Yes! AntiSpoof is fully compatible with ViaVersion and can even use ViaVersion's information to enhance its detection capabilities.
Q: Will this block all modified clients?
A: This depends on your configuration. You can set it to block all non-vanilla clients, or you can whitelist specific client brands that you want to allow (like Lunar Client or Badlion).
Q: How does this compare to traditional anti-cheat plugins?
A: AntiSpoof focuses specifically on client brand and channel detection, which is a different approach from movement/combat hack detection. It's best used alongside traditional anti-cheat plugins for complete protection.
Q: What does the /antispoof runcheck command do?
A: This command re-analyzes existing player data and re-runs the detection checks for a player or all online players. It's useful when you've updated your configuration and want to check players against the new rules without making them rejoin.
Technical Questions
Q: Can players bypass this plugin?
A: Sophisticated hackers with custom clients can potentially bypass any detection method. However, the vast majority of cheaters don't go to those lengths.
Q: Does AntiSpoof work with Velocity/BungeeCord/Waterfall?
A: AntiSpoof is designed for Spigot/Paper servers. While it works in a proxy environment, it should be installed on the backend servers, not on the proxy itself.
Q: What are plugin channels?
A: Plugin channels are communication channels that mods and plugins use to exchange data between client and server. They're how most mods implement their functionality.
Q: How do I add custom regex patterns?
A: Add your patterns to the values list under either blocked-brands or blocked-channels. For example, to block all Fabric mods, you might add "(?i).*fabric.*".
Q: What's the performance impact?
A: AntiSpoof is extremely lightweight. The checks only run when players join and when channel registration packets are sent, which is infrequent.
? Support & Development
Getting Help
- GitHub Issues: Report bugs or suggest features on our Issue Tracker
- Discord: Message me on Discord for direct support (GigaZelensky)
Contributing
Contributions are welcome! To contribute:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature)
- Commit your changes (
git commit -m 'Add some amazing feature')
- Push to the branch (
git push origin feature/amazing-feature)
- Open a Pull Request
Development Guidelines
- Ensure compatibility with Java 21+
- Follow existing code style and architecture
- Add appropriate documentation for new features
- Maintain backward compatibility when possible
? Complete Configuration Example
# ___ __ _ _____ ____
# / | ____ / /_(_) ___/____ ____ ____ / __/
# / /| | / __ \/ __/ /\__ \/ __ \/ __ \/ __ \/ /_
# / ___ |/ / / / /_/ /___/ / /_/ / /_/ / /_/ / __/
# /_/ |_/_/ /_/\__/_//____/ .___/\____/\____/_/
# /_/
# Made by GigaZelensky
# ──────────────────────────────────────────────────────────
# AntiSpoof Configuration
# ──────────────────────────────────────────────────────────
# Welcome to AntiSpoof. This plugin helps server admins detect and manage
# client-side modifications by analyzing client information sent by players.
#
# ⚠️ Note: While this plugin enhances security, it is not foolproof.
# Skilled users can (ironically) spoof their client details to bypass detection.
#
# By default, the plugin only verifies whether a player claiming to use
# 'vanilla' has registered plugin channels, something that is impossible
# on a true vanilla client.
# ──────────────────────────────────────────────────────────
# ⏳ Delay (in seconds) before checking for client spoofing.
# Set to 0 for an immediate check upon player login (unrealiable). (Default: 1)
delay-in-seconds: 1
# ️ Debug Mode
# If enabled, logs client channels and brand details in the console when a player logs in.
debug: false
# ──────────────────────────────────────────────────────────
# Core Detection Settings
# ──────────────────────────────────────────────────────────
# Vanilla Spoof Detection
# Detects when a player claims to use vanilla but has registered plugin channels
vanillaspoof-check:
# Whether to check if a player claiming "vanilla" client has plugin channels
enabled: true
# Whether to send alerts to Discord for this violation type
discord-alert: true
# Custom alert messages for this specific violation
alert-message: "&8[&cAntiSpoof&8] &e%player% flagged! &cVanilla client with plugin channels"
console-alert-message: "%player% flagged! Vanilla client with plugin channels"
# Whether to punish the player if detection is positive
punish: false
# Punishment actions to execute
# Available placeholders: %player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &cVanilla spoof detected: %reason%"
# - "ban %player% &cVanilla client spoofing detected"
# Super Strict Mode (Not Recommended)
# Blocks players who either:
# - Do NOT have a "vanilla" client, OR
# - Have registered plugin channels (indicating mods/plugins)
# ⚠️ This is an extremely strict mode and may block legitimate players
non-vanilla-check:
# Whether to enable this strict check
enabled: false
# Whether to send alerts to Discord for this violation type
discord-alert: false
# Custom alert messages for this specific violation
alert-message: "&8[&cAntiSpoof&8] &e%player% flagged! &cClient modifications detected"
console-alert-message: "%player% flagged! Client modifications detected"
# Whether to punish the player if detection is positive
punish: false
# Punishment actions to execute
# Available placeholders: %player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &cNon-vanilla client with channels detected"
# - "tempban %player% 1h &cUsing a modified client"
# ──────────────────────────────────────────────────────────
# No Brand Detection Settings
# ──────────────────────────────────────────────────────────
# Some hacked clients avoid detection by not sending a client brand at all
# This check flags players who connect without providing any brand information
no-brand-check:
# Whether to flag players who don't send a client brand
enabled: true
# Whether to send alerts to Discord for this violation type
discord-alert: true
# Custom alert messages for this specific violation
alert-message: "&8[&cAntiSpoof&8] &e%player% flagged! &cNo client brand detected"
console-alert-message: "%player% flagged! No client brand detected"
# Whether to punish the player if detection is positive
punish: false
# Punishment actions to execute
# Available placeholders: %player%, %reason%
punishments:
- "kick %player% &cNo client brand detected"
# - "ban %player% &cSuspicious client detected (no brand)"
# ──────────────────────────────────────────────────────────
# Channel Detection Settings
# ──────────────────────────────────────────────────────────
blocked-channels:
# Enable channel-based detection
enabled: false
# Whether to send alerts to Discord for blocked channel violations
discord-alert: false
# ⚪ Whitelist Mode
# - FALSE: Block listed channels.
# - SIMPLE: Only allow players with at least one whitelisted channel.
# - STRICT: Only allow players who match the exact whitelist and have no extra channels.
whitelist-mode: FALSE
# List of channels to block/whitelist
values:
- "^fabric-screen-handler-api-v1:open_screen$"
# Add more channels to block here
# - "another:blocked:channel"
# - "(?i).*litematica.*"
# - "(?i).*fabric.*"
# Custom alert messages for this specific violation
alert-message: "&8[&cAntiSpoof&8] &e%player% flagged! &cUsing blocked channel: &f%channel%"
console-alert-message: "%player% flagged! Using blocked channel: %channel%"
# Alert when a player's plugin channel is modified
modifiedchannels:
enabled: true
# Whether to send Discord alerts for modified channels
discord-alert: false
alert-message: "&8[&cAntiSpoof&8] &e%player% modified channel: &f%channel%"
console-alert-message: "%player% modified channel: %channel%"
# Whether to punish the player if detection is positive
punish: false
# Punishment actions to execute
# Available placeholders: %player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &cBlocked channel detected: %channel%"
# - "tempban %player% 1d &cUsing blocked mod channels"
# ──────────────────────────────────────────────────────────
# Client Brands Configuration
# ──────────────────────────────────────────────────────────
# This section allows for granular control over different client types.
# Each brand can have its own detection patterns, alert messages,
# punishments, and special exemptions.
client-brands:
# Master switch for the client brands system
enabled: true
# Default settings for brands not explicitly configured
default:
flag: true
alert: true
discord-alert: false
punish: false
# Default alert message if not specified for a brand
alert-message: "&8[&cAntiSpoof&8] &7%player% using unknown client: &e%brand%"
console-alert-message: "%player% using unknown client: %brand%"
# Brand-specific configurations
brands:
# Lunar Client Configuration
lunar:
enabled: true
values:
- "^lunarclient:v\\d+\\.\\d+\\.\\d+-\\d{4}$"
# Whether to count the player as flagged by AntiSpoof
flag: false
# Whether to send in-game alerts for this brand
alert: true
# Whether to send Discord alerts for this brand
discord-alert: false
# Custom alert messages for this brand
alert-message: "&8[&eAntiSpoof&8] &7%player% is using &9Lunar Client &7version: &b%brand%"
console-alert-message: "%player% is using Lunar Client: %brand%"
# Whether to punish players using this brand
punish: false
# Punishment commands if punish is true
punishments: []
# Channels that must be present for this brand to be legitimate
required-channels:
- "lunar.*" # Must have at least one lunar channel
# Punish players if they do not have the channel(s)? Set to false to simply alert.
required-channels-punish: false
required-channels-punishments:
- "kick %player% &cLunar Client spoofing detected"
# Badlion Client Configuration
badlion:
enabled: true
values:
- "^badlion.*"
- "^BLC.*"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% is using &b%brand%"
console-alert-message: "%player% is using Badlion Client: %brand%"
punish: false
punishments: []
required-channels: []
required-channels-punish: false
required-channels-punishments:
- "kick %player% &cLunar Client spoofing detected"
# Forge Configuration
forge:
enabled: true
values:
- "^fml,forge.*"
- "^forge.*"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% is using &b%brand%"
console-alert-message: "%player% is using Forge: %brand%"
punish: false
punishments: []
required-channels:
- "(?i).*forge.*"
required-channels-punish: false
required-channels-punishments:
- "kick %player% &cChannel spoofing detected"
# Fabric Configuration
fabric:
enabled: true
values:
- "^fabric$"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% is using &b%brand%"
console-alert-message: "%player% is using Fabric: %brand%"
punish: false
punishments: []
required-channels:
- "(?i).*fabric.*" # Matches any channel containing "fabric" (case insensitive)
required-channels-punish: false
required-channels-punishments:
- "kick %player% &cChannel spoofing detected"
# LabyMod Configuration
labymod:
enabled: true
values:
- "^labymod.*"
flag: false
alert: true
discord-alert: false
alert-message: "&8[&eAntiSpoof&8] &7%player% is using &b%brand%"
console-alert-message: "%player% is using %brand%"
punish: false
punishments: []
required-channels: []
required-channels-punish: false
required-channels-punishments:
- "kick %player% &cChannels spoofing detected"
# Hacked Clients Configuration
hacked:
enabled: true
values:
- "(?i).*wurst.*"
- "(?i).*impact.*"
- "(?i).*aristois.*"
- "(?i).*future.*"
- "(?i).*meteor.*"
- "(?i).*inertia.*"
- "(?i).*sigma.*"
- "(?i).*liquidbounce.*"
flag: true
alert: true
discord-alert: true
alert-message: "&8[&cAntiSpoof&8] &e%player% is using &c&lknown hacked client: &f%brand%"
console-alert-message: "ALERT! %player% is using known hacked client: %brand%"
punish: true
punishments:
- "kick %player% &cHacked client detected: %brand%"
# - "ban %player% &cUse of hacked client detected"
# Vanilla Configuration
vanilla:
enabled: true
values:
- "^vanilla$"
flag: false # Only flags if the player is caught spoofing
alert: false # Don't alert for vanilla clients by default
discord-alert: false
alert-message: "&8[&cAntiSpoof&8] &7%player% is using &d%brand%"
console-alert-message: "%player% is using %brand%"
punish: false
punishments: []
# Special settings for vanilla
# "strict-check" flags if the client has ANY plugin channels (Must be enabled to detect VanillaSpoof)
# You can add this "strict-check" to any client brand and only then will it be processed by the earlier "vanillaspoof-check"
strict-check: true # Enable strict checking for vanilla (must have NO channels)
vanilla-variation: # When a client shows "Vanilla" or "vAnilla2" but not "vanilla"
enabled: true
values:
- "^(?!vanilla$).*?(?i)vanilla.*"
flag: true
alert: true
discord-alert: true
alert-message: "&8[&cAntiSpoof&8] &e%player% using fake Vanilla: &c%brand%"
console-alert-message: "%player% is using fake Vanilla: %brand%"
punish: false
punishments: []
strict-check: true
blankbrand: # When a client sends a blank brand channel
enabled: true
values:
- "^$" # regex for empty/blank brand
flag: true
alert: true
discord-alert: true
alert-message: "&8[&eAntiSpoof&8] &7%player% &eis using a blank brand"
console-alert-message: "%player% is using a blank brand"
punish: false
punishments: []
# ──────────────────────────────────────────────────────────
# Bedrock Handling Settings
# ──────────────────────────────────────────────────────────
bedrock-handling:
# Choose how to handle Bedrock players.
# Options:
# - "IGNORE": Completely ignore these players; process them like regular players.
# - "EXEMPT": Process them but don't punish them for failing checks.
#
# Either way, Bedrock players won't get the anti-spoof treatment.
# "EXEMPT" mode is highly recommended as "IGNORE" can easily falsely punish Bedrock players.
mode: "EXEMPT"
# Geyser Spoofing Detection
# Detects players claiming a client brand including a variation of "geyser" without being verified
# as Bedrock players by the Floodgate API.
geyser-spoof:
# Whether to enable geyser spoofing detection
enabled: true
# Whether to send alerts to Discord for Geyser spoofing violations
discord-alert: true
# Custom alert messages for this specific violation
alert-message: "&8[&cAntiSpoof&8] &e%player% flagged! &cGeyser client spoofing"
console-alert-message: "%player% flagged! Geyser client spoofing with brand: %brand%"
# Whether to punish the player if detection is positive
punish: false
# Punishment actions to execute
# Available placeholders: %player%, %reason%, %brand%
punishments:
- "kick %player% &cGeyser client spoofing detected"
# - "ban %player% &cGeyser client spoofing"
# Check Player Prefix:
# This option checks whether a player is identified as a Bedrock player by verifying their prefix.
# When enabled, the system will verify if the player's username or identifier starts with the specified prefix.
# Default prefix is ".", and if a player's client brand includes "geyser" in any form without matching
# the expected prefix, they will be flagged.
prefix-check:
enabled: true
# The prefix used to identify Bedrock players.
prefix: "."
# ──────────────────────────────────────────────────────────
# Discord Webhook Settings
# ──────────────────────────────────────────────────────────
discord:
enabled: false
webhook: ""
embed-title: "**AntiSpoof Alert**"
embed-color: "#2AB7CA"
violation-content:
- "**Player**: %player%"
- "**Violations**:%violations%"
- "**Client Version**: %viaversion_version%" # Requires Viaversion and PlaceholderAPI
- "**Brand**: %brand%"
- "**Channels**:"
- "%channel%" # Vertical channel list
# Global settings for all alerts (used as fallback)
# These options control whether to send join messages for players to Discord
# even when they don't trigger any violations
global-alerts:
# Whether to send alerts to Discord when players join with a brand
join-brand-alerts: false
# Whether to send alerts to Discord when players register initial channels
initial-channels-alerts: false
# ──────────────────────────────────────────────────────────
# Update Checker Settings
# ──────────────────────────────────────────────────────────
# Checks for updates from GitHub when the server starts
update-checker:
# Whether to check for updates on startup
enabled: true
# Whether to notify admins when they join
notify-on-join: true
# ──────────────────────────────────────────────────────────
# Legacy Punishment Settings
# ──────────────────────────────────────────────────────────
# Legacy global punishment system (for backward compatibility)
# These punishments will be used if a specific check has 'punish: true'
# but doesn't have its own punishments defined
# Available placeholders: %player%, %reason%, %brand%, %channel%
punishments:
- "kick %player% &cSuspicious client detected!"
# - "ban %player% &cClient spoofing detected"
# ──────────────────────────────────────────────────────────
# Legacy Alert Messages
# ──────────────────────────────────────────────────────────
# Legacy global alert system (for backward compatibility)
# These messages will be used if a specific check is enabled
# but doesn't have its own alerts defined
# Available placeholders: %player%, %reason%, %brand%, %channel%
# Defines the message sent to players with the `antispoof.alerts` permission
# when a spoofing attempt is detected.
messages:
# Message shown to players with antispoof.alerts permission
alert: "&8[&cAntiSpoof&8] &e%player% flagged! &c%reason%"
# Message logged to console (no color codes needed)
console-alert: "%player% flagged! %reason%"
# Message for multiple violations
multiple-flags: "&8[&cAntiSpoof&8] &e%player% has multiple violations: &c%reasons%"
# Message for console when multiple violations
console-multiple-flags: "%player% has multiple violations: %reasons%"
? License
AntiSpoof is licensed under the GNU General Public License v3.0 - see the LICENSE file for details.
Copyright (C) 2025 GigaZelensky
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Made with ❤️ by GigaZelensky
⭐ Star us on GitHub if you find this plugin useful! ⭐
评论 0
登录后参与评分
还没有评论,来抢沙发吧