Screeps Lab boostCreep(): Requirements, Usage, and Return Codes
Learn StructureLab.boostCreep() requirements, bodyPartsCount usage, return codes, current-tick scheduling, and how to verify exact boosted body parts afterward.
TOPIC · 17 GUIDES
Focused English articles connected to resources, organized with the same filters used by the main article library.
Learn StructureLab.boostCreep() requirements, bodyPartsCount usage, return codes, current-tick scheduling, and how to verify exact boosted body parts afterward.
Recover an owned active Power Spawn, calculate base and PWR_OPERATE_POWER processing amounts, require Power and POWER_SPAWN_ENERGY_RATIO Energy, preserve a configurable room reserve, store GPL and resource snapshots, handle return codes, and verify later deltas.
Freeze one transfer revision, reserve the exact Terminal against send and market-deal conflicts, submit once, normalize ledger descriptions, and verify the actual full or partial outgoing transaction next tick.
Change, extend, or cancel one owned Screeps market order with nullable room fingerprints, conservative fee budgeting, one-writer request IDs, raw return codes, and next-tick state verification.
Treat ticksToDecay as the next decay pulse, reject unsafe path deadlines, preserve repair() results, explain the current-engine repair-before-decay boundary, and verify EVENT_REPAIR amount and Energy spent on the next tick.
Recover Tombstone and Ruin resources without chasing doomed targets: reject incomplete structure-aware paths, block closed hostile Ramparts, preserve target identity, and verify the processed withdraw amount on the next tick.
Distinguish general, limited, and read-only Stores; interpret resource arguments, zero and null correctly; handle Lab and specialized capacities; and calculate safe withdraw and transfer amounts.
Freeze one reviewed order revision, reserve the creation fee and account mutation slot, call createOrder once, and verify the exact new order ID in the next account snapshot.
Freeze one reviewed deal revision, reserve both an account deal slot and the exact Terminal, submit once, and verify the new transaction ID and actual partial or full amount next tick.
Bind confirmation to the exact Nuker and target, record only an accepted launch, verify the launcher's zeroed resources and cooldown, and match the exact Nuke object when target vision exists.
Plan multiple same-room Link sends with shared target-capacity reservations, submit each source once, and verify exact source and target IDs in the next tick's transfer events.
Validate the same-tile Extractor and Miner, record only accepted harvest calls, match the exact EVENT_HARVEST on the next tick, and separate event identity from Store overflow and depletion.