Star Rupture Factory Automation Guide
A good Star Rupture factory is easy to inspect when a machine stops: inputs are visible, routes are short, power is understandable, and a new machine can be added without rebuilding the whole base. The exact recipes and available tools can change during Early Access, so use this as a layout method rather than a list of permanent item names or ratios.
Build around four readable zones
1. Inputs
Place extraction and incoming storage where the player can see the feed. Leave room for a second source if the current recipe later becomes the bottleneck.
2. Processing
Group machines that perform the same stage. Keep their input and output sides consistent so a damaged or blocked line is easy to trace.
3. Buffers
Use containers at meaningful hand-off points. A buffer should reveal whether the upstream machine or downstream consumer is failing.
4. Assembly and defense
Keep critical production and player routes accessible. Do not bury the only repair or power connection behind decorative construction.
Choose a logistics pattern
| Pattern | Use it when | Main trade-off |
|---|---|---|
| Short direct line | One recipe is close to its inputs | Simple to debug, less flexible if the source moves. |
| Central storage | Several recipes share ingredients | Easy access, but a central route can become the bottleneck. |
| Modular districts | The base is growing or the world is shared | More walking or hand-offs, but safer expansion and maintenance. |
| Test line | A new recipe or build version is unproven | Consumes space, but protects the production save from a bad rebuild. |
Diagnose a stalled line before expanding it
- Check whether the destination is powered and configured for the intended output.
- Check the last container or connection before the idle machine.
- Follow the input back one stage at a time instead of rebuilding everything.
- Stop non-essential machines briefly and see whether the symptom changes.
- Reproduce the smallest version of the line in a test save.
Do not turn an observed stall into a made-up server setting. Record the recipe, world, build, machine state, and log time so the same test can be repeated after a patch.
Leave room for change
- Keep a clear side for adding one machine or a larger buffer.
- Separate player walkways from the tightest production routes.
- Make critical power and storage reachable without deconstructing a whole district.
- Mark the owner and purpose of shared modules in a sign or group note.
- Back up before a major move; use the save-transfer guide when changing hosts.
Factory size and multiplayer performance
When a base becomes difficult to build in, ask whether every player sees the same pause. A client-only frame drop points toward rendering or local settings; a synchronized pause points toward server simulation, save activity, or a build-specific issue. Capture both observations before buying more resources. See large-base build/deconstruct troubleshooting and server requirements.
Version check
Use the official announcement feed to identify update timing. The dedicated server itself is still described as experimental in Creepy Jar's setup article.
Related guides
- Production planner and bottleneck worksheet
- When building reports an unstable location
- Dedicated server setup
- Connection troubleshooting
Run the factory on managed Star Rupture hosting with the live resource options shown on the plan page.