AntiCheat Safety
Anticheats are not all the same, and there is no permanently safe config. Your ability to bypass depends on the modules and settings you use, and that can vary by server.
If you are new to clients or anticheat concepts, it is smart to learn your limits on an alt first. New users are usually higher risk until they get familiar with what is and is not safe.
How anticheats detect players
Most anticheats detect in two broad ways:
Direct checks (hard checks)
These are checks for things that should not happen at all.
- Impossible movement - flying, speed, etc.
- Invalid packet order/state.
- Actions outside what normal game rules allow.
If a module is doing something fundamentally impossible according to normal game logic, it is usually easy for anticheats to catch.
Note that detection is not always a ban. Some servers will simply mitigate or nullify suspicious actions instead of flagging immediately.
For example, some servers just ignore out-of-range hits rather than banning for them, so a module like Reach can appear to "do nothing" when its just the server choosing to ignore those attacks.
Heuristic checks (soft checks)
These are checks based on patterns and suspicion scoring.
- Server-side heuristics: score behavior over time.
- Human heuristics: staff observation and manual review.
In practice, heuristics are less about one single action and more about whether your overall gameplay profile looks natural across time.
Anticheats can assign weighted score to many smaller signals, then raise action only after enough score accumulates. Staff review works similarly, but with human judgement instead of strict rules.
Many systems are cumulative. One flag may not ban you, but repeated suspicious patterns can build up into a ban.
How users usually get banned
Most bans are caused by one of these:
- Using modules that are directly detectable by design.
- Using unsafe settings on otherwise safer modules.
- Using settings that are fine elsewhere but too aggressive for a specific server.
Even safe modules and safe settings are not a guarantee forever. Anticheats evolve, and detections can happen over time.
False bans are also possible.
False bans
A false ban is when a legitimate player is punished by anticheat. Every anticheat will produce some false bans at some point, usually from overly sensitive checks or lag/desync. Completely false bans are however relatively rare compared to bans from detectable modules or unsafe settings. It's important to keep in mind the possibility, but don't assume a ban is false.
Vape's philosophy
Vape's design philosophy prioritizes modules that operate within human-possible behavior for long-term safety.
That means core module design focuses on realistic in-game actions rather than chasing raw performance at any cost.
At the same time, settings are user-controlled. We cannot practically enforce per-server limits as anticheats change and safe thresholds are never fully defined.
So even when features are designed to be safe, your risk and performance are still in your hands through the modules and settings you choose.
Practical safety mindset
- Ask: "Is this module doing something a human could possibly do in an unmodified game, with just their mouse and keyboard?"
- Avoid modules/settings that grant impossible capabilities (for example, flying, extended reach, zero delay on inventory actions, etc).
- Avoid modules/settings that would be suspicious even if they were technically humanly possible (for example, constant 20 CPS AutoClicker).
- Use settings and modules that multiple experienced users currently recommend for your server. Public Profiles are a good starting point.
- Re-check recommendations over time, because server anticheats change. Follow the forums to keep up with current advice.
Risk labels
Throughout the docs, we use labels to quickly communicate risk level. Note that not every module is going to have one of these labels, we just assign them where we feel it's necessary to point out. Lacking ghost doesn't mean its unsafe.
Ghost: Ghost
Safe when tuned realistically. Replicates human mechanics.
This does not mean "safe at all values". It means the feature can reliably be used in a safe way while using appropriate settings.
Warning: Warning
High-risk functionality that is trivial to detect.
Avoid these completely unless you know what you're doing and/or don't care about getting banned.
New user checklist
- Start conservatively with fewer modules, and begin with modules/settings you reasonably judge to be practically safe.
- Before jumping in, check multiple sources of advice for your specific server (for example Public Profiles and the forums).
- Keep your intel current over time, not just at the start. Re-check after updates, server changes, or meta shifts.
- Do not rage increase settings after losses.
- Instead of forcing aggressive values, look for additional safe modules that still give strong advantages, and learn from what experienced users currently run.
Common questions
"Why did I get banned if I was using safe modules?"
Usually because of settings or the modules that you used. A module can be generally safe, but configured in a way that is too risky for a specific server. One module may be completely safe on one server, but easily detectable on another.
"A feature used to work/bypass. Why is it not working now?"
It's not uncommon to see old videos, stories, or personal experiences of using modules that no longer work today.
Anticheats evolve over time, and old settings or module habits often stop being viable. Some things that worked years ago may now be reliably detected entirely or are at least mitigated.
Vape also evolves, and safer alternatives are added over time to keep giving strong advantages within current limits. Keep up with Updates and recent forum guidance in the forums instead of relying on old meta.
The good news is your opponents on these servers are also subject to the same constraints of the anticheat. And since Vape is designed to work within those constraints, you are actually at a greater relative advantage the stricter the anticheat is.
"If a module is marked safe, can I always use any settings?"
No. "Safe" means it can be used safely, not that every configuration is safe.
"How do I judge if a module is risky?"
You may use your own judgment based on the principles above. But generally following the advice of experienced users is the best way to stay safe.
"Are public profiles always safe?"
No. They are references, not guarantees, and can be outdated. Use Public Profiles as a baseline, then validate against recent forum feedback in the forums.
Check for recent negative reviews on the profile.
If you were banned while using a public profile its highly encouraged that you leave a negative rating on it to protect other users.
"What should I do after a ban?"
Depends the the circumstances of the ban.
If you're a new user, thought you were doing everything right with supposedly safe modules and settings, and got banned anyway: In all likelyhood, you were using something that was not actually safe for your server. Your ability to bypass is almost entirely dependant on the modules and settings used, and this is different per server/anticheat.
Its absolutely still possible that its a fault on our end, a supposedly safe module with supposedly safe settings getting you banned. But this is relatively rare - if you're being cautious by going off of multiple other users advice, you probably wouldn't see them recommending detectable modules/settings.