Ludo Import Brief¶

Purpose¶

This document is a compact, Ludo-ready summary of EchoSpire: Portals intended to support UX ideation, feature framing, screen planning, and product-positioning exercises.

It is deliberately shorter and more tool-friendly than the main canon documents.

Copy/Paste Summary¶

EchoSpire: Portals is a single-player, run-based roguelike deckbuilder set inside a ruined reality engine called the EchoSpire. Players create faction-aligned heroes, take on authored faction quests, and enter unstable realms made of broken timelines, machine-scars, and ideological battlefields. Each run is deterministic from a seed, combines deckbuilding combat with route planning and fog-of-war exploration, and culminates in anchoring or resolving a realm-scale crisis. The long-term game structure blends repeatable roguelike runs with faction campaigns, persistent hero progression, and rival-hero encounters that express political conflict between the game's five factions.

The game's tone is cathedral sci-fi rather than fantasy: gothic mega-structure ruins, impossible machinery, sacred industrial spaces, and morally compromised factions trying to survive the collapse of reality. Factions are central to both mechanics and UX. The Valerii embody stability through stasis, the Syntacta logic through data, the Aethari prosperity through transmutation, the Annalis truth through record, and the Salvari survival through scavenging. Classes are equally identity-driven: Anchor, Drifter, Conduit, Machinist, and Catalyst each deliver a distinct combat fantasy from the opening deck.

For UX and feature ideation, the defining product shape is a campaign-backed deckbuilder where each run usually stays inside a single realm. The player receives a quest briefing, enters a fogged realm map, explores sectors through rift nodes, fights or negotiates through encounters, reveals the map by stabilizing an Anchor Rift, and completes a final objective, boss, or ideological confrontation. Realm passives materially change how the run feels, so the UX must surface the realm rule clearly and keep it visible without clutter. The product should feel strategic, legible, deterministic, and faction-authored rather than chaotic or purely random.

Structured Product Summary¶

Title¶

EchoSpire: Portals

One-Line Pitch¶

A single-player cathedral-sci-fi roguelike deckbuilder where faction-aligned heroes explore unstable reality fragments, fight through deterministic runs, and reshape the political future of a shattered mega-structure.

Genre And Format¶

Single-player roguelike deckbuilder
Narrative campaign layered over repeatable runs
Deterministic, seed-based run structure
Faction-driven worldbuilding and progression

Platform Direction¶

PC desktop
Steam as the initial shipping target
Unity client with shared deterministic gameplay core

Setting¶

The world centers on the EchoSpire, a colossal ruined reality engine.
The original caretakers fractured reality through incompatible attempts to control the Spire.
The result is the Reality Bleed: overlapping timelines, broken physics, unstable realms, and ideological civil war.
The visual tone is cathedral sci-fi: sacred ruins, industrial machinery, brutal grandeur, and fractured realities.

Player Fantasy¶

Become a faction champion inside a collapsing universe.
Navigate dangerous realm sectors with incomplete information.
Build a mechanically expressive deck around a strong class identity.
Enforce, exploit, or resist a faction doctrine through combat and quest outcomes.
Return from runs stronger, with campaign consequences and persistent progression.

Core Gameplay Loop¶

Choose or continue a faction-aligned hero.
Receive a faction quest briefing.
Enter a single unstable realm with a seed-driven layout.
Explore under fog of war and route across rift nodes.
Fight battles, resolve events, shop, rest, and protect objectives.
Stabilize an Anchor Rift to reveal the wider realm structure.
Push toward a final boss, confrontation, or quest objective.
Return with rewards, progression, and narrative consequences, or fail and return as a collapsed echo.

Product Pillars¶

Faction psychology matters as much as faction mechanics.
Deterministic systems support trust, testing, and strategic planning.
Every class should feel distinct from the first deck.
Realms are not cosmetic biomes; each realm changes both fiction and play.
Campaign structure should feel authored and political, not like disconnected errands.

Core Systems To Preserve In UX¶

Fog-of-war map exploration
Anchor-reveal map progression
Single-realm quest structure with sector escalation
Realm-wide passive effects that change decision-making
Class-specific combat engines
Faction-specific campaign framing
Rival Hero encounters as named faction enemies
Persistent hero progression outside the current run

Factions¶

Valerii: stability through stasis; authoritarian protection, walls, shields, lockdown.
Syntacta: logic through data; optimization, abstraction, cold system control.
Aethari: prosperity through transmutation; wealth, mutation, risk, excess.
Annalis: truth through record; memory, censorship, archival judgment.
Salvari: survival through scavenging; outlaw improvisation hiding repair work that keeps the Spire alive.

Classes¶

