At its core, an "Aim Lock" (often called "Hard Lock" or "Magnetism") refers to a script or setting that forces a player’s reticle to stick to an enemy target with minimal human input. The Config File (short for configuration file) is the text-based document containing the parameters, variables, and keybinds that control this behavior.
Unlike traditional aim assist found in console ports (which slows down sensitivity over a target), an Aim Lock Config typically drives the mouse cursor toward the target automatically. These are most commonly found in: Aim Lock Config File
An "Aim Lock" configuration file acts as the brain of an input-refinement system. It tells the software how to interpret mouse movements, how to identify targets, and how to smooth or correct the user's input to maintain a lock on a specific point. At its core, an "Aim Lock" (often called
A solid config file balances three competing priorities: Stealth (how natural the movement looks), Responsiveness (how quickly it reacts), and Precision (how accurately it holds the target). "aim_lock": "enabled": true, "fov": 15
Most Aim Lock Configs are written in JSON, XML, or a proprietary scripting language (like LUA or AutoHotkey). A standard .cfg file for a Source game might look like this abstracted example:
"aim_lock":
"enabled": true,
"fov": 15.0,
"smoothing": 4.5,
"lock_bone": "head",
"priority": "closest_crosshair",
"keybind": "MOUSE5",
"requires_ads": true
Let’s break down these commands: