A useful comparison begins with the decision in front of you. Configuration ranges, skill costs and effect conditions answer different questions. This guide uses Ironhorn, Terralime, Chubee, Sharkitten and Tearwick to show how to turn their records into a shortlist without inventing damage calculations.
Editorial reviewed
Start with a question the record can answer
Before comparing two entries, name the job you need done. Do you want an Amethyst Mine worker, an attack that applies Paralyzed, or a way to leave the field while helping the next Lumi? These are different choices. A high Attack maximum cannot answer all of them. Open each candidate and identify the relevant trait, signature and supporting skill before treating the overall stat line as a recommendation.
For example, Ironhorn and Terralime both have Mining Lv1 recorded. That makes them reasonable candidates for the same initial shortlist, but their traits point in different directions. Ironhorn has a facility-specific mining benefit; Terralime has a combat trigger when defeated. The useful comparison asks which assignment or battle condition you actually expect, rather than assuming that a shared job label makes the two entries interchangeable.
Read configuration ranges without turning them into guarantees
The dex displays minimum and maximum values from the maintained configuration. Ironhorn has a Work range of 76–132, while Terralime has 49–81. These intervals overlap between 76 and 81. Ironhorn therefore has the higher displayed ceiling, but the ranges alone do not establish that every Ironhorn you obtain must outperform every Terralime. A ceiling comparison and an individual comparison are different claims.
Sorting by Highest Work uses the maximum. It is a browsing aid, not a production simulator. The same distinction applies to Attack, Defense and HP. You should compare values from compatible configurations and then check the actual conditions in your game. Do not multiply a Work maximum by a trait percentage to publish output per minute: the maintained record does not define the formula connecting those quantities.
Separate skill Power from final damage
Power is a field attached to a skill. It is useful for distinguishing attacks and identifying conditional changes, but it is not a measured damage result. Ironhorn has Iron Head and Raid listed with the same base cost and Power. Iron Head adds a Defense-level benefit; Raid depends on an attack-speed condition. Equal headline fields therefore conceal a real difference in when the skill is useful.
A comparison such as Power divided by cost can be a descriptive ratio, but it ignores defense, effects, target count, weather and the value of a setup action. It cannot establish the best move. First compare effects that solve your problem, then compare the recorded expenditure. If the record says that Power changes under a condition, state the condition explicitly instead of silently treating the boosted value as the default.
A zero or missing field needs a different interpretation
A zero-Power action can still change a battle. Earth Barrier raises Defense Level, and Sharkitten’s Charge Up prepares its next eligible skill rather than dealing immediate damage. Zero does not mean useless. These actions spend an opportunity to create a later benefit, so their value depends on whether the user survives and whether the next action can use that preparation.
A missing field is different from a zero. Tearwick’s Candle Tears has no conventional Energy value recorded because it is an Exertion skill; do not label it a free attack. The cost semantics have to be checked separately. Likewise, a multi-hit attack with an incomplete scalar Power should not be assigned an invented total. Read the effect and any recorded hit information, preserving the difference between absent data and an explicitly recorded number.
Turn each trigger into a checkable decision
Conditions usually matter more than adjectives such as strong or versatile. Terralime’s Earth Gel reduces the enemy’s Defense Level when Terralime is defeated. Its Earth Retreat is a departure action. Leaving and being defeated are separate events, so an Earth Retreat plan cannot promise the Earth Gel benefit. If your strategy requires both outcomes, explain how each would actually occur rather than combining them in one sentence.
Chubee provides another distinction. Bee Sting adds a chance of Paralyzed on attacks, while Hive Toss records a fixed application. A chance is not a reliable substitute for a guaranteed setup when your next action needs a stack. Compare the uncertainty with the resource and timing costs. Do not invent stack limits, duration, or the order of simultaneous effects when the record does not define them.
Compare a short sequence instead of isolated moves
Write a two-action plan in plain language. With Sharkitten, you might consider Charge Up followed by Meow Punch. Charge Up has a recorded cost and a next-skill boost that expires upon leaving. The plan therefore needs both the resources for the preparation and a reason to stay in. If you must switch immediately, the setup no longer answers the same problem.
With Chubee, a stack-building action followed by a stack-dependent attack is a different kind of sequence. Check whether the target still has the required condition when the second action occurs. This approach exposes dependencies without pretending to simulate an entire battle. It also helps identify a cheaper fallback: when the condition is absent, select a move for its ordinary effect rather than relying on its conditional payoff.
Read the skill element as well as the Lumi element
A creature’s element list does not tell you the type of every attack it can use. Terralime’s Earth Spike is recorded as Normal despite its name. Reading the name as a type would lead to a mistaken matchup decision. Use the element field on the actual skill, and distinguish that attack choice from the creature’s defensive identity.
The separate element chart records single-element relationships with directional arrows. It does not supply a numerical damage multiplier or a verified formula for combining two defender types. Use it to ask a coverage question, then open the relevant current creature and skill records. A favorable arrow cannot cancel a resource shortage, an unfulfilled trigger or an unsuitable target, and a missing chart element must stay unresolved.
Make a shortlist that can survive a version change
Keep your comparison compact: the role, the relevant range, the exact enabling condition, the resource cost and one fallback. Ironhorn’s mine assignment, Terralime’s defeat trigger and Chubee’s stack plan are examples of different roles, even if two candidates share an element or similar maximum values. Choose for the role you need, and keep a second option for the condition you cannot guarantee.
Before spending resources, check the names and descriptions in your current game version. Historical launch teams and the current client dex can differ. If a key field has changed, revisit the comparison from that point rather than trusting an old conclusion. The aim is a decision you can explain and verify, not a single score that hides uncertain rules behind a precise-looking number.