Anchor: defensive mass tank that retains block through Density and converts defense into crushing burst.
Drifter: evasive assassin that applies Echo-Lock and executes at precise timing windows.
Conduit: high-risk area-damage caster that borrows against future energy through Overload.
Machinist: combat engineer that deploys Constructs and wins through setup and board control.
Catalyst: unstable tempo manipulator that mutates cards into anomalies and plays around controlled chaos.

Run And Content Structure¶

Each run represents a faction quest.
Most quests stay inside one realm rather than jumping between unrelated worlds.
Realm complexity comes from sector identity, moving opposition, staged objectives, and state changes.
Rift nodes include combat, elite, event, shop, rest, sanctuary, treasure, protection, anchor, and boss spaces.
Rival Heroes create direct faction-versus-faction encounters and future-proof the combat model for optional PvP foundations.

UX Priorities¶

Make faction identity obvious at selection, briefing, combat, and rewards.
Make class identity readable from the opening deck and early decisions.
Keep the realm passive visible and understandable throughout the run.
Communicate fog of war, route discovery, and anchor-reveal clearly.
Distinguish map sectors so one realm feels like a real place rather than a flat node chart.
Support readable combat state, intent, statuses, constructs, and triggered effects.
Present campaign stakes and recurring characters without breaking run pacing.

Important UX Surfaces¶

Faction and hero selection
Quest briefing and narrative dispatch
Realm overview and passive presentation
Fogged map with sectors and node routing
Combat HUD with hand, energy, statuses, enemy intent, and class resources
Event and choice presentation
Reward, deck edit, and upgrade flows
Run-end summary and persistent progression

Keywords¶

cathedral sci-fi, roguelike deckbuilder, deterministic runs, faction politics, unstable realities, single-realm quests, fog-of-war map, rival heroes, gothic industrial, campaign-driven replayability

Guardrails¶

Do not frame the game as generic fantasy.
Do not frame randomness as the primary appeal; strategic determinism matters.
Do not treat factions as cosmetic skins.
Do not treat realms as simple biome swaps.
Do not design the UX around only combat screens; route-planning, quest framing, and realm readability are equally important.

Suggested Ludo Prompt Variant¶

Design around a single-player cathedral-sci-fi roguelike deckbuilder called EchoSpire: Portals. The player chooses a faction-aligned hero, receives a quest, and enters a deterministic single-realm run built from fog-of-war exploration, node routing, deckbuilding combat, realm-wide passive effects, and a final ideological or boss confrontation. The game's five factions are mechanically and narratively distinct, and the UX should emphasize faction identity, class readability, map discovery, anchor-based reveal, strong run legibility, and campaign stakes in a ruined reality-engine setting.

Ludo Field Coverage¶

The sections below intentionally mirror common Ludo input fields. They only include areas where the current official canon already provides enough detail to improve downstream AI ideation.

Mechanics¶

EchoSpire: Portals is built around deterministic single-player deckbuilder runs. The player navigates a fog-of-war map inside one unstable realm, chooses routes across rift nodes, resolves card-based combat, manages class-specific combat mechanics, reacts to realm-wide passive rules, and completes a quest objective before returning to the hub layer with persistent hero progression.

The core class mechanics are:

Anchor: Density, a stackable mass resource that retains Block across turns and powers defensive-to-offensive conversion.
Drifter: Echo-Lock, a target-marking system that enables precise execution windows.
Conduit: Overload, an energy debt system that allows short-term power at future cost.
Machinist: Constructs, deployable board entities with durability and automated behaviors.
Catalyst: Mutation and Anomalies, temporary unstable card transformations that create high-volatility turns.

Objectives¶

The primary objective of a run is to complete a faction quest inside a single unstable realm. Depending on quest type, this can mean stabilizing an Anchor Rift, surviving protection objectives, defeating a rival hero, securing an artifact, breaking into a strategic site, or defeating a final boss tied to the realm's central crisis.

At the campaign level, the player advances one faction's four-act story arc from indoctrination to political resolution while developing a persistent hero.

Progression Systems¶

Progression exists on two layers:

Run progression: card rewards, relic acquisition, shops, upgrades, route choices, and state changes inside the current realm.
Persistent hero progression: heroes level from 1 to 10 and choose one of two class-specific powers at each level from 2 through 10.

The progression model is intentionally not a pure stat treadmill. The main reward is specialization choice and build expression rather than flat permanent numeric inflation.

Faction identity and class mastery stay separate: faction passives unlock through faction progression, while hero level powers come from class progression rows.

Levels¶

The game's core play structure is not traditional linear levels. Instead, each run takes place inside one realm that functions as the full operational theater for a quest. That realm is divided into sectors with escalating pressure.

The recommended escalation shape is:

