INPUTS

Route and body assumptions

One-way route tilesRequired delivery per tickCARRY partsMOVE partsOther weighted body partsCARRY capacity BoostLoaded-leg terrainEmpty-leg terrainLoading overhead ticksUnloading overhead ticksReplacement safety buffer

RESULT

Hauling throughput plan

The selected body can cover the target throughput at the calculated Creep count.

Total body parts: 15
Payload per trip: 500
Loaded ticks per tile: 1
Empty ticks per tile: 1
Round-trip cycle ticks: 52
Throughput per Creep: 9.6154
Creeps required: 2
Complete cycles per lifetime: 27
Estimated lifetime delivery: 13,500
Spawn time: 45
Start replacement at TTL: 90
MOVE needed for 1 loaded tile/tick: 5

The planner assumes a full payload on the loaded leg, empty CARRY parts on the return leg, a stable route, and no traffic. It does not model path recalculation, pull chains, damaged MOVE parts, fatigue already present, hostile delays, source downtime, transfer failures, or container capacity.

Read-only Creep probe

const creep = Game.creeps['HAULER_NAME'];
if (creep) {
  console.log({
    name: creep.name,
    room: creep.room.name,
    position: creep.pos,
    ticksToLive: creep.ticksToLive,
    fatigue: creep.fatigue,
    carryParts: creep.getActiveBodyparts(CARRY),
    moveParts: creep.getActiveBodyparts(MOVE),
    usedCapacity: creep.store.getUsedCapacity(),
    freeCapacity: creep.store.getFreeCapacity(),
    replacementLead: 90
  });
}

BOUNDARIES

A route model cannot see traffic

The loaded leg assumes every CARRY part contains resource. Empty CARRY parts do not add return-leg fatigue, while any additional non-MOVE parts remain weighted on both legs.

Path changes, damaged MOVE parts, pull chains, hostile delays, source downtime, blocked transfer targets, and container capacity must still be checked in the live room.

Understand MOVE and fatigue ratios →Verify Container withdrawal logic →Official Creep movement documentation ↗