Yes, using no-recoil scripts in Rust is cheating: Facepunch calls them cheats and has banned for them since 2018. In June 2025, Facepunch said EAC had stepped up efforts targeting recoil cheats, often called scripting. If you automate recoil control, you risk a permanent ban.
Is scripting in Rust cheating?
Yes. Facepunch explicitly classifies no-recoil scripts as cheats, so the answer for automated recoil control is clear.
On February 16, 2018, the official Rust account posted: “No-Recoil scripts are cheats” and announced that bans would begin that day. You can read the wording in the official Rust warning about no-recoil scripts.
The June 2025 Rust update provides a later enforcement reference. Facepunch said its anti-cheat partner, EAC, had begun additional efforts targeting recoil cheats, often referred to as scripting.
That gives you both the stated rule and a specific announcement about enforcement. If your question is whether software can compensate for recoil without counting as cheating, Facepunch's answer is no.
Are Rust mouse macros bannable?
Yes, a mouse macro that compensates for recoil is a recoil script by what it does and carries the same ban risk.
Look at the action being automated. If the macro supplies the mouse movement needed to counter recoil, it is automating recoil control for you. Calling it a mouse feature, a helper or a macro does not change that function.
For example, when you press a button and a stored sequence supplies recoil compensation, the relevant feature is that compensation. The product label does not give you an exception to Facepunch's rule.
Keep that distinction in mind when reading claims about macros. A statement that a tool works through mouse software does not answer whether its use is permitted in Rust.
Can Rust detect recoil scripts?
Facepunch says EAC targets recoil scripts, but it does not disclose the detection methods behind account bans.
Its EAC ban guidance says it keeps the specific cheats, software and detection methods private. The same guidance says bans may be issued after a delay rather than immediately when a violation is detected.
The public evidence has limits: it supplies no reliable detection percentage, exact ban timetable or complete list of allowed and banned macros. Nobody outside the detection process can honestly calculate your individual odds from these statements, and you should not assume that every other macro is allowed.
An account remaining playable after script use therefore tells you little about later enforcement. A few sessions without a ban cannot prove that a tool is permitted or that it will escape detection.
How often does Facepunch ban Rust cheaters?
Facepunch reports substantial enforcement, but its published totals do not give you a fixed ban schedule.
By the June 2025 update, Facepunch said it had banned more than 142,000 cheaters that year. Its review of 2025 later reported more than 338,000 total bans, including more than 296,000 permanent bans.
Those are broader enforcement totals. They should not be presented as counts of recoil-script bans, and the permanent bans are included in the total rather than added on top.
The review also said the majority of cheaters were being removed in less than seven hours of playtime. That wording matters: playtime is not elapsed time after a violation, and a statement about the majority is not a deadline for every account.
Facepunch also announced plans to introduce a new third-party anti-cheat layer. That announcement describes an intended addition; it does not confirm that the layer had already launched.
What happens if you get banned for Rust scripts?
An EAC ban is permanent unless overturned through review, and a Rust EAC ban displays a Game Ban status on your Steam profile.
Those consequences are set out in Facepunch's explanation of EAC bans. You should not expect the ban to expire after a temporary suspension period.
The review exception matters if a ban was issued incorrectly, but it is not a promise of removal. When deciding whether to use recoil automation, treat a permanent ban as a possible consequence of that choice.
Can you appeal a Rust EAC ban or use another account?
You can seek review of an EAC ban, but using another Steam account to get around an active game ban counts as ban evasion.
Facepunch says its support team cannot independently overturn an EAC-issued ban. If you believe your ban is incorrect, follow the review route described in the official EAC ban support guidance. A request to Facepunch Support does not give that team authority to remove it.
Creating a fresh account or using an existing second account to circumvent the active ban falls under the stated evasion rule. Changing accounts does not overturn the original decision.
Does buying a Rust script change the ban risk?
No. The Evicted store lists Rust Scripts Evicted, and using it carries the ban risk described here. You can find related listings on the Rust scripts page, but commercial availability gives you no permission from Facepunch to automate recoil and no assurance against a ban.
What should I know about Rust script bans?
Is a recoil mouse macro cheating? Yes. Automating recoil compensation puts it within the recoil scripting Facepunch calls cheating.
Does no immediate ban mean a script is safe? No. Facepunch says EAC bans can be delayed.
Will a Rust EAC ban show on Steam? Yes. It appears as a Game Ban status on your profile.
Can Facepunch Support remove my EAC ban? It cannot independently overturn one; removal requires the appropriate review process.
Recoil scripts are cheating under Facepunch's stated policy and can cost you your Rust account through a permanent ban.
