Which effects require successful Mirrors High Vanishing Evasion?
The official introductions use a successful Vanishing Evasion as a condition for specific effects. An attempted movement is not a complete record of that condition. Before asking why a bonus is missing, ask whether your observation actually identifies the event the source names. If it does not, keep the success question open rather than using the expected bonus to prove its own trigger.
This page compares two exact published kits, not every current character or a verified control tutorial. The table above keeps the numerical effects compact. The useful next step is to select the right source line and decide what evidence would address it. A larger number in another character's kit does not resolve whether your own event qualified.
Ability slot matters as much as the character
Mirrors High Vanishing Evasion appears in Yoruichi's Innate and Byakuya's Spirit effect, but their lines have different windows. Do not copy one onto the other because both mention the same event. Also distinguish the initial and final wording of the particular Innate before looking for an extra effect. The ability-stage guide owns the broader initial-versus-final reading task; here it is one eligibility check.
A worksheet should name the variant and slot, not simply “evasion buff”. Otherwise a later reader cannot tell which description was being evaluated. The exact variants covered are Flash Master Yoruichi and Squad 6 Captain Byakuya. Their complete kit context remains in the Yoruichi guide and Byakuya guide, rather than being repeated as two builds on this page.
Do not assume a listed Spirit effect is active on a copy merely because that character is owned. Inspect the current copy's visible ability information. If access, progression or wording is unclear, the correct worksheet state is unresolved. This guide does not infer an unlock schedule from a published slot number.
Observe the right result in the right window
Choose one effect to investigate. An Attack observation, a current Mortal Blow timer and the team's remaining Switch timer answer different questions. A resource change answers another question again. Keeping them separate avoids interpreting a change in one part of the interface as confirmation of every effect associated with an event.
Use the duration printed on the selected line when organizing notes. An observation made after that stated window is not a clean check of an effect within it. Record the displayed Count unit and the point at which you observed the result. Do not silently replace Counts with seconds or assume that two separately triggered windows start together.
Stocks also deserve a separate field. Record the state you can actually identify rather than multiplying a percentage by every movement you attempted. A maximum-stock label does not verify refresh timing, expiration behavior, successful event count or how several buffs combine in the damage calculation. This page supplies no such formula.
Two illustrative decisions
Fictional example, not a playtest: a reader selects Yoruichi's initial Innate but investigates the additional timer effect found in the final description. The first correction is to match the ability stage. Repeating the same movement would not fix the mismatch between the selected source and the effect being sought.
In another fictional note, a reader selects Byakuya's Spirit line but uses Yoruichi's window as the observation period. The source comparison now reveals a different mistake: the timing reference came from the wrong kit. Keep the observed result, correct its label and plan a comparison against the selected line instead. Neither example establishes how a real battle will behave.
A portable observation note
Record the game version, exact variant, active ability line, identified event and the single result you watched. Add the observed point in the stated window, any visible stock state and what remains uncertain. A useful mismatch report makes it possible to distinguish a different copy, an unidentified event and a different observation target.
The inspector on this page turns those three decisions into a review you can export. Its output reflects your selections, not a measured success rate or a game-state detector. Use “uncertain” whenever the record cannot support a choice. The next observation should address that missing fact, rather than manufacture a complete answer from an incomplete screenshot.
For resource event amounts, continue to the Draw Point Bonus guide. For timer terminology, use Switch cooldown. Cover Change and Chain Attack cover different event conditions; Physical versus Spiritual damage covers action categories. None of those labels should be substituted for a successful-evasion condition.