Project P.I.T.T. makes the quota grow every time you meet it

You are a new intern at a company with one instruction: craft rubber ducks and feed them to the pit. At the centre of the facility sits the Maw, a vast corporate hole with an appetite that only grows the more you feed it. Make ducks, throw them in, earn your place. The company is watching.

The interesting part is that none of that is abstracted. This is first person and everything is an object you handle. You are not selecting a duck from a production menu and watching a counter tick — you are making a thing, carrying it, and getting rid of it over an edge. The tools you unlock are forces rather than commands: magnets, fans, panels, pistons, launchers. Building a production line here means arranging things that pull, push and blow, letting go, and finding out what the simulation does with your idea.

Then the demands escalate. Ducks stop being enough. New products get stranger, automation arrives, and simple production turns into assembly — objects start connecting in ways that were not part of the plan. You chain combos and improve throughput for higher payouts, so the game is scoring your rate, not your total. Each phase, the Maw expands and the facility shifts around it, and your responsibilities get harder to explain to anyone outside the building.

What makes this version unusual is that it refuses to let you leave the floor. Most factory games are about earning your way out of manual labour: you build the belt, you step back, you watch the graph. Project P.I.T.T. keeps your hands in the machine while the machine gets bigger, and it does it inside a brutalist PSX facility that never answers the obvious questions. Where are you. Who is your employer. Why is any of this a job.

How Games Use Feedback Loops is the essay this game is built out of. It argues that positive loops snowball a lead until something corrects them, and negative loops pull the leader back so the ending is still in doubt. The Maw is a positive loop given a body: feeding it makes it bigger, and bigger means it needs more feeding. The design question is what plays the corrective role. In most escalation games it is a difficulty curve you cannot see. Here it is your own contraption falling apart under a throughput it was never built for, which is a much more honest brake because you can look straight at the part that failed.

The Rise of the Systemic Game covers why a fan and a magnet in the same room are worth more than either one scripted. Systemic design gets its power from objects and rules that act on each other, producing plans and accidents nobody authored. A launcher does not know it is aimed at a piston. That is the whole promise of a physics production line: the good runs and the disasters come from the same property, and a developer who tunes the accidents out has thrown away the reason to build the game this way.

Morality in the Mechanics is why the satire could land instead of just being a coat of paint. It makes the case that karma meters flatten ethics, and the sharpest moral design hides inside the money and survival systems the player is already operating. A corporate satire that criticised the company in dialogue would be a lecture. One where the critique is the payout formula — where you are personally optimising a pipeline to feed something that will never be full — puts the player in the position the joke is about.

Project P.I.T.T. is made by Froke and published by Pretty Soon. It is out now on Windows, Mac and Linux, filed under Action, Casual, Indie and Simulation — a genre spread that reads as indecision on a store page and is usually a good sign in a sandbox, because it means the thing does not sit cleanly in one shelf.

The pitch is deliberately small and it does not oversell: craft, throw, unlock, automate, repeat at a worse scale. Everything the game has to prove is in the middle hours, when the ducks stop mattering and the contraptions have to carry it.

If a job with an unreasonable quota is the appeal, Librarian is the other side of the same idea. Librarian names a number — 3,072 books — and locks the door until every one is shelved, so the work is finite and the ending is a fact. Project P.I.T.T. never names a number at all. Same menial labour, same physical handling of objects, opposite promise about whether finishing is a thing that exists.