RUNTIME EVIDENCE HUB

Was this Screeps conclusion actually run?

This hub connects accepted guide claims to Screeps Console or live multi-tick runtime evidence. You can inspect the runtime level, API, return code, environment, verification time, and recorded observation instead of treating documentation review or offline simulation as live proof.

Start from a symptom → · Search APIs and return codes → · Read the verification boundary →

CONSOLE TESTED

2

English guides mapped to source articles with accepted Screeps Console testing.

LIVE MULTI-TICK

0

English guides mapped to source articles with accepted live multi-tick room evidence.

ACCEPTED EVIDENCE

6

Structured runtime records that also pass the guide-level Markdown acceptance boundary.

01

SCREEPS CONSOLE

Screeps spawnCreep(): Create Your First Creep

Use dryRun to validate a WORK-CARRY-MOVE body, submit one safe spawnCreep() request, read its return code, and verify the new Creep across later ticks.

Verified Sep 4, 2026 · shard3 · W39N52 · 4 structured evidence records
Accepted Runtime Evidence

Screeps Console · StructureSpawn.spawnCreep · returned -10 · shard3 · W39N52 · Game.time 82745772 · verified Sep 4, 2026 · Explicit dryRun with an empty body returned ERR_INVALID_ARGS (-10); no spawn intent was submitted.

Screeps Console · StructureSpawn.spawnCreep · returned -6 · shard3 · W39N53 · Game.time 82174496 · verified Aug 11, 2026 · Real Screeps Console observation: with Spawn1 idle in W39N53, room energyAvailable and energyCapacityAvailable were both 2300. A dryRun StructureSpawn.spawnCreep request used 24 WORK parts costing 2400 Energy and returned ERR_NOT_ENOUGH_ENERGY (-6). This proves the insufficient-Energy dry-run return path only; it did not start a spawn.

Screeps Console · StructureSpawn.spawnCreep · returned -3 · shard3 · W39N53 · Game.time 82174435 · verified Aug 11, 2026 · Real Screeps Console observation: Spawn1 called StructureSpawn.spawnCreep with [WORK,CARRY,MOVE], the already-used name ev_spawn_82173700, and dryRun:true. The call returned ERR_NAME_EXISTS (-3). This record proves the duplicate-name dry-run return path only; it did not create a new Creep.

Screeps Console · StructureSpawn.spawnCreep · returned 0 · shard3 · W39N53 · Game.time 82173700 · verified Aug 11, 2026 · Real Screeps Console sequence on shard3/W39N53: a dryRun for [WORK,CARRY,MOVE] returned OK (0) at Game.time 82173657; a real StructureSpawn.spawnCreep request for unique name ev_spawn_82173700 returned OK (0) at 82173700 with 2300 room Energy available; later observations at 82173719 and 82173746 confirmed that exact Creep existed in W39N53 with body [WORK,CARRY,MOVE] and spawning=false. The intermediate Spawn.spawning window was not directly observed, so this evidence does not claim that state was captured.

Open guide verification status → · Continue troubleshooting →

02

SCREEPS CONSOLE

Screeps upgradeController(): Build Your First Upgrader Loop

Build one Upgrader1 loop that harvests from an active Source, moves within Controller range 3, spends Energy with upgradeController(), and switches state across ticks.

Verified Aug 11, 2026 · shard3 · W39N53 · 2 structured evidence records
Accepted Runtime Evidence

Screeps Console · Creep.upgradeController · returned -9 · shard3 · W39N53 · Game.time 82172807 · verified Aug 11, 2026 · Real Screeps Console observation using fresh Game lookups in the same expression: har_W39N53_2609 had 5 active WORK, 50 Energy, and range 15 to the room Controller. Creep.upgradeController returned ERR_NOT_IN_RANGE (-9); immediately observed Energy remained 50 and Controller progress remained 627315.

Screeps Console · Creep.upgradeController · returned 0 · shard3 · W39N53 · Game.time 82172766 · verified Aug 11, 2026 · Real Screeps Console observation using fresh Game lookups within one expression: upg_W39N53_1503 was range 3 from the Controller with 95 Energy and 5 active WORK parts; Creep.upgradeController returned OK (0). This record proves the successful return path under those observed preconditions only; it does not claim that later Controller progress growth was caused solely by this Console invocation.

Open guide verification status → · Continue troubleshooting →