Game Fantasy — Omega War
Stage 1 research-scope review · skill: game-fantasy · page created 2026-06-10
No synthesized fantasy research has been performed. This page proposes the research scope, source plan, assumptions, and output paths for defining Omega War's player fantasy, emotional pillars, vibe references, one-sentence hook, and first-session promise. Items tagged scope evidence are discovery context, not findings. Stage 2 begins only after final compiled YAML approves this scope.
1. Known Context scope evidence
1.1 Upstream artifacts (both approved 2026-06-10)
research/idea-brief.md— Omega War: browser-first 3D RTS, Operation Unthinkable (~July 1945), tactical layer (CoH × Broken Arrow with deck-as-roster × base building) + strategic European war-map layer (EndWar × Wargame: RD); stylized low-poly, "historically inspired, not accurate"; single-player first.research/game-audience.md— approved segments: primary: campaign wargamers (SP-first operational; motivated by the "total war board" fantasy, mastery without ladder anxiety, persistence); secondary: deck/division tacticians (roster identity, collection); tertiary: alt-history narrative enthusiasts (premise plausibility, faction lore, exile-formation drama; conversion unproven — A-R3). Positioning anchor: Operation Unthinkable is unmined in RTS. Live framing risk: "clean Wehrmacht" criticism environment (A-R5). Suggested hook material recorded there: "the RTS about the WW3 that almost happened in 1945 — playable in your browser."
1.2 User scope decisions (recorded this session)
| Decision | User answer (2026-06-10) |
|---|---|
| Research depth | Broad web sweep — comparables' emotional positioning plus alt-history media vibes (books, films, video essays), adjacent genres, player-motivation writing. |
| Artifact use cases | All three: (a) design north star — what emotions the moment-to-moment combat and deck/base hybrid must deliver; (b) hook & positioning — one-sentence hook + vibe references for eventual store page; (c) first-session promise — what the first 15–30 minutes must make the player feel, to scope the vertical slice. |
1.3 Reusable evidence from the audience sweep scope evidence
The audience research (2026-06-10) already captured store-positioning copy for WARNO ("the ultimate World War III battle simulator… hundreds of units on a beautiful and brutal battlefield") and Broken Arrow (campaign-first, "craft your unique army deck… 300 units, 1,500 combinations"), motivation quotes (roster identity, "total war board" feel, spectacle-skewed creator titles), and the complaint register. Fantasy research will reuse this where valid and add emotion-specific evidence rather than re-collecting it.
2. Proposed Research Scope
2.1 Research questions
| Use case | Research questions |
|---|---|
| A. Design north star |
FRQ1 — What emotional language do the comparables use in their own marketing (store copy, trailers) — what fantasy do CoH, WARNO/Wargame, Broken Arrow, Steel Division, and EndWar each sell? FRQ2 — What emotions do players actually report in positive reviews and "why I love this game" threads (command weight, tension/relief cycles, spectacle awe, plan-comes-together satisfaction) — the lived fantasy vs the marketed one? FRQ3 — What specific emotional beats define the operational-commander fantasy for the primary segment (map-level dread, husbanding veteran units, front-line collapse/rally), per Army General / campaign-mode praise language? |
| B. Hook & positioning |
FRQ4 — How is the Operation Unthinkable / WW3-1945 premise framed emotionally where it already lives (alternatehistory.com threads, AlternateHistoryHub-style essays, board-game marketing, fiction like the "1945/1946" trope) — dread? tragedy? forbidden-what-if fascination? FRQ5 — What hook patterns work for niche strategy titles (one-line capsule formulas of successful wargames/indies) and which elements (premise, mechanics-hybrid, browser delivery) should lead Omega War's one-sentence hook? |
| C. First-session promise |
FRQ6 — What do genre first sessions deliver today (time-to-first-battle, tutorial structure in comparables) and where do they emotionally fail (onboarding-cliff complaints from the audience artifact)? FRQ7 — Which vibe references (games, films, books, music/tone) should anchor Omega War's aesthetic-emotional register, consistent with stylized low-poly and "historically inspired, not accurate"? |
2.2 Deliverable shape (canonical artifact contract)
- Player fantasy — one primary fantasy statement plus per-segment variants (campaign wargamer / deck tactician / alt-history enthusiast).
- Emotional pillars — 3–5 named pillars with design implications each (what the tactical slice and strategic layer must make the player feel).
- Vibe references — games / film / literature / tone anchors with what to borrow from each.
- One-sentence hook — 2–4 candidate formulations, one recommended.
- Fast first-session promise — what minutes 0–30 must deliver emotionally, mapped to vertical-slice scope.
2.3 Non-goals
- No genre-convention mapping (that is
/game-genre-map) and no full comparable teardowns (/game-comparables). - No store-page asset production or capsule/trailer testing (
/game-store-page-test). - No mechanics design — emotional targets only; loop design stays in
/game-core-loop. - No re-collection of audience evidence already in
research/game-audience.md.
Gate — Scope / Non-goals required
Approve the research questions (FRQ1–FRQ7), deliverable shape, and non-goals above?
3. Source Plan
Availability is a plan, not verified coverage. Method note carried from the audience cycle: research subagents have no web access in this environment; the sweep runs in the main session. scope evidence
| Category | Planned sources (examples) | Serves | Known limits |
|---|---|---|---|
| F1. Comparables' marketing language | Store descriptions + trailer copy for CoH 2/3, WARNO, Wargame: RD, Steel Division 2, Broken Arrow, EndWar (legacy); how each names its fantasy. Partial reuse from the audience sweep. | FRQ1, FRQ5 | Trailer analysis is text-level (titles/descriptions), not frame-by-frame. |
| F2. Player emotional language | Positive-review sampling and "why do you love X" threads (Steam reviews/discussions, r/warno, r/wargame, r/CompanyOfHeroes, r/RealTimeStrategy); Army General praise threads for operational-fantasy beats. | FRQ2, FRQ3, FRQ6 | Vocal-minority bias; review sampling qualitative. |
| F3. Premise emotional framing | alternatehistory.com Unthinkable threads (tone of fascination); alt-history video-essay framing; Hollandspiele/S&T board-game marketing copy; alt-history fiction framing (Conroy-style 1945 fiction); "clean Wehrmacht" criticism sources (carried from audience artifact) as tone guardrails. | FRQ4, FRQ7 | Emotional reads of forum tone are interpretive — labeled as inference. |
| F4. Hook & first-session patterns | Capsule/one-liner formulas of successful niche strategy titles (Regiments, Sea Power, OpenFront, Broken Arrow); writing on RTS onboarding and time-to-fun; demo-first-session structures. | FRQ5, FRQ6 | "What worked" is survivorship-biased; treated as patterns, not laws. |
Gate — Evidence Coverage required
Approve the four source categories (F1–F4) and their limits as sufficient coverage for FRQ1–FRQ7?
Gate — Coverage Checkpoint (sweep depth) required
"Broad web sweep" was your recorded preference for the fantasy work. Confirm the stopping rule for Stage 2:
4. Assumptions & Confidence (pre-research)
| # | Assumption | Confidence | What would change it |
|---|---|---|---|
| F-A1 | The fantasy is written primarily for the campaign wargamer segment (per approved audience ranking); deck tacticians and alt-history fans get supporting variants, not equal weight. | High (follows approved artifact) | User re-weighting; playtest evidence of different cohort mix. |
| F-A2 | Tone target is grounded-but-stylized: serious operational weight without milsim grimness or pulp camp — consistent with low-poly art and "historically inspired, not accurate." | Medium (inferred from idea brief) | User preference for darker (TNO-like dread) or lighter (pulpy what-if) registers — Stage 2 will present the spectrum. |
| F-A3 | The one-sentence hook should lead with the premise (Operation Unthinkable — unmined, creator-friendly), with the mechanical hybrid and browser delivery as support. | Medium (hypothesis from positioning anchor) | FRQ5 hook-pattern evidence; user taste. |
| F-A4 | The "clean Wehrmacht" guardrail (A-R5) constrains the fantasy: the emotional register must accommodate honest framing of re-armed German formations (tragedy/moral weight, not hero-washing). | High (carried from approved register) | Nothing at this stage; shapes pillar wording. |
| F-A5 | The first-session promise targets the tactical vertical slice only (one battle: deployment from a fixed deck, capture points, cover/suppression, base building, basic AI) — the strategic layer is promised, not delivered, in session one. | High (idea-brief slice definition) | Slice scope changes upstream. |
Gate — Assumptions / Confidence required
Accept F-A1–F-A5 as the working baseline for Stage 2? (F-A2 and F-A3 are the genuinely open ones — note any tone or hook-lead preference now and Stage 2 will weight it.)
5. Artifact Destination & Proposed File Changes
| Stage | Path | Status |
|---|---|---|
| Stage 2 (working) | research/_working/preliminary-game-fantasy-research.md | Non-canonical working packet (flat mode); fully rendered into this page; archived and removed at Stage 3. |
| Stage 2 (this page) | alignment/game-fantasy-omega-war.html | Updated in place with findings + artifact gates (prior version archived first). |
| Stage 3 (canonical) | research/game-fantasy.md | New canonical artifact: player fantasy, emotional pillars, vibe references, one-sentence hook, fast first-session promise. |
| Stage 3 (index) | alignment/index.html | Entry added now as review; flips to confirmed. |
| Stage 3 (glossary) | research/glossary.md | Only if new approval-worthy terms emerge in Stage 2 (e.g., pillar names). |
| Stage 3 (tasks) | tasks/*.md | None planned a priori. |
Gate — Artifact Destination (Stage 2 working packet) required
Approve research/_working/preliminary-game-fantasy-research.md as the Stage 2 working-packet destination, with this page updated in place?
Gate — Proposed File Changes (Stage 3 canonical set) required
Approve the Stage 3 mutation scope: write research/game-fantasy.md, update alignment/index.html, archive + remove the working packet, convert this page to confirmed, append approved glossary terms if any, and touch tasks/*.md only if real follow-up work emerges?
6. Post-Approval Route
Gate — Post-Approval Route required
After research/game-fantasy.md is approved and written (Stage 3), what happens next? (Game-pack default sequence: /game-genre-map follows.)
7. Compile
Feedback-only YAML
Available as soon as any section-feedback control is set; gate questions need not be answered.
Final approval answers
Aggregates all 7 required gate questions plus any section feedback. Enabled when every required question has a selection.
Page: alignment/game-fantasy-omega-war.html · review · 2026-06-10 · game-fantasy (Stage 1 of staged research workflow)