A detailed look at the Blurred Fortnite aimbot interface and the settings you can use to tune aim assistance on Windows.
Blurred groups its aim controls into a dedicated interface so the important options are easier to understand and configure. The current feature set includes a weapon group selector, enable control, a dedicated keybind, prediction, FOV, hitbox selection and smooth type. The goal of this page is to explain what each control is for and where it fits in a practical setup.
Weapon groups let you organise your aim settings around different weapon categories instead of treating every weapon the same way. The enable control determines whether the module is active, while the aimbot keybind gives you a clear input for controlling when the feature is engaged.
Prediction is useful when your target is moving and you want the configured aim behaviour to account for movement. FOV defines the area in which the feature considers targets. A smaller FOV can keep the behaviour more selective, while a wider setting covers a larger area. Hitbox selection lets you choose which body area the aim system prioritises when more than one target point is available.
These controls work best when treated as a set rather than tuned independently. Start with a conservative profile, test it in a controlled session, and change one setting at a time. Blurred also supports configurable smooth types, which can be adjusted alongside FOV and target-point choices.
Triggerbot is a separate input-focused feature. Review its dedicated page before combining it with your aimbot configuration.
Explore Triggerbot →Use the web menu guide to understand where settings live and how to keep your configuration organised.
Open Web Menu Guide →For broader setup questions, use the beginner guide and troubleshooting guide.
A useful profile begins with the controls you actually understand. Pick a weapon group, bind an activation key, select a target point, then tune prediction and FOV. Once those values behave consistently, adjust the smooth type instead of changing everything at once.
For maintainability, keep a conservative default profile and a separate test profile. The Cloud Configs guide explains why this makes updates and troubleshooting easier.