Information status · Official information
Inherit Training Transfer Guide
A source-labelled Aniimo Inherit guide covering transfer direction, same-family eligibility, training progress, Capafruit, pre-confirmation checks and evidence limits.
What Inherit is for
Inherit is a training-management tool for moving an invested profile onto a more suitable Aniimo instead of rebuilding it from zero. Official material confirms automatic Capafruit transfer. The broader workflow below comes from version-labelled public-build 1.0 interface records and should be rechecked after updates.
Identity and training are separate
Community public-build records show that both Aniimo remain in the Collection: the transfer changes their training profiles rather than consuming the source. Species, form, personality and other identity traits stay with each Aniimo; levels and named training progress move according to the preview.
Read the transfer direction before confirming
The recorded interface places the trained source on the left and the intended recipient on the right. Do not rely on memory or a guide screenshot: compare both names, levels, Resonance and Potential panels in the current confirmation screen before accepting.
Check eligibility before planning a transfer
Version 1.0 records normally limit Inherit to the same evolution family and may reject Aniimo assigned to combat or exploration formations. Basic Irisalis is reported as a source-side family exception. These are community-observed client rules, not permanent official guarantees.
What the versioned client record says moves
The public-build help record lists EXP and level, Resonance stage and star rank, Capability Awakening, Capafruit effects and other training progress as one package, with surplus training items returned. Exact fields, refund handling and eligibility should be confirmed in the live preview.
A safe six-step workflow
First compare the exact form, Innate Potential, personality and skill fit. Remove both Aniimo from active formations if required. Put the trained profile on the source side, select the intended recipient, read every before-and-after value, then review the displayed fee and confirm only when the direction is correct.
When Inherit is useful
Use it when a clearly better same-family recipient matches the role you need and the existing training investment is worth preserving. It is a safety net for roster upgrades, not evidence that every new copy deserves an immediate transfer.
What this guide does not freeze as fact
The current fee, every selection restriction and the Irisalis exception are client-version details. Aniimo.GG does not present a third-party screenshot, one account result or an old numeric cost as a permanent official rule; the current confirmation screen takes priority.
Pre-confirmation checklist
| Check | Why it matters | Evidence boundary |
|---|---|---|
| Source and recipient | Prevents reversing the intended transfer | Public-build 1.0 interface record |
| Family eligibility | Avoids planning an invalid pairing | Community-observed; Irisalis exception needs live confirmation |
| Identity traits | Form, personality and Innate Potential stay tied to the individual | Verify in the current comparison |
| Training preview | Confirms level, Resonance and Capability changes | Version-labelled client help |
| Capafruit | Effects transfer automatically | Official developer letter |
| Displayed fee and refund | Values can change by version | Trust the live confirmation screen |
Official confirmation is limited to the stated Capafruit improvement. Other workflow details are clearly labelled public-build 1.0 observations.
FAQ
Does Inherit delete the source Aniimo?
Version-labelled public-build records show both Aniimo remain in the Collection and exchange training profiles; verify the current preview before confirming.
What does Inherit transfer?
Community client records list level and EXP, Resonance, Capability Awakening, Capafruit and other training progress. The official developer letter specifically confirms automatic Capafruit transfer.
Can any two Aniimo use Inherit?
Public-build 1.0 records normally require the same family, with a reported source-side exception for basic Irisalis. Treat the current selector as authoritative.
Does personality or form transfer?
They are identity traits, not the training package. Compare the exact before-and-after preview so you do not confuse the recipient's identity with the incoming training.
Should I trust a fixed Inherit cost from a guide?
No. Fees and restrictions are version-dependent; use the amount shown in the live confirmation screen.
Official source
- Official September 3 developer letter ↗
- Community public-build 1.0 training record ↗
- Third-party illustrated Inherit workflow ↗
Update log
- — Published a source-labelled Inherit workflow separating the officially confirmed Capafruit transfer from versioned client observations and volatile costs.
- — Article published from official and clearly labeled beta sources.