Screeps: Arena

// About this game

Screeps: Arena is best understood as bot arena built around code as the main verb, not as a normal game with a small programming minigame attached. Arena keeps the Screeps idea — units controlled entirely by your JavaScript — but trades the 24/7 world for bounded, asynchronous PvP matches. You write the strategy once and watch it execute against another player's code, then iterate. It is a friendlier on-ramp than Screeps: World, with the same satisfying "my code did that" payoff. The useful question for a new player is not simply "is it about programming?", but what kind of thinking it asks for: JavaScript and TypeScript, pvp, bot arena and open-source, and a willingness to test an idea by letting the simulation run. Released in 2022 by Screeps, it sits in the catalog because the program you write is the thing that actually changes the game state.

The core play is adversarial automation. You submit logic, watch it collide with someone else’s logic, study the replay, then decide whether the weakness was sensing, positioning, targeting, risk management or plain overfitting. Good arena games make every loss useful because the opponent exposes assumptions your tests did not cover. In Screeps: Arena, that means the fun is in the gap between an intention and a working implementation. You start with a rough plan, translate it into the tools the game provides, then watch the result expose every missing condition. A direct solution may pass the first level or match, but the better solutions usually come from noticing a pattern: repeated movement, wasted work, poor targeting, bad routing, a race condition, a blocked path, or a decision that should have been stored as state instead of hard-coded.

The language side is centered on JavaScript and TypeScript, but the transferable skill is broader than syntax. You practice decomposition, debugging, iteration and the habit of reading the rules before blaming the machine. The advanced rating matters because the game rewards players who can structure larger solutions, reason about edge cases and tolerate several failed iterations before the system behaves. Because it is online, the game also has a social or persistent edge: your code has to survive contact with leaderboards, shared state, other players or changing live conditions instead of only beating a frozen puzzle once. The best sessions are usually not the ones where everything works immediately; they are the ones where a failed run gives you a clear hypothesis for the next version. If the game has leaderboards, ratings or community solutions, those become useful mirrors rather than just bragging rights, because they show how many different shapes a correct program can take.

Screeps: Arena is strongest for players who like the feeling of making a system slightly smarter each time they touch it. It will be less satisfying if you want fast reflex challenges, cinematic spectacle or a puzzle with only one intended answer. The reward is more specific: seeing your own instructions harvest, fight, route, query, build, solve or survive without your hand on the controls. As a paid game, it needs to justify its place by offering enough authored puzzles, polish or replayable optimization depth to make the programming loop worth returning to. Taken on its own terms, it is a practical way to turn programming concepts into a visible loop, where every bug is part of the play and every improvement has a concrete effect on the world in front of you.

// What you’ll write

Arena uses ES modules and a match-scoped loop. The official API exposes prototypes such as StructureSpawn and utility lookups for finding your objects.

import { getObjectsByPrototype } from 'game/utils';
import { StructureSpawn } from 'game/prototypes';

export function loop() {
  const spawn = getObjectsByPrototype(StructureSpawn).find(s => s.my);
  if (spawn) spawn.spawnCreep([WORK, CARRY, MOVE]);
}

Screeps Arena API docs ↗