Signal Skills Guide: Why They Trigger, Why They Sometimes Fail

A Signal Skill is a response to an enemy status, and the published skill rules express that as a consume condition: the skill lists the exact status it needs, the minimum stacks, the level and ascension step, and any extra activation conditions. When all of them are true, the Signal prompt becomes available and tagging the hero in fires the skill. When any one of them is false, the prompt stays hidden. The hero database /heroes exposes these conditions for every skill level, so "why is my Signal missing" becomes a checkable list instead of a mystery.

The most common mistake is treating the status name as enough. The consuming skill must match both the status and the direction: the opener's skill must apply that status to an enemy, and the finisher's Signal must consume it. Two skills sharing a word but not a direction never connect. The team builder /team-build evaluates the same direction rules across a full three-hero line-up.

When a Signal does not appear, verify the opener first. Confirm that the opener's skill actually applies the required status to an enemy at its current level, that the target was not immune or interrupted before the status landed, and that the status is still present when the Signal window opens. If the status expires, is cleansed, or the enemy dies first, the consume side never sees it.

Read the skill's published requirements in the hero database /heroes rather than assuming the first skill level is enough. Several applies only gain their status at higher levels or after an ascension step, and some require stacks. A route that looks valid on the roster page can be unusable until the hero is invested.

The receiving Signal must be unlocked and leveled. Confirm the skill is equipped, the level is high enough, and any listed prerequisites are met. In the current roster, consume sets vary widely: Sion consumes Shock, Theresia and Roxy consume Bleed and Stun, Othello and Dana consume Down and Ice, Cerese consumes Air and Ice, and Charlotte consumes Poison and Air. Match the opener to the finisher's actual consume list, and use the hero database /heroes to compare candidates for the missing slot.

Some Signals also cost resources when they fire or carry activation conditions beyond the status. The published rules show these conditions per level, so a Signal that costs more than it returns may justify a different finisher even when the chain technically connects. Compare the full route cost in the material planner /material-planner before investing.

Skill data proves what the game says a skill can do; the live fight still decides whether the target behaves. Reproduce the chain against ordinary enemies at your current level and change one variable per attempt: slot order, skill level, opener, or target type. If the Signal fires only against some enemies, the difference is usually a resistance or a behavior on the target side, which is a separate problem from a broken chain.

Keep a record of what you changed, because the same failure can have several causes and they compound. A team that fails at low levels often connects after the opener's status unlocks at a higher level, while a team that worked at low levels can break when new equipment changes kill speed and the target dies before the Signal window.

When one Signal never fires, fix the specific edge. Replace the opener with a hero that applies the missing status, or replace the finisher with one whose consume list includes the status you already apply. The team builder /team-build reports which edge is broken, and the hero database /heroes lists every apply and consume set, so a substitute can be chosen for one direction instead of rebuilding the team. After the swap, rerun the same combat test and confirm the Signal appears before spending more materials on the new line-up.

Cooldown and timing are the last variables worth checking when the edge is confirmed. A Signal that is still on cooldown when the status lands, or a status that expires before the Signal window opens, reads exactly like a broken chain even though the direction is correct. Space the opener's status application so it lands as the consuming skill comes off cooldown, and verify the order in the team builder /team-build before blaming the roster. The two checks together—direction first, timing second—solve most "Signal never appears" reports.