The worker label, a job level and a Work range are useful starting points, but they do not describe the same thing. This guide compares recorded workers and shows why Ironhorn’s mine benefit, Cinderbear’s workshop benefit and a battle trait should lead to different assignment decisions.
Editorial reviewed
Separate category, job level and Work
The maintained dex includes 47 entries categorized as Worker. That category helps you find candidates, but the individual job field tells you the recorded assignment: Mining, Kindling, Cooling or Crafting, with a listed level where available. Work is a separate configuration range. Do not turn the category itself into a promise that a creature can perform every home activity.
Begin with the facility you want to support and filter the roster to candidates with the relevant recorded job. Then read their traits. A battle-oriented passive may be useful elsewhere while adding no documented home-production benefit. The category filter is only the first step; checking the actual job and trait prevents a strong-looking stat line from sending you toward a creature that solves the wrong problem.
Ironhorn is a specific Amethyst Mine choice
Ironhorn has Mining Lv1 and a Work range of 76–132. Its Wallbang trait records an Amethyst Sand mining-speed increase of 40 percent when assigned to Amethyst Mine. The named facility and named output are part of the condition. If that is your current bottleneck, Ironhorn deserves a close look because the record directly addresses the job.
If you are evaluating a different mine or another material, do not copy the same benefit into your calculation. The description does not establish a universal mining bonus. It also does not say how the percentage combines with upgrades, other workers or the underlying Work value. Use the trait to identify the relevant assignment, then verify the current facility description before reporting an expected output.
Terralime shows why a shared job is not a shared benefit
Terralime also has Mining Lv1, but its Work range is 49–81 and its Earth Gel trait concerns an enemy’s Defense Level when Terralime is defeated. That is a combat event. It should not appear as a production bonus simply because the creature belongs to the Worker category or shares Ironhorn’s job level.
Comparing the two Work ranges is still useful: Ironhorn has the higher displayed ceiling, while the intervals overlap between 76 and 81. This is a shortlist comparison, not proof that every individual Ironhorn will always produce more. If you only need an available Mining Lv1 assignment, compare what you actually own. If you specifically need the documented Amethyst Mine benefit, the trait distinction becomes the clearer reason to prefer Ironhorn.
Cinderbear belongs to a different facility decision
Cinderbear records Kindling Lv2 and a Wildfire trait that raises Amethyst production speed by 40 percent when assigned to Crystal Workshop. This is not Ironhorn’s Amethyst Sand mining effect. The shared percentage and related material names can make the two benefits look similar, but their job, facility and output conditions are different.
Choose between them by asking which part of your workflow is constrained. A Workshop assignment and a Mine assignment do not compete in exactly the same way. If you need both stages, inspect each relevant facility rather than selecting one universal winner. The records do not provide enough information to quantify a complete production chain, so avoid publishing a combined hourly forecast based only on those two trait descriptions.
Compare Cooling and Crafting on their own terms
Icitle has Cooling Lv1 and Quick Freeze, with a recorded 30 percent Cooling-speed increase. Hushhare has Crafting Lv1 and Enthusiasm, with a recorded 30 percent Crafting-speed increase. Equal percentages do not make the jobs interchangeable. First match the job to your task, then compare candidates within that role.
A battle signature is also not a home-performance measure. Icitle’s Icy Sigh and Hushhare’s Whoosh Spin are attacks with their own costs and Power. Their combat skill lists can inform a separate battle choice, but those fields do not document faster cooling or crafting. Keeping the decisions separate helps you use the same creature record for two purposes without mixing the evidence.
Use Work ceilings to browse, then check actual constraints
The dex’s Highest Work sort uses the maximum configuration value. It can surface candidates quickly, especially when a category contains many entries. After sorting, reopen the shortlist and check the minimum, maximum, job and facility condition. A maximum alone hides overlap and can distract from a unique passive that only matters in the place you intend to assign the worker.
The dex does not confirm acquisition locations for these entries. A shortlist therefore cannot promise that a particular worker is currently obtainable on your server. Use what your game actually shows to evaluate availability and any real cost of changing assignments. This guide provides a way to compare recorded capabilities; it does not invent a farming route or claim that an upgrade will pay for itself after a certain number of hours.
Two practical assignment scenarios
If your immediate task is producing Amethyst Sand at Amethyst Mine, compare Ironhorn against another recorded Mining Lv1 candidate. Identify the facility-specific Wallbang condition first, then compare their Work intervals. The decision changes if you are using a different facility: the named speed benefit no longer supplies the same reason. Write down that condition so you can revisit the assignment when your production goal changes.
If your immediate task is a Crystal Workshop output, start with the Cinderbear record instead of transferring the mine comparison wholesale. Check Kindling Lv2 and the Wildfire facility text in your version. For a Cooling or Crafting task, begin with the relevant job candidates such as Icitle or Hushhare. This approach is deliberately task-specific: it avoids an overall worker ranking that obscures the benefit you need today.
Keep a small, verifiable assignment note
For each planned assignment, record the worker, job level, Work interval, named trait condition and current facility. Then compare the displayed game result under the same facility state if you want to learn more. Keep upgrades and other assignments consistent while observing, because changing several things together makes it difficult to identify what caused the difference.
If your result differs from the maintained record, check the game version and server before concluding that the trait never works. Report the exact field and context through Contact rather than a broad claim that the whole worker is broken. The useful outcome is an assignment you can explain from a named condition, plus a clear place to update that reasoning when the game changes.