Overwatch aimbot keybinds: Hold, Toggle and Always explained

What Hold, Toggle and Always actually mean

Start with Hold when comparing activation modes: the physical action and intended active period are easy to match. Press and hold the assigned key, then release it. Toggle changes that relationship: releasing the key does not stop the toggled state; another fresh press does. Always removes the keypress requirement while the enabled feature and its other conditions permit it to run.

An activation mode is not a promise that a target is available or that every selected action supports the feature. If nothing happens, check the feature’s enabled state, current hero/action and target conditions as well as the key. Rebinding the same control repeatedly cannot resolve an unrelated eligibility problem.

Aim key, menu hotkey and panic key are different

The aim key belongs to the selected feature. Menu Hotkey shows or hides the interface. Panic Key pauses features and hides overlays until it is pressed again. Hiding the menu is therefore not the same action as pausing the product.

The sample menu starts with Mouse4 for Flickbot, G for Trackbot and LMB for Triggerbot. Menu Hotkey is Insert and Panic Key is End. Treat these as visible sample defaults, not a requirement that those bindings fit your own keyboard, mouse or game controls.

Check for shared bindings before saving a setup. If the same physical button also triggers a game action, that game action and the feature activation can happen together. Choose deliberately; a comfortable button is more useful than copying a popular binding without understanding the conflict.

A clean way to configure one aim binding

Choose the hero and action first. Open the relevant feature tab and its Activation section, then inspect the enable switch. Select Hold, click Key & mode and press the intended keyboard key. Check the displayed key label and mode together. Repeat for another feature only when you want that feature to have its own activation behavior.

In the website preview, this is an interface demonstration: assigning a key changes the sample settings. The browser is not controlling an installed product or an Overwatch match. Use it to learn where the controls are and how settings are grouped.

If you are organizing several setups, the hero settings and saved profiles guide explains the distinction between editing the current hero/action and loading a named configuration.

Why aim keeps running, stops early or never starts

Begin with the behavior you expected. If you expected release-to-stop but selected Toggle or Always, the mode is the first thing to correct. If you expected a keypress to do anything while the feature is disabled, check the enable switch before changing the key.

Check whether Panic Key paused the product, whether you are editing the intended hero/action, and whether the named profile was actually loaded. These are separate checks: a displayed binding can be correct while the rest of the configuration is not the one you intended.

Save the behavior you intended

Record the feature, hero/action, key and mode together. A note such as Trackbot / Primary / G / Hold is more useful than simply writing G. Keep one known baseline so the next change has something clear to compare against.

For settings that appear to revert or apply somewhere else, use the Overwatch config troubleshooting guide. You can compare the complete controls and shatter’s Overwatch access options on the product page.