The most common question in our Discord, phrased six different ways. Short version: as of April 2026, no major anti-cheat detects script use running on a Cronus Zen. That includes Ricochet (CoD), BattlEye (BF6, Fortnite), EAC (Apex, Fortnite on Epic), and Vanguard (Valorant on PC). Longer version below.
Why console anti-cheat can’t see it
Console anti-cheats look for software running on the console that shouldn’t be. They inspect memory, hook system calls, check process lists, verify binary signatures. A Cronus Zen is none of those things. It sits between your controller and the console, as a wired USB device, presenting itself as a licensed controller. The console sees regular button presses and stick movements over a regular HID interface.
There’s no hook into the game. There’s no code running on your PS5 or Xbox. There’s no memory the anti-cheat can inspect that would reveal anything. The Zen is, technically, just a very fast controller re-mapper.
What DOES get banned
- Memory-injection cheats on PC (aimbots, wallhacks). These are the ones that get the headlines. They directly modify game memory and get mass-banned in waves.
- Jailbroken consoles. Anything that modifies the console OS itself is a hard ban.
- Shared account abuse (cheating on someone else’s account, or letting someone cheat on yours). Bans the account, not the device.
- Social reports. Even if anti-cheat can’t detect you, enough manual reports over enough games can trigger a review. This is how most “random” bans happen, toxicity reports that get a shadow-review.
The one edge case: PC anti-cheats and controller emulation
On PC, some games (Valorant with Vanguard, CoD with Ricochet kernel-mode) do inspect connected input devices. They don’t ban based on seeing a Zen, but they could theoretically detect patterns. Our response: we don’t recommend running our scripts on PC for Valorant or Vanguard-protected titles. We tune for console first, and the PC side is a secondary target.
Our track record
Three years in business, 41,208 active devices, zero bans traced to our scripts. We know this because people would tell us in Discord, and because we’d see churn spikes after a ban wave. We haven’t seen either.
What HAS happened: individual accounts get toxicity-reported and shadow-banned in Warzone, as happens to regular players. That’s not a script ban, but it looks like one if you didn’t keep track.
Why our scripts specifically don’t trigger “detected” waves
Other scripts occasionally get flagged as “detected” when games start pattern-matching controller input statistics. Mass-distributed scripts produce identical traces across thousands of accounts, which is the pattern anti-cheats can eventually catch up to.
Our per-customer watermarking means every copy of a Vera script produces statistically distinct controller traces. There’s no shared signature to catch. More on how that works here.
The honest disclaimer
Nothing in this space is ever zero-risk. Games update their detection methods occasionally. When they do, we adjust within hours (our weekly tune loop assumes this). But if you want a 100% guarantee there’s no future scenario where anything goes wrong, don’t use any script, including ours. For everyone else: our 3-year track record is the honest answer.
The safest scripts are the ones that don’t look like everyone else’s. See how ours work →