All articles
    Engineering

    How Anti-Cheat Works in VeloRix Tournaments

    Cheaters are the fastest way to kill a tournament community. Here is an honest look at the layers we use to catch them, what we can detect, and what we cannot.

    VeloRix Engineering7 min read

    Ask any Indian mobile gamer why they stopped using a tournament app and the answer is almost always the same: hackers. Someone with auto-headshot walks into a paid lobby, wins, and the organiser either does not notice or does not care. We built VeloRix after losing entry fees to exactly that, so this is the part of the product we are most opinionated about.

    This post is not a marketing page. We want to be specific about what our system does and equally specific about its limits, because any platform claiming a hundred percent cheat-free environment is lying to you.

    Layer one: identity and entry

    Most cheating is repeat behaviour by a small number of accounts. Making it expensive to create new identities removes a surprising share of the problem before a match even starts. Every VeloRix account is tied to a verified contact method, and we track device fingerprints so that a banned player cannot simply register again on the same phone in five minutes.

    We also require in-game IDs to be locked before a tournament closes registration. Late ID swaps are a classic trick used to sneak a smurf or a hired ringer into a lobby that was advertised as a beginner bracket.

    Layer two: statistical anomaly detection

    Cheating produces numbers that honest play does not. We aggregate per-match results and flag accounts whose statistics sit far outside the distribution for their bracket. The signals we weigh most heavily:

    • Headshot ratio that stays abnormally high across many matches, not just one hot game.
    • Kill counts that are inconsistent with survival time — twenty kills in four minutes is not a good day, it is a script.
    • Damage-per-match curves with no variance. Real players have bad games; aimbots do not.
    • Win rate concentrated in specific lobby types, which usually indicates coordinated account sharing.
    • New accounts posting veteran-level statistics from their very first tournament.
    A statistical flag is never an automatic ban. It is a signal that pushes a match into human review, and nothing more.

    Layer three: evidence and human review

    Every tournament result can be disputed by participants within a fixed window after the match ends. Disputes require evidence — a clip, a screenshot, a recording. Our moderators review the evidence against the flagged statistics rather than acting on either alone.

    For prize-pool tournaments, payouts are held until the dispute window closes. This is deliberately inconvenient. It is also the only way to avoid paying a cheater and then being unable to recover the money.

    Layer four: room integrity

    A large share of what players call 'hacking' is actually organiser fraud: fake room IDs, rooms that never start, passwords leaked to friends, or results announced without a match ever happening. We treat this as part of the same problem.

    • Room credentials are released to registered participants only, at a fixed time before the match.
    • Every credential release, result submission and prize distribution is written to an immutable audit log.
    • Organisers cannot edit results after the dispute window closes without leaving a visible trail.

    What we cannot do

    We are a tournament platform, not the game developer. We do not have kernel-level access to your device, we do not read the game's memory, and we do not install anything invasive on your phone. That is a deliberate privacy choice, and it comes with a real cost: we cannot detect a cheat at the moment it executes the way an in-game anti-cheat can.

    What we can do is make cheating unprofitable. If a cheater's account is flagged, their payout is held, their evidence is reviewed and their device is banned, the economics stop working. Most cheating in mobile tournaments is opportunistic rather than sophisticated, and removing the easy money removes most of it.

    How to help

    Record your matches when a prize pool is involved. Screen recording costs you almost nothing and turns a 'he said, she said' dispute into a five-minute decision. When you report someone, include the match ID, the timestamp and what specifically looked wrong. Reports that say only 'he was hacking' are the hardest ones to act on, and they are unfortunately the most common.

    Keep reading