Cheati
一个可配置的、注重减少误报的反作弊系统,适用于 Paper 服务器——涵盖移动、战斗以及世界/库存漏洞。
Cheati 监控你的服务器已经产生的玩家数据,并实时向你的工作人员标记可疑活动。它的核心原则是:抓出作弊者不应意味着惩罚正常玩家。Cheati 的设计投入了大量精力,以避免因延迟、击退、冲刺跳跃或玩家每天做的各种正常但 unusual 的行为而触发警报。
由你决定其干预程度——从静默的工作人员警报,到主动阻止作弊移动,再到自动执行你设定的惩罚命令。所有检测项均可配置,且支持热重载。
它检查什么
移动 — 速度(Speed)、飞行(Fly)、无掉落(NoFall)、耶稣步(Jesus,水上行走)、穿墙(Phase,穿墙)、踏步(Step)、无减速(NoSlow,包括蜘蛛网、灵魂沙、浆果丛和粉末雪)
战斗 — 距离(Reach)、杀戮光环(KillAura)、自动点击器(AutoClicker)
世界与库存 — 快速破坏(FastBreak)、核弹(Nuker)、脚手架(Scaffold)、自动工具(AutoTool)
可选的包级别检测 — 计时器(Timer,需要 PacketEvents 插件)
不仅仅是警报
带有衰减违规缓冲区和非衰减终身计数的员工警报,使得孤立的误报逐渐消失,而持续的作弊行为会持续浮现。
使用 /cheati vl <player> 查看某位玩家针对各项检测的终身违规记录。
每检测项可选的动作预防。移动违规会通过追踪回退到玩家最后一个已知良好位置来纠正(而非粗暴的回弹);战斗和世界违规会取消 offending action;“无掉落”检测会施加原本被规避的下落伤害。仅在需要的地方启用它。
可选的自动惩罚。Cheati 不重新发明封禁机制,而是在你设定的违规阈值时运行你的控制台命令——这样它可以无缝接入你已经信任的任何惩罚插件(LiteBans、AdvancedBan、原版 /ban 等)。
专为避免误报而构建
这是大部分工作所在之处:
对正常移动规则不适用的状态进行集中豁免——例如鞘翅滑翔、载具、激流、漂浮等。
在传送、重生、击退、世界切换、登录、鞘翅开关、游戏模式切换和三叉戟投掷后提供宽限期。
速度/击退追踪——服务器应用的速度(击退、爆炸、鱼竿拉扯、风弹)会在真正关键的几刻内放宽相关上限,从而防止正常的发射被误读为速度或飞行作弊。
延迟补偿——宽限期根据每位玩家的真实延迟进行缩放,因此高延迟玩家不会因仅仅是延迟的问题而被标记。
在飞行检测中使用基于重力的垂直预测,并与 Minecraft 的实际移动物理进行比较,而不是松散的启发式算法。
每项检测的绕过权限——允许从特定检测中豁免受信任的账号(cheati.bypass.<check>),而不降低其他所有保护。
要求
服务器Paper 1.21+(或其分支如 Purpur / Pufferfish)Java21+PacketEvents可选——仅用于包级别的 Timer 检测
Cheati 使用 Paper 特定的 API,无法在纯 Spigot 或 Bukkit 上运行。
命令与权限
/cheati reload — 热重载配置文件
/cheati alerts — 切换警报可见性
/cheati vl <player> — 查看玩家的违规记录
cheati.alerts — 接收警报并使用 /cheati alerts 或 /cheati vl(默认:op)
cheati.admin — 使用 /cheati reload(默认:op)
cheati.bypass / cheati.bypass.<check> — 豁免所有检测,或仅豁免某一项检测(默认:false)
配置
所有内容均在 config.yml 中进行了内联文档说明并可配置——包括检测开关、灵敏度阈值、每项检测的预防措施、宽限期、延迟缩放和自动惩罚阶梯。编辑后运行 /cheati reload 即可生效,无需重启服务器。
关于调优的注意事项:每个服务器的玩家群体移动方式各不相同。Cheati 附带了合理的默认设置,但在观察自己服务器的玩家警报流量之前,最好先开启执行功能(预防和自动惩罚)。配置文件中的注释指出了如果在出现误报或漏报时应调整哪些值。
Cheati
A configurable, false-positive-conscious anticheat for Paper servers — covering movement, combat, and world/inventory exploits.
Cheati watches the same player data your server already produces and flags suspicious activity to your staff in real time. It's built around one principle: catching cheaters shouldn't mean punishing legitimate players. A huge amount of Cheati's design goes into not firing on lag, knockback, sprint-jumps, or the dozens of normal-but-unusual things players do every day.
You decide how far it goes — from quiet staff alerts, to actively blocking cheated movement, to running your own punishment commands automatically. All per-check, all configurable, all reloadable live.
What it checks
Movement — Speed, Fly, NoFall, Jesus (water-walk), Phase (wall-clip), Step, NoSlow (including cobwebs, soul sand, berry bushes, and powder snow)
Combat — Reach, KillAura, AutoClicker
World & inventory — FastBreak, Nuker, Scaffold, AutoTool
Optional packet-level — Timer (requires PacketEvents)
More than alerts
Staff alerts with a decaying violation buffer and a non-decaying lifetime count, so isolated false reads fade out while sustained cheating keeps surfacing.
/cheati vl <player> to review a player's lifetime violations per check.
Opt-in action prevention, per check. Movement violations are corrected with a tracked setback to the player's last known-good position (not a crude rubber-band); combat and world violations cancel the offending action; NoFall applies the fall damage that was dodged. Enable it only where you want it.
Opt-in auto-punish. Instead of reinventing bans, Cheati runs your console commands at violation thresholds you set — so it plugs straight into whatever punishment plugin you already trust (LiteBans, AdvancedBan, vanilla /ban, anything).
Built to avoid false positives
This is where most of the work went:
Centralized exemptions for states where normal movement rules don't apply — flight, elytra gliding, vehicles, riptide, levitation, and more.
Grace windows after teleports, respawns, knockback, world changes, logins, flight toggles, gamemode changes, and trident launches.
Velocity/knockback tracking — server-applied velocity (knockback, explosions, fishing-rod pulls, wind charges) widens the relevant caps for the few ticks it actually matters, so legitimate launches don't read as Speed or Fly.
Latency compensation — grace windows scale with each player's real ping, so high-latency players aren't flagged for what's really just lag.
Gravity-based vertical prediction in the Fly check, compared against Minecraft's actual movement physics rather than a loose heuristic.
Per-check bypass permissions — exempt a trusted account from one specific check (cheati.bypass.<check>) without dropping every other protection.
Requirements
ServerPaper 1.21+ (or a fork such as Purpur / Pufferfish)Java21+PacketEventsOptional — only needed for the packet-level Timer check
Cheati uses Paper-specific API and does not run on plain Spigot or Bukkit.
Commands & permissions
/cheati reload — live-reload the configuration
/cheati alerts — toggle alert visibility
/cheati vl <player> — view a player's violations
cheati.alerts — receive alerts and use /cheati alerts / /cheati vl (default: op)
cheati.admin — use /cheati reload (default: op)
cheati.bypass / cheati.bypass.<check> — exempt from all, or one specific check (default: false)
Configuration
Everything is configurable and documented inline in config.yml — check toggles, sensitivity thresholds, per-check prevention, grace windows, latency scaling, and auto-punish ladders. Edit and run /cheati reload to apply without a restart.
A note on tuning: every server's playerbase moves differently. Cheati ships with sensible defaults, but enforcement (prevention and auto-punish) is best switched on after watching alert traffic for your own players first. The config comments call out which values to adjust if you see a false positive or a miss.
评论 0
登录后参与评分
还没有评论,来抢沙发吧