Clone Builders Crew Status: How to Read Each Clone's Activity
Check Clone Builders crew status in the Crew management window: labels such as CLONE 1: BUILDING plus a live piece counter. What the building state means and what's unverified.
Quick answer
While a project is underway, guides point to the Crew management window as the display to read Clone Builders clone status from: each clone working on the job has its own status line there, paired with a live piece counter for the model being assembled.
- Each clone working on the job has its own status line during the project.
- The window pairs those status lines with a live piece counter for the current model.
- It is the display to check when you want to know what each clone is doing right now.
What the documented active building state shows
Tips
BUILDING is the documented active label
Each active worker shows a per-clone label such as CLONE 1: BUILDING. This is the only crew-window state label that is documented; idle, waiting, finished, or error labels are not documented, so treat any other text you see as unverified rather than assumed.
Live piece counter
Alongside the per-clone statuses, the window shows a live piece counter for the model being assembled.
What a BUILDING clone is doing
A clone in this state is working on the build idea it was given. Guides describe clones handling individual parts, combining them into larger sections, and assembling the final structure.
Clear, focused ideas work best
Guide coverage describes clear, focused build ideas as producing the most reliable building results.
How clone status relates to the assigned project
Clone activity in the crew display tracks the job you assign, not free-roaming behavior. After you write a prompt and select a location, three clones are assigned to the job, collect the pieces, and put the model together in real time while you walk around to inspect their work. The official game page frames the same loop as giving your clones an idea and watching them get to work, with the NPC clones using a structured building system to place, resize, move, and assemble parts into creations in the world.
A third-party framework for reading other clone actions
A player-made behavior guide offers a state vocabulary for interpreting what an individual clone is doing after it receives a task. In that framework, a clone may remain idle, move toward a work area, perform a construction action, respond to danger, assist another unit, or return to a recovery state. The guide presents these as a diagnostic language rather than on-screen text, and its state names are not confirmed to match the labels shown in the Crew management window — its danger, defensive, and recovery states in particular go beyond the purely constructive building loop described elsewhere for the game.
Mistakes to avoid
- Problem
- Deciding a clone is broken
- Fix
- Run the guide's diagnostic questions first: is the clone stuck in travel, repeatedly switching targets, waiting for materials, or reacting to a defensive condition?
- Problem
- Judging a pause with no context
- Fix
- Note whether the clone remains active, switches targets, returns to idle, enters a defensive state, or waits for access or materials before you change anything.
- Problem
- Reading the framework as in-game labels
- Fix
- Treat these state names as that guide's interpretation. The only label documented in the Crew management window is BUILDING.
Symptom-based reading of clone behavior
Comparison
| Symptom | Common Cause | Recommended Check |
|---|---|---|
| Clone stays idle | No valid task or unavailable target | Confirm assignment and target state |
| Clone circles an area | Route or access problem | Inspect entrances and blocked tiles |
| Clone abandons construction | Higher priority interruption | Review defense and task rules |
| Two clones duplicate work | Shared target selection | Divide work zones or roles |
| Clone waits near a structure | Missing material or access | Check supply route and build range |
| Clone retreats repeatedly | Persistent threat condition | Improve safety or adjust patrol logic |
The same guide advises testing one behavior at a time — changing the task, route, structure, and defensive rules all at once makes it hard to identify the cause of a problem. Treat the whole table as a troubleshooting interpretation: it borrows generic colony-sim vocabulary (blocked tiles, patrols, threats) that is not confirmed as Clone Builders mechanics and does not describe verified crew-window states.
Status labels can change after updates
Recheck status labels and their meanings whenever clone behavior is updated, because Clone Builders is explicitly experimental. The official game page states the game is constantly evolving, so players should expect experiments, strange clone behavior, new features, and probably a few disasters along the way. The fan wiki likewise notes that the biggest update categories include clone behavior experiments and building-system changes, and recommends that returning players check the latest systems before beginning a major project because the game continues to change over time. Since only BUILDING is currently documented as a crew-window label, read any other status text directly off your own screen after each update instead of assuming an older meaning still applies.
Related Guides
Clone Crew: What Your Clones Do
Learn what NPC clones actually do on a job: how they place, resize, move, and assemble parts from your prompt in real time.
Unassign Clones: Remove or Clear the Crew
Free up workers mid-build: remove one clone or clear the whole crew with Unassign, Deassign, and Deassign all.
Build Queue: Why Builds Wait
Find out why builds sit in Queued, how to read waiting jobs, and how to free clones with Unassign and Deassign.