A follow-up starts with a condition
A follow-up attack is an attack activated through a Kit’s stated conditions, rather than simply choosing it from the normal Basic ATK and Skill options. The condition is part of the ability: it might involve an ally’s attack, an enemy’s attack, a health threshold or a Character-specific resource.
That makes the trigger as important as the damage multiplier. Increasing the damage of an attack that never activates does not solve the team’s problem. Start by reading what must happen, who must cause it and whether another condition must already be active.
The same broad label can hide different rules
Use the Kit descriptions on Character pages to separate the trigger from its limits. Do not transfer one Character’s activation rules to another just because both contribute follow-up damage.
Scroll horizontally to see all columns.
| Example | Required event | Important boundary |
|---|---|---|
| Herta’s Talent | An ally’s attack brings an enemy’s HP percentage to 50% or below. | The HP-threshold condition matters; this is not every ally action. |
| Clara’s normal Counter | An enemy attacks Clara. | An attack on a different ally does not meet this normal trigger. |
| March 7th, Preservation | An enemy attacks a Shielded ally. | The Talent also has a per-turn activation limit. |
Alongside the trigger, look for charges, stacks, maximum activations and reset wording. “Once per turn” and “uses a charge” describe different restrictions. A stat increase does not automatically remove either restriction.
Read a threshold as an event
The four-star Herta’s Talent reacts when an ally’s attack causes an enemy’s HP percentage to fall to 50% or lower. The relevant event is the attack meeting that health condition. It is not a timer that simply gives Herta another attack whenever she takes a turn.
Ask what changed on the enemy
A target at 60% HP that an ally’s attack brings to 40% illustrates the threshold condition. Do not turn that example into a promise that every later hit below 50% triggers another attack. See Herta’s Kit for the actual Talent, rather than borrowing rules from The Herta’s different kit.
Counters react to the stated enemy event
Counters are reactive attacks. Read whose exposure to an enemy action matters: the Counter user, a Shielded ally, or any ally under a special state. Those differences explain why two counter-focused Characters may want different support conditions.
Clara makes the distinction clear. Her normal Talent retaliates against enemies that attack her. Her Ultimate enhances Svarog’s Counter so an attack on an ally can trigger it, with a limited number of enhanced uses. The expanded trigger belongs to that enhanced state; it is not a permanent rewrite of the normal Talent.
More allied turns do not themselves supply an enemy-attack trigger. Before adding action advance to a plan, ask which event you need more often. The Speed and Action Order guide explains the difference between taking a turn sooner and changing an ability’s conditions.
Timing does not tell you every damage rule
An extra turn, an Ultimate used between turns and a triggered attack can all interrupt the ordinary flow. That shared timing does not make them interchangeable attack types. Likewise, an ability dealing an additional instance of damage is not enough evidence that it activates every follow-up-specific effect.
Read explicit classification text as well as the trigger. Phainon’s Calamity: Soulscorch Edict, for example, launches a Counter but explicitly treats its damage as Skill DMG. “Counter” explains the reactive action; the damage clause supplies an additional rule. Do not infer how every equipment bonus stacks from the animation or one keyword alone.
This matters when choosing Light Cones or Relic sets. Check the exact attacks their bonuses cover and the current Kit they are meant to support.
Check the trigger before blaming the build
If an expected attack does not happen, work through the ability in order:
- Event: did the required attack or threshold event actually occur?
- Recipient: was the correct unit attacked or affected?
- State: was the Shield, mark or enhanced state still active?
- Limit: were charges available, and had the activation allowance been used?
A visible animation is not a complete explanation of the combat sequence. For disputed interactions, check the individual Kit and encounter rules rather than assuming a universal order for all triggered actions.
Support the event, then support the damage
First make the required events repeatable. Then add compatible amplification and enough protection to keep the sequence working. A teammate who produces useful triggers can contribute more to the plan than one whose bonuses rarely apply.
Triggered damage still belongs to a team with an action and resource budget. The setup may need Skills, Ultimates or maintained states even when the triggered attack is not a button you choose. Use Team-building fundamentals and Skill Points and Energy to test the full sequence before treating a collection of follow-up users as a finished team.