A Home Ability determines which jobs an Aniimo can perform. Its ability level, personality and food affect work output, but a faster worker does not automatically take over an occupied facility. Availability, existing assignments and replacement restrictions matter too.
Which Aniimo can work
The worker needs the Home Ability required by the facility's current operation. Different stages of one recipe can call for different abilities. Some operations also restrict which Aniimo can perform them.
The recommended ability level is not always a hard entry requirement. For the reviewed mining operations, possessing Earth can be enough to qualify even below the recommendation; the level difference still affects output. Do not extend that exception to every job.
A worker must also be available in the Production Area. An active Homeland incident, such as sickness, blocks eligibility in the reviewed selection checks. Powered production follows a different path from ordinary Aniimo-powered work.
Home Abilities and their levels lists the English names and described tasks.
Calling a worker versus automatic assignment
These are different selection paths:
| Action | What is compared | Important distinction |
|---|---|---|
| Facility call-worker action | Calculated work output of eligible Production Area candidates | Picks the greatest positive output it finds; a candidate can already be working at another facility |
| Ordinary free-worker allocation | Available jobs for an unassigned Aniimo | Keeps existing assignments; it is not a global ranking of every worker by speed |
| Replacement check for an occupied slot | Candidate output against replaceable incumbents | Runs only when replacement is permitted; equal output does not qualify |
The facility call-worker action checks the facility's slot capacity and sends an assignment request. The final accepted assignment is managed separately. It should not be described as a promise that pressing the button evicts an occupied slot or finds the best arrangement for the whole Homeland.
Automatic allocation also considers the type of work, available slots and facility priorities. Previous location and distance can enter its comparisons. We cannot yet describe a complete live ordering of every candidate and job, so neither “closest always wins” nor “highest ability always wins” is a supported rule.
Keeping an assignment
The ordinary free-worker pass first checks whether the Aniimo already has a non-empty assignment. If it does, that pass leaves it alone. The job selector independently preserves an existing assignment unless reconsideration is explicitly forced.
Aniimo already has a job
→ ordinary free-worker pass skips it
Aniimo has no job
→ check availability and candidate facilities
→ check open slots or permitted replacement
This explains why making a stronger worker available does not, by itself, rearrange the whole workforce. It does not establish that assignments are permanent: a separate action can remove, reset or change them.
Replacing the current worker
For the reviewed Mine, Claw Game Cooker, Blazing Stove, Woodworking Bench and Chimney Kiln operations, the replacement helper blocks automatic replacement during an ongoing production round.
The helper has a round-finished exception, but the timing of live checks at that boundary is not confirmed. A production batch finishing is not sufficient evidence that the entire workforce is rescanned every time.
When the comparison is permitted:
- An incumbent whose allocation is marked manual is excluded by this helper.
- The candidate must have strictly higher calculated work output.
- Among eligible incumbents, the helper can select the weakest worker below that candidate's output.
The management panel sends a force-assignment input for a manual selection. Its complete relationship to the stored manual marker is not established, so this guide does not promise an indefinite lock for every assignment made through the panel.
Returning after sickness or injury
Player observation: an identified worker can remain displaced after another worker has taken its former position.
That is consistent with the assignment and replacement restrictions above. A identified Aniimo has no special reclaim priority in the reviewed replacement helper. If it returns as an unassigned candidate, its previous job is still subject to slot availability and replacement rules.
There is another possible state: if the original assignment remains recorded, the client can return to that recorded work after the incident behavior ends. How this is reconciled with a replacement occupying the slot is not confirmed.
How hauling enters the decision
Hauling demand is checked per facility. It depends on stored output, a recipe threshold and the presence of Home storage; it is not simply a request for the highest Hauling level in the Homeland.
- The facility must have positive stored output.
- Output must reach the recipe's hauling threshold. Where no explicit threshold exists, the reviewed helper uses 60% of the output limit.
- Home storage must be available.
- The candidate must have Hauling.
Some mining recipes have small explicit thresholds, so a Mine can need collection well before its output buffer is full. Hauling level changes carrying capacity in a separate table; the ordinary transport check does not require Hauling Lv.4.
A candidate can be skipped before its mining job is checked
For a Hauling-capable candidate, the facility helper checks collection before its ordinary production slot. If hauling demand exists but another worker is already collecting or approaching to collect from that facility, this helper returns no job for that candidate instead of continuing to the production-slot check.
A worker without Hauling does not enter that branch. Under those conditions it can reach the mining check while a stronger, Hauling-capable miner is skipped.
This is a conditional candidate-selection behavior. The ordinary pass preserves existing jobs before reaching it, so this branch alone cannot pull an actively assigned miner out of its job. It can help explain filtering among unassigned candidates, not prove how an occupied Mine originally changed workers.
Hauling capacity
| Hauling level | Carrying capacity |
|---|---|
| 1 | 60 |
| 2 | 80 |
| 3 | 100 |
| 4 | 120 |
These values are distinct from the Home Ability tooltip points. The management screen also has a recommended hauler count based on the number of relevant facilities. That display is not established as a hard rule reserving particular miners for hauling.
Reassignment actions and timing
The management screen's allocation button sends an explicit reset-all-worker-assignments request, then refreshes the display after a successful response. Individual assignment and unassignment requests also exist. The full server-side reset and reassignment procedure is not established here.
No fixed expiry for manual assignments, automatic daily reset, logout reset or guaranteed whole-workforce rescan after each batch has been confirmed.
The client has a roughly one-second AI-state check, but that check repairs missing behavior plans from existing state. It is not a one-second job-selection cycle.
Checking an unexpected assignment
Record who occupies the facility panel, which Aniimo are idle, active incidents, the recipe and production stage, and whether output is waiting for collection. Distinguish an Aniimo listed as a producer from one merely carrying nearby output.
Observing whether the change follows a manual allocation action, recovery, a recipe change or a finished batch can narrow the possibilities. None of those observations should be replaced with an assumed timer.
Home Abilities and work aptitude · Facility upgrades · Production recipes · All topics