Why waves.ac starts in shadow mode
Every anti-cheat vendor promises detections. Very few talk about the thing that actually burns communities down: the false ban. One streamer banned mid-event on a bad heuristic costs a game more trust than a hundred cheaters ever did. So waves.ac is built around a rule that sounds slow and turns out to be fast: watch first, act second.
Shadow mode is the default, not a feature
When you drop the waves SDK into your experience, nothing happens to your players. Not a kick, not a warning, nothing. The engine scores play against each player's own baseline, and every verdict lands in your console with the signals and confidence that produced it. You watch it run against your real population: your teleporters that are supposed to teleport, your speed boosts that are supposed to break the speed limit.
That calibration period is where most tools fail silently. If a detector is wrong about your game, you find out from angry players. In shadow mode you find out from a dashboard row, and you tune the threshold before it ever touches a person.
Evidence or it does not ship
waves.ac will not issue a ban without a machine-readable reason and the evidence behind it. That constraint shapes the whole system. A single weak signal is capped at a flag and can never reach a ban on its own; escalation takes independent signals agreeing, or the same person caught in more than one game. Uncertainty downgrades the response every time, and every rung below a network ban, a kick, then a short local ban, can be taken back by your own staff. A full audit log is included on every tier, because reversibility is not a premium feature.
Identity without the snake oil
On Roblox, server code cannot read a player's IP address or hardware. Tools that advertise hardware bans on this platform are describing something the platform does not allow. Our answer to ban evasion is a weighted graph of legitimate platform signals, the kind Roblox actually exposes to a game server, and no more than that. When a fresh account looks like a banned one, it becomes a case for your team to review, and confirmed enforcement flows through Roblox's official Ban API with alt propagation. We do not publish which signals carry the weight, for the obvious reason.
Where it stands today
The platform is live: behavioral detection engine, review queue, identity cases, trust scoring, webhooks, staff roles, audit logging, and a Luau SDK that streams signed events from your servers. Accounts start free in shadow mode with no card. If you run a Roblox experience and you are tired of choosing between cheaters and false bans, this was built for you.