Rust PC · Industrial automation
Rust Conveyor Min, Max and Buffer: Keep a Reserve Without Stalling Transfers
On this page
Use Minimum to retain a source reserve, Maximum to limit the destination stock, and Buffer for batch-sized transfers. Minimum is not the old batch-size setting: Facepunch changed that behavior and added Buffer separately.
Published October 18, 2026 · Developer revisions and current item references reviewed
Build the smallest useful test first
- Disconnect unrelated sources and destinations. Record the source count, destination count and one item filter before changing numbers.
- Set only the reserve you need first. Add a batch requirement only after a simple transfer works.
- Test below and above the chosen threshold using the same item. Read the current transfer state before assuming the conveyor is broken.
- Add the destination cap last. Check the resulting counts, not just whether a green light appeared.
A controlled example
For an illustrative reserve of 10 and a buffer of 15, start with 24 items and then add one more. The intended threshold comparison is 10 + 15 = 25; the extra item is what separates an insufficient batch from an eligible one. This is a diagnostic setup, not a promise about items moved per server tick.
Make the system serve the actual goal
Keep the production reserve tied to its purpose. A reserve of ingredients for hand crafting belongs to the source decision; a desired stock of finished supplies belongs to the destination decision. Moving the same number between Min and Max changes which side you are protecting. Write down that distinction before copying somebody else’s filter.
Match the symptom to the next check
| What you see | What to check |
|---|---|
| Nothing moves | Remove the extra batch condition and confirm the source exceeds its reserve. |
| Too much leaves storage | Inspect the source Minimum rather than adjusting only the destination cap. |
| The first batch starts, then stops | Check both available stock and destination state before repeatedly toggling power. |
Version and setup limits
The April 2026 patch fixes a Minimum-filter case involving other passing items. Test the current server with one item before diagnosing a complex multi-filter network.
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.