Clone Builders Saves: Where the Save Control Is and What It Stores

Quick answer

Saving in Clone Builders runs through the Saves control on the in-game HUD. A third-party walkthrough dated September 24, 2026 describes Saves as the control used to store completed projects, with the completion banner marking when a build counts as finished. Loading or reusing a saved build later is not documented yet, so confirm the control's behavior in game.

• Saves sits in the HUD control row: Speed, Noclip, Tools/Edit, Minigames, and Saves.
• It stores completed projects — builds flagged by a top-of-screen banner such as 'complete!' plus your prompt.
• The banner confirms a build is done; the walkthrough doesn't describe the banner itself as performing the save.
• Slot counts, menu contents, load steps, and persistence across sessions or servers aren't documented — verify them in game.

Where the Saves control appears

In Clone Builders, saving is a control on the in-game HUD rather than a separate menu reached from outside a session. Per the walkthrough, while your clone crew works you can move around the server, and the HUD carries a row of controls: Speed, Noclip, Tools/Edit, Minigames, and Saves. In that row, Saves is the control used to store completed projects, alongside Noclip for flying through structures and Tools/Edit for editing parts.

What can be saved, and when a build counts as finished

The save system is described as a place to store completed projects — builds that have finished. The walkthrough defines the finished stage by the progress counter and the completion banner: a build starts at 0% – 0/176 pieces and climbs as parts go in; when the model finishes, a banner appears at the top of the screen naming the creation and marking it complete, for example a message reading 'complete!' with your prompt. That banner is your confirmation that the project is done — the stage at which a creation counts as a completed project that the Saves control exists to store.

Two boundaries matter here. First, the banner only confirms completion; nothing in the walkthrough says the banner or the game auto-saves the build at that moment. Second, piece counts and banner wording vary by prompt — the 0% – 0/176 pieces figure comes from the walkthrough's sample build.

Protecting saved projects around updates

The Clone Builders update guide treats saved projects as work to protect rather than describing save mechanics. Its pre-update checklist says: "Before testing record your current layouts, settings, and saved projects for easy comparison." Among the things to check in an update it lists system changes to "saving, sharing, permissions, performance, or project loading," and asks whether older builds still load correctly, because that "protects saved work and shared projects." For hands-on testing it proposes the task "Save a revision" with the pass condition "Changes remain after reopening," plus the follow-up "Check whether the original stays intact."

This is generic update-review advice for builders, not a documented description of the Saves menu. It indicates only that saved projects are expected to survive updates and should be verified by reopening.

What to verify in game

Several parts of the save picture aren't documented yet, so check them directly rather than assuming:

• What the Saves menu contains, and how a saved creation is opened or reused later.
• The number of save slots and any storage limits.
• Whether any auto-save happens when a build finishes.
• Whether saved builds persist across servers, sessions, or devices.

Clone Builders is an evolving experimental game whose systems change over time, so re-check the HUD label "Saves," save limits, slots, and persistence behavior before relying on them. A practical routine: after your next completed build, open the Saves control and note exactly what it offers, then reopen the session to confirm the project is still there.