A stalled Modulus: Factory Automation campaign is usually not asking for one more belt. It is asking for a missing dependency: a second module stream, a production resource, a building output, or a Datashard tier that the next unlock consumes. The fastest way forward is to trace the requested item back to raw extraction, then keep every earlier tier running while the new branch comes online.
This route follows the released PC game and is bounded to Patch 1.1.1, dated July 6, 2026. The launch-week walkthroughs still say Droid, Droid Core, and Droid Assembly; the current client renamed those to Android, Advanced Core, and Android Assembly. Read the live objective and Tech Tree first if a label or cost differs.
Use outputs, not ranks, as your campaign checklist
Rank opens doors, but a new number beside your save does not prove that the factory behind it is stable. Before buying the next island or Tech Tree node, confirm that the current delivery can continue without hand-feeding. These are the useful campaign checkpoints:
| Checkpoint | What must run unattended | What it unlocks or prepares |
|---|---|---|
| Basic production | Basic Cores and Basic Bots reaching their consumers | The first complete building-to-building dependency |
| Grey loop | Grey Processors entering a Data Center and Grey Datashards reaching the Delivery Dock | Rank 2 Tech Tree access and early building upgrades |
| Blue paint | Hexacrystal and Oil feeding the refinery and Dye Mixer, then Paint reaching a Painter | Module Challenges and blue construction modules |
| Android line | Advanced Cores feeding an Android Assembly, with Androids delivered | The advanced processing branch and reliable rank growth |
| Blue loop | Blue Processors plus Grey Datashards entering a second Data Center | Blue Datashards and advanced operators |
| Inter-island scale | Coolant, freight routes, and yellow production remain stable under load | Superior production and monument construction |
Do not retire a lower tier merely because its successor exists. Blue Datashards consume the work of the grey chain, and later buildings reuse module families learned earlier. A campaign that cannibalizes every old output for the newest objective tends to oscillate between shortages.
Build the first core as two inspectable module lines
The tutorial establishes the grammar: Miners extract Polyrock, a Furnace turns it into Cubes, Cutters change the geometry, an Assembler defines the required arrangement, and a crane submits the result to a building. Keep that first line visible. It becomes the reference against which later lines can be debugged.
The second Basic Core module is the first warning against copying an entire factory blindly. Reuse the extraction and early cutting stages where their output shape still matches, then branch before the new operation. The launch route uses a second cut and an Assembler to make the required long piece, followed by a split to feed two cranes. The exact orientation belongs in the live module preview; the reusable lesson is that one correct intermediate can serve more than one destination.
- Pin or open the requested module before placing the branch.
- Rotate the candidate pieces inside the Assembler until the preview, including empty space, matches.
- Let at least several outputs pass before connecting a crane.
- If one crane starves while another belt backs up, correct the split rather than adding miners.
Once the Basic Core Facility is producing, use a Harvester Pad to take its output toward the Basic Bot Assembly. The black component introduces the Monotoner; the other component can be cut from a shape already produced for the core facility. This is the first worthwhile shared intermediate in the campaign.
Keep the grey chain alive after the Delivery Dock opens
The Basic Processing Plant needs both its own construction modules and a continuing supply of Basic Cores. Treat those as separate problems. Finish and test the building modules first. Then connect the Harvester Pad carrying Basic Cores and watch the plant produce Grey Processors before routing anything to the Dock.
A Data Center has two inputs. For the first Grey Datashard recipe, split the Grey Processor stream so both ports receive the required material, then send the output to the Delivery Dock. Reaching Rank 2 exposes the Tech Tree, but do not immediately spend every Grey Datashard. You need a working balance between unlocks, floor upgrades, and the continuing deliveries that grow the account.
The launch path spends early Grey Datashards on the second floor for grey buildings and the Basic Refinery for blue pigment. If your current tree shows a different price or prerequisite, follow the live branch. The important sequence is unchanged: create room for upgraded basic production, then claim an island with Hexacrystal and Oil before committing to blue modules.
Blue paint is a four-resource handoff
A placed Painter is not a blue-production system. The full handoff is:
Polyrock modules build the Basic Refinery; Hexacrystal enters that refinery; refined material and Oil meet in the Dye Mixer; Paint then reaches the Painter.
Build and validate that chain from left to right. The Basic Refinery requires three construction modules, and the third is the first shape complex enough to punish an ambiguous layout. Instead of memorizing a screenshot-relative recipe, divide it into named subassemblies: two long black pieces, one white combined piece, then the final two merges shown in the live target. Flip pieces inside the Assembler rather than rebuilding an upstream line to compensate for the wrong orientation.
When the refinery is complete, put an Extractor on a blue Hexacrystal deposit and carry the output into the refinery. An Oil Rig supplies the other raw branch. The Dye Mixer needs both processed material and Oil; only its output should feed the Painter. If the objective does not advance, inspect those four handoffs in that order. A full paint belt cannot repair a refinery that never received its production resource.
Use MOD-A to learn what happens to both Stamper outputs
The first Painter unlocks Module Challenges, and MOD-A is the practical introduction to the Stamper. A stamp does not merely decorate a block: it separates the kept form from the removed voxels. Either output can matter later, so route or discard each one deliberately.
The launch objective accepts one completed MOD-A design, while finishing all three gives more rank progress. That makes the challenge a useful branch, not a reason to dismantle the paint line. Keep the first design simple, then use the later targets to practice two operations that recur in advanced buildings:
- Remove a row or central section while preserving the surrounding frame.
- Recover a stamped-out piece and combine it with an untouched branch in a later Assembler.
- Inspect both Stamper exits before assuming the apparently unwanted side is scrap.
Patch 5 added a choice for which stamped result leaves each side and a separate scrap-behavior toggle. A launch screenshot can therefore disagree with the current routing without the recipe being wrong. Configure the present Stamper UI, then reconnect the belts.
Translate Droid-era instructions before building the Android tier
After the module challenge, the campaign moves to advanced cores and Androids. Older walkthrough text calls these the Droid Core Facility and Droid Assembly. Happy Volcano’s April 7 terminology update changed the names only; it did not change their function.
Place the Advanced Core Facility where blue paint can reach its construction line without crossing every basic belt. Its targets combine blue, white, and black geometry, including stamped openings. The safe workflow is to produce one color-correct intermediate at a time, compare it with the live preview, and only then join the final pieces.
Connect the facility output to a Harvester Pad. The Android Assembly consumes Advanced Cores, so its production resource is not interchangeable with its construction modules. First finish the building, then attach the core feed, then route completed Androids to the Delivery Dock. If the objective remains at zero, check the Android output belt before rebuilding any module line.
Blue Datashards require the grey factory to meet the blue factory
The next step is not simply a blue version of the first Data Center. Build an Advanced Processing Plant and keep Advanced Cores flowing into it. Its output is Blue Processors. A new Data Center then combines that stream with Grey Datashards, not Grey Processors.
This distinction catches many otherwise correct layouts. Trace the two inputs by product name:
- Blue side: Advanced Core Facility to Advanced Processing Plant to Blue Processors.
- Grey side: Basic Core Facility to Basic Processing Plant to Grey Processors, then a Data Center to Grey Datashards.
- Final conversion: Blue Processors plus Grey Datashards enter the blue recipe in another Data Center.
Do not divert the only Advanced Core output away from Android production if Android deliveries are still your reliable source of rank progress. A new island or a second core facility costs space up front but prevents one objective from starving another.
Move transport and coolant before yellow production consumes the map
Blue Datashards open advanced operators. Advanced Cutters and Assemblers make later geometry easier, but they require Coolant delivered through a Supply Tank. Build the coolant branch as infrastructure, then connect advanced operators gradually. Patch 5 added two coolant-efficiency upgrades: one unit supports 16 operations at base, then 32 and 64 after the upgrades. Those live values make the upgrades meaningful before a large yellow rebuild.
Freighters become the cleaner alternative once production spans multiple islands. The launch route places their unlock around Rank 8, but verify the current Tech Tree. A working route needs two Freight Hubs, a defined load point, and a defined unload point. Give each hub a resource-purpose name and reserve its numbered docks. A route that exists in the control panel can still move nothing when the resource arrives at the wrong dock.
Yellow production adds Solarite, yellow pigment, superior buildings, Mechs, and Yellow Datashards. Stabilize the blue and coolant networks before starting it. A factory that cannot sustain Blue Datashards will not become healthier when a third color and another core tier compete for the same transport space.
Treat each Neural Monument as a saved library of earlier modules
The launch route records unlock costs of 4,000 Grey Datashards for Grey Nexus, 2,000 Blue Datashards for Blue Vault, and 1,000 Yellow Datashards for Yellow Spire. Check those figures in the current client before committing a long production run. They describe the captured launch build and may move in a later balance update.
The monument modules reuse the logic of the buildings that precede them: grey construction families for the Grey Nexus, advanced blue families for the Blue Vault, and the yellow/superior tier for the Yellow Spire. Preserve a blueprint or an uncluttered reference cell for each successful family. Rebuilding from that verified cell is safer than reconstructing a complex target from memory.
Submit modules in controlled batches. Once a particular requirement is filled, a belt that continues pushing that shape can block a crane or occupy the approach needed by another requirement. Patch 1.1.1 also changed monument behavior: pausing now stops the charge and progress, and fixes were issued for lost non-shape resources and modules discarded when a GNN Gate upgrade was canceled. Update before diagnosing an old save, pause deliberately, and inspect the live requirement counter after each batch.
When progression freezes, separate a design error from a client error
Start with the smallest observable state. Does the final consumer show the correct resource? Is the last operator moving? Does the first upstream belt that stops have a full output or an empty input? Only after that should you reload or rebuild.
Patch history matters. Since launch, official fixes have covered frozen factories, Cutters stopping, crane conflicts, drone links, long conveyors, Module Challenge saves, mirrored Assembler states, Freighter cargo, and GNN progress. Patch 1.1.1 specifically addressed a Salvager-related factory stop, thread safety in Statistics/Achievements, and Freighter jitter. If the entire factory stops despite valid inputs and open outputs, confirm version 1.1.1 or newer before converting the whole island into a workaround.
Mods add a separate boundary. Official mod support disables Steam achievement unlocks while a mod is active, and a save opened with mods is permanently marked as modded. Reproduce a suspected production bug with mods disabled before treating it as a campaign rule.
Sources & credits
Valve’s official Steam listing identifies AppID 2779120, Happy Volcano as developer, Kwalee as publisher, the April 2, 2026 release, and the current 36-achievement set. The official Modulus site confirms the cut-paint-stamp-assemble loop and the low-pressure design. Current names, patch boundaries, coolant changes, Stamper behavior, and troubleshooting notes were checked against Happy Volcano’s Steam announcements through Patch 1.1.1.
The progression order was reconciled across three readable launch-week walkthrough parts. Their image-relative layouts were converted into dependency checks, and their pre-April-7 Droid terminology was updated to the current client. Trainer advertisements, an unattributed cheat page, a conflicting fan SEO wiki, a joke guide, and warning-marked Community items supplied no route facts.