Overwatch hero profiles: save a setup you can return to

Know which context a setting belongs to

Some preferences are shared across the interface. Other controls belong to a hero, and some belong to a particular action within that hero. In the current sample menu, player-visual preferences are shared, while Combat includes hero and action-specific values. Changing the hero therefore should not be expected to reset every setting you can see.

Look at the hero name and action selection together before editing. Primary and Secondary are different contexts, not merely alternate names for one configuration. The available actions and their released behavior still need to match the product's supported feature list.

Name the reason for a profile

Names such as baseline, smaller targeting area or clearer player labels make a comparison understandable. Best, new and final become confusing as soon as another version exists. A short name should tell you why the profile differs, while a separate note can keep the exact settings and date.

Keep the scope in your notes too. A smaller-targeting-area experiment may change only the selected hero's action, while a shared visual preference can affect the display across heroes. The profile name identifies the experiment; the note identifies which part of the configuration actually differs.

Selecting, saving and loading are separate actions

In the browser sample, selecting a profile chooses the record you want to work with. Load applies its saved settings. Save updates that selected record with your current sample settings. Creating a profile captures a named starting point. These are different operations, so check the selected name before saving over a baseline.

A simple habit prevents confusion: save the baseline, create a separately named experiment, make one change, and compare by loading each. If you overwrite both records with the same values, their different names will not preserve the difference you intended to test.

• Start with a named baseline and confirm it is saved.
• Create a second profile describing one planned change.
• Confirm the selected hero and action before editing.
• Save the experiment, then load the baseline to compare.
• Delete a profile only after checking which record is selected.

A reset is different from loading your baseline

Restore defaults returns the relevant controls to their supplied values. Loading a profile returns them to values you saved. Those starting points can be different. If your baseline contains deliberate changes, restoring defaults is not a substitute for keeping that profile.

The same distinction helps when a change appears to affect more than one page. Flickbot and Trackbot share the current Combat FOV within the selected hero and action context. Seeing that value on both pages is not evidence that two unrelated profiles were overwritten. Read the control's scope before diagnosing a save problem.

Keep browser samples separate from installed settings

The website's sample profiles exist to let you try the workflow. They remain in the current browser session as you navigate, but refreshing the page starts the sample again. They do not transfer into the installed product or modify a game session. Take a note of an idea you want to revisit rather than treating the preview as a cloud backup.

When using a released product, follow its current profile instructions and keep notes with the relevant version. An Overwatch update or a product update can change the context around a saved setup. A dated baseline and a clear purpose make those later comparisons much easier.