DMA setup for Rust: EAC and the monthly wipe cycle
Rust runs Easy Anti-Cheat plus Facepunch's own server-side analysis, and a forced-wipe update ships on the first Thursday of every month. What that cycle means for a DMA build.
Short answer
Rust runs Easy Anti-Cheat and Facepunch's own server-side analysis, with a forced-wipe update on the first Thursday of each month. A DMA card goes in the game PC and the reader on a second PC, and radar and loot data need no input device. For Rust, this store sells an external cheat (/products/rust) and a DMA cheat with a Blurred build (/products/rust-dma).
On this page9
- Which anti-cheat does Rust use?
- When does Rust update and wipe?
- Why a hardware ban costs more than a broken build
- What hardware does a Rust build need?
- In what order should you start everything?
- Pre-session checklist for Rust
- Common Rust problems and how to fix them
- Common questions about Rust builds
- Is a Rust build working this month?
Which anti-cheat does Rust use?
Rust uses Easy Anti-Cheat with a kernel-mode driver on the game PC, and Facepunch routes EAC game bans through EAC rather than its own support. Facepunch adds its own server-side work: recoil pattern analysis, hit-registration checks and input-stream behaviour, all judged on the server, where no client-side architecture reaches. Rust also runs a public, scheduled ban programme rather than quiet enforcement, and it hands out hardware-keyed bans more readily than most EAC titles. On this title, server-side behavioural judgement and aggressive hardware bans matter more than the anti-cheat's name does.
When does Rust update and wipe?
Rust has the most predictable calendar in this catalogue, because it tells you in advance when an update will break your build. Almost no other title does that, so plan around it rather than being surprised by it.
- Monthly update
- First Thursday of every month, around 19:00 UTC
- What it changes
- The client moves and every server force-wipes, because map generation changes with the build
- Between updates
- Smaller patches and server-side changes land without a headline
- Ban rhythm
- Facepunch runs a public weekly ban wave, traditionally on Thursdays
- Practical expectation
- Treat the first Thursday of the month as a hard stop for any build until a new status is published
Warning
Why a hardware ban costs more than a broken build
A broken build costs you an evening, but a hardware-keyed ban costs you the identity of the machine. Rust is one of the titles where that difference is real rather than theoretical. It is also why the spoofer question comes up on Rust more than on any other title. No setup advice and nothing sold anywhere makes a ban impossible. If you are not willing to lose both the account and the machine identity, reconsider this title.
What hardware does a Rust build need?
Rust is a strong case for a read-only build, because what wins a session is information. A radar or ESP on a second screen shows where people are, which direction they come from and what is worth carrying, with no input device. Aim assistance adds an input device the game PC must accept as an ordinary mouse, and Rust's server-side recoil analysis watches exactly what that device changes. A fuser is optional, since it only moves the overlay from a second screen onto your main monitor.
In what order should you start everything?
Rust sessions are long and interruptions are expensive, so the checks before a session matter more here than on a round-based title.
- Check the status board before you plan a session, and check the date of the last Rust update against it
- Boot the game PC and let Windows settle
- Boot the second PC and confirm the card enumerates
- Start the reader and attach to the card before the game launches
- Launch Rust through Steam and let EAC load with the game
- Attach to the game process once you are in a server, not at the main menu
- If a fuser is in the path, run borderless windowed so alt-tabbing to a map site does not resync the signal
Pre-session checklist for Rust
- It is not the first Thursday of the month, or if it is, you have already accepted the build is down
- You checked the status board row for this title today
- The last Rust update predates the published status, not the other way around
- The card is in its data port and the reader attached before the game launched
- You are prepared for a hardware-keyed ban as the worst case, not just an account ban
- Nothing else on the second PC shares the USB controller with the card
- Borderless windowed is set if a fuser is in the video path
Common Rust problems and how to fix them
| Symptom | Likely cause | Fix |
|---|---|---|
| Everything broke on a Thursday | The monthly update landed, which is the scheduled break and not a fault | Stop and wait for a new status to be published, because retrying an old build against a new client achieves nothing |
| Build works on one server and not another | Server-side configuration or a modded server, not the card | Test on a second official server before assuming the build is down |
| Reader drops mid-session after hours of play | Almost always the USB path — a marginal cable, a hub, or thermal drift on the card | Go direct to a rear USB 3 port with a short known-good cable, and check airflow around the card |
| Game launches but EAC reports an integrity problem | A Steam file verification issue or an interrupted update on the game PC | Verify the game files through Steam and let the update finish before involving the reader |
Common questions about Rust builds
Will my build survive the monthly update?
Assume not, because the first-Thursday update moves the client and forces a wipe on every server. Plan the evening around the status board rather than around hope.
Is radar-only worth it on Rust?
It is a strong fit, because position and loot information carries most of the value in Rust. A read-only build has no input device, no fuser and far fewer failure points.
Does a DMA build avoid Rust's hardware bans?
No. A hardware ban is tied to identifiers the game PC exposes, and a DMA card does not change those. That is a spoofer question, and a separate purchase with its own honest limits.
Does Facepunch's server-side analysis see a DMA build?
It sees what you do, such as recoil patterns, hit registration and input rhythm, and architecture does not change any of that. This is the part of Rust's detection that no hardware choice addresses.
Is Rust safer than Valorant for this?
It is a different risk, not a smaller one. Rust has no boot-level platform requirements, which makes configuration easier, but it enforces harder on behaviour and bans hardware more readily. Neither title is safe, and we will not rank them for you as if they were.
Info
Is a Rust build working this month?
The calendar and the anti-cheat are stable facts, but whether a Rust build works this month is not. The live status board shows when a status was published and when Rust last shipped a build. If the game's date is newer, the row is stale and you have your answer.
Sources
The per-title details come from running the build rather than from a published document, and they change with the first-Thursday wipe.
Read next
- DMA setup for Escape from Tarkov: BattlEye and raid length
- DMA setup for Apex Legends: EAC and the season cycle
- What are DMA cheats and how do they work
- Permanent vs temporary HWID spoofer
- How to read the build status board
- DMA setup for Call of Duty: one anti-cheat, a new game every year
- DMA setup for Dead by Daylight: EAC, anti-cheat trials and 4v1 play
- Deadlock: a shooter with a MOBA underneath it
Still stuck? Open a ticket on Discord
All guides