The Perfect Aniimo Is More Than a High Potential Number

A high Potential total is easy to love because it turns six fields into one headline. It is also easy to misuse. The total tells you how many points are present. It does not tell you whether those points support the job you need, whether the exact form improves your roster or whether a lower-total copy carries a skill you should preserve.

The practical definition of a “perfect” Aniimo is therefore conditional: perfect for which role, which team, which account and which cost?

Potential exposes six visible fields: HP, ATK, P.DEF, M.DEF, BREAK and REGEN. Adding them feels objective. A larger sum looks like a better catch, and a single threshold feels easier to remember than a role-by-role comparison.

The problem is not the arithmetic. The problem is the missing question.

A total cannot tell you whether an ATK-heavy shape belongs on a sustain project, whether a breaker lacks BREAK, or whether the copy with fewer points has the exact skill and form your roster needs. The Potential guide explains the system; the Aniimo evaluator turns it into a conservative decision.

Choose the job before grading the copy.

The evaluator uses five broad combat intentions: damage, BREAK, sustain, support and general use. These are editorial comparison lenses, not hidden in-game quality grades. They simply stop every copy from being measured with the same field priorities.

This first decision changes everything that follows. A copy can be excellent for one job and unconvincing for another without either appraisal being dishonest.

Compare the six-field shape, not only the sum.

Imagine two copies of the same exact form. Copy A has the higher total, but most of its advantage sits in fields the intended role barely uses. Copy B has fewer points overall, yet its strongest fields align with the job and the planned rotation. Copy B can be the better immediate project.

That is not a universal rule that lower is better. It is a reminder that useful concentration can beat irrelevant surplus. The reverse is also possible: a balanced high-total copy may be the better generalist when you do not yet know its final job.

There is no responsible “anything below X is bad” cutoff. The role, form, skill set and upgrade plan have to be known first.

Potential does not change form identity.

Thornblade keeps its central Sword Dance loop across several published forms, while its element coverage changes. The Thornblade build treats Grass, Lightning and Water profiles as matchup choices. A lower-total exact form that adds the team’s missing answer can therefore be more valuable than a higher-total duplicate of the profile you already own.

Prismana requires the same discipline. It is a form system, not a guaranteed power multiplier. Sparkling is a separate appearance status. Use the Prismana guide and Sparkling guide to keep those axes distinct.

Before comparing totals, record:

• the exact form;
• its verified elements and role;
• its useful skills;
• whether that exact form is already owned; and
• which replacement route is actually known.

Personality can change the job fit after the Potential comparison looks settled. Read the actual trait and named effect, then compare both with the intended role.

A desirable stat shape paired with an unhelpful personality may still be worth keeping if the other layers are strong. A lower-total copy with a role-aligned personality may be the cleaner project. Neither outcome should be reduced to a universal personality tier list.

The evaluator records what you know and marks unresolved personality details as uncertainty. It does not invent the missing roll.

One copy can fail the combat-project test and still pass the donor test.

Acquired skills are preserved as a separate layer because the Inherit system can make a mediocre fighter strategically useful. If a skill is valuable to another project, “do not invest in this copy” is not the same as “safe to release this copy.”

Use three labels instead:

1. Combat project when the whole copy fits the intended role.
2. Inheritance donor when the acquired skill is the main value.
3. Hold for review when the inheritance result or uniqueness check is unresolved.

That middle category is one of the main reasons a total-only sorter is dangerous.

An upgrade only exists relative to what you already trained.

Compare the new catch with the current copy on the same exact form and job. Then check what would be lost by switching: personality, acquired skill, completed upgrades, team links and collection uniqueness.

The Aniimo evaluator requires a clearly better comparison before it can even consider the phrase “trade or release candidate.” A marginal edge is not enough. Unchecked form, skill, evolution, collection or Homeland value blocks that recommendation completely.

This gate is intentionally conservative because discarding is destructive and rebuilding is expensive.

A fresh copy with a cleaner stat shape is not automatically a better project than a fully trained copy.

Count the work already completed:

• levels and direct Potential investment;
• Resonance progress;
• personality work;
• Held Item selection and enhancement tied to the build;
• skill inheritance already performed; and
• the time-sensitive or uncertain materials needed to repeat it.

Sunk cost should not trap you forever, but switching should produce a meaningful upgrade. If the projected gain is small and the rebuild is large, holding the new copy can be smarter than replacing the old one immediately.

Not every useful Aniimo belongs on the active battle team.

Homeland work can preserve a copy that does not win the combat comparison. Use the Homeland guide and Homeland optimizer to inspect the actual production role rather than treating every non-combat result as failure.

Collection value also matters. An exact form you do not own, a Sparkling appearance or a difficult replacement route may justify a keep. That does not make the copy your next damage project. It gives it a different job.

The clean labels are combat value, donor value, Homeland value and collection value. A copy can score strongly in one and weakly in another.

A lower-total copy can be the better keeper when one or more of these statements is true:

• its Potential distribution aligns better with the intended role;
• its exact form adds missing element or role coverage;
• its personality supports the build more cleanly;
• its acquired skill has direct combat or donor value;
• it is the only owned copy of that exact form;
• it performs needed Homeland work;
• the higher-total copy is a redundant duplicate; or
• replacing the trained copy would cost more than the practical gain.

These are reasons to compare, not automatic verdicts. The evaluator exposes which reason contributed and which missing fact could still reverse the outcome.

Only after every box is resolved should the destructive option enter the conversation. The trading guide covers the separate rules and risks of moving value between players.

Open the Aniimo evaluator, choose the exact form and intended job, enter the six-field Potential shape, then add personality, acquired skill, investment, collection and Homeland checks. Compare the result with the copy you already own instead of grading it in isolation.

The tool returns a role such as combat project, donor, worker, collection keep or hold for review. It also explains every contribution and preserves uncertainty rather than converting an unchecked box into “no value.” The companion Should You Keep This Aniimo? guide explains the release locks in full.

For a worked progression and resource example, read Perfecting an Aniimo Without Paying: Scorchhowl. That article follows one finished build. This framework answers the earlier question: whether the copy in front of you should become that kind of project at all.