Why the Collector releases small piles
In STEEL GULLET, Oxideworks identifies the Collector as the machine for combining compatible piles. Players report that it combines what is available at the same time. A light pile leaving the machine can point to staggered arrivals instead of a broken Collector.
Full Steam release unless a source specifies the demo. Evidence checked . Guide updated .
Steps
- Take a pair of piles with matching material and state. Feed them on a small line where you can see when each pile reaches the Collector. Inspect the outgoing mass.
- Run the same check with the two arrivals spaced farther apart. If the output gets lighter even though the inputs have the same material, the arrival pattern is likely relevant to this build.
- Watch the downstream merger separately. A steady stream of smaller piles may occupy the shared belt while heavier piles on another branch wait. Isolate the output before changing the Collector or routing.
How to tell it worked
You can tell whether small output comes from arrivals, incompatible items or downstream congestion. Your final line handles normal arrivals without assuming a fixed output weight.
If you are still stuck
Treat a request to make the Collector wait for a target mass as a proposal. Do not design a line around a guaranteed mass that your test does not produce.
Separate compatibility from arrival timing
Choose two piles that match on the visible properties you can inspect. Keep their arrival paths short and observe the Collector when both reach it together. Record the incoming mass and the output you actually see. Then do the same with a pair that reaches the Collector at different moments. Compare the output in those two cases before assuming a minimum output weight or a particular waiting period.
If only the simultaneous sample produces a larger pile, that result is consistent with the reported arrival behavior. If the simultaneous case also stays separate, compare the inputs more closely. Look at their forms and material labels. Repeat the test with a pair you can confirm is compatible. A difference between those tests gives you a better basis for diagnosing the Collector than changing its arrival pattern and material at once.
Watch what the next belt is doing
Keep the output of the Collector away from the shared merger during the first trial. Watch whether a large pile leaves and can move away. Then observe the same branch with the downstream line connected. If the operation combines piles but the next section still queues, compare its outlet with the point at which the two streams join. One of the reports described many small piles crowding a merger while a different branch waited.
Test one sample per branch and then let both branches run. Inspect the first common section at the busiest moment. A trouble-free isolated path can still produce delays when both streams send output together. In that case the useful difference is the downstream load. If the isolated Collector output stays small, focus on the inputs and timing before rebuilding the merger.
Record a repeatable result
Write down which inputs you matched, how close together they arrived, what left the Collector and where it waited. That record can distinguish a real capacity or timing question from a belt routing issue. The discussions include a request for waiting until a target mass. Treat that as a proposed behavior while testing the current version. Keep enough belt capacity for the output you actually observe, including small piles that leave between larger combinations.