ARTICLE LIBRARY
Browse 64 published guides by system, difficulty, content type, or topic. Start with What Is Screeps? A Programming Strategy Game or follow the beginner sequence through How to Combine Your First Screeps Room Loop.
10 matching guides
Create one reviewed market order with a one-time Memory request, validate Terminal ownership, calculate the 5% fee and Credit reserve, reject duplicates, snapshot the request, handle ERR_FULL without hard-coding a disputed order limit, and verify the order afterward.
Execute one specified sell order with a one-time request, refresh the current order snapshot, use amount rather than remainingAmount, enforce a price ceiling, Credit and Terminal Energy reserves, estimate transaction cost, disable before deal(), and verify the transaction afterward.
Plan one direct Terminal transfer with a one-time request, validate TERMINAL_MIN_SEND and the 100-character description, separate ordinary-resource and Energy budgets, preserve reserves, disable before send(), and verify outgoing transactions and Store changes afterward.
Validate three owned active Labs, resolve the REACTIONS recipe, check reagent stores, output mineral compatibility, free capacity, range 2, cooldown, and a one-time production request before calling runReaction() and verifying the next tick.
Match a Lab mineral to BOOSTS, count eligible unboosted body parts, calculate LAB_BOOST_MINERAL and LAB_BOOST_ENERGY budgets, enforce range 1, ownership and activity, submit one reviewed boost request, and verify exact body-part changes afterward.
Validate an owned active Factory, resolve the COMMODITIES recipe, check all components and output capacity, respect cooldown, match commodity level to the Factory level and PWR_OPERATE_FACTORY effect, submit one reviewed production request, and verify Store deltas 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.
Use an explicit one-time Memory request, confirmation phrase, owned Controller checks, safeMode, safeModeAvailable, safeModeCooldown and upgradeBlocked preflight, disable before activateSafeMode(), save the return code, and verify later state.
Calculate the TTL and Energy gained per renewal, reject CLAIM Creeps, require explicit Boost removal approval, coordinate Spawn time, move adjacent, stop at a target TTL, and handle every documented result.
Schedule Observer vision, store the accepted request, read the target Room on the next tick, preserve bounded intel, handle return codes, and avoid claiming that current visibility proves the new request completed.
English articles are published only after source review, official API checks where applicable, JavaScript syntax review where code is present, duplicate-intent checks, and a final score of at least 96.