Sector Band 1: Orientation Pressure, where the player learns the realm's current stakes and enemy identity.
Sector Band 2: Doctrine Pressure, where synergies, hazards, and routing complexity increase.
Sector Band 3: Collapse Pressure, where the realm expresses its full threat identity through bosses, rivals, and tighter resources.

Rules¶

Important rules and constraints include:

Runs are deterministic from seed data.
Most quests stay inside one realm rather than hopping between unrelated worlds.
The map begins under fog of war.
Stabilizing an Anchor Rift reveals more or all of the realm map.
Realm passives materially affect the whole run and must be visible to the player.
Rift node types currently include Combat, Elite, Boss, Event, Shop, Rest, Treasure, Anchor, Protection, and Sanctuary.
Protection and escort objectives are a first-class system; every class must have at least one viable protection line.
Rival Heroes are official encounter types built from faction-and-class logic rather than generic monsters.

How To Play¶

Choose or continue a faction-aligned hero.
Receive a quest briefing that frames the mission and narrative stakes.
Enter a deterministic realm map with limited visibility.
Explore by choosing routes across rift nodes such as combat, events, shops, and rests.
Build combat advantage through cards, class mechanics, rewards, and map choices.
Stabilize an Anchor Rift to reveal more of the realm and open deeper routes.
Survive escalating sector pressure, resolve the quest's major conflict, and defeat the final encounter or complete the objective.
Return with rewards, persistent hero progress, and campaign consequences, or fail and return as a collapsed echo.

Rewards¶

Rewards come from combat victories, events, treasure, shops, quest outcomes, and boss clears. Reward types include new cards, relics, currencies, services, quest artifacts, codex unlocks, and persistent hero progression.

The design intent is that rewards should reinforce class identity, route planning, and long-term hero expression rather than only producing generic power inflation.

Loot And Equipment¶

The current canonical equipment direction is centered on cards, relics, currencies, artifacts, and faction-specific service rewards rather than armor-slot loot. Heroes begin with a 20-card starter deck composed of 15 class cards and 5 faction cards.

Treasure, elite, and boss nodes can bias toward relics and higher-value rewards. Shops can offer cards, relics, services, intelligence, or faction-specific contraband.

Difficulty Progression¶

Difficulty increases on multiple axes rather than only raw stats:

enemy stat budget
enemy behavior complexity
encounter composition
map and economy pressure
realm-level mutators

Standard fights scale through stronger pairings, elites scale through sharper mechanics and anti-stall tools, and bosses express the full identity of the quest or region.

Game Start¶

The player starts by choosing a hero defined by faction and class. A level 1 hero begins with a baseline class kit, faction choice, and tutorial destination or current campaign point. The first meaningful context is a quest briefing that explains why this hero is entering the realm and what the faction expects them to accomplish.

Defeat¶

A run ends in failure when the hero is defeated or when critical mission conditions fail, such as losing a Protectable in a protection objective where survival is mandatory. Failure returns the player from the run as a collapsed echo rather than advancing the current mission successfully.

Strategy¶

Successful play depends on:

understanding the class resource system and when to convert it into payoff
routing intelligently under incomplete map information
evaluating the realm passive and adapting card value to it
preparing for protection, rival, elite, and boss encounters rather than only generic combat
building toward a clear specialization path while staying flexible enough to survive the current realm

Determinism is important to the strategy layer because it supports trust, planning, balancing, and player learning.

Penalties¶

Penalties should come from fair, legible consequences rather than hidden punishment. Current canonical penalty spaces include run failure, objective failure, failure penalties on some rift types, self-damage or burnout from risky class mechanics, and economic or routing pressure caused by poor decisions.

Game World¶

Storyline¶

The game takes place after the collapse of the Aevum Spire, a reality engine once used to hold the universe in a single stable timeline. Four leaders attempted incompatible recalibrations of the Spire, fracturing reality and triggering the Reality Bleed: overlapping histories, unstable physics, and violent realm collisions.

The long-form storyline follows faction campaigns structured in four acts:

Indoctrination
Expansion
Fracture
Resolution

Each campaign teaches a faction worldview, reveals its hidden cost or central lie, and culminates in a faction-specific local victory inside the broken Spire.

Playable Characters¶

The player controls a hero defined by faction and class. The official playable classes are Anchor, Drifter, Conduit, Machinist, and Catalyst, with faction eligibility determined by the class-faction matrix.

Heroes are persistent entities rather than disposable anonymous runs. They level over time, make specialization choices, and can become faction legends in their timeline.

Lore And Systems¶

The five Great Houses are successor factions formed from the collapse of the former Aevum Sentinels:

