CURRENT-PATCH FILE // v1.0.5Official · observed · community
Phase 1 production

Rubber Duck automation that clears itself

A reliable early line is deliberately simple: visible source, short direction, staged airflow, local containment, wide catch, Maw.

v1.0.5

Quick answer

Prove the base source before upgrading it. Community observations report one Duck every five seconds (12/min) at base and one every two seconds (30/min) after the speed upgrade. Treat those as observed rates, not guaranteed constants for every patch.

Baseline layout

Automated Duck Workbench → short straight lane → staged Fans → local side walls → wide catcher → Maw. Give every Fan one job: clear the source, carry through one real dead zone, or correct the final approach. Do not ask one Fan to launch across the whole room.

Upgrade after a clearance test

  1. Run the current rate for at least 20 products.
  2. Mark the first place where the pile grows.
  3. Remove physical obstructions before buying force.
  4. Add a roof only where Ducks visibly escape upward.
  5. Increase source speed only when entrance and catcher both clear themselves.
Loose Rubber Ducks around an automated Duck machine
Observed cleanup state: loose Ducks hide the real transport path. Source: TimeToGrind, I Built an Automated Duck Machine, around 2:19:19.

Stop spending when

  • the source does not develop a growing pile;
  • the same section no longer throws Ducks out;
  • the catcher handles the current rate;
  • the line runs while you work elsewhere.

Then move money to Cash Registers. Add Bumpers for combo experiments only after the direct route is stable; use the Magnet for recovery rather than as the main conveyor.

Sources and evidence

The observed rate also appears in the community Duck automation guide and the attributed video. Rates remain community observations.

Evidence policy