Agents and abilities

Learn the agent before changing the plan

Each agent combines a role with a particular set of abilities. The Agents pages describe the current roster, ability slots and important behavior. Start with one agent and learn what each ability actually does before trying to copy a complicated sequence from a video. Two abilities that look similar may have different targeting, charges or confirmation inputs. The in-game interface is the place to check what is currently available during a round.

Read slots and charges separately

The usual ability slots are C, Q, E and X, but your configured bindings may differ. An ability icon identifies an action; its charge display tells you how many uses remain. A visible icon does not necessarily mean the action can be used immediately. Check purchased charges, preparation state and any conditions described for the ability. If you changed bindings, test the configured key instead of assuming the default shown in an old guide still applies.

Understand equipment and activation

Some abilities act immediately; others first equip an object or a targeting interface and need another input to finish. Practice both stages deliberately. Brimstone's tactical interface, for example, is described with selection and confirmation actions, whereas Jett's movement abilities follow a different sequence. When an ability appears not to work, establish whether the first input equipped it successfully before investigating the final action. This distinction is especially useful in a short bug report.

Treat signatures individually

The E slot is associated with an agent's signature ability, but signatures do not all share identical recharge rules or charge counts. Read the selected agent's description rather than applying one agent's behavior to another. Jett's Tailwind and Phoenix's Curveball have their own documented conditions. A charge disappearing after a valid use is not by itself a defect, and buying or using an ability should be judged against the rules for that particular agent.

Build utility around a clear purpose

Before using an ability, decide what information, space or protection it should provide. A smoke can block a sightline, but placing it without considering teammates can make their next action harder. A movement ability may create access to an angle without making that position safe. Practice explaining the purpose in one sentence. If the purpose is unclear, a simpler action is often easier for the rest of the team to understand and follow.

Learn ultimate requirements

The X slot is the ultimate. The agent page lists its required ultimate points and describes its behavior. Check the actual point display before assuming it is ready. An ultimate can also involve equipment or targeting steps, so readiness and activation are separate questions. When comparing a clip with your experience, confirm it features the same agent and build. Do not rely on another game's version of an ability as the specification for VALOSTRIKE.

Use a small practice routine

Pick one ability, use it from a fixed position and observe where it lands or what changes. Repeat from a second position, then add movement. Test primary and alternate actions only when the description supports them. Keep your crosshair and sensitivity unchanged while learning the ability, otherwise it becomes difficult to tell whether a missed placement came from unfamiliar controls or a new aim setting. Stop the routine when you can explain the sequence consistently.

Distinguish failure from counterplay

An ability producing no obvious benefit is not necessarily a bug. The target may have moved, the placement may not cover the intended area or the action may require a final confirmation. Review what the interface showed at the moment of use. If you can, compare the visible effect with the ability description. Report unexpected behavior with specific observations, rather than saying only that the agent is weak or that an opponent should have been eliminated.

Example of a useful ability report

“I selected Brimstone, opened the tactical map, chose a location and used the confirmation input. A charge was removed, but no smoke appeared at that location in the next few seconds” gives support a sequence to investigate. Include the map area, approximate time and whether it repeats. It is better to say “I did not see the effect” than to assert that the server never created it when you cannot observe that directly.

What to include when asking for help

Send the agent, ability name and slot, bindings if customized, remaining charges, map or mode and exact input sequence. Mention whether the action equipped, whether a charge changed and whether other players could see the effect. A short recording beginning before activation is more useful than an isolated screenshot afterward. Keep the report to the relevant sequence and hide unrelated chat or private information. Use Gameplay & bugs so the team receives the correct context.

Build an ability learning sheet

For each ability, note its slot, whether a charge is currently available, how the target is selected and what confirms or cancels the action. Test these observations in a practice environment. Learning the complete input sequence prevents a common misunderstanding: seeing an ability selected and assuming its effect has already been used. Watch the charge display and the visible result together.

Keep behavior and strategy in separate notes. “The effect appears after this confirmation input” is an observation about the control. “Use it before entering this area” is a tactical suggestion that depends on teammates and opponents. When the first statement is unclear, practice it before relying on the second in a match. This makes later troubleshooting much more precise.

Coordinate without overwhelming your team

Useful ability communication identifies the intended area and timing. Give teammates enough notice to react, and say when your available charges change. A long explanation during an active fight can be less useful than a short call that the ability is ready or unavailable. If your plan depends on another player, confirm that they understood it instead of assuming a familiar agent combination automatically creates coordination.

After the round, discuss what actually happened. Did the ability activate, did it reach the intended position, and could teammates act on it? Those are different questions. A successful activation can still produce a poor tactical result. Describe a possible bug using the activation and effect, rather than using the lost round as proof that the ability malfunctioned.

Handle changes after an update

If an ability feels different after a release, read the relevant News entry and inspect its current description before changing several settings. Record the date or version information visible to you. A guide or clip made before a balance change may use different values or behavior. If the current description and observed result disagree, quote the specific label in your ticket and describe your test.

Do not assume a report about one agent establishes a problem with every ability. Compare one action at a time. For instance, a targeting input working for one slot but not another is more informative than “abilities sometimes fail.” Mention whether the issue is present in practice, in a live round, after respawning or only on a particular surface.

Frequently asked ability questions

Does a full ultimate indicator mean it has already activated? Readiness and activation are separate states. Check the current prompt, input and resulting effect. If the display changes without the expected action, include both states in your report.

Should I learn every agent at once? Start with one manageable set of controls and add another agent when you can explain the first one's basic sequence. Familiarity helps you notice unusual behavior and communicate what your team can expect.