QuasiPITech Contact
Game prototype

Fleet Flow

Prototype · v0.2

An idle game where you manage a warehouse robot swarm — and the puzzle is traffic.

TypeScriptCanvas 2DViteIdle / tycoon
Illustration for Fleet Flow
hall
24 × 16one-way lanes
cargo types
3orders with expiry
upgrades
4incl. smart routing
tests
20incl. a gridlock regression
What it is

Fleet Flow in short

The core loop is designing flow and avoiding jams. The only way to steer the fleet is to paint one-way lanes on a grid; more robots help until they start blocking each other. It grew out of the fleet-software work, and it is a game rather than a simulator.

Status

What works, and what does not

Works today
  • Paint one-way lanes with the mouse; a robot may enter a lane only travelling its direction
  • Three cargo types, with shelves clustered by region
  • An order board with rewards and expiry
  • Build shelves, packing stations and chargers; demolish them
  • Four upgrades, including congestion-avoiding routing
  • A robot that is blocked steps aside after a short wait, so the hall cannot gridlock for ever
Not ready yet
  • Balance is unfinished: once the fleet stabilises there is little pressure.
  • A single hall; no saves and no sound yet.
Under the hood

What had to be got right

01

The lane is the lever

Painting a whole row one direction seals it and splits the floor — and the player undoes it with the erase brush. The puzzle is that every fix has a cost.

02

A bug that became a rule

At five robots two head-on robots in a one-wide corridor blocked each other for ever. The fix — step aside after 1.2 seconds — is now guarded by a regression test.