VoidAC

Void 2.8.35

CoordinateOffset compatibility

- New option coordinate-offset-compat. Turn it on if you run CoordinateOffset or a similar plugin that hides players' real coordinates. Without it, Void sees the fake coordinates and can false flag. - Players have to rejoin after you enable it (Server restart is advised). - Leave it false if you don't use one of those plugins.

EXPERIMENTAL: DO NOT USE ON PRODUCTION SERVERS

The new killaura checks below are EXPERIMENTAL.

Do NOT enable them on a live / production server.

Only enable them on a test server if you want to help development by reporting false flags and detections. (set killaura-dedicated-experimental-checks: true in `config.yml)

New: dedicated killaura checks (EXPERIMENTAL, test servers only)

Three new checks aimed at modern killauras: - AutoClickerD: flags players who attack at the exact moment their weapon is fully charged, every time, for 48 hits in a row. A human can't keep that timing. - AimGcd: flags rotations during a fight that don't match how a real mouse moves the camera. - AimSnapReturn: flags players who snap onto a target for the hit and snap straight back afterwards. - Want to help? Run them on a test server and send us your alerts (both real cheaters and false flags).

bug fix and optimization.

Void 2.8.1

Added

- New small-caps option in config.yml (off by default). It renders Void's messages in small caps (ᴠᴏɪᴅ ѕᴛʏʟᴇ). It is meant for English only: languages with accents or non-Latin scripts show mixed text. Staff with void.alerts get an in-game warning 5 seconds after joining if it is enabled with another language. - /void help is now paginated (/void help 2), with clickable arrows and clickable commands that fill in the chat. - /void punish now prints a clear summary with the ban ID, duration and reason. - PL and RO languages are now supported on Void. (let me know if something is translated wrongly!)

Changed

- Redesigned all command messages with a consistent look: ✔ for success, ✖ for errors, ⚠ for warnings, and clean label │ value rows. This covers help, alerts, verbose, brands, reload, profile, history, log, debug, list, perf, punish, unban, punishments, banwave and optimizer. - Command messages now use your configured prefix instead of a fixed one. - Usage errors, the update notice shown to admins on join and the /void version result are clearer. The update link is now clickable. - Updated all bundled languages (de, en, es, fr, it, ja, nl, pt, ru, tr, zh). English text that was left untranslated in several of them is now translated, and the Japanese spectate return message is clickable again.

Fixed

- Corrected a typo in the French log-not-found message.

Upgrading

- Existing servers keep their current messages.yml. To get the new look, delete messages.yml and let Void regenerate it. The config.yml update adds small-caps automatically.

Void 2.8.0

Full Minecraft 26.3 support

- Commands work again on Paper 26.3 (Cloud 2.0.1). - New 26.3 entity interpolation for accurate reach and hitboxes, position-based teleports, punch packet, cushions, shelf mushrooms, vehicles floating in any fluid and new block hitboxes.

Complete 26.2 support

- Sulfur geysers are simulated, sulfur cubes and 26.2 mob sizes are tracked, friction and air drag are exact below 26.2.

Smarter connection handling

- Players with a frozen client (minimized with vsync) are no longer kicked while they still answer keep-alives. New option max-frozen-client-time (default 300s) in every language. - Movement sent with an expired transaction clock is cancelled and the player is disconnected immediately.

Fewer false flags

- Sneaking off a block edge while sprinting. - Standing up from a cushion or dismounting in the air. - Mounting horses, boats and other vehicles: speed and ground state now start from the vehicle. - Closing an inventory while seated or right after dismounting (MultiActionsD). - Swim hops through bubble columns and honey on 1.21.2+.

Stronger detection

- Player hitboxes follow crouching, swimming and crawling poses on 1.14+. - Keepsprint bypass on 1.21.2+ closed. - Inventory sneaking on 1.21.9+ is detected (MultiActionsC). - 1.8 wither skeleton hitbox, RotationPlace/RotationBreak buffer fix.

Better diagnostics

- Diagnostic logs are written live and kept on shutdown, and show start velocity, allowed movement range and vehicle timing. (Only useful if false positives / bypasses occur, development-wise.)

Performance

- Collision searches no longer allocate per block, AntiESP and decoys do less work when disabled.

VoidAC 2.7.2

Added

- WallHit detection. Detects attacks against players covered by blocks using multi-angle ray tracing and multiple eye heights. - WallHit cancellation. After reliable confirmation, subsequent attacks through blocks are cancelled, including in Creative. - WallHit configuration. Added WallHit.block-impossible-hits, with fallback to Reach.block-impossible-hits. - Experimental AntiESP and AntiFreecam. Underground chunk masking, entity filtering and dynamic visibility updates. Disabled by default.

Fixed

- Corner attacks that were not detected on modern clients. - Artificial ray tracing gaps caused by applying legacy tolerance to clients running 1.18.2 and newer. - WallHit confirmations lost during the Reach processing path. - Creative attacks and modern interaction packet handling. - Null Block Entity Data NBT that could cause client-side decode errors. - Automatic punishments.yml updates while preserving existing groups and custom settings.

Changed

- Block ray tracing tolerance is now client-version aware. - WallHit uses a temporary confirmation window to reduce false positives without leaving the bypass open. - Alerts now include the detected block, precheck result and cancellation status. - Optimized the AntiESP cache to reduce recalculations, duplicate packets and movement overhead.

#VoidAC 2.7.1

Fixed

AntiSpoofA now respects the config (I forgot to hook it into the config...). The blacklisted client kick from AntiSpoofA is no longer forced unconditionally. It is now hooked into the config, so servers can decide whether Void should automatically disconnect players detected on blacklisted client channels.

Added

- Added anti-spoof.auto-kick to enable or disable automatic kicks from AntiSpoofA. - Added anti-spoof.kick-message to customize the kick message used when auto-kick is enabled.

Changed

- AntiSpoofA still alerts staff when it detects a blacklisted client channel. - Automatic disconnects now only happen when anti-spoof.auto-kick: true.

VoidAC 2.7.0

Fixed

Punishments and unbans now stay synchronized. /void unban removes the native Void ban and can execute the configured external unban command. This fixes cases where Void reported that a player was not banned, but Essentials, LiteBans, or the vanilla ban list still prevented them from joining. Offline-mode punishment handling. Active bans can now fall back to a case-insensitive player name lookup when the UUID generated by an offline-mode server or proxy does not match the UUID stored when the punishment was issued. Self punishment is now blocked. Staff members can no longer accidentally ban themselves with /void punish or add themselves to a ban wave. Console commands are not affected. Invalid punishment durations are rejected. Values such as exploiting can no longer be interpreted as a duration. Void accepts seconds, minutes, hours, days, weeks, compound values such as 1d12h, and permanent bans. Ban wave scheduling. The first automatic wave now waits from the oldest queued entry. Later waves wait from the previous execution time, preventing waves from executing immediately after a restart. Version-specific false positives. PacketOrderA, PacketOrderH, PacketOrderK, BadPacketsG, BadPacketsZ, CrashI, VehicleE, and VehicleF now run only on client versions where their packet behavior is valid.

Added

- /void punish <player> [duration] [reason] now accepts custom reasons with multiple words. - /void banwave add <player> [duration] [reason] now accepts custom reasons. - Missing reasons fall back to Cheating. The fallback can be changed with punishments.manual-punish.default-reason and ban-wave.default-reason. - Manual punishment and ban wave templates now support the {reason} placeholder. - Custom ban wave reasons are stored in banwave.dat and survive server restarts. Existing queue files remain compatible. - Ban wave list output now displays the reason assigned to every queued player. - Added punishments.unban-command for integrations with vanilla bans, EssentialsX, LiteBans, AdvancedBan, and other punishment plugins. - Added viaproxy-warn-on-join to disable ViaProxy join warnings on multi-version and Geyser networks.

Changed

- Manual punishments and ban waves now normalize durations before storing or executing them. - Existing punishment templates without {reason} automatically receive a reason line, so customized server configurations continue working. - Offline ban wave entries are also stored in Void when an external ban command is used, preventing the external plugin and Void from disagreeing.

Void 2.6.9

- Fixed a crash on servers with sulfur spikes. The block was registered with the pointed dripstone collision shape but never as an offset block, so every world update touching one threw and interrupted block tracking for that player, which could in turn cause movement false flags away from the block itself.

VoidAC 2.6.8

Fixed

Console flooding from crasher tools. A malformed packet used to dump a full netty stack trace to the log, so tools that spam invalid packet ids could bury your console in seconds. It is now a single line, and the player is still kicked. Set debug-packet-exceptions: true in the config if you need the full trace back for debugging.

Added

- Malformed packets now report who sent them. Staff get an alert naming the player.

Changed

- Transaction ids are randomised per player instead of counting down from a fixed starting point so that modified client can't detect VoidAC.

VoidAC 2.6.7

Two false flag fixes for modern clients, a couple of hot path cleanups, and the documentation now has a home.

Fixed

Reach and hitbox false flags on 1.21.9 and newer clients. From 1.21.9 the client only restarts an entity's interpolation when the target actually changes. Void restarted it every time, so when a server re-sent a position an entity was already moving towards, Void's copy of the hitbox stayed behind the real one for the rest of that movement and legitimate hits got flagged. Most visible on servers with plugins that resend entity positions, and on entities that move constantly. False flags on 26.1 and newer clients in the packet order checks. Void read client status action 2 as "the player opened their inventory". On 1.7 through 1.15 that is what it means, but 26.1 reuses the same byte to request gamerule values, so a normal client could get flagged for a slot change or an inventory click, and in one case have the click cancelled outright. Affects PacketOrderE and PacketOrderK, which only run with experimental checks enabled. Update checker. bdevs.it has shut down (now it's just a wiki page), so Void no longer queries it. Modrinth is the only source now.

Added

- Documentation is now at https://bdevs.it

Performance

- BadPacketsV no longer allocates a vector on every position packet, which is the busiest path in the plugin. - The interpolation hitbox is now computed from the two endpoints of the step range instead of walking every step and merging boxes. Same box, from up to 19 allocations per call down to one.

VoidAC 2.6.6

Optimization release. No check behaves differently, no config changes, drop it in over 2.6.5 and restart.

VoidAC 2.6.2

Fixed: false Simulation flags when landing after flight

Landing while flying, creative flight, spectator, or elytra produced Simulation violations on the first tick back under prediction. Landing while sneaking made it worst of all, with offsets large enough to trigger an immediate setback, so players were flagged and rubber-banded every single time they touched down. The player's collision box was not being advanced while flight was active, so it stayedfrozen wherever they were last checked. The first tick that got predicted again tested its collision against that stale box, missed the floor the player had just landed on,and reported the whole descent as a violation. This also affected leaving spectator mode and ending an elytra flight, which share the same code path.

Addition: Implemented back code from 2.6.0

Fixed some critical findings that made the simulation engine crash and ban legit players.

Removed 26.x support, implementing it back soon.

VoidAC 2.6.0

Critical: auto-punish could ban legitimate players

If you have punishments.auto-punish enabled, please read this. The threshold was compared against a single check's violations, not the total across all checks as the config described — and it defaulted to 10. Simulation reaches 10 violations on completely honest players as a matter of course (its own alert threshold is 100), so enabling auto-punish would remove real players from your server. Thresholds are now configured per check, with sensible built-in minimums that protect you even if your config file predates this option. The global default moved from 10 to 100.

False positive fixes

- GroundSpoof no longer flags players whose game window is minimised or sitting in the pause menu. A starved client stops ticking evenly, and its ground status was being judged against ticks it never ran. - Fixed water and lava currents applying a push the client never made. Below vanilla's cutoff a negligible current was scaled up to a full-strength push — several times larger than the flag threshold, on every tick in flowing water. - Fixed 1.8–1.13 players drifting on every tick while on the ground: the ground speed calculation was missing the branch those versions use. - Fixed jump prediction on pre-1.20.5 clients, which read a value those versions do not use, and on pre-1.14 clients using Jump Boost. - Fixed levitation being mispredicted by the tick-skip estimator. - Fixed pre-1.17 players in boats and minecarts having their position discarded. - Fixed swimming predictions offering jumps the player never pressed. - Book writing no longer flags when the only page is blank. - Improved precision across fluid levels, diagonal movement and sprinting to match the client exactly. - Sprint hunger check now runs with settled state and correctly treats 6 food as hungry. - Added missing collision shapes for potted golden dandelion and sulfur spike.

Fixes

- Fixed "No SLF4J providers were found" errors on startup. Log output from PacketEvents, the connection pool and Redis was being silently discarded; it now reaches the console.

Additions

- Support for 26.2's attribute-driven friction, air drag and bounciness, including the reworked bed and slime bounce. Older clients are unaffected. - Updated to PacketEvents 2.13.1.

VoidAC 2.5.7

Fixes

- Fixed movement prediction accuracy: collision handling was slightly polluting the player's tracked velocity, causing tiny per-tick drift that could compound into false positives over time. - Fixed slime block bounce detection not accounting for thin blocks (carpets, slabs, etc.) stacked on top of a slime block, which could cause false flags when landing. - Fixed boats and minecarts being incorrectly slowed down by cobwebs and sweet berry bushes, that slowdown is only meant to apply to living entities. - Fixed a memory leak in cross-version movement packet conversion (a buffer was never released). - Fixed a rare disconnect-related NPE when the alert system looked up a player who had already left. - Fixed FastBreak occasionally using outdated ground state information right as a block finished breaking. - Improved elytra gliding precision. - Fixed duplicate-packet handling using the wrong version check on servers running exactly 1.9. - Freecam detection is now disabled by default in freshly generated configs, to avoid surprising new server owners with an experimental check enabled out of the box.

Additions

- Added detection for breaking blocks with a spear (1.21.11+).

Rotation fix Server-side relative teleport packets (relative yaw/pitch flags) are now tracked correctly, preventing potential false flags on rotation checks after a teleport. Anti-autoclicker (A, B, C) Three new complementary checks were added: A catches fixed-interval bots via low inter-click interval variance (CV) B catches randomized bots that fake per-click jitter but still keep a suspiciously flat CPS average over time C catches bots sending multiple attack packets within a single client tick, which is physically impossible for a vanilla client All three are fully configurable in config.yml. Offline ban/punish fix Bans on offline players were not always enforced on rejoin. Two bugs fixed: a UUID mismatch that can occur on proxy setups (name-based fallback added to the login check), and external ban commands like LiteBans not reliably handling offline targets (VoidBanManager now stores the ban as a guaranteed fallback in those cases). Both ban wave and /void punish are covered. Added ViaProxy compatibility and ViaVersion attenuation (check config.yml) to reduce false positives caused by differing vector management.