What Should My Rust Cheat Settings Be?
For Rust use Smoothness 0.5-0.6, Aim FOV 4-6 degrees, Hitbox Priority Head with Chest fallback at 100m+, Visibility Check on, Recoil Compensation on (Rust has significant patterns), Humanizer Trigger Delay 100-160ms. Enable Item ESP for rare loot but cap at 50m. Disable Building ESP. Avoid Thursday updates — Facepunch ships patches Thursdays and EAC signatures arrive within the same window. Save to a Solo/Group config slot.
Rust is a different cheat-tuning problem than Fortnite or PUBG. Engagements stretch from point-blank to 200+ meters, recoil patterns are core mechanics rather than RNG, and item value drives the meta — both the goals and the detection vectors look different. The settings below are a defensible starting point.
Why Rust differs from other FPS tuning
Rust's recoil patterns are skill-based — AK, MP5, M249, and Bolt Action all have learnable spray patterns. Facepunch's stat scoring treats accuracy at range as a function of weapon mastery. This means: 1) recoil-comp aimbot fits the believable bell curve, 2) item ESP is more useful than in BR games, and 3) Thursday updates are the highest-risk session window.
Aimbot smoothness
0.5-0.6. Rust engagements at longer range need slower aimbot tracking to look like recoil-comped spray rather than snap-shots. Closer than 30m, 0.45 is fine — close-range Rust is fast and reaction-time-dominant. The Raw menu's range-based smoothness (slower at distance, snappier up close) is the right setting.
Aim FOV
4-6 degrees. Rust's open sightlines mean wider FOV grabs distant unrelated targets — keep it tight. 4 degrees inside builds and close engagements, 6 outside. The Raw menu's FOV-by-range setting handles this automatically if enabled.
Hitbox priority
Head priority with Chest fallback at 100m+. Below 100m head priority is fine — Rust's head hitbox is consistently sized. Beyond 100m, bullet drop and recoil make head shots from spray difficult, so server-side stats expect chest hits at distance. Pure head-priority at 200m produces a hitbox-distribution pattern that's the easiest Facepunch flag in the system.
Visibility check
ON. Rust's procedural terrain means wallhacks track through hills and bushes — visibility-off aimbot snaps to distant enemies on the other side of a ridgeline, producing impossible shot patterns. Visibility check on keeps engagements honest.
Recoil compensation
ON. AK and M249 patterns benefit most. The Raw menu's compensation strength should be set to 0.7-0.85 — not 1.0. Perfect recoil compensation is the textbook detection signature Facepunch and EAC trained their behavioral models on after the 2022-2023 no-recoil ban waves. 0.7-0.85 produces a clean spray with a small residual deviation that matches a strong legit player.
Item ESP
ON. Set Filter to Rare and Higher. Max Distance 50m. Show: weapons, scrap, components, electrical components, military crates. Hide: stones, wood, food (clutter). Item ESP at long range produces obvious loot-magnet behavior in replay reviews and server logs.
Building ESP
OFF. Spotting builds through the world is conspicuous on server-side analytics — sudden raids on unexposed builds get flagged. Use the normal Rust map and stash-hunting flow.
Thursday update windows
Facepunch ships Rust patches every Thursday at variable times. EAC signature updates often arrive in the same window. Check the forum status board before every Thursday session. The Raw loader auto-pauses on detection but the safer habit is to skip Thursdays entirely for 6-12 hours after patch.
Config slots
Save Solo (smoothness 0.6, FOV 5, recoil-comp 0.75), Group (smoothness 0.55, FOV 6, recoil-comp 0.80), and Roam (smoothness 0.5, FOV 5, recoil-comp 0.85). Load slots based on play style. For more on Rust-specific anti-cheat behavior see how does Facepunch detect Rust cheaters and the Raw Rust product page.
Related Pages
Sources
- About Easy Anti-Cheat — Epic Games
- Rust News — Facepunch Studios
- BattlEye Support FAQ — BattlEye Innovations
Related Questions
Replay reviewers (Fortnite FNCS staff, Apex ALGS officials, PUBG Global Series committee) watch full match replays at half-speed looking for pre-aim through walls, sub-100ms snap reactions, perfect pre-fire on corner peeks, gaze on occluded enemies, and abnormal target switches. Behavior — not settings — is what they catch. Don''t pre-fire empty corners, don''t track players through walls, take small visual cues before engaging, miss occasional shots intentionally. Skip tournament-tier play entirely.
Open the cheat menu with INSERT, expand the Aimbot section, set Hitbox Priority to Head + Chest, Smoothness to 0.4-0.6, FOV to 4-8 degrees, Visibility Check on, and Humanizer Trigger Delay to 80-150ms. Bind Aimbot Hold to RIGHT MOUSE for ADS-only activation. Avoid Smoothness below 0.3, FOV above 12 degrees, or visibility check off — those settings are what replay reviewers and behavioral anti-cheats catch. Save to a config slot when finished.
Open the menu with INSERT, navigate to Visuals or ESP, enable Player Boxes, Skeleton, and Health Bar, set Max Distance to 200-300 meters depending on the game, and enable Visibility Color so visible enemies render one color and occluded enemies another. Avoid loud overlays like neon green skeletons or 1000m render distance — replay reviewers catch obvious ESP usage. Disable Item ESP entirely in tournament-tier games. Save to a config slot.
For Fortnite use Smoothness 0.5, Aim FOV 5-7 degrees, Hitbox Priority Head + Chest, Visibility Check on, Humanizer Trigger Delay 90-140ms randomized, and Aimbot Hold bound to right mouse for ADS-only activation. Disable always-on aimbot and any FOV setting above 10 degrees — Fortnite FNCS replay review catches both. For ESP, use 250m max distance, player boxes plus skeleton, and subtle red/grey visibility colors. Save to a Ranked config slot.
Facepunch bunches monthly Rust bans into the first Thursday of each month — coinciding with the force wipe and content patch. The pattern lets cheat detection signatures trigger silently during the month, then release as a batched ban wave alongside the wipe, making it harder for cheat operators to trace which specific build version got flagged. Continuous real-time bans still happen via EAC, but the headline wave is Thursday-anchored.
