Rust Bans: EAC, VAC, and Fair Play — How Not to Lose Your Account
Rust bans 2026: how EAC differs from VAC and Facepunch bans, what actually gets you banned, what isn't cheating, how to appeal, and how to avoid a dumb ban.
9 min read · 1,570 words
Introduction
A Rust account isn't just $40 for a copy of the game. It's hours of playtime, a skin inventory, server reputation, and your spot in a team. You can lose all of it in one evening: for a program you ran "just to try," for a friend who decided to "try a cheat for one wipe," or for a chat message a moderator takes the wrong way. Unbans in Rust almost never happen — Facepunch and Easy Anti-Cheat operate on zero tolerance, not warnings.
The problem is most players don't really understand who bans them and for what. They mix up EAC bans with VAC bans, server bans with game bans, send appeals to the wrong place, and get a canned response. Meanwhile, they're scared of things that have nothing to do with cheats: crosshair overlays, stretched resolution, console commands from graphics settings.
This guide breaks down the ban system layer by layer: who issues bans, for what, what actually gets you banned, what doesn't, where to appeal, and which everyday habits you should drop to avoid getting caught in the crossfire.

Four Types of Bans: Who Bans Whom
Rust has four independent ban mechanisms, and they're not connected.
1. Server-specific ban (community/modded). Issued by the admin or moderator of a specific server. Reasons can be anything — from breaking server rules to the owner's personal grudge. Doesn't affect other servers. Appeals go only to that server's Discord.
2. Game ban from Facepunch. The developer bans the account in the game itself. Formally applies to all official servers. Reasons aren't just cheats: playing with cheaters, racist remarks, ban evasion.
3. EAC ban (Easy Anti-Cheat). Rust's main anti-cheat. Triggers automatically when it detects third-party software interfering with the game. A Game Ban mark appears on your Steam profile. All EAC bans are permanent — there are no temporary ones.
4. VAC ban. Valve's anti-cheat. Rust is protected by EAC, so VAC bans here are rare and usually carried over from another game. A VAC ban from another game doesn't block Rust, but it's visible on your Steam profile and often gets you rejected when applying to a clan.
One more thing to remember: EAC doesn't just work on the account. The anti-cheat collects hardware identifiers, so "buy a second account and play from the same PC" is a scenario the system knows how to detect.
What Actually Gets You Banned
The list is shorter than it seems, but every item ends the game forever:
- Any software that interferes with the game process — aimbots, ESP/wallhacks, no-recoil scripts, speedhacks, DMA devices. This one's obvious.
- Scripts and macros that automate gameplay. The key word is automation. A mouse macro that compensates for AK recoil for you is a cheat, not "peripheral tuning."
- Playing with a cheater. Facepunch bans the whole group, not just the software owner. If you knew (or could have known) your teammate was cheating and kept playing — you're caught in the same wave. Appeals on this point almost never go through.
- Racism and toxic content. The studio's stance here is harsher than on many other violations, and these bans are typically not appealable.
- Ban evasion. A new account on the same hardware, buying a "clean" account, using Family Sharing — all of this gets flagged and leads to a ban on the new account.
- Account sharing. Let your brother or friend play, and they run a cheat — you get the ban. To the anti-cheat, it's one account and one computer.
What Is NOT Cheating
Here's where players worry for nothing. Legal and undetected:
- A crosshair overlay, as long as it runs independently of the game process. Facepunch has explicitly confirmed that EAC-compatible overlays like Crosshair X don't lead to bans. The simplest safe option — a marker dot on your monitor — no anti-cheat will ever see.
- Stretched resolution and any monitor settings.
- Console commands from F1: `graphics.*`, `input.rawinput`, grass settings, draw distance, FOV. This is the game's standard interface.
- Key binds via `bind` — including binds for crouching, weapon switching, and voice chat.
- External calculators and wipe maps, stats sites, base planners, browser-based recoil trainers.
- Raising gamma on your monitor. Technically undetectable, but also nearly pointless: since the night lighting shader was added, the game lights a small radius around the player and keeps everything else pitch black. Cranking gamma to "see enemies in the field" no longer works.
There's one gray area — macros. Binding one key to one action is safe. A sequence of mouse movements that replicates the recoil pattern is not.
Appeals: Where to Write and What to Expect
First rule: figure out who banned you, or your appeal goes nowhere.
| Ban type | Where to write | Chances |
|---|---|---|
| Server ban | Server's Discord, to admins | High, if it's a mistake |
| Game ban (Facepunch) | Submit a Request form at support.facepunchstudios.com | Low |
| EAC | EAC appeal form | Very low, response usually in 3-14 days |
| VAC | No appeals available | Zero |
EAC officially states that bans are not lifted on request. The only scenario for reversal is when the ban wave itself is deemed erroneous — then bans are lifted automatically, without player involvement. Opening a ticket doesn't speed that up.
Facepunch, however, has a second chance policy: if enough time has passed since the ban (roughly eight months or more), you haven't tried to evade it, and you haven't re-offended, returning via a fresh Rust purchase on a new account stops being automatically pursued. Trying to come back earlier almost guarantees a new ban — this time with no right to appeal.
Writing an appeal only makes sense in one case: you genuinely didn't run anything. Then write short, to the point, list the software you have installed, and don't argue with the wording. Emotional letters and "I have 6000 hours" don't affect the outcome.
How to Avoid a Dumb Ban
Most "unfair" bans are actually the result of everyday carelessness.
- Close everything that touches process memory. Cheat Engine, debuggers, trainers for single-player games, custom overlays. Even if they're not aimed at Rust, EAC's kernel driver reacts to attempts to access foreign memory.
- Check aggressive antivirus and RGB software. Rarely, but these programs cause false positives and conflicts with the anti-cheat. If EAC complains at launch — start with them.
- Don't give your account to anyone. Not for an hour, not "just to look at the base." One cheat launch from your account — and there's nothing to explain.
- Don't buy accounts. Besides the chargeback risk, you inherit the previous owner's entire history, including unresolved suspicions.
- Leave any team where someone "shoots too well." Not out of politeness, but out of calculation: ban waves hit the whole group, and "I didn't know" isn't an argument here.
- Keep chat neutral. Voice chat in Rust is recorded and reportable. A joke on a public server can cost you your account.
- Install the game through Steam and don't touch the files. Any "optimizers," swapped DLLs, and unpacked builds are a direct path to detection.
FAQ
Can I get an EAC ban lifted through third-party "unban" services?
No. Services promising "100% unban" either sell a template appeal you could write yourself, or instructions for ban evasion — i.e., changing hardware and buying a new account. Ban evasion itself is a violation: if it's detected, the new account gets blocked with no right to appeal.
Will I get banned if my teammate turned out to be a cheater?
Yes, this happens regularly. Facepunch bans whole groups because a cheater usually "feeds" the team: calls out targets, shoots through walls, helps with raids. If you see a teammate knowing more than they should — leave the group and don't join servers with them. That's the only real protection.
Is third-party mouse software considered cheating?
By itself, no — drivers from Logitech, Razer, and similar manufacturers are used by millions of players. What makes it a cheat is the macro content: if it replicates the recoil pattern or auto-clicks for you, that's gameplay automation and grounds for a ban. A simple key bind or DPI adjustment raises no issues.
What do I do if a community server admin banned me?
Go to the server's Discord and talk to the moderation team — this ban doesn't spread to other servers, so you can keep playing anywhere else. It helps to save a screen recording or clip of the moment you got banned for: most major projects have an internal appeal process, and objective evidence works there.
Conclusion
Rust's ban system is simple: EAC catches third-party software and bans forever, Facepunch bans for behavior — cheating, keeping cheater company, racism, and ban evasion — and server admins act on their own rules. Appeals only work at the server level; EAC and VAC reverse decisions themselves if the system made a mistake, not the player.
The practical takeaway is even simpler. Don't run anything that touches the game's memory, don't share your account, don't play with people whose aim raises questions, and don't type things in chat you'll regret. Every other way to improve your game — graphics settings, sensitivity, crosshair overlay, recoil training — is fully legal and gives you more than any cheat, because it doesn't end with losing your account.
Sources: support.facepunchstudios.com (articles "EAC Banned," "Ban Second Chances"), Easy Anti-Cheat (ban policy and appeal form), corrosionhour.com ("How to Appeal RUST Bans"), rust.facepunch.com/news (lighting and anti-cheat updates), Steam Community discussions on EAC-compatible overlays.