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 08 · 7 GUIDES
Operations and Debugging
Return codes, CPU, bucket, event logs, notifications, diagnostics, and safe operations. This page connects the system overview to focused lessons, diagnostics, and operational boundaries.
RELATED TOPICS
Browse focused archives
JavaScript, Debugging, Rooms, CPU
SYSTEM MAP
Operational debugging and recovery loop
Measure and record first, isolate failures next, shed noncritical work under pressure, then restore work gradually after recovery.
- 01Measure
CPU, bucket, state metrics
- 02Observe
Logs, notify, Event Log
- 03Isolate
Room or module error boundaries
- 04Degrade
Reduce noncritical work
- 05Recover
Cooldown, retry, and verify recovery
08
Published guides in this system
Use the labels to distinguish sequential lessons, task-focused guides, debugging workflows, safety pages, and references.
- LessonScreeps First Room Code: A Small Loop You Can Verify14 min read · Beginner
- GuideScreeps CPU Profiling: Measure Code with Game.cpu.getUsed()12 min read · Intermediate
- GuideScreeps Game.notify(): Send Rate-Limited Alerts Safely11 min read · Intermediate
- GuideScreeps Room.getEventLog(): Read Previous-Tick Events11 min read · Intermediate
- DebuggingScreeps RoomVisual: Transparent Fills, Labels, and Paths10 min read · Intermediate
- DebuggingScreeps Room Error Isolation: Keep Other Rooms Running18 min read · Intermediate
- GuideScreeps CPU Bucket Degradation: Protect Critical Tasks and Recover Gradually16 min read · Advanced
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 →