Spawn is not working
Check whether the Spawn is busy, then use the real spawnCreep(..., { dryRun: true }) return code to choose the branch.
Check 1
DETERMINISTIC PROBLEM SOLVING
Work from the observed state to the next check
Choose the behavior you can see and answer a small set of verifiable questions. The resolver does not execute your code or infer hidden state; it follows deterministic branches and hands the result back to the existing API, guide, tool, Tick Lab, and accepted Runtime Evidence paths.
Boundary
This deterministic V1 does not use AI inference or execute arbitrary JavaScript, and it does not write to Runtime Evidence or your Screeps game state. To improve the flow, the site records a limited set of anonymous structured Resolver events on a best-effort basis; these records do not accept free text, IP addresses, Referer, User-Agent, or geolocation. When state is unknown, the flow asks you to capture the real return value first.
Knowledge Graph V1 is connected
The resolver now consumes the same read-only graph semantics: 228 nodes, 207 relations, and 0 unmapped items. Open Knowledge Coverage →
READ-ONLY SNAPSHOT
Screeps Doctor V2
Choose a supported symptom and paste a strict V1 Snapshot. Doctor parses structured facts locally in the browser and reuses canonical Resolver / Diagnostics / API IDs for deterministic diagnosis. It does not execute Screeps actions, write Memory, or upload the Snapshot.
Maximum 4096 characters; unknown fields are rejected.
PROBLEM RESOLVER V1
Turn symptoms into the next concrete check
The resolver owns only deterministic questions and branch logic. After an outcome is fixed, read-only Knowledge Graph relations can project related API, guide, and tool paths while their canonical ownership stays with the existing registries.