Space Alert

Readiness

draft-ready (confidence=0.74, rules=0.65, fun=0.90). BGG rank: 377; year: 2008; weight: 2.97; playtime: 30 min

Core Loop

Space Alert is a cooperative real-time game played against a CD/app soundtrack that narrates a 10-minute spaceship mission. During the real-time phase, players simultaneously program their actions by playing numbered cards into a personal queue of up to 5 action slots (representing turns 1–12, with some slots blank). Actions include: move (between sections A/B/C or upper/lower deck), shoot (fire weapons in your current section), charge (power reactors/shields), and special actions. Players shout, coordinate, and panic while the soundtrack announces incoming threats (internal and external). No one may look at other players' queues during real-time.

After the real-time phase ends, the group resolves all 12 turns sequentially using the programmed queues. Threats (enemy ships, asteroids, internal saboteurs) advance on a track each turn and deal hull damage if not intercepted. Weapons fire only if someone is in the correct section AND the reactor has enough charge AND the action was programmed. Most losses come from under-powered weapons, players in the wrong section, or conflicting plans.

Turn Structure and State

• No manual/BGA/transcript source is present; card relies on memory plus BGG context.
• BGG description anchor: Space Alert is a cooperative team survival game. Players become crew members of a small spaceship scanning dangerous sectors of the galaxy. The missions last just 10 real-time minutes (hyperspace jump, sector scan, hyperspace jump back) and the only task the players have is to protect their ship. During play, the central computer will announce the presence of various threats on one of the supplied 10 minute [...]

Win Condition and Arc

The crew wins if the ship survives all 12 turns with at least 1 hull point remaining. Threats that reach the ship deal hull damage; internal threats disable ship systems. The arc is chaotic learning: first plays are usually catastrophic losses that teach the communication meta; experienced groups develop terse call-and-response patterns.

Decision Primitives

BGG mechanisms: Action Queue, Area Movement, Cooperative Game, Elapsed Real Time Ending, Hand Management, Programmed Movement, Real-Time, Simultaneous Action Selection, Solo / Solitaire Game

Memory-derived primitives:

• Real-time simultaneous card programming (under time pressure)
• Deferred resolution (actions resolve post-real-time, in sequence)
• Cooperative resource management (shared reactor power, shields)
• Threat track (enemies advance and damage if not destroyed)
• Communication under constraint (shouting, no queue-peeking)

v4 controlled primitives: time_pressure_realtime, forced_table_talk, simultaneous_action_selection, cascading_failure, communication_constraint

Top iOS archetype fits: coop 5.8, balatro 4.5, wordle 3.3.

Why It Is Fun

The deferred-resolution twist means all mistakes are visible in painful detail during the resolution phase — you watch your well-intentioned plan collapse because two players both programmed "charge" when one should have moved to fire. The postmortem is as fun as the game.

Player-voice evidence:

• Brilliant game design. In my book this is one of the best truly cooperative game out there.
• Top real time game. Needs repeated plays with the same group to be fully appreciated.
• This fixes the co-op problem of backseating by making it too hard to do! The strict time limit is amazing
• Can be stressful, needs the right group. Difficulty really ramps up, so it gives you a real sense of accomplishment when you succeed. Unfortunately, there is often one clear scapegoat when you fail, not sure that's great.
• My wife and I both LOVED this game, but it doesnt play well at 2 and we didnt have a regular group at the time so had to run through the intro games every single time we played and we got over doing that ($70.14 Games Empire)

Friction and Failure Modes

• Treat Sonnet-memory edge rules as draft until confirmed by manual, BGA, or transcript.
• Needs at least one stronger rules authority before final extraction use.

Translation and Design Hooks

• Use this card to ask: which primitive carries the fun if theme/licensing is removed?
• For iOS, look for short-session compression, clear state visualization, and a digital-only twist.
• For new tabletop design, look for the tension source and decide whether to preserve or invert it.

Edge Rules and Gotchas

• Double actions: certain cards let a player take two actions in one slot, but these are rare and must be played during real-time with full knowledge of what comes next
• Androids (player role variant): some players play as robots with different hand constraints — fewer cards but different action types
• Serious vs. training missions: the soundtrack has multiple difficulty levels; training missions omit some threat types
• Internal threats (e.g., "Pulse cannon malfunction") occupy ship sections and must be fought by crew members using melee/special actions, not weapons
• If two players try to move to the same elevator at the same time they may block — this is resolved strictly by turn order in the resolution phase
• The "5-seat" layout: sections A, B, C share one row of consoles; upper/lower deck has second row. Players must be in the correct section AND deck to use specific weapon

Sources Used

[
  {
    "kind": "bgg_comments",
    "path": "data/bgg_comments/38453.txt",
    "quality": 0.75,
    "note": "positive/player-voice sample"
  },
  {
    "kind": "llm_memory",
    "path": "data/llm_memory_sonnet/38453.md",
    "quality": 0.65,
    "note": "sonnet-self-rated-8"
  },
  {
    "kind": "github_code",
    "path": "data/code_implementations/38453.md",
    "quality": 0.6,
    "note": "GitHub implementation signal"
  },
  {
    "kind": "wikipedia",
    "path": "data/wikipedia/38453.md",
    "quality": 0.55,
    "note": "board-game-suffix"
  }
]