⛏OreFactoryGuideFIELD MANUAL // UNOFFICIAL

Ore Factory Squad Pallet Dispenser & Warehouse Robot Guide

Attach a Pallet Dispenser to a machine or belt, fix red placement, prove one Robot move, and recover a stuck pallet task.

By Ore Factory Guide Team · Updated 2026-10-15
On this page
  1. Quick answer
  2. Prove one manual pallet move first
  3. Test the Dispenser signal and replacement pallet
  4. Use Robot help for an active Contract
  5. v1.0.9: choose the Robot's job before adding capacity
  6. v1.1.0 additions and the historical v1.1.1 hotfix
  7. Keep the three pallet machines separate
  8. Pallet Dispenser placement and signal checklist
  9. Useful Robot fixes from v1.0.6
  10. If the Robot still does not move
  11. Sources

Processing & buffers

Bring / prerequisite
A valid output, Robot and Pallet Drop Zone
Check this UI first
Output face, then Mark for Robot and the route
Move on when
Placement, signal, route and destination can be checked separately.

Palletizer, Pallet Dispenser and Pallet Packer are different; the full-automation achievement is not the minimum manual test.

Quick answer

Place the Pallet Dispenser directly in front of a machine or belt output. That is the developer's placement rule, and the Dispenser automatically signals a Warehouse Robot. If placement stays red, clear the output face and test another valid machine or belt output before moving the rest of the warehouse. Then prove one manual move with a Pallet Drop Zone and Mark for Robot so you can separate placement, signal, route, and destination problems.

The in-game Warehouse Robot tutorial says a Pallet Drop Zone is required and explains Mark for Robot
Gameplay frame from a video uploaded August 9, 2026: the tutorial requires a Pallet Drop Zone, explains manual Mark for Robot, and says a Pallet Dispenser can signal the robot automatically. The video does not show a version number.

Prove one manual pallet move first

  1. Place one Warehouse Robot.
  2. Place one Pallet Drop Zone.
  3. Interact with one pallet and select Mark for Robot.
  4. Read the Robot status and watch that exact pallet reach the Drop Zone.
  5. Only then test a Pallet Dispenser signal, filters, more destinations, or more Robots.
A pallet interaction prompt showing Mark for Robot
Gameplay frame from August 9, 2026 showing the Mark for Robot interaction. It proves the manual trigger exists, not that every pallet type or route is supported.
The Warehouse Robot panel showing Going to Drop Zone
Gameplay frame from August 9, 2026 showing Warehouse Robot status Going to Drop Zone after a pallet was marked. It does not establish a universal travel time or route-clearance rule.

Test the Dispenser signal and replacement pallet

The developer says that, when your configured conditions are met, the Dispenser signals a Robot pickup and supplies a replacement pallet. After the manual test, watch one automatic cycle: condition met, pickup completed, replacement present. A working manual route with no automatic pickup points back to the Dispenser condition or signal. The answer does not establish a general empty-pallet recovery rule, exact fill threshold, or every current UI field.

Use Robot help for an active Contract

The developer also describes packaging and loading the truck when Pallet Drop Zones hold enough matching pallet resources for an active Contract. Check each requested product and quantity, use the appropriate Robot priority below, then observe one handoff. This is not a complete current-UI or vehicle-loading walkthrough. Keep the manual Pallet Packer workflow available until the automated handoff works.

v1.0.9: choose the Robot's job before adding capacity

The official v1.0.9 notes say you can interact with a Warehouse Robot and choose whether it prioritizes:

Treat that as a purpose choice, not as a promise that one priority solves every blocked route. Use the smallest manual move above to prove the path first, then match the priority to the handoff you are testing. The patch also documents several stuck-Robot fixes and an option to cancel the Robot's current pallet-carrying task. If a current task remains stuck, cancel it, return to one pallet and one Drop Zone, and record what the status shows before rebuilding the whole line.

v1.1.0 additions and the historical v1.1.1 hotfix

Masters of Oil lists a Merge Robot and stackable building boxes among its warehouse additions. The subsequent v1.1.1 hotfix is a historical oil-workflow update, not a statement of today's version. Its notes do not publish a replacement rule for the Warehouse Robot, Pallet Dispenser, Palletizer, or Drop Zone sequence on this page.

Do not assume a new item fixes a red Dispenser preview, a blocked destination, or a stuck pallet task. Keep using the one-pallet test, then decide whether the new item solves a specific visible storage or layout problem. For oil-specific factory planning, use the oil factory layout guide.

Keep the three pallet machines separate

Goal Use this entity What it does not mean
Move one pallet manually Warehouse Robot + Pallet Drop Zone + Mark for Robot A Palletizer is required for this one-pallet test
Signal a move automatically Pallet Dispenser, as named by the documented tutorial Every contract filter or save will work without faults
Build the achievement combination Warehouse Robot + Palletizer + Drop Zone for Full Automation Palletizer and Pallet Packer are the same machine
Pack customer-contract goods Pallet Packer workflow A Pallet Dispenser is the contract-packing machine

Pallet Dispenser placement and signal checklist

Visible symptom Do this first Avoid this mistake
Placement preview stays red Attach the Dispenser in front of a machine or belt. Clear that output face, rotate or reposition the Dispenser, and test one valid output before moving the wider line That it can stand anywhere in a clear floor area, or that every machine side is a valid attachment point
The signal does not produce a Robot move Prove Mark for Robot manually, read the Robot status, confirm a Drop Zone, then match the Storage or Packaging and Delivery priority That a Dispenser signal bypasses filters, routes, priorities, or a blocked destination
A full or partial pallet is not handled as expected Read the current pallet label and machine status, then compare one pallet at a time An exact fill threshold: the collected sources do not define one
The Robot keeps carrying or waiting on one pallet Use the v1.0.9 option to cancel the current pallet task, clear the route, and repeat the one-pallet test That cancellation fixes every save, route, or incompatible pallet

Useful Robot fixes from v1.0.6

Official v1.0.6 scene with a Warehouse Robot, pallet, and elevated belts
Official v1.0.6 image showing a Warehouse Robot, pallet, and elevated belts in the same scene. It is layout context, not proof of an optimal route or Robot count.

If the Robot still does not move

  1. Confirm a Pallet Drop Zone exists and the pallet is actually marked.
  2. Read the Robot status. No task points to the trigger; Going to Drop Zone points to the destination or path.
  3. If the current pallet-carrying task is visibly stuck, use the v1.0.9 cancellation option and retry the one-pallet test.
  4. Check whether the selected priority matches the handoff: Storage, or Packaging and Delivery.
  5. Add a filter only after the manual move succeeds.

If the Robot still fails after the one-pallet test, stop adding machines and Robots. Record the visible status, route, filter, priority, and destination so the remaining problem is specific enough to reproduce.

For belt and filter setup, use the automation and Smart Filter guide. For contract packing, use the Pallet Packer guide.

Sources

The developer answer supports Dispenser attachment, signal, replacement pallets, and active-Contract help described above. The v1.0.9 notes cover Robot priorities, task cancellation, and overlapping pallets. The v1.1.0 announcement names the warehouse additions; v1.1.1 is historical oil-workflow context, not today's version.

The older WaLaSy automatic-pallet walkthrough helps identify placement and handoff symptoms. Use the current developer answer and patch notes for the actual fix.