- Space King Board Game scenarios are not yet documented through a public official scenario list.
- Confirmed theme: Public discussion centers on battling aliens with official Space King miniatures.
- Best preparation: Track objectives, setup details, and victory conditions as official material appears.
- Avoid assumptions: Do not treat fan descriptions as confirmed rules, maps, or mission data.
- Scenario priority: Evaluate replay value through objectives, terrain, enemy pressure, and decision variety.
Space King Board Game scenarios: What Is Confirmed
The available public material does not provide a complete scenario catalog, rulebook, map list, or official mission structure. The strongest usable signal is thematic: the project is presented around Space King miniatures, alien combat, and a campaign-style setting. A public Space King board game discussion on Facebook expresses enthusiasm for playing missions focused on eliminating aliens, but it does not establish official objectives or rules.
That distinction matters when preparing a fan wiki article. A scenario page should separate confirmed information from interpretation, speculation, and community-created content. Until official scenario documents are published, the safest approach is to organize the topic as a planning guide rather than claim that specific missions, rewards, factions, or board layouts already exist.
Publicly supported elements:
- The project is associated with the Space King board game.
- Official Space King miniatures are part of the announced project direction.
- Alien combat is central to the public-facing theme.
- Campaign-style mission language is associated with the setting.
- A complete public scenario index is not available in the supplied material.
| Scenario Detail | Public Status | Wiki Treatment |
|---|---|---|
| Alien combat theme | Supported by public discussion | Present as thematic context |
| Official miniature range | Mentioned in campaign promotion | Present as project information |
| Mission catalog | Not publicly documented | Mark as unconfirmed |
| Victory conditions | Not publicly documented | Do not assign rules |
| Map layouts | Not publicly documented | Avoid invented locations |
| Campaign rewards | Not publicly documented | Await official publication |
Do not label a fan-made mission as official. Use clear tags such as “Community Scenario,” “Speculative Format,” or “Awaiting Official Details.”
A reliable scenario database can still be prepared before launch. Create fields for the mission name, source, publication date, player count, setup, objective, failure condition, special rules, and linked miniatures. Leave unknown fields blank instead of filling them with expected tabletop conventions.
How to Read a Scenario Brief
A useful scenario brief should tell players what they are trying to accomplish and what changes the normal game state. The exact terminology may differ when the official rules arrive, but most mission documents can be reviewed through the same information categories.
Use the following structure when adding a new scenario page:
| Scenario Field | What to Record | Why It Matters |
|---|---|---|
| Mission identity | Official title and source | Prevents duplicate or unofficial naming |
| Setup | Board, units, terrain, and tokens | Defines the starting state |
| Primary objective | The main task players must complete | Explains how success is measured |
| Failure condition | Trigger that ends or worsens the mission | Clarifies pressure and risk |
| Special rules | Scenario-specific effects | Separates mission rules from core rules |
| End state | Win, loss, or alternate conclusion | Supports accurate results tracking |
Objective types to watch for
A scenario can feel different without requiring a completely different ruleset. When official briefs become available, classify objectives by the decisions they create rather than by dramatic wording alone.
- Elimination: Remove a designated enemy force or target.
- Extraction: Reach a location and leave with a unit, item, or civilian group.
- Defense: Protect a point, structure, convoy, or resource for a stated duration.
- Sabotage: Interact with objectives before an opposing force reaches them.
- Breakthrough: Move units across the board while managing enemy pressure.
- Investigation: Search locations or complete sequential discoveries.
Combat Scenario
Focuses on enemy pressure and target selection. Record whether enemies arrive in waves, begin on the board, or guard a fixed location.
Positioning Scenario
Emphasizes movement, zones, routes, and board control. Note any restricted areas or required destinations.
Timed Scenario
Adds urgency through rounds, escalating threats, or limited actions. Record the exact trigger rather than assuming a standard timer.
A strong wiki entry should explain how each objective affects play without promising an experience the official rules do not support. For example, “requires players to protect a location” is safer than claiming that the location generates resources every round unless a published rule confirms it.
When a scenario uses unfamiliar terminology, quote the official wording first, then add a short plain-English explanation beneath it.
Scenario Setup Workflow
Use this workflow whenever a confirmed scenario document, preview, or rulebook excerpt becomes available. It keeps the article useful while preventing unsupported additions.
Capture the Source
Save the official title, publication date, URL, and document version. If the scenario appears in a campaign update, link the update directly and record the date as 2026 when applicable.
Separate Setup from Rules
List every starting component separately: board elements, miniatures, tokens, cards, player roles, and deployment instructions. Do not merge an inference into the official setup list.
Identify the Objective
Copy the primary objective in concise language. Then record secondary objectives, optional tasks, and any conditions that change the result.
Record Pressure Points
Note enemy arrivals, round limits, restricted movement, escalating effects, or resource limits only when the source states them.
Test the Article Structure
Check that a new player can find setup, objective, turn pressure, completion conditions, and source links without reading speculation.
| Setup Check | Required Entry | Common Editorial Error |
|---|---|---|
| Starting position | Deployment zones or placement instructions | Assuming symmetrical deployment |
| Required pieces | Named units, miniatures, cards, or tokens | Listing unconfirmed expansions |
| Objective location | Exact space, zone, or target if stated | Inventing map coordinates |
| Scenario timer | Rounds or event trigger if published | Assuming a fixed round count |
| Completion | Official success condition | Replacing it with “defeat all enemies” |
| Failure | Official loss or escalation condition | Treating optional setbacks as defeat |
For a future scenario page, present the setup in the same order that players use it at the table. Start with the board, then place markers, deploy forces, explain special rules, and finally state the opening objective. This order reduces ambiguity and makes later corrections easier.
A scenario entry is ready for publication when readers can identify what to place, what to do, and how to finish without relying on hidden assumptions.
Replay Value and Scenario Comparison
Scenario comparison should focus on documented structure, not unsupported power rankings. Since the public material does not publish a confirmed mission list, use a neutral comparison framework once official scenarios are available.
Evaluate each mission across five practical categories:
- Objective variety: Does the task differ from simple elimination?
- Decision pressure: Does the scenario force meaningful choices?
- Board impact: Does terrain or positioning change the plan?
- Threat development: Do enemy actions or events alter the situation?
- Replay potential: Can different setups or outcomes create new decisions?
| Evaluation Axis | Low Variety | Moderate Variety | High Variety |
|---|---|---|---|
| Objective | Single target with one clear route | Primary and secondary tasks | Multiple objectives with changing priorities |
| Threat | Static enemy placement | Limited escalation | Threats alter routes or timing |
| Board use | Few meaningful zones | Several useful positions | Terrain strongly affects choices |
| Outcome | One straightforward result | Alternate success levels | Branching or state-based conclusion |
| Replay value | Similar opening each time | Some tactical variation | Different approaches remain viable |
Objective Depth
Check whether the mission asks for more than defeating enemies. Secondary tasks can create useful tension when officially supported.
Map Interaction
Record whether locations, routes, cover, obstacles, or zones affect the scenario. Never infer these features from artwork alone.
Threat Escalation
Track published events, reinforcements, or environmental changes. Distinguish fixed triggers from optional rules.
Outcome Clarity
Explain success, failure, and alternate outcomes in separate bullets so players can resolve the mission consistently.
Avoid assigning an “S-tier” label to scenarios unless a future official or community review project defines a transparent rating system. A wiki should document what a scenario does, not decide which mission every player must prefer.
Use descriptive labels such as “objective-focused,” “combat-heavy,” or “high-pressure” only when the scenario text supports them.
Scenario Preparation Checklist
Before playing or publishing a scenario, verify every item below. This checklist works for official missions, preview content, and clearly labeled community designs.
Scenario Readiness:
- Confirm the scenario title and source link
- List every required miniature, card, token, and terrain element
- Write the primary and secondary objectives separately
- Record official success, failure, and timing conditions
- Label all interpretation or fan-created material clearly
Player-facing preparation
Players should read the objective before arranging pieces, but they do not need to memorize every special rule. Keep the table reference short and place detailed exceptions below the main setup.
| Preparation Stage | Player Action | Wiki Presentation |
|---|---|---|
| Before setup | Gather required components | Component list |
| During setup | Place board elements and forces | Numbered instructions |
| Before the first turn | Read objectives and failure rules | Objective callout |
| During play | Check triggers as they occur | Special-rules table |
| At resolution | Apply the stated outcome | Results section |
If a scenario includes campaign continuity, record the state that carries forward. Examples might include surviving units, damaged locations, unlocked routes, or narrative consequences, but only list these when the official scenario text confirms them.
Community scenario labeling
Community missions can add value to a fan wiki, especially when the official catalog is still developing. They should use a separate namespace or category and include:
- Creator name or handle.
- Original publication date.
- Required materials.
- Intended player count, if provided.
- Playtest status.
- Clear statement that the scenario is unofficial.
A community scenario should not be presented as balanced, tested, or endorsed unless its creator explicitly provides that information.
The same standard applies to screenshots, campaign jokes, social posts, and promotional language. They can establish tone or audience interest, but they do not automatically establish mechanics.
FAQ and Source Notes
Q: Are official Space King Board Game scenarios publicly listed?
No complete official scenario catalog, rulebook, map list, or victory-condition reference is established by the supplied public material. Treat future announcements as the authority.
Q: What type of missions should players expect?
The public theme points toward alien-combat missions involving Space King miniatures, but specific objectives and mission formats should not be treated as confirmed until officially published.
Q: Can fan-made scenarios be added to the wiki?
Yes. Place them in a clearly labeled community section with creator credit, source information, required components, and an explicit unofficial status.
Q: How should a new scenario page be organized?
Use a consistent order: source, scenario summary, required components, setup, objectives, special rules, success and failure conditions, replay notes, and update history.
The most dependable editorial approach is to maintain two separate records:
- Confirmed scenario data: Directly supported by official campaign material, rulebooks, or developer announcements.
- Community interpretation: Reviews, expectations, fan missions, and thematic analysis that are useful but not canonical.
As new information arrives in 2026, update the source date, preserve previous wording in the revision history, and identify which fields changed. This makes the scenario index easier to audit and prevents early speculation from becoming mistaken for established game data.
| Source Type | Suitable Use | Reliability Label |
|---|---|---|
| Official rulebook | Rules, setup, objectives, outcomes | Official |
| Official campaign update | Project announcements and previews | Official announcement |
| Creator interview | Quoted design intent | Developer statement |
| Community review | Player reaction and expectations | Community opinion |
| Fan scenario | Unofficial playable content | Community scenario |
| Promotional joke or slogan | Tone and setting flavor | Promotional context |
Add an “Updated” line to every scenario page and revise only the fields supported by the newest source.
For now, the strongest scenario guide is one that remains useful without inventing a mission roster. Track the alien-combat theme, organize future rules into consistent fields, and keep official and community material visibly separate.