START HERE
Read the system in a useful order
Begin with lessons or foundational guides, then move to debugging, safety, and advanced operations. Each article states the evidence level it actually reached.
Open the first guide →SYSTEM 02 · 13 GUIDES
Spawn and Creep Lifecycle
Body design, spawn return codes, role memory, renewal, recycling, and emergency recovery. This page connects the system overview to focused lessons, diagnostics, and operational boundaries.
RELATED TOPICS
Browse focused archives
Creeps, Movement, Debugging, Spawn, JavaScript, Energy
SYSTEM MAP
Spawn and Creep lifecycle
Treat the need for a Creep as a lifecycle of body design, Energy, spawning, work, replacement, and retirement rather than one spawnCreep() call.
- 01Demand
A role gap or replacement condition
- 02Body + Energy
Size the body against available capacity
- 03spawnCreep()
Store dryRun and real results
- 04Work + TTL
Track work and lifetime
- 05Replace / recycle
Avoid downtime and wasted capacity
KNOWLEDGE CLUSTER · DEMONSTRATOR
Spawn & Creep Lifecycle: one problem space, five ways to work with it
Body design, spawning, Energy constraints, queues, replacement, renewal, recycling, and recovery. The learning module remains the primary article owner. This layer only connects that same durable cluster to graph-derived tools, diagnostics, experiments, APIs, and return codes.
01
LEARN
Learn this system in order
9 primary guides are organized into 3 learning stages. Start from the first guide before jumping into isolated errors.
02
BUILD
Turn constraints into a plan
Use the graph-related tools to turn capacity, timing, and resource constraints into an executable plan before they become runtime failures.
03
SOLVE
Diagnose the failure path
Start from the canonical diagnostic symptoms for this cluster, then move into the deterministic Resolver when a guided branch-by-branch check is useful.
04
VERIFY
Verify the runtime model
Use the related Tick Lab experiment to inspect modeled return values and tick boundaries, while keeping modeled results separate from accepted Runtime Evidence.
05
EXPLORE
Explore APIs and return codes
The current explicit graph surface connects this cluster to 3 APIs and 11 return-code nodes.
Graph-related surface: 3 API · 1 symptom · 2 tools · 1 Tick Lab · 11 ReturnCode
02
Published guides in this system
Use the labels to distinguish sequential lessons, task-focused guides, debugging workflows, safety pages, and references.
- LessonScreeps Creep Body Parts: WORK, CARRY, and MOVE8 min read · Beginner
- LessonScreeps spawnCreep(): Create Your First Creep8 min read · Beginner
- LessonScreeps Creep Roles: Harvester, Upgrader, and Builder8 min read · Beginner
- DebuggingScreeps spawnCreep() Errors: Diagnose Every Return Code12 min read · Intermediate
- GuideScreeps Dynamic Creep Body: Minimum, Target, and Emergency Plans13 min read · Intermediate
- GuideScreeps Emergency Harvester Recovery: Track the Exact Spawn Request17 min read · Intermediate
- GuideScreeps renewCreep(): Requirements, Cost, and Return Codes22 min read · Advanced
- GuideScreeps recycleCreep(): Verify the Exact Creep Retirement23 min read · Intermediate
- GuideWhy room.energyAvailable Stays Below Capacity in Screeps19 min read · Intermediate
- GuideScreeps Prespawn Replacement: Start the Next Creep Before the Current One Dies17 min read · Intermediate
- DebuggingScreeps Spawn Exit Blocked: Diagnose Directions and Occupied Tiles17 min read · Intermediate
- GuideScreeps Multi-Spawn Queue: Priority, Deduplication, and Shared Energy20 min read · Intermediate
- DebuggingScreeps Arena spawnCreep(): Find Your Spawn8 min read · Intermediate
Need a guide that is not listed?
Search by API method, error code, or symptom first. Zero-result English searches are recorded anonymously and can be submitted as a public content request.
Search the English section →