StarRupture Pull System: How Logistics Actually Work
StarRupture uses pull-based logistics, not push. Understanding this changes how you design factories. Here's how pull requests work and common mistakes to avoid.
Pull vs Push: Why It Matters
StarRupture uses PULL logistics, not push. This confused me for hours. Machines request items when they need them—they don't just receive whatever you send.
Once I understood this, my bottleneck problems disappeared. Pull systems are self-balancing IF you set them up correctly.
How Pull Requests Work
When a machine needs input, it sends a request to connected storage or dispatchers. Items only travel when needed.
This prevents overflow and ensures high-priority machines get resources first. No more clogged fabricators!
How To Optimize For Pull
Keep input buffers SMALL. Large buffers slow down pull response because requests wait until buffer space opens.
Use Storage Depots as central hubs. They respond to pull requests from multiple machines efficiently. I run everything through 2 central depots now.
3 Pull System Mistakes I Made (So You Don't Have To)
Mistake 1: Overfilling input queues. A machine with 100 pending items ignores new requests until it processes the backlog.
Mistake 2: Mismatched production rates. If smelters output faster than fabricators consume, the pull system can't fix it. Balance your machines.
Mistake 3: No central storage. Without depots, pull requests have nowhere to draw from. Always have buffer storage.
Related guides
StarRupture Rail System: How To Build Your First Automated Factory
Rails transform StarRupture from tedious hauling to automated production. Here's how to build rail networks, set up dispatchers, and avoid common mistakes.