Direct Answer
Set up a short visible recoverable lane, stage the three Phase‑4 inputs (Duck / Cash Register / Piñata) on separate lanes, balance supply across those lanes, protect Piñatas during transport, then merge late into the factory hub chain: Automation → Shift Scheduler → Trade Terminal → Panel Rack → x300 Combo. For recipe/workbench fixes see Anomaly Phase 4. Current 1.0.7 piston behavior (tools stick, movement follows, off locks position, on resumes) applies inside this setup.
Quick Steps
- Build a short visible recoverable lane up-front so you can catch overflow and observe failing inputs.
- Create three distinct input staging lanes for Duck, Cash Register, and Piñata — keep Piñata on its own gentle lane.
- Use local balancing (splitters/priority routing) so no single input starves the others; keep lanes separate until just before the final merge.
- Protect Piñatas in transport (separate lane, avoid high-speed impacts or mixing) and test with small batches.
- Hook each stage into the hub chain: Automation → Shift Scheduler → Trade Terminal → Panel Rack → x300 Combo.
- If an input overflows or stops, use the visible lane and isolated shutdowns to diagnose which feed failed.
- If you need recipe/workbench changes, consult Anomaly Phase 4.
Prerequisites or What You Need
- Basic automation components: movers, splitters/routing, pistons (1.0.7 behavior applies), and local buffers.
- Factory hub components in this chain: Shift Scheduler, Trade Terminal, Panel Rack, x300 Combo.
- A short, visible recoverable lane (front-end buffer) to observe flow and catch failed output.
- Access to the Anomaly Phase 4 page for current recipe/workbench troubleshooting.
- Note community-confirmed behavior: panels snap, tools can stick to moving parts, and each mover type should handle a single job.
Full Explanation
- Short visible recoverable lane first: This front buffer is the quickest way to see which input is backing up or failing. Players consistently report it saves rebuild time and helps spot jammed or empty feeds before they affect the whole chain.
- Three-input staging: Phase‑4 production uses three inputs (Duck / Cash Register / Piñata). Current full-release community findings indicate best uptime when each input is staged separately and balanced before merging.
- Supply balancing: Don’t merge inputs early. Use local splitters or conditional routing so each lane keeps roughly equal throughput into the final assembly. The exact splitter/router settings depend on your local production rates and must be tuned per factory — there is no universal numeric setting.
- Protect fragile Piñatas: Community-confirmed practice is to keep Piñatas on a dedicated, gentle lane and avoid aggressive merges or high‑speed collision zones. Separate the Piñata lane until just before the final combine to reduce breakage.
- Separate lanes before final merge: Keep each input lane distinct through most of the transport path to simplify diagnosis and balancing. Merge late and only after buffers smooth out short bursts.
- Diagnose overflowing / failed input: Use the visible recoverable lane and isolate each feed (stop or slow it) to confirm which input is overflowing or stalled. Visual lane fill levels and stopping one input at a time are the standard community troubleshooting steps. For recipe/workbench fixes and confirmed recipe details, consult Anomaly Phase 4.
- Pistons (1.0.7) — verified behavior to include:
- Tools can stick to piston heads.
- Attached tools follow piston movement.
- Turning a piston off locks its current piston position.
- Turning it back on resumes the prior motion. Treat sticky tools and piston locking as part of your transport and timing considerations; do not rely on pistons to reset or re-home unless you intentionally toggle them.
- Other confirmed facts to preserve: panels snap into place, tools can be sticky, and movers should be assigned one job each to avoid contention. Integrate these behaviors into your lane design and mover assignments.
Common Mistakes
- Merging inputs too early and creating collisions that damage Piñatas or cause downstream jams.
- Skipping the short visible recoverable lane and losing the fastest diagnostic feedback.
- Treating pistons as stateless movers — on/off changes lock/restore position and can leave tools stuck where you don’t expect.
- Assigning multiple jobs to one mover type or relying on panels to compensate for poor routing — panels snap but won’t fix upstream imbalance.
- Forgetting to consult Anomaly Phase 4 for recipe/workbench inconsistencies before redesigning automation.
What To Do Next
- Build a minimal three-lane test rig with a small buffer and run short batches to tune balancing.
- Add the hub chain components: Shift Scheduler rules, Trade Terminal hooks, and output staging into Panel Rack → x300 Combo.
- If a recipe or workbench issue appears, check Anomaly Phase 4 for community fixes.
- Track changes and check Updates for any engine or piston behavior patches that affect your layout.
Related Guides
- Anomaly Phase 4 — recipes and workbench fixes.
- Shift Scheduler — hub timing and job routing.
- Trade Terminal — economy hookup and export rules.
- Panel Rack — panel snapping and output staging.
- x300 Combo — final combo handling.
- Updates — engine and behavior patch notes.
FAQ Q: Will a tool attached to a piston stay attached during movement? A: Yes. Current full-release behavior (1.0.7) confirms tools can stick to piston heads and will follow piston movement.
Q: If I turn a piston off, will it return to a home position? A: No. Turning a piston off locks it in its current position; turning it back on resumes the previous motion sequence.
Q: How do I stop Piñatas from breaking in transport? A: Community findings recommend a dedicated gentle lane for Piñatas, avoiding aggressive merges and late-stage collisions. Keep the Piñata lane separate until the final merge and test with small batches to tune handling.
Q: Where do I check recipe or workbench issues that affect Phase 4 output? A: See Anomaly Phase 4 for the latest community-confirmed fixes and notes on workbench/recipe problems.
Q: What’s the recommended hub chain for Phase 4 automation? A: Use the known hub chain: Automation → Shift Scheduler → Trade Terminal → Panel Rack → x300 Combo.