How Do I Bind My Aim Key in RawCheats?
Open the cheat menu with INSERT, navigate to Settings then Keybinds, click the field next to Aimbot Key, and press the key or mouse button you want to use. Defaults are RIGHT MOUSE (hold to activate), but any key, mouse button, side button, or pedal works. The new bind saves immediately and persists across sessions when you save your config slot. Avoid binding aimbot to keys overlay software uses, like F10 GeForce Experience capture.
Aim key binding is the first setting most users change. The default of RIGHT MOUSE (hold-to-aim) suits most FPS muscle memory, but the menu accepts any input — keyboard key, mouse button, side button on a 12-button MMO mouse, foot pedal via remap software, or controller button via Steam Input.
Open the keybinds panel
INSERT opens the menu by default. Navigate Settings to Keybinds. Each aimbot-related action has its own bind: Aimbot Hold (the activation key), Aimbot Toggle (one-tap on/off), Aim Smoothness Cycle (steps through smoothness presets), and Visibility Check Toggle (turns off-target-check on or off). Click any row, press your desired input, the bind saves immediately.
Default bind rationale
RIGHT MOUSE on hold is the default because every FPS player already uses right click for ADS. Aimbot activating only while aiming-down-sights produces stat lines indistinguishable from a careful hipfire-vs-ADS player — behavioral anti-cheat like Anybrain and Activision Ricochet struggle to separate ADS-locked aimbot from a strong gunfighter. Aimbot-always-on is the worst possible bind from a detection standpoint.
Mouse button binding
Side buttons on the Logitech G502, Razer Naga, and Corsair Scimitar all register cleanly. The Raw menu reads the raw HID button index, not the manufacturer label, so any button shows as Mouse4, Mouse5, Mouse6, etc. Binding aimbot to a thumb side button is common — it frees right-click for ADS while letting you toggle aimbot on demand.
Don't conflict with overlay software
Avoid binding to keys that overlay or capture software steals first: F10 (GeForce Experience instant replay), Win+Alt+G (Xbox Game Bar capture), F9 (Discord PTT default), F8 (OBS hotkey default). The aimbot key fires in the cheat process, but if another overlay catches the key first the input never reaches the cheat. Pick something unbound everywhere else.
Hold vs Toggle
Hold-to-aim is universally safer. Toggle binds (press once to enable, press again to disable) produce extended on-targeting periods that look unusual in server-side replay analysis. FNCS-tier Fortnite replay review and PUBG Zakynthos catch sustained perfect tracking that doesn't gate on ADS, so hold-only is the recommendation for high-stakes play.
Smoothness cycle bind
Bind Aim Smoothness Cycle to a side key. In ranked play, cycle to the higher-smoothness preset (0.5-0.7 — slower, more humanlike). In pub stomp lobbies where detection risk is low, cycle to a snappier preset. Letting smoothness adapt to context keeps stats believable across game modes.
Controller binding via Steam Input
Steam Input lets you bind any controller button to a keyboard key — set the controller's South button to map to Mouse4, then bind aimbot to Mouse4 in the Raw menu. Works for Xbox controllers, PlayStation controllers, and Steam Controller. The cheat doesn't care about input source, only the final key event.
Saving
Once binds are how you want them, save to a config slot in the menu (Configs to Save Slot 1, 2, 3, etc). Otherwise binds revert on next session start. Saved slots persist across spoofer runs, loader updates, and game patches.
For full setting tuning see what should my Fortnite aimbot settings be and the setup-safely cluster.
Related Pages
Sources
- Anybrain AI Anti-Cheat — Anybrain
- RICOCHET Anti-Cheat — Activision
- 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.
Open the cheat menu with INSERT, navigate to the Configs tab, click an empty slot (1-10), and click Save to store your current aimbot, ESP, humanizer, and keybind settings. To load, click a populated slot and click Load. Configs persist across sessions, spoofer runs, loader updates, and game patches. Name slots descriptively — Ranked, Pub, Scrim, Tournament — so you grab the right one fast at session start.
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.
