Private testing live / Swift 2.0
Swift is the packet-level anti-cheat for Minecraft networks that cannot afford guesswork. It replays vanilla physics, kills the advantage in real time, and gives your staff evidence that survives appeals — across every server you run.
SWIFT›Ghost_UserflaggedClicks/MissTime·HIGH
attack 4 ticks after a miss · vanilla refuses for 9
SWIFT›BoatRiderflaggedVehicleFly/BoatSpeed·BLATANT
boat in open air rose 0.2600 vertically · gravity allows 0.2200
SWIFT›Ghost_UserflaggedSilentAim/Excursion·MEDIUM
camera restored to 0.0° after a 14s fight · 2 exits in 2m
sample output 89 detections armed punishments off by default
Bypass killers
Every release is tested against the clients people actually run — including Anubis 0.9.9's silent rotation and base finder. When a bypass lands, the answer ships with a regression test, not a promise.
A silent aura can hide where it aims. It cannot hide the exit. When the camera snaps back to exactly where it started, that is not a hand — it is a client restoring state. Two exits in two minutes flag.
Kills silent aurarotation spoof
The first hit still needs a snap. Swift catches a one-tick turn that beats the player's own best turn outside combat and lands with the look ray on a player.
Kills snap aimsilent first-hit
Vanilla refuses attacks for nine ticks after a miss. An auto clicker that clears the counter sends packets a real client cannot. Swift reads the packet order, not the CPS.
Kills auto clickerclicker bypass
Anubis's base finder probes blocks around a section to make the server answer. Three digs in one tick that no look ray could pick is a scan, not mining.
Kills Anubis base findernuker probe
A boat is not a helicopter. Every move is bounded by friction, water and air — and translated clients are judged too. The 10 blocks/s boat fly no longer skims past.
Kills boat flyvehicle speed
A vanilla client reports a falling player every tick. Twelve tick-ends with no position is a freeze, not lag — a stalled network withholds both, so Swift is not fooled by either.
Kills AirStuckposition freeze
Anubis 0.9.9 · bypass map
Hidden ores are removed from the section palette as well as the blocks, so Anubis's base finder has nothing to read — and the probe scan that follows (up to 18 starts a tick) is caught by FastBreak/Unseen. Base finders that only read data the client already has remain an information problem, not a packet problem: no anti-cheat can detect them from the wire. We publish that limit instead of pretending a packet check solved it.
Full arsenal
Combat, movement, world, protocol and visibility share one packet pipeline, one config, one evidence log and one cloud. Nothing is sold as an add-on. You are not buying a detection list — you are buying the end of the argument.
Speed, no-slow, fly, phase, ground spoof, liquids, glide, riptide, boats and mounts, knockback, air-stuck.
Hits that miss every hitbox, pass through walls, come from a distance no arm could cover, or fire before a human can react.
Camera paths no hand produced: post-attack movement, centre lock, snap-back, mouse-grid assist, axis lock, silent rotations.
Zero-tick auras, ID prediction, anchor chains, totem refills and forged mace smashes.
Air place, impossible cursors, placing through walls, scaffold rotations, fast break, nuker, interaction reach, inventory actions.
Timer, blink, extra moves, position holds, bad packets, ping spoof, latency abuse and sequential knockback evidence.
Ores, chests, barrels, shulkers, spawners and players behind walls are withheld until a line of sight opens. ESP boxes, tracers and nametags have nothing to draw. No second plugin to buy.
37 check modules plus the pre-join client gate, and 100+ named sub-checks in the 2.0 build. The 89 detections are the buyer-facing flag outcomes shown in alerts; silent systems such as LatencyAbuse and XRay never flag.
Camera replay
A flag gives you numbers. A replay gives you the moment. Swift rebuilds the recorded fight from the player's own view — fixed crosshair, moving hitbox, attack and swing ticks — so staff can see what the client was doing without a screen recording.
The recorded fight, tick by tick, from the server's own capture.
The camera view shows the aim path and hitbox. The 3D view rebuilds the players and their movement.
Flag replays sit on player profiles and public ban records; Discord ban embeds play the same replay as a GIF.
Sample replay. Real fights are rebuilt from the server's recorded ticks; terrain is not reconstructed.
Enterprise control plane
Swift Cloud is the operational layer, not a bolted-on dashboard: live flags, central evidence, shared bans, per-server keys and an audit log. The cheat ends in-game. The argument ends in the panel.
Overview, live alerts, players sorted by risk, AI verdicts, ban review and check health. Your staff opens one tab and sees the whole network.
Swift CloudBan once and every connected server enforces it. Every ban carries its flags and the evidence behind them, so a shared ban is never a blind ban.
Fleet-wideEvery cloud ban gets a public record with the checks, the evidence and a one-click appeal. Your staff can show the work instead of defending a score.
Public ban pagesIssue and revoke a key per server. Every staff action is recorded. A compromised key does not become a network-wide incident.
ControlCombatAI/Cloud reads every two-second fight, learns from confirmed cheaters, clean players and pardons across servers, and is cross-validated on players it has never seen. It only flags when measured clean-player false flags stay at 0.5% or less.
AI, measuredThe cloud is optional. With it off, nothing is sent home. MySQL 8 is optional. No licence key, no whitelist, no DRM.
No lock-inPublic flags link
When a player is banned, the alert links to a public flags page: the checks, severity, timeline and appeal. No screenshots to hunt down, no “trust me”.
Machine learning
When the cloud is connected, every two-second fight becomes a motion sequence. Confirmed cheaters, clean players and pardons become training data; grouped cross-validation on players it has never seen becomes its report card. It retrains on a 30-minute loop by default, but stays advisory until it clears an AUC of 0.92 and keeps clean-player false flags at or below 0.5%.
Advisory until it passes. On its own it never bans; it is supporting evidence.
Real flags, real bans, real evidence — the same panel your staff would use on day one.
Performance & compatibility
Packet handlers run on network threads. Visibility, database, Discord and cloud sync run off-thread. The main thread only makes the O(1) Bukkit calls that cannot move.
Fixed memory per player. One jar. Anti-X-ray and anti-ESP included. Every threshold, alert, setback and punishment weight is configurable; /swift reload applies changes live.
Why networks standardize
Most anti-cheats hand you a suspicion score and a prayer. Swift hands you the packet, the tick and the vanilla rule it broke — then lets your staff decide.
Movement, knockback, falls, elytra, tridents, boats and horses are replayed tick by tick against the 26.2 client's own physics. A flag means the move left what an unmodified client can produce — not that it looked odd.
Every client is pinged every tick, so entity positions, knockback and teleports are pinned to the moment the client processed them. Reach and hitbox checks judge the hitbox the attacker's screen was showing. Lag is not a flag.
Speed, fly, phase, NoFall, boat fly, anti-knockback and timer cheats are set back to where the player started. Reach hits, aura attacks, forged smashes and illegal placements are blocked before the server applies them. Suspected cheaters also lose damage before a ban is proven.
Hover alerts, player inspection, tick-by-tick traces, camera replays, Discord webhooks, optional MySQL history and public ban pages with an appeal link. Native staff menus on Java and Bedrock keep the workflow in-game. Every alert carries the numbers behind it.
Punishments ship off. Statistical findings are low weight and can never ban alone. An outbreak guard removes a check from every case while it flags too many players at once. Bedrock players are recognised before their first move and never judged by Java rules.
Launch plan
Swift 2.0 is running on SwiftSMP with the cloud panel, shared bans and live evidence. Early access is the next step; public release follows.
Running live with the cloud panel, shared bans and evidence records. Every Anubis bypass is reproduced, answered and regression-tested before it ships.
Tebex licences, the 2.0 jar, all 37 modules and cloud onboarding for the first networks.
Public release with the full control plane, combat AI and shared-ban network, backed by the same evidence chain.
Early access
One jar, every check, and the cloud when you want it. Packages and prices load live from Tebex — nothing is charged until you confirm on Tebex.
Questions
Swift flags moves and actions an unmodified client cannot produce, and every flag carries the numbers behind it so staff can check it. No anti-cheat can promise zero false flags on every server, so automatic punishments ship off: watch alerts for a few days, then turn them on. A false flag can be replayed from the flag log and a /swift trace.
A live dashboard for every server, central evidence for every flag, shared bans, per-server keys and an audit log. The combat AI learns from confirmed cheaters and clean players across connected servers and is cross-validated on players it has never seen. The cloud is optional; with it off, nothing is sent home.
The AI is tested only on players it has never seen. It stays advisory until its default gate is met—an AUC of 0.92 or better and no more than 0.5% of clean players flagged. Every verdict includes a probability and the reasons behind it, and on its own it never bans: it is supporting evidence for the deterministic checks.
Yes. A cloud ban record carries the checks and evidence behind it, and its public ban page includes an appeal link. Staff can open the player's profile, read the flag numbers and attach a tick-by-tick trace. You are defending evidence, not a suspicion score.
Packet handlers run on network threads. Visibility workers, database flush, Discord delivery and cloud sync run off-thread. spark measured Swift at 0.08% of the main thread; the main thread only makes the O(1) Bukkit calls that must stay there.
Only if you turn automatic punishments on. Bans then rest on proof: a deterministic finding repeated, two corroborating checks, or a persistent pattern on a clean connection. Score only lengthens a proven ban. An outbreak guard removes a check from every case while it flags too many players at once. Staff with swift.bypass are never punished.
Minecraft 1.21 to 26.2 on Paper and Paper forks, with one jar. Swift models the 26.2 client exactly and is verified in play on 26.2. On other server versions it runs and alerts; automatic punishments and setbacks stay locked until you have tested it there and switch them on.
Yes. Geyser and Floodgate players are recognised before their first move is checked and are never judged by Java physics. Anti-X-ray and anti-ESP still apply to them.
No licence key, no whitelist, and with cloud disabled nothing is sent home. The cloud dashboard is optional. The jar is obfuscated and carries the marketplace buyer stamp for leak tracing.
Join the Discord for the opening time, or use the store above once Tebex packages appear. Early-access licences are delivered through Tebex and include updates through the 2.0 cycle.
Swift 2.0 is in private testing. Get the launch ping, early-access keys and a walkthrough of the cloud panel.
Minecraft 1.21 – 26.2 · Paper & forks · PacketEvents 2.13+ · Java 21+