Binds in Rust are not cheating — they are the game's own console feature, and everyone competitive uses them. Here are the ones that actually change how you play, and how to make them permanent.
Open the console with F1 and type bind <key> <command>. To make a bind permanent, put the same line in cfg/client.cfg while Rust is closed. To remove one, use bind <key> "".
bind mouse3 "duck;jump"
bind q gestures.point
bind f swap_seats
bind x "attack;duck"
bind mouse4 +voiceAuto-run with a gather loop saves a lot of clicking on farm servers:
bind d "forward;sprint"
bind mouse1 "+attack;+attack2"Be careful with combined attack binds on some servers — a few community servers treat rapid combined inputs as scripting. On official servers these are fine.
bind k kill
bind l combatlog
bind p "consoletoggle"
bind home "graphics.fov 90"
bind end "gc.collect"bind home "graphics.fov 90" is a nice safety net — one key restores your FOV if a patch reset it.
Anything that automates recoil control or fires faster than a human can click is a script, and EAC bans for it. The binds above are input convenience, not automation — that is the line, and it is not a subtle one.
No. bind is a built-in console command and normal binds are fine. Scripts that automate recoil or auto-fire are a different thing entirely and will get you banned.
Type bind followed by the key and empty quotes, for example bind mouse3 "" in the F1 console.
Console binds are not saved permanently. Put them in cfg/client.cfg while the game is closed and they survive.