Dial in your Rust settings.

Rust rewards visibility more than raw frame rate these days. Push gamma and brightness up a little from default — shadows hide players, and you want fewer places for someone to hide from you, not more.

Turn off motion blur and depth of field entirely. Both exist purely for cinematic screenshots and both actively hurt your ability to track a moving target.

Shadow quality is the one setting worth testing on your own hardware. Lower shadow distance can reveal players earlier at range, but very low settings can also flatten depth cues that help you judge distance in a fight. There's no universal right answer — test both for a session and see which you actually play better with.

Enable raw input in the settings menu. It bypasses Windows' mouse acceleration curve entirely, which means every flick is exactly as consistent as your hand, not your OS.

Pick one sensitivity and stick with it for at least a full wipe before changing it again. Muscle memory takes longer to build than most players give it credit for, and constantly tweaking sensitivity resets that clock every time.

Footsteps carry more useful information than almost anything else in Rust — surface type, distance, even rough direction. A cheap pair of open-back headphones will out-perform expensive closed speakers for this specific job.

If your headphones support it, enable HRTF-style spatial audio in Rust's audio settings. It won't make footsteps louder, but it makes directionality noticeably easier to read.

A handful of console commands are worth binding or memorizing:

• fps.limit 0 — uncaps your frame rate (set a number instead if you need thermal headroom)
• net.graph 1 — shows real-time ping and packet loss, useful for diagnosing lag before blaming the server
• graphics.aa 0 — disables anti-aliasing; a common trade of visual smoothness for a few extra frames

None of these are secret exploits — they're documented client settings. Treat any guide that promises a hidden FPS trick with suspicion.

Rust's default control layout works, but it leaves a lot of clicks on the table. Every custom bind you set is just a console command tied to a key, entered through the F1 console using the pattern bind <key> <command>. Learn a handful of these and actions that used to take a menu and a mouse click collapse into a single tap.

A few binds are worth setting up before your next wipe:

• bind capslock sprint — turns sprint into an on/off toggle instead of a held key. Leaving off the + makes the bind flip state each press rather than only staying active while held, so you're not pinning shift down on a long run between monuments.
• bind g dropitemsingle — drops a single item from your active slot without opening your inventory. Faster than tabbing in to hand a teammate one bandage or one round of ammo.
• bind q slot2 — jumps straight to a specific hotbar slot instead of hunting for it on the number row, useful for a weapon or med kit you want on instant recall during a fight.
• bind mouse3 inventory.toggle — opens your inventory from a mouse button, so your left hand never has to leave WASD to reach Tab.
• input.clearbinds — not a bind itself, but worth remembering. Run it in the console to wipe every custom bind and fall back to Rust's defaults if things get tangled.

For the full command list beyond binds, see our RCON & console command reference. Brand new to Rust? Start with the new player guide instead, or browse Rust server hosting if you're still shopping for a server.