Project P.I.T.T. Progression by Product
Progression by Product: Use the product and visible current objective to identify the relevant phase reference.
Use the product and visible current objective to identify the relevant phase reference. The phase numbering comes from older player evidence; the original Upgrade Progression guide retains ownership of what-unlocks-next advice.
Duck and Cash Register
Start from the current product rather than a guessed quota. The product profile and phase reference distinguish production, transport and transition questions.
Sources:
Piñata and Anomaly
Later product handling can fail before progression is the issue. Separate intact transport, recipe composition and a visible terminal requirement.
Sources:
Do not replace the visible objective with an assumption
If an upgrade is missing, record its terminal state. A source-limited registry and an older walkthrough are not complete current prerequisites.
Sources:
Evidence and verification limits
The fuller answer is maintained at /upgrade-progression. This reference does not create a second authoritative mechanic.
Evidence for this section (2)
SINGLE COMMUNITY REPORT · checked 2026-09-26
An older first-hand guide describes the sequence Duck, Cash Register, Piñata, Anomaly and illustrates their production lines.
Build relevance: Older full-release community observation; no independent 1.0.8 replay
Limit: No universal unlock quantities, optimal layouts or throughput are adopted.
Steam Community — achievement and strategy guide (older-build gameplay; not a 1.0.8 replay) ↗
OFFICIAL CURRENT · checked 2026-09-26
The official store describes making ducks, feeding the Maw and developing physics-based production lines.
Build relevance: Live Steam store checked September 26
Sources: Steam Community — achievement and strategy guide (older-build gameplay; not a 1.0.8 replay) ↗ · Official Steam store page ↗
Primary source: Steam Community — achievement and strategy guide (older-build gameplay; not a 1.0.8 replay) ↗. Scope: full game.
A source-check date is not an in-game test date. Historical fixes and community observations retain their stated scope.