A conditional bonus is useful only when its trigger is met. Check terrain for Iris, the family-and-sex condition for Susuta, and HP management for Malevsera before treating their traits as always-on power.
In this guide
Iris: terrain and a hit counter are separate conditions
Iris’s Disco Aniimo trait includes a grass-terrain damage bonus and a Dance Power counter gained from skill hits after entering battle. At 24, the next skill has no EP cost. The two clauses answer different questions: where you are fighting, and what has happened during the fight.
For a practical check, first confirm the terrain state shown by the game, then observe whether your skill actually hits and advances the relevant effect. Do not assume that an attractive grassy-looking screenshot establishes the mechanical terrain flag. If the expected result is absent, inspect the condition before concluding that the skill is broken.
References: Official Index · iris
Susuta: check the companion condition before entering battle
Appeal names an opposite-sex Susuta-family member in the team, with a temporary BREAK-efficiency benefit on entering battle. This is a more specific requirement than simply adding another Water creature. Read the family and sex information you actually have before planning around the bonus.
The preparation step is to confirm the required companion condition. The action is entering battle under that condition. The result to look for is the stated temporary benefit, not a permanent increase to every BREAK action. Keep the cooldown in mind when repeating a comparison.
References: Official Index · susuta
Malevsera: a larger bonus can mean a less forgiving routine
Malevsera’s Bloodthirst increases damage as HP is lost, with a cap. Its Demonic State adds another layer by changing skill costs to a share of current HP and providing recovery when the state ends under the documented rules. Read these together rather than treating low HP as a free upgrade.
A sensible learning objective is first to understand how to end the state and recover, then to examine the damage benefit. This is an editorial practice order, not a claim that deliberately taking damage is optimal. If you cannot reliably manage the exit condition, a less demanding companion may suit the immediate task better.
References: Official Index · malevsera
What to do with an unusual source value
Helmut’s current Guardbreak Resonance description contains a zero-valued increase. We do not turn that into a confident build recommendation or silently replace it with a plausible number. Use the other documented actions, compare the current client, and revisit the official entry when that specific value matters.
The general habit is simple: trigger, action, expected result. Write those three parts before testing a trait. It becomes much easier to distinguish a missed condition, a source ambiguity and a genuine behavior difference.
References: Official Index · helmut
Sources & reference notes
Reviewed 2026-09-14. These references describe the scope of this record; details can change.
How we document information
