Rust PC · Industrial automation
Rust Industrial Splitter: Share Supplies Without Mistaking It for Priority Storage
On this page
Use the Industrial Splitter to create multiple outgoing item paths. It is not an electrical splitter and it does not create extra supplies. Check which receiving containers can accept the item before using a simplified equal-share example to plan restocking.
Published October 18, 2026 · Developer revisions and current item references reviewed
Build the smallest useful test first
- Start with one source, one conveyor and the splitter, then connect the intended receivers.
- Use the same test item and leave enough receiving space on each branch. Avoid different destination filters during the first comparison.
- Count the source decrease and each destination increase. Restore limits one branch at a time.
- If one destination needs priority, describe that policy explicitly instead of assuming a parallel split means first-fill priority.
A controlled example
With three eligible receivers and an illustrative 600-item shipment, 200 per receiver is the simple three-way distribution example used in the original developer explanation. It is not a promise that every temporary state, blocked destination or modded-server tick will display those numbers immediately.
Make the system serve the actual goal
Distribution and stock targets solve different problems. Equal new deliveries do not necessarily equalize existing inventories: receivers beginning with 0, 100 and 500 remain different after the same addition. If your goal is to maintain a stock threshold, plan the quantity rules around that goal rather than expecting a splitter alone to balance every box.
Match the symptom to the next check
| What you see | What to check |
|---|---|
| One output receives nothing | Check its connection, capacity and item eligibility before replacing the splitter. |
| The boxes never hold equal totals | Separate equal incoming shares from equal final stock. |
| The first box must fill before the second | That is a priority policy, not the simple parallel-splitting model. |
Version and setup limits
The example assumes eligible, unblocked paths. Treat server settings and actual receiver state as part of the test.
Keep a note of the server and the one setting changed between observations. A modified server can differ from the default design; a historical demonstration is not a measurement of the installation in front of you. Restore the full line in stages after the isolated test works, checking the destination stock after each stage rather than assuming every new connection preserves the result.
Sources
Retrieved October 18, 2026. The troubleshooting order and arithmetic examples are independently written editorial guidance, not a personal gameplay test or a guaranteed server result.