Forms and evolution tracking
The Aniilog tracks three different kinds of variation, and mixing them up produces false conclusions. Separate environmental forms, evolution stages and cosmetic differences before comparing any two records.
Three kinds of different
An environmental form reflects where the Aniimo lives, an evolution stage reflects progression, and a cosmetic variant changes appearance without changing the kit. Each answers a different question.
- Forms: expect stat or element shifts tied to habitat (coastal, highland, bay).
- Stages: expect role and silhouette changes, like the Emberpup line moving toward dark-fire BREAK.
- Cosmetics: log them for completion, but never rank around them.
Track evolution as a condition, not a level
Current test notes tie evolutions to stated progression conditions rather than raw experience alone. Write the condition down when the client shows it, and mark it pending when it does not.
- Record the exact requirement text the first time an evolution unlocks.
- Do not spend evolution materials to “check” an unverified requirement.
- Retest lineage claims after each patch; conditions are balance levers.
Compare like with like
Before declaring one Aniimo stronger, confirm both records share stage and form. A basic-stage coastal form losing to an evolved highland form tells you nothing.
- Annotate every comparison with stage and form labels.
- Keep one reference specimen per line unevolved for baseline tests.
- Move mismatched comparisons to WATCH instead of publishing them.
Field note template
Keep observations reproducible
Write down your region, test build, Aniimo form, level, teammates, target and result. A useful beta note explains its conditions.