Creatures of Sonaria creature stats work as a profile, not a single score. Health and damage matter, but weight changes combat exchanges; speed is limited by stamina and turning; growth changes the risk of losing a slot; appetite and thirst shape the route; abilities and resistances can reverse a matchup. Compare fields only after fixing the creature’s age, current build, and intended job.
Open the current stat sources
Start with Creature Info in the live experience. The official Roblox description tells PC players to press K for controls, and current community Basic Gameplay documentation describes a Creature Info window that includes species, diet, size tier, gender, mutations, traits, current health, movement fields, plushies, age, and creature-specific controls. Other platforms should use the current Menu Actions/help interface.
Use the community Recode Creature Stats List for sorting and cross-creature comparison. It marks tier, diet, mobility, and work-in-progress data visually. Never select the Legacy table for a current build. If a table value disagrees with your live panel, use the live value for immediate play and record the discrepancy with a date.
Read core survival stats
A raw damage value does not describe whether the attack lands, how often it can be used, or how the target’s weight changes the result. A fast sprint does not describe how long the creature can maintain it. High health does not make an exposed resting pose safe.
Compare movement as an escape system
Record walk, sprint, stamina, stamina regeneration, turn behavior, jump or dart, and the creature’s mobility category. For fliers and gliders, compare takeoff, glide, flight, recovery, and landing conditions rather than mixing flight speed with ground sprint. For aquatic and semi-aquatic creatures, include depth, shore transition, and whether the route provides underwater cover.
Use a repeatable test route: a straight segment, a turn around a landmark, a short climb or water transition, and a recovery stop. Test at the same age and without unrelated buffs. The goal is not to publish a perfect speedrun number; it is to know whether the creature reaches shelter with reserve stamina.
Add abilities, traits, and ailments
Stats shown on a sheet may be modified by traits, plushies, age, status effects, pack conditions, weather, elder progression, or temporary abilities. Label the base species profile separately from a particular stored slot. A valuable double-trait or mutated slot should never be used as the only example of the species.
Read active abilities by input, range, cost, cooldown, duration, and follow-up. Read passives by trigger and condition. Read resistances by the exact ailment and magnitude shown in the current data. “Has resistance” is not the same as immunity, and a status label does not prove the displayed stack formula works exactly as described by an old guide.
Use Traits for permanent slot modifiers and Abilities and Ailments for temporary combat states. Keep those layers visible when explaining why two stored creatures of the same species perform differently.
Build a fair comparison
- Fix the scenario: escape, survival, solo duel, pack support, farming, nesting, or map travel.
- Compare the same growth stage and current build date.
- Use the live Creature Info panel for the slot and the Recode stat table for sorting.
- Pair health, damage, weight, movement, stamina, appetite, and abilities.
- Remove temporary buffs or list them separately.
- Test the route or matchup rather than declaring a winner from a spreadsheet.
- Recheck after a redesign, balance note, or unexpected live discrepancy.
For survival, weight mobility and resources more than theoretical damage. For a duel, include reach, turning, status application, resistance, and disengagement. For a pack, include support abilities and information. For missions, growth time and route speed may dominate every combat number.
Handle update-sensitive numbers
Write a stat as “value observed on date, at age/stage, with these modifiers.” Avoid copying a large full-roster table into an article, because it becomes stale and creates horizontal overflow on mobile. A responsive card or personal spreadsheet can store only the candidates you are comparing.
If two current sources disagree, do not average them. Check the live panel, verify form or subspecies, age, realm, and recent update. Mark one as community reported and preserve the disagreement until a repeatable test resolves it.
Frequently asked questions
What are the most important creature stats?
For survival: health, movement, stamina, appetite/thirst, diet, mobility, and escape abilities. For combat: add damage, weight, attack timing, turning, statuses, and resistances. The intended job decides the weighting.
Do stats change while growing?
Current community documentation says several fields change with age. Always compare the same growth stage and inspect the live slot rather than applying a full-grown row to a juvenile.
Does the highest damage mean the strongest creature?
No. Weight matchup, health, attack timing, reach, movement, statuses, resistance, terrain, and player execution can matter more than the headline number.
Evidence note
The stat-field structure is Community corroborated through current Recode Basic Gameplay, Creature Stats List, and Combat references, checked 2026-08-22 UTC. Exact numbers remain dated community data unless directly observed in the live panel.