Valerii: stability through stasis
Syntacta: logic through data
Aethari: prosperity through transmutation
Annalis: truth through record
Salvari: survival through scavenging

The world's underlying systems are built around unstable attached realms, faction doctrine, deterministic realm generation, and political conflict over how reality should be controlled, exploited, rewritten, or secretly repaired.

Universe And Setting¶

EchoSpire: Portals is set inside a colossal ruined mega-structure called the EchoSpire. The aesthetic is cathedral sci-fi: sacred industrial ruins, immense infrastructure, impossible machine architecture, and broken realities bleeding into one another.

The game's conceptual framework is ideological survival in a shattered reality machine. The world is not heroic fantasy in space; it is institutional failure, political doctrine, and cosmic collapse rendered at human scale.

Enemies¶

Enemy forces include anomaly creatures, hostile realm entities, faction troops, elite specialists, bosses, and Rival Heroes. Rival Heroes are especially important because they make inter-faction conflict feel personal and politically meaningful rather than abstract.

Enemies are expected to scale in both stats and behavior complexity across sector bands and encounter types.

Environments And Biomes¶

The game's environment model is realm-based rather than standard biome-based. A realm is a broken reality fragment with four identity layers:

visual flavor
historical or conceptual flavor
mechanical flavor
narrative flavor

Official realm categories include Climatic Collapse, Historical Echo, Foreign Civilization, Machine Scar, Conceptual Failure, and Ideological Occupation.

NPCs¶

Campaigns require recurring named relationships, including at least:

one superior or handler
one ally or subordinate
one ideological rival
one recurring outsider perspective

Current named faction leaders include High Commander Valerius IX, the Arch Logos, Baroness Lux, the First Scribe Olar, and Kaelen the Custodian.

Locations¶

The most important location is the EchoSpire itself, but the player operates inside attached realms and their internal sectors, breach-sites, command zones, industrial districts, archives, civic spaces, and unstable cores. A single realm should feel like a real place with districts, history, and changing stakes rather than a flat node board.

Key Narrative Objects¶

Key narrative object types include:

the EchoSpire and its shattered core
Anchor Rifts and Aegis Anchors used to stabilize reality
quest artifacts and relics
soul-data and archival records
faction infrastructure such as stasis generators, logic arrays, salvage machinery, and ritual systems

Art And Production¶

Art Style¶

The visual direction is cathedral sci-fi with gothic architecture, sacred ruins, industrial machinery, shattered timelines, and faction-specific ideological styling. The world should support dramatic contrast between fortress sectors, machine scars, frozen empires, broken treaties, drowned archives, luxury mutation markets, and maintenance districts trying to repair reality.

Onboarding And Tutorial¶

The tutorial direction is faction-specific indoctrination rather than generic training. Each tutorial should teach the same question through a different faction lens: what do you do when reality itself has failed?

Valerii: control it.
Syntacta: solve it.
Aethari: exploit it.
Annalis: purify it.
Salvari: survive it long enough to secretly fix it.

This means onboarding should introduce mechanics and story together, not as disconnected systems.

UI And UX Design¶

The most important UX goals are:

make faction identity obvious at selection, briefing, combat, and rewards
make class identity readable from the opening deck and early choices
communicate realm passive rules clearly and persistently
make fog of war, node routing, sector identity, and anchor-based reveal legible
support readable combat state including hand, energy, statuses, enemy intent, constructs, and triggered effects
present campaign stakes and recurring characters without breaking run pacing

The core UI surfaces are faction and hero selection, quest briefing, realm overview, fogged map, combat HUD, event choices, reward flows, and run-end progression summaries.

Technical Specifications¶

Current official technical direction:

target platform: PC desktop
initial shipping target: Steam
client: Unity in C#
backend: ASP.NET Web API in C#
gameplay rules: shared deterministic core library
structured data store: PostgreSQL
telemetry and analytics store: ClickHouse
cache and messaging: Redis
admin authoring layer: Blazor Server or lightweight React SPA against the API

The architectural rule is that core owns rules and clients own presentation. The shipping Unity client should not silently fork gameplay rules away from the shared core.

Audience And Retention¶

Target Audience¶

Based on the product shape, the clearest target audience is players who enjoy strategic single-player roguelike deckbuilders, strong worldbuilding, deterministic systems, and faction-driven campaign structure. The game is positioned closer to a systems-heavy PC strategy audience than to a casual mobile audience.

Player Retention¶

The main retention drivers already present in the canon are:

multiple factions with distinct campaign timelines
multiple classes with strong mechanical identities
persistent hero progression to level 10
repeatable deterministic runs
post-campaign Infinite Spire endgame for optimization, relic hunting, higher difficulty, and replayability
Rival Hero and faction-conflict systems that expand encounter variety