Short version: a VAC ban comes from Valve’s anti-cheat, a game ban comes from the game’s developer. Rust is protected by Easy Anti-Cheat (EAC), not VAC, and when EAC catches a cheat, Steam adds a game ban to the profile. So a Rust player caught by the anti-cheat shows a game ban while the VAC field stays empty. There is also a third kind, the project ban, and Steam does not know about it at all.
VAC ban
VAC is Valve Anti-Cheat, used in VAC-secured games. The ban is public on the profile: Steam shows how many bans there are and how many days since the last one.
What Steam does not show is which game the ban came from. Rust does not use VAC, so a VAC ban on a Rust player was earned somewhere else, and it does not lock them out of Rust by itself. But people who cheat rarely stop at one game, so after a VAC ban the rest of the report deserves a closer read.
Game ban
A game ban is issued by the game’s developer. For Rust that mostly means an EAC ban: the anti-cheat catches a cheat and a "game ban" appears on the profile. The details are in what an EAC ban is and whether it can be appealed.
Same problem here: Steam shows the fact and how long ago, but not the game. A game ban on a Rust player is a strong reason to look closer, but not proof they were caught in Rust specifically. That is why RustRecon shows game bans as a fact and leaves them out of the risk score: there is no reliable way to tie one to Rust.
Project ban
The third kind, and the most telling one for Rust. A specific server’s admins watched a demo or called the player in for a check, then banned them by hand. Steam has no idea these bans exist.
The large Russian projects publish who they banned, and rustbans.ru collects those lists in one place. A project ban carries what Steam lacks: the project, the date and the reason. The reason matters more than the fact. A ban for chat abuse and a ban for aim are different stories, and many projects treat refusing a check the same as cheating.
Community and trade bans
A Steam profile, and the report, can show two more marks: a community ban and a trade ban. Steam issues these for violations within Steam itself, in the community or when trading items. They have no direct link to cheating in Rust, so when vetting a player for cheats, treat them as background rather than evidence.
Side by side
| VAC ban | Game ban | Project ban | |
|---|---|---|---|
| Issued by | Valve’s anti-cheat | The game’s developer (in Rust, via EAC) | Server admins |
| Given for in Rust | Not used in Rust | Cheats caught by the anti-cheat | Cheats, refused checks, server rules |
| Visible on Steam | Yes | Yes | No |
| Names the game or reason | No | No | Yes: project, date, reason |
| Where it applies | The game it came from | The game it came from | That project’s servers |
What it looks like in a check
Paste a profile link or SteamID into RustRecon. For free you see:
- Steam bans, VAC and game, with how long ago;
- how many projects banned the player.
With Pro you see which projects banned them, why and when, and whether each ban is still in force or lifted. The full breakdown of all three kinds is on checking a player’s bans.
Which ban tells you more
Ranked by weight for Rust:
- A project ban for cheating. People looked at this specific player’s gameplay and reached a verdict. Several projects reaching the same verdict is a pattern.
- A game ban. For a Rust player most likely EAC, but Steam does not name the game.
- A VAC ban. Context: the player got caught in some other game.
Empty ban fields do not mean a clean player. A new Steam account takes five minutes to make, so account age and real hours get read alongside the bans.
More on that in why Steam account age matters in Rust. And keep in mind that the report does not detect cheaters. It gathers open data; the call is yours.