Aim assist that does not fight you
Every aimbot problem is a tuning problem. Too tight and you cannot look away from a target. Too loose and it does nothing. Four sliders decide which of those you get, and only one of them is about strength.
The four controls
Bone priority
Head is the obvious pick and the wrong default for most people. A head-only target selection follows the smallest hitbox in the game, which means it snaps to a moving point and looks exactly like what it is. Chest is a wider target, corrects less often, and reads as ordinary mouse movement.
Nearest visible is the setting for people who play fast. It picks whichever bone is closest to your crosshair at the moment of acquisition, so a target behind cover who peeks a shoulder gets the shoulder rather than an unreachable head.
Field of view is a filter, not a strength
FOV decides who is even eligible. A 4° cone means the assist only engages when your crosshair is already close — it finishes a shot you were going to hit anyway. A 30° cone means it will pull across a doorway to a target you never saw, which is both obvious and disorienting.
If the assist feels like it is fighting your mouse, the FOV is too wide. Drop it by five degrees and it stops grabbing.
Smoothing, and the curve nobody mentions
Smoothing is the number of milliseconds the correction spends travelling. At zero the crosshair teleports, which is visible to anyone watching your killcam and unreliable against a strafing target. At 120 ms the motion is a fast human flick.
The useful range is 45–90 ms. Below 45 you are buying speed you do not need. Above 120 you are tracking a target that has already moved.
Bone: chest. FOV: 7°. Smoothing: 65 ms. Hold key: your aim-down-sights button. Play three matches before changing anything — tuning against a single fight is how people end up with settings that only work in one corridor.
Why a hold key beats always-on
An always-on assist corrects while you are looting, while you are driving, while you are typing in chat. A hold key ties the correction to an intent you already express — you are aiming, therefore you want help aiming. It also gives you a way to prove the difference: hold it, release it, feel the gap.
The key is rebindable to anything the game accepts, including mouse buttons. It does not need to be the same as your fire button, and for most people it should not be.
The visibility gate
With visibility on, the assist will not acquire a target that world geometry blocks. This is the difference between an assist and a wallbang, and it is the single setting that keeps the behaviour defensible in a review. It costs a trace per acquisition — negligible at these distances.
Turn it off and the assist will happily correct toward a target behind a wall, which is both useless for hitting them and the most obvious possible signature.
What it will not do
- It does not predict movement. It corrects toward where the bone is, not where it will be.
- It does not fire. There is no triggerbot, and no plan to add one.
- It does not ignore recoil for you. Recoil control is a separate concern from aim correction.
Tuning against a real match
The panel stays live mid-match. Change smoothing while a fight is happening and you feel the difference in the next engagement, not the next session. Everything you set is written to the active profile, and Save writes that profile to disk so Load brings it back exactly.
The mistake is tuning in a menu. Aim assist is a timing system, and timing only exists in a match.
Keep reading
Keys are issued one at a time
Lifetime, bound to one machine, updates included. Message @kongthebest on Discord.
See access details