文本版本
VoidAC 是一款免费、开源的基于预测的反作弊系统,专为 Minecraft 服务器设计,是 Grim 的分叉版本
- 免费且开源(GPLv3)。 无需授权密钥,无需认证服务器,无付费层级。你在 GitHub 上看到的代码就是实际运行的代码。
- 开箱即用即安全。 自动封禁默认处于关闭状态。全新安装仅会发出警告、记录日志并(如果你配置了的话)发送 Discord Webhook,以便你在让任何人受到惩罚之前先观察自己的玩家。
- 根据你的服务器自行调整。 可选的“阈值优化器”会研究你信任的玩家的行为标志,并推荐处罚阈值。它永远不会自行更改你的配置文件。
- 一切皆有文档记录且可切换。 插件可以发起的所有网络请求均在下面的“透明度”部分列出。
“基于预测”是什么意思
大多数反作弊系统将玩家的移动与固定限制(速度 X、距离 Y)进行比较。这些限制是一种妥协:足够宽松以避免误伤合法玩家,但这留下了作弊的空间。
VoidAC 的移动检查(Simulation)工作方式不同。对于每个移动数据包,它会在服务器上重新计算原版客户端从上一状态(输入、摩擦力、碰撞、击退、液体、鞘翅、载具等)可能到达的位置集合,并将其与玩家实际所做的操作进行比较。如果客户端报告的移动无法通过游戏规则产生,则会标记。这是 GrimAC 开创的架构,VoidAC 继承自它。
这是一个坚实的基础,而非魔法:没有反作弊系统,无论是基于预测的还是其他类型,都不能保证在每个服务器、客户端和网络条件下零误报。延迟、代理、修改版客户端和版本转换都会造成边缘情况,VoidAC 将它们视为需要修复的错误(参见支持)。
检测覆盖范围
源代码中包含超过 130 个命名检查。其中一些启发式或协议健全性检查而非证明,表格说明了哪些是哪类。
| 领域 | 覆盖内容 | 工作原理 |
|---|---|---|
| 移动 | 速度、飞行、水和岩浆移动(耶稣步)、攀爬、鞘翅、击退和爆炸速度、相位、减速、下落/地面欺骗、冲刺规则(7 项检查)、载具(7 项检查) | 预测引擎加规则检查 |
| 计时器 | 计时器、tick 计时器、负计时器、计时器限制、载具计时器 | 数据包时间平衡,带有可配置的延迟允许值 |
| 战斗 | 攻击距离、盒体扩展、穿墙打击、实体穿透、自我交互、多重交互、自动点击器(3 项检查)、自动装备末影珍珠 | 服务端射线投射和交互规则,以及用于自动点击器的点击统计信息 |
| 瞄准 | 重复查看数据包和以 360 度模数包裹旋转的客户端 | 旋转健全性检查。这些捕获某些作弊客户端的具体缺陷,而非每种辅助瞄准 |
| 建造与破坏 | 伪造、远距离、位置错误、旋转错误及空气/液体放置、多重放置、快速破坏、错误破坏、无挥动破坏等(19 项检查) | 针对客户端应看到的世界状态进行验证。这涵盖了类似脚手架的行为 |
| 物品栏与动作 | 物品栏点击验证(5 项检查)、多重动作(7 项检查) | 服务端物品栏模型 |
| 数据包与漏洞利用 | BadPackets(26 项检查)、PacketOrder(16 项检查)、Post、事务顺序、崩溃(9 项检查)、聊天(4 项检查)、鞘翅漏洞利用(9 项检查)、载具漏洞利用(6 项检查) | 协议验证 |
| 自动化 | Baritone 风格的路径规划 | 启发式 |
| 作弊客户端 | 已知的作弊客户端品牌和插件频道(AntiSpoofA) |
基于签名。 仅捕获自我声明的客户端。默认踢出,可在 config.yml 中切换(anti-spoof.auto-kick) |
检测质量因检查、客户端版本、网络条件和配置而异。如果你想确切知道某个检查的作用,源代码是公开的。
基岩版: 通过 Geyser 或 Floodgate 连接的玩家完全不受检查(所有检查都被跳过),因为 Java 移动规则不适用于基岩版客户端。只有当 VoidAC 运行的服务器上安装了 Geyser 或 Floodgate 时,这才有效。
为真实服务器打造
延迟与状态补偿
VoidAC 跟踪每个客户端实际确认的内容(通过 ping/事务数据包),并且仅在客户端本应看到时才对其自身模型应用服务端更改。这涵盖世界变化(方块、实体)、物品栏、冷却时间、烟花和击退。它的存在是为了减少由延迟和不同步引起的误标记。
每位玩家的世界模型
每位玩家都有自己的补偿视图用于碰撞和移动,因此预测使用的是客户端认为自己在其中的世界,而不是服务器已经推进到的世界。
多版本与 Via 支持
版本特定行为(碰撞盒、移动怪癖、旧客户端看不见的方块)在引擎中处理,包括 OptiFine 的 FastMath。支持使用 ViaVersion、ViaBackwards 和 ViaRewind 的服务器,并且存在跨版本玩家的可选衰减设置(viaversion-attenuation),默认禁用。
线程与平台
数据包处理和预测运行在数据包线程上,而不是主服务器线程上,并且 VoidAC 声明支持 Folia。实际成本取决于你的硬件、玩家数量和插件,因此请测量性能:/void perf 显示预测引擎自身的计时。
管理与处罚
自动处罚
在 punishments.yml 中按检查组配置:违规计数、间隔时间和命令列表。内置操作包括 [alert]、[log]、[webhook] 和 [proxy]。你可以添加任何控制台命令(如 kick、tempban,或你选择的封禁插件)。
此外,config.yml 中的 auto-punish 可以在单个检查达到其阈值时执行封禁或踢出操作。该功能默认禁用。随附配置文件中的注释解释了为何像 Simulation 这样的检查需要比战斗类检查更高的阈值,并警告不要降低这些阈值。
手动处罚与封禁波次
/void punish <player> <duration> [reason]:内置封禁,带有模板化的踢出屏幕和封禁 ID。/void banwave add|list|remove|execute|clear:将嫌疑者加入队列,稍后统一封禁。封禁波次功能在配置中启用,但玩家只有在被手动添加或开启queue-on-auto-punish时才会进入队列。/void unban:移除通过 VoidAC 发出的封禁。- 任何封禁插件均可使用:设置
prefer-custom-ban: true并提供命令模板,例如litebans:tempban {player} {duration} {reason}(随附模板使用 LiteBans 语法,如果你使用其他插件请进行修改)。
调查标记
| 命令 | 用途 |
|---|---|
/void alerts |
切换你自己的警报显示 |
/void verbose |
同时显示接近触发的情况,而不仅仅是已触发的标记 |
/void profile <player> |
查看客户端版本、品牌及相关信息 |
/void spectate <player> 和 /void stopspectating |
旁观某玩家 |
/void history <player> |
按会话存储的违规历史,可按检查名称筛选 |
/void debug <player> |
切换某玩家的预测追踪 |
/void log 和 /void dump |
导出追踪数据或诊断转储(请参阅“透明度”部分了解输出位置) |
/void perf |
预测引擎计时 |
/void brands |
显示客户端品牌 |
/void reload |
重新加载配置 |
违规历史
标记会被存储,以便玩家在登出后回顾。默认后端是本地 SQLite 文件。MySQL、PostgreSQL、MongoDB 和 Redis 后端通过各自的后端配置文件支持,保留时间可配置(默认值:违规记录保留 365 天,会话记录保留 90 天)。整个系统可以禁用(database.enabled: false)。
全方位警报
支持控制台、游戏内工作人员、Discord Webhook,以及通过可选的 VoidBridge 插件(适用于 BungeeCord 和 Velocity)在网络代理中跨服务器同步(消息经过签名且防重放,共享封禁和警报,并按服务器分组)。
阈值优化器(可选启用)
不同服务器的延迟、插件和游戏风格各异,因此在一个服务器上合适的处罚阈值在另一个服务器上可能并不适用。优化器帮助你根据自己的数据选择合适的阈值。
- 在
config.yml中设置threshold-optimizer.enabled: true并执行/void reload。 - 给予可信玩家权限
void.optimizer.legit。 - 运行
/void optimizer start并让服务器以正常游玩状态运行(插件建议至少运行 24 小时)。 - 运行
/void optimizer stop,然后运行/void optimizer save。 - 查看
threshold-optimizer-report.yml,并根据实际情况自行调整你的配置。
工作原理:对于每个检查项,它会记录拥有 legit 权限的玩家所达到的最高违规等级(VL)。如果某个检查项有至少 5 个合法标记,它将推荐 ceil(最高合法 VL x 1.5)。数据不足的检查项将被标记为 insufficient-data。
它不是什么:它不会编辑你的配置文件,也不会自行在后台运行,且推荐结果的质量取决于样本数据。一个玩家在一个晚上产生的五个标记属于稀疏数据,因此在更改生产环境的阈值前请收集更多数据。运行时它会占用少量额外 CPU 资源,完成后请停止它。收集的数据会保留在内存中,直到保存或被丢弃。
Anti-Xray 和 StorageESP(可选,默认关闭)
- Anti-Xray(仅限 Paper): VoidAC 可以为你写入 Paper 内置的 anti-xray 设置(
AntiXray.configure-paper: true)。需要完全重启服务器才能生效。此功能使用的是 Paper 引擎,并非独立的反透视检测器。 - StorageESP 诱饵: 向客户端发送虚假的存储方块以误导 ESP 模组,并可标记与诱饵交互的玩家。拥有
void.storageesp权限的玩家可绕过此功能。
配置中还包含一个实验性的 anti-esp 功能。它明确标记为不适用于生产环境且处于禁用状态。请勿在生产服务器上启用它。
配置与语言
文件在首次启动时生成于 plugins/Void/ 目录下(包括 config.yml、punishments.yml、messages.yml、discord.yml 及数据库文件)。配置文件会在版本间自动更新。
主配置和消息文件附带十三种语言:英语、德语、西班牙语、法语、意大利语、日语、荷兰语、波兰语、葡萄牙语、罗马尼亚语、俄语、土耳其语和中文。处罚、Discord 和数据库模板已翻译为其中 11 种语言(目前波兰语和罗马尼亚语仅覆盖主配置和消息)。
要求
- Java 17 或更高版本。
- Paper、Spigot、Purpur 或 Folia。支持的 Minecraft 版本范围为 1.8 至 26.1。26.2 和 26.3 版本的服务器会被识别,但这些版本上的完整反作弊行为尚未验证,因此在依赖之前请先进行测试。
- PacketEvents 已捆绑,无需单独安装。
- 可选:ViaVersion、ViaBackwards、ViaRewind、Geyser、Floodgate、PlaceholderAPI、ProtocolLib。
- 可选:在 BungeeCord 或 Velocity 上部署 VoidBridge 以实现全网络警报和封禁。
安装方法:将 jar 文件放入 plugins/ 目录,启动服务器,阅读 config.yml,并在启用任何自动处罚功能前,先开启警报运行几天。
透明度
你正在赋予一个插件控制谁可以在你的服务器上玩游戏的权力,以下是它确切还会做什么。所有这些内容都在公开源代码中。
网络请求
- 版本更新检查: 每小时一次,VoidAC 会向公共 Modrinth API 查询最新版本,并通过
void.alerts权限告知管理员。不会发送任何关于你服务器的信息。 - bStats: 标准的匿名插件统计数据。可通过全局配置文件
plugins/bStats/config.yml禁用。 - Discord Webhook: 仅在你配置了 Webhook URL 时启用。嵌入消息中的头像由 Discord 客户端从
crafthead.net加载。 - Pastebin: 仅当你在
pastebin-api-key中填入自己的 API Key 时启用。如果没有 Key,/void log和/void dump命令会将文件保存至你的服务器,而不会上传到任何地方。 - VoidBridge: 仅与你自己的服务器通信,使用你控制的共享密钥进行身份验证。
你可能意想不到的事项
/ac、/anticheat和/blackowlzz命令会打印一条简短的“本服务器使用 VoidAC”提示信息,并附带 Modrinth 和 Discord 链接。默认情况下允许所有玩家执行。若要从玩家列表中隐藏此提示,请移除玩家的void.advert权限(或将其设为 false)。- 当插件作者自己的 Minecraft 账号加入运行 VoidAC 的服务器(仅限在线模式服务器)时,拥有 alerts 权限的管理员会收到加入通知,该账号会收到一条包含版本、平台、玩家数量、TPS 和语言信息的私聊状态消息。即使你禁用了上述信息命令,作者的账号依然可以获取这些信息。这些操作均不授予任何权限,不更改任何设置,也不向服务器外发送数据。
anti-spoof.auto-kick默认处于开启状态,会踢出那些客户端声明自己是已知作弊客户端的玩家。如果你只想接收警报而不直接踢人,可将其设置为false。- 1.18.2 至 1.19.3 版本的 Forge 客户端默认会被断开连接(通过
disconnect-blacklisted-forge-versions配置项),因为这些 Forge 版本自带了扩展的玩家攻击距离。
权限说明
void.exempt 权限可使某玩家跳过所有检测。管理员权限(如 void.alerts)默认赋予 OP,而 void.advert 权限默认对所有玩家开放。
支持与误报处理
VoidAC 由一名开发者维护,支持主要依靠社区力量。如果合法玩家被错误标记,请提交报告:请包含检测项名称、玩家的客户端版本、延迟(ping)以及他们当时正在执行的操作,如果可能的话附上 /void dump 输出。误报报告是引擎持续改进的重要依据。
开源与致谢
VoidAC 在 GNU GPL v3 许可证下发布,并基于同样采用该许可证的 GrimAC 构建。你可以阅读代码、自行编译、报告问题并提交修复方案。仓库中包含针对惩罚机制、配置、本地化、数据包版本校验及反 ESP 逻辑部分的单元测试。
- GrimAC,由 MWHunter (DefineOutside) 及贡献者开发:预测引擎及原始反作弊基础框架。
- LightningGrim,由 Axionize 开发:酌情采纳了其上游修复内容。
- PacketEvents:数据包处理层。
版权所有 © 2026 blackowlzz, MWHunter (DefineOutside) 及贡献者。
Text version
VoidAC is a free, open-source, prediction-based anticheat for Minecraft servers, fork of Grim
- Free and open source (GPLv3). No license key, no authentication server, no paid tier. The code you read on GitHub is the code that runs.
- Safe out of the box. Automatic bans are off by default. Fresh installs only alert, log and (if you configure it) send Discord webhooks, so you can watch it on your own players before letting it punish anyone.
- Tune it on your own server. An opt-in Threshold Optimizer studies flags from players you trust and recommends punishment thresholds. It never changes your config by itself.
- Everything is documented and switchable. Every network request the plugin can make is listed in the Transparency section below.
What "prediction-based" means
Most anticheats compare a player's movement against fixed limits (speed X, distance Y). Those limits are a compromise: loose enough not to hit legit players, which leaves room for cheats.
VoidAC's movement check (Simulation) works differently. For every movement packet it recomputes, on the server, the set of positions the vanilla client could have reached from the previous state (input, friction, collisions, knockback, liquids, elytra, vehicles and more), and compares that with what the player actually did. If the client reports movement the game rules cannot produce, it flags. This is the architecture GrimAC pioneered, and VoidAC inherits it.
It is a strong foundation, not magic: no anticheat, prediction-based or not, can promise zero false positives on every server, client and network. Lag, proxies, modded clients and version translation all create edge cases, and VoidAC treats them as bugs to fix (see Support).
Detection coverage
More than 130 named checks ship in the source. Some of them are heuristics or protocol sanity checks rather than proofs, and the table says which is which.
| Area | What is covered | How it works |
|---|---|---|
| Movement | Speed, fly, water and lava movement (Jesus-style), climbing, elytra, knockback and explosion velocity, Phase, NoSlow, NoFall / ground spoof, sprint rules (7 checks), vehicles (7 checks) | Prediction engine plus rule checks |
| Timers | Timer, tick timer, negative timer, timer limit, vehicle timer | Packet timing balance with a configurable lag allowance |
| Combat | Reach, hitbox expansion, hits through walls, entity pierce, self-interact, multi-interact, AutoClicker (3 checks), AutoTotem | Server-side ray casts and interaction rules, plus click statistics for AutoClicker |
| Aim | Duplicate look packets and clients that wrap their rotation modulo 360 | Rotation sanity checks. These catch specific flaws in some cheat clients, not every aim assist |
| Building and breaking | Fabricated, far, out-of-position, wrong-rotation and air/liquid placement, multi-place, fast break, wrong break, no-swing break and more (19 checks) | Validated against the world state the client should see. This covers scaffold-style behavior |
| Inventory and actions | Inventory click validation (5 checks), multi-actions (7 checks) | Server-side inventory model |
| Packets and exploits | BadPackets (26 checks), PacketOrder (16 checks), Post, transaction order, Crash (9 checks), Chat (4 checks), Elytra exploits (9 checks), Vehicle exploits (6 checks) | Protocol validation |
| Automation | Baritone-style pathing | Heuristic |
| Cheat clients | Known cheat client brands and plugin channels (AntiSpoofA) |
Signature-based. Only catches clients that announce themselves. Kicks by default, switchable in config.yml (anti-spoof.auto-kick) |
Detection quality varies by check, client version, network conditions and configuration. If you want to know exactly what a check does, the source is public.
Bedrock: players connected through Geyser or Floodgate are not checked at all (all checks are skipped for them), because Java movement rules do not apply to Bedrock clients. This only works if Geyser or Floodgate is installed on the server VoidAC runs on.
Built for real servers
Latency and state compensation
VoidAC tracks what each client has actually acknowledged (via ping/transaction packets) and applies server-side changes to its own model only when the client would have seen them. This covers world changes (blocks, entities), inventory, cooldowns, fireworks and knockback. It exists to reduce false flags from lag and desync.
Per-player world model
Each player has their own compensated view of the world used for collision and movement, so predictions use the world the client believes it is in, not the one the server has moved on to.
Multi-version and Via support
Version-specific behavior (collision boxes, movement quirks, blocks that older clients cannot see) is handled in the engine, including OptiFine's FastMath. Servers using ViaVersion, ViaBackwards and ViaRewind are supported, and optional attenuation settings exist for cross-version players (viaversion-attenuation), disabled by default.
Threading and platforms
Packet handling and prediction run on packet threads rather than the main server thread, and VoidAC declares Folia support. Real cost depends on your hardware, player count and plugins, so measure it: /void perf shows the prediction engine's own timing.
Moderation and punishments
Automatic punishments
Configurable per check group in punishments.yml: a violation count, an interval and a command list. Built-in actions are [alert], [log], [webhook] and [proxy]. You can add any console command (kick, tempban, your ban plugin of choice).
Separately, auto-punish in config.yml can ban or kick when one check reaches its own threshold. It is disabled by default. The comments in the shipped config explain why checks like Simulation need a higher threshold than combat checks and warn against lowering them.
Manual punishments and ban waves
/void punish <player> <duration> [reason]: built-in ban with a templated kick screen and a ban ID./void banwave add|list|remove|execute|clear: queue suspects and ban them together later. The ban-wave feature is enabled in the config, but players only enter the queue if you add them or turn onqueue-on-auto-punish./void unban: removes bans issued through VoidAC.- Any ban plugin works: set
prefer-custom-ban: trueand a command template such aslitebans:tempban {player} {duration} {reason}(the shipped template uses LiteBans syntax, so change it if you use something else).
Investigating flags
| Command | Purpose |
|---|---|
/void alerts |
Toggle alerts for yourself |
/void verbose |
Also show near misses, not only flags that fired |
/void profile <player> |
Client version, brand and related info |
/void spectate <player> and /void stopspectating |
Spectate a player |
/void history <player> |
Stored violation history by session, filterable by check name |
/void debug <player> |
Toggle the prediction trace for a player |
/void log and /void dump |
Export a trace or a diagnostic dump (see Transparency for where it goes) |
/void perf |
Prediction engine timing |
/void brands |
Show client brands |
/void reload |
Reload configuration |
Violation history
Flags are stored so you can review them after the player logs out. The default backend is a local SQLite file. MySQL, PostgreSQL, MongoDB and Redis backends are supported through per-backend config files, and retention is configurable (defaults: 365 days for violations, 90 days for sessions). The whole system can be disabled (database.enabled: false).
Alerts everywhere
Console, in-game staff, Discord webhooks, and across a proxy network with the optional VoidBridge plugin for BungeeCord and Velocity (signed, replay-protected messages, shared bans and alerts, grouping by server).
Threshold Optimizer (opt-in)
Different servers have different lag, plugins and playstyles, so a good punishment threshold on one may be wrong on another. The optimizer helps you pick thresholds from your own data.
- Set
threshold-optimizer.enabled: trueinconfig.ymland/void reload. - Give trusted players the permission
void.optimizer.legit. - Run
/void optimizer startand let the server run with normal play (the plugin recommends at least 24 hours). - Run
/void optimizer stop, then/void optimizer save. - Review
threshold-optimizer-report.ymland apply what makes sense to your config yourself.
How it works: for each check it records the highest violation level reached by players with the legit permission. If a check has at least 5 legit flags, it recommends ceil(highest legit VL x 1.5). Checks with less data are marked insufficient-data.
What it is not: it does not edit your config, it does not run in the background by itself, and a recommendation is only as good as the sample. Five flags from one player on one evening is thin data, so collect more before changing production thresholds. It uses a small amount of extra CPU while running, so stop it when you are done. Collected data is held in memory until saved or discarded.
Anti-Xray and StorageESP (optional, off by default)
- Anti-Xray (Paper only): VoidAC can write Paper's built-in anti-xray settings for you (
AntiXray.configure-paper: true). It needs a full restart to apply. This uses Paper's engine, it is not a separate xray detector. - StorageESP decoys: sends fake storage blocks to clients to mislead ESP mods, and can flag players who interact with a decoy. Players with
void.storageespbypass it.
An experimental anti-esp feature also exists in the config. It is clearly marked as not production ready and is disabled. Do not enable it on a live server.
Configuration and languages
Files are generated on first start under plugins/Void/ (config.yml, punishments.yml, messages.yml, discord.yml, database files). Configs update themselves between versions.
Thirteen languages are bundled for the main config and messages: English, German, Spanish, French, Italian, Japanese, Dutch, Polish, Portuguese, Romanian, Russian, Turkish and Chinese. Punishment, Discord and database templates are translated into 11 of them (Polish and Romanian currently cover only the main config and messages).
Requirements
- Java 17 or newer.
- Paper, Spigot, Purpur or Folia. Minecraft 1.8 through 26.1 is the supported range. Servers on 26.2 and 26.3 are recognized, but full anticheat behavior on those versions has not been verified yet, so test before relying on it.
- PacketEvents is bundled, you do not need to install it.
- Optional: ViaVersion, ViaBackwards, ViaRewind, Geyser, Floodgate, PlaceholderAPI, ProtocolLib.
- Optional: VoidBridge on BungeeCord or Velocity for network-wide alerts and bans.
Install: drop the jar in plugins/, start the server, read config.yml, and run with alerts on for a few days before enabling any automatic punishment.
Transparency
You are giving a plugin control over who can play on your server, so here is exactly what else it does. All of this is in the public source.
Network requests
- Update check: once an hour, VoidAC asks the public Modrinth API for the latest version and tells staff with
void.alerts. Nothing about your server is sent. - bStats: standard anonymous plugin statistics. Disable it globally in
plugins/bStats/config.yml. - Discord webhooks: only if you configure a webhook URL. Avatars in embeds are loaded from
crafthead.netby the Discord client. - Pastebin: only if you put your own API key in
pastebin-api-key. Without a key,/void logand/void dumpsave files to your server and upload nothing. - VoidBridge: talks only to your own servers, authenticated with a shared secret you control.
Things you might not expect
- The
/ac,/anticheatand/blackowlzzcommands print a short "this server uses VoidAC" message with the Modrinth and Discord links. It is allowed for everyone by default. Remove thevoid.advertpermission from players (or set it to false) to hide it. - When the plugin author's own Minecraft account joins a server that runs VoidAC (online-mode servers only), staff with alerts see a join notice, and that account receives a private status message (version, platform, player count, TPS, language). The author's accounts can also get an answer to the info command above even if you block it. None of this grants any permission, changes any setting or sends data off your server.
anti-spoof.auto-kickis on by default and kicks players whose client announces a known cheat client. Set it tofalseif you would rather only be alerted.- Forge clients on 1.18.2 to 1.19.3 are disconnected by default (
disconnect-blacklisted-forge-versions) because those Forge versions shipped with extended player reach.
Permissions
void.exempt skips all checks for a player. Staff permissions such as void.alerts default to OP, while void.advert is open to everyone.
Support and false positives
VoidAC is maintained by one developer, and support is community-based. If a legitimate player gets flagged, please report it: include the check name, the player's client version, ping and what they were doing, and attach a /void dump if you can. False-positive reports are how the engine gets better.
Open source and credits
VoidAC is released under the GNU GPL v3 and is based on GrimAC, which uses the same license. You can read the code, build it yourself, report issues and send fixes. The repository includes unit tests for parts of the punishment, config, localization, packet-version and anti-ESP logic.
- GrimAC by MWHunter (DefineOutside) and contributors: prediction engine and original anticheat foundation.
- LightningGrim by Axionize: upstream fixes incorporated where applicable.
- PacketEvents: packet layer.
Copyright 2026 blackowlzz, MWHunter (DefineOutside) and contributors.
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 VoidAC
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
Void 2.9.0
修复
- AntiKB 绕过(Grim #2371):当空闲玩家(在 0.03 移动范围内)旁边发生方块变化时,会重新计算待处理的击退和爆炸效果,并可能丢弃玩家已获得的速度,导致击退效果从未生效。现在,当重新计算未找到新值时,Void 会保留之前的速度。
- BadPacketsU:"使用物品"放置数据包的预期 Y 坐标现在被比较为客户端发送的原始 12 位值,因此当 PacketEvents 以 1.14 之前格式解码位置时(适用于旧服务器或无法识别的服务器版本),不再出现误报。
- AimSnapReturn:闪烁并返回的移动不再被用作下一次快照的起点,因此单次振荡不会被重复计数。当应用豁免条件时(传送、载具、旁观者模式),命中计数器也会重置。
变更
- 基岩版玩家:Floodgate 玩家(Geyser)现在不受专用杀戮光环检查(AimGcd、AimSnapReturn、AutoClickerD)的限制,因为手柄和触控输入不遵循鼠标灵敏度网格。
- 添加了针对名为
22ix或使用我的 UUID 的账户的未验证调试消息(可通过设置unverified-dev-debug-greet关闭)。该消息仅显示基本的 Void 信息且不授予任何权限,它只是帮助我在用户服务器上调试。
关于这个资源的讨论、问题反馈与使用心得
还没有讨论,来发第一帖吧
你是这个资源的作者?登录后可认领此资源。
相似资源
插件
PacketEvents 是一款专为 Minecraft Java 版打造的协议库,旨在简化数据包的处理与传输。
插件
ExyliaPlugins 的库。
插件
通过对话框或铁砧界面帮助你的 Anthme
插件
重新定义服务器上的生物运输方式。使用高度可定制的口袋道具,安全地捕获、存储和释放任何实体。
插件
为基于 Spigot/Paper/Folia 的服务器添加对 Vivecraft 的支持
插件
用于绘制游戏内地图或在浏览器中随探索实时进行地图绘制的实时地图。
评论 0
登录后参与评分
还没有评论,来抢沙发吧