Runtime Evidence Hub | Screeps 运行证据

2篇包含 Console 验证

0篇包含真实主循环验证

6条公开 accepted Evidence

RUNTIME EVIDENCE HUB

从运行证据反查 API、返回码与文章结论

这里只展示同时通过 Evidence 审核和文章 Markdown 验证状态的 accepted Evidence。Console 与 Live 是运行证据；文档核对、离线推演不会被冒充成真实 Runtime。

验证级别API返回码时间

当前显示 2 / 2 篇已验证内容

Screeps Console2026年9月4日shard3 · W39N524 条运行证据

怎样让 Spawn 创建新的 Creep？认识 spawnCreep()

写给 Screeps 新手的第一只 Creep 创建教程：找到 Spawn，准备 WORK、CARRY、MOVE，检查 spawnCreep() 返回值，并正确理解 Game.creeps 与 spawning 状态。

已接受的 Runtime EvidenceScreeps Console · StructureSpawn.spawnCreep · 返回 -10 · shard3 · W39N52 · Game.time 82745772 · 验证于 2026年9月4日 · Explicit dryRun with an empty body returned ERR_INVALID_ARGS (-10); no spawn intent was submitted.Screeps Console · StructureSpawn.spawnCreep · 返回 -6 · shard3 · W39N53 · Game.time 82174496 · 验证于 2026年8月11日 · 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 · 返回 -3 · shard3 · W39N53 · Game.time 82174435 · 验证于 2026年8月11日 · 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 · 返回 0 · shard3 · W39N53 · Game.time 82173700 · 验证于 2026年8月11日 · 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.

查看文章验证状态 →用搜索继续排查 →

Screeps Console2026年8月11日shard3 · W39N532 条运行证据

怎样让 Creep 自动升级 Controller？

安全创建并控制 Upgrader1，让它在 Source 与 Controller 之间往返，认识 upgradeController()、Memory 状态切换和返回结果。

已接受的 Runtime EvidenceScreeps Console · Creep.upgradeController · 返回 -9 · shard3 · W39N53 · Game.time 82172807 · 验证于 2026年8月11日 · 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 · 返回 0 · shard3 · W39N53 · Game.time 82172766 · 验证于 2026年8月11日 · 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.

查看文章验证状态 →用搜索继续排查 →