Files
sor/public-site-plan.md
2026-04-30 19:27:52 -04:00

28 KiB

Aeternalis Public Website Plan

Status: Draft R3 Target domain: aeternalisgames.com Purpose: Public game website, player account portal, webclient launch point, card catalog, leaderboard, and AI asset transparency hub.


Vision

aeternalisgames.com should feel like the front door to a living strategy card game, not a static documentation site. The first screen should sell the fantasy, show real game/card visuals, and get players to the next useful action fast: play, register, learn, browse cards, or check rankings.

The site has two jobs:

  • Make new players want to try Aeternalis.
  • Give existing players a fast, polished hub for play, account info, cards, rankings, and transparency reports.

Every page should feel connected to the game world through card art, board imagery, set identity, faction/affinity color, motion, soundless visual feedback, and crisp game UI patterns.


Story Foundation

Working title:

  • Origin: Stone of Revival

Core premise:

  • Since time immemorial, the sky held four stars: the life-giving Sun and three distant sister planets. Beyond them was assumed to be void, desolate and empty. Humanity believed it was alone.
  • The player is a Channeler, one who reaches into the living memory of all things to recover knowledge from the past and strengthen the present.
  • Great Channelers can commune with the Origin Stone, a cosmic vessel whose surface protects memories of what has been, what is, and what may yet be.
  • Through the Origin Stone, Channelers connect with Archspirits: mighty beings of ages past whose memories, worlds, experiences, and powers can be temporarily revived.
  • Channelers use Terramorpha to shape constructed mindscape worlds, bringing lands, paths, and battlefields into being through thought and will.
  • During one communion, the player encounters an unknown corrosive entity deep within the Origin Stone. It attacks through psychic space with strange spirits, impossible powers, and violence from lands never seen.
  • In response, the Channeler forms defensive worlds, summons Archspirits, sacrifices spirits to fuel growth, and reshapes terrain mid-conflict to survive.
  • Victory forces the entity back, but the mindscape is changed. The trance breaks. The night sky now holds a fifth star: a new planet that should not exist, yet does.
  • Other Channelers begin encountering the same menace. Every fight in the mindscape, even a loss, creates another star in the night sky.
  • What began as survival becomes hope: the endless void can be undone, the sky can be filled with worlds, and the lost experiences beyond the Origin Stone can be restored.

Player-facing fantasy:

  • You are a Channeler.
  • Channel Archspirits.
  • Shape the mindscape with Terramorpha.
  • Survive the psychic assault.
  • Revive lost worlds as new stars.
  • Turn every battle into a testament of will.

Primary marketing hook:

  • Channel the Archspirits. Shape the mindscape. Fill the void with stars.

Alternate short hooks:

  • Every battle births a world.
  • The fifth star was only the beginning.
  • Revive what was lost. Defend what may yet be.

Product Principles

  • Game-first presentation: lead with actual cards, board state, character/entity art, screenshots, and short gameplay clips where available.
  • Story-backed UX: pages should use the language of Channelers, Archspirits, Terramorpha, the Origin Stone, mindscapes, and new stars where it helps sell the game.
  • Fast path to play: the Play action should always be obvious, especially on mobile.
  • No dead brochure pages: every major page should do something useful.
  • Public content without friction: how-to, cards, leaderboard, and AI transparency should be available without login.
  • Account actions without clutter: login/register/account pages should feel polished but direct.
  • Shareable game knowledge: card filters, card detail pages, leaderboard views, and how-to sections should have stable URLs.
  • Transparent asset reporting: AI asset disclosure should be clear, searchable, and linked directly from affected content.
  • Mobile is a primary platform for browsing and account tasks, even if gameplay is better on larger screens.

Visual Direction

Desired Feel

The site should feel like a premium tactical card game:

  • Dramatic but readable.
  • Rich with art and card surfaces.
  • Clean enough for serious strategy browsing.
  • Animated enough to feel alive, without slowing down navigation.
  • Cosmic, sacred, and dangerous: a meeting point between ritual memory, psychic combat, and newly born worlds.

Story Motifs

Use these visual motifs across the site:

  • The Origin Stone as a central relic/symbol.
  • Four known stars plus the impossible fifth star.
  • Expanding constellations as battles create worlds.
  • Mindscape terrain forming under pressure.
  • Archspirit silhouettes emerging from memory.
  • Corrosive unknown entity effects as threat language.
  • Terramorpha paths, tiles, and land-shaping as gameplay language.

Art And Media

Use real game assets wherever possible:

  • Hero background: full-bleed board/gameplay scene or strong key art.
  • Home page: rotating featured cards, set art, faction/affinity callouts, gameplay screenshot/video.
  • Catalog: actual card thumbnails and full card images.
  • How-to: board diagrams, card examples, and short visual examples.
  • Leaderboard: season banner art and rank iconography.
  • Lore sections: Origin Stone, Channeler, Archspirit, mindscape, and fifth-star imagery.

Avoid generic fantasy filler. If an image does not show Aeternalis cards, the board, characters, ruins, UI, or set art, it should not be a primary visual.

UI Style

Recommended direction:

  • Dark game UI foundation with controlled contrast.
  • Accent colors driven by affinity/faction/set, not one global purple/blue wash.
  • Card-like surfaces for cards only; avoid making every section look like a card.
  • Sharp, readable data areas for catalog and leaderboard.
  • Subtle motion for hover, page transitions, card flips/previews, and leaderboard rank changes.

Visual components:

  • Icon buttons for search, filters, account, play, sort, favorite/share.
  • Segmented controls for catalog views and leaderboard seasons.
  • Filter chips for active catalog filters.
  • Tooltips for symbols, rarities, card types, and affinity icons.
  • Tabs for account sections and card detail subviews.

Core Player Journeys

New Player

  1. Lands on home page.
  2. Sees the game identity, Origin Stone/fifth-star imagery, real visuals, and a concise pitch.
  3. Chooses Play Now, Register, or How To Play.
  4. Learns core rules through visual examples.
  5. Opens the webclient or creates an account.

Returning Player

  1. Lands on the site or directly opens /webclient.
  2. Logs in if needed.
  3. Enters the webclient quickly.
  4. Can check account info, recent rank, or leaderboard without digging.

Competitive Player

  1. Opens leaderboard or card catalog.
  2. Filters current season/rankings or searches cards by set/type/affinity.
  3. Opens card detail pages for exact text and related cards.
  4. Shares filtered views or card links.

Transparency Reviewer

  1. Opens /ai-assets.
  2. Reads the plain-language disclosure.
  3. Opens the full report.
  4. Filters by card, set, asset type, status, or tool/source category.
  5. Follows links from report entries to affected cards/entities.

Information Architecture

Public Pages

  • /

    • High-impact home page.
    • Primary actions: Play Now, Create Account, How To Play, Browse Cards.
  • /story

    • Story/lore page for Origin: Stone of Revival.
    • Introduces Channelers, the Origin Stone, Archspirits, Terramorpha, the unknown menace, and the fifth star.
  • /how-to-play

    • Visual onboarding and rules guide.
    • Should teach through examples, not long walls of text.
  • /cards

    • Full public card catalog.
    • Search, filters, sorting, card grid/list toggle, shareable URLs.
  • /cards/{slug}

    • Card detail page.
    • Full card art, rules text, stats, abilities, related cards, set data, AI disclosure links.
  • /leaderboard

    • Current season rankings.
    • Season tabs, mode filters, rank visuals, player search.
  • /ai-assets

    • Plain-language explanation of AI asset usage.
  • /ai-assets/report

    • Complete searchable AI asset report.
  • /webclient

    • Stable public route for launching the playable client.
  • /news

    • Optional but strongly recommended for patch notes, set releases, events, and announcements.
  • /support

    • Support, bug report, account help, community/contact links.
  • /privacy

    • Privacy policy.
  • /terms

    • Terms of service.

Auth Pages

  • /register
  • /login
  • /logout
  • /forgot-password
  • /reset-password
  • /verify-email

Account Pages

  • /account

    • Account dashboard.
  • /account/profile

    • Display name, avatar/profile metadata, player identity.
  • /account/security

    • Password, active sessions, 2FA later.
  • /account/game

    • Rank/MMR summary, recent matches, collection/card unlock summary if supported.

Home Page Experience

The home page should be an interactive game landing experience.

First Viewport

Must include:

  • Aeternalis name/logo as the dominant first signal.
  • Full-bleed game/key art background showing the Origin Stone, mindscape battle, board state, or fifth-star sky.
  • Concise one-sentence game pitch.
  • Primary Play Now button.
  • Secondary Create Account or How To Play action.
  • A visible hint of the next section below the fold.

The hero should not be a split card layout or a generic gradient. It should show the game.

Recommended hero copy:

  • H1: Aeternalis
  • Supporting line: Channel the Archspirits. Shape the mindscape. Fill the void with stars.
  • Primary action: Play Now
  • Secondary action: Learn the Origin

Below The Hero

Recommended sections:

  • Story teaser:
    • Four stars were all humanity knew.
    • The Origin Stone opened a path through memory.
    • The fifth star proved the void could be changed.
  • Featured cards from the current set.
  • "How a match unfolds" interactive strip:
    • Channel an Archspirit.
    • Shape terrain with Terramorpha.
    • Sacrifice and empower spirits.
    • Survive the psychic assault.
    • Birth a new star.
  • Current season snapshot:
    • Top 3 leaderboard players.
    • Season name/time remaining.
  • Latest news/patch notes.
  • AI transparency callout:
    • Short statement with link to full report.

Home Page Polish

  • Card hover preview with readable enlarged art/text.
  • Animated board/gameplay snippets when assets are available.
  • Smooth section transitions.
  • Persistent Play action in nav.
  • Mobile hero keeps actions above the fold.

Navigation

Primary nav:

  • Play
  • Story
  • Cards
  • How To Play
  • Leaderboard
  • News
  • AI Assets

Account nav:

  • Logged out: Log In, Create Account.
  • Logged in: display name/avatar menu with Account, Webclient, Log Out.

Navigation behavior:

  • Play should be first or visually strongest.
  • Mobile nav should expose Play without opening a menu.
  • Current page state should be obvious.
  • Account menu should never hide critical public links.

Webclient Entry

Route: /webclient

Recommended behavior:

  • If authenticated, launch or redirect into the webclient.
  • If unauthenticated, show a polished launch gate:
    • Log In
    • Create Account
    • Continue as Guest only if guest play exists.
  • Preserve return URL after login.

Deployment options:

  • aeternalisgames.com/play
  • play.aeternalisgames.com
  • client.aeternalisgames.com

The public site should keep /webclient as the canonical route even if the backing deployment changes.


Registration And Account Flow

Registration

Required fields:

  • Email.
  • Display name.
  • Password.
  • Confirm password.
  • Terms/privacy acceptance.

Experience goals:

  • Keep the form short.
  • Show inline validation.
  • Explain display name rules before submit.
  • Use strong error messages without exposing account enumeration details.
  • After success, route directly toward email verification or webclient launch.

Recommended validations:

  • Unique email.
  • Unique display name.
  • Password strength.
  • Email format.
  • Age/region compliance if needed.

Login

Login identifiers:

  • Email.
  • Password.

Experience goals:

  • Fast return to webclient.
  • Clear forgot-password route.
  • Remember-me option if the auth model supports it.

Account Dashboard

Show:

  • Display name.
  • Email verification state.
  • Account creation date.
  • Player ID.
  • Current rank/MMR summary.
  • Current season status.
  • Recent matches if available.
  • Quick actions:
    • Open webclient.
    • Edit profile.
    • Change password.

Do not expose email, internal account IDs, moderation state, or admin-only fields outside authenticated account views.


How-To-Play Page

The how-to page should act like an interactive rules primer.

Sections:

  • What is Aeternalis?
  • What is a Channeler?
  • How to win.
  • The board.
  • Card types.
  • Resources and costs.
  • Turn structure.
  • Movement and positioning.
  • Combat and targeting.
  • Abilities and effects.
  • Terramorpha and land shaping.
  • Sacrifice and spirit growth.
  • Deckbuilding basics.
  • First match walkthrough.
  • Glossary.

Presentation:

  • Use diagrams and example cards.
  • Keep each concept short, then allow expansion.
  • Link rule terms to glossary anchors.
  • Link example cards to /cards/{slug}.
  • Use tabs or step controls for the first-match walkthrough.

Success criteria:

  • A new player should understand what to do in their first match after reading this page.
  • An experienced player should be able to find a specific rules concept quickly.

Story Page

Route: /story

Purpose:

  • Give the game its public narrative identity.
  • Explain why battles happen.
  • Connect card/game systems to the fiction.
  • Create a strong source page for trailers, store pages, community links, and press kits.

Recommended structure:

  • That We Know
    • Four stars: the Sun and three sister planets.
    • The void beyond.
    • Channelers and living memory.
    • The Origin Stone.
    • Archspirits and temporary revival.
    • Terramorpha and constructed mindscape worlds.
  • That We Do Not
    • The unknown corrosive entity.
    • Psychic assault through the Origin Stone.
    • Defensive worlds and spirit conflict.
    • Sacrifice, growth, and terrain shaping under pressure.
    • The fifth star.
    • Other Channelers entering the same conflict.
    • Every battle creating a new star.
  • Your Role
    • Channel the Archspirits.
    • Discover lost memories.
    • Fight the menace in the mindscape.
    • Restore worlds to the sky.

Presentation:

  • Use cinematic panels, not a wall of prose.
  • Pair each lore idea with a game concept.
  • Include a timeline/constellation visual showing four stars, the fifth star, then many emerging worlds.
  • Link into how-to sections for game mechanics:
    • Channeling -> summoning/playing cards.
    • Terramorpha -> board/terrain mechanics.
    • Sacrifice -> growth/resource mechanics.
    • Psychic assault -> match conflict.

Suggested page copy snippets:

  • From time immemorial, the sky held only four stars.
  • The Origin Stone remembers what reality has forgotten.
  • To channel an Archspirit is to revive a world for one decisive moment.
  • The fifth star was not discovered. It was created.
  • Every battle in the mindscape leaves a light in the sky.

Card Catalog

The card catalog is one of the most important public pages. It should feel like a premium collection browser, not a basic table.

Catalog Views

Required views:

  • Grid view for visual browsing.
  • Compact/list view for dense strategy review.
  • Detail page for each card.

Card result display:

  • Card art thumbnail.
  • Name.
  • Type.
  • Set.
  • Affinity/faction.
  • Cost.
  • Rarity if supported.
  • Short rules text.
  • Key stats.
  • Story tags when useful, such as Archspirit, Spirit, Ruin, Instinct, Repentance, or Terramorpha-related mechanics.

Filters

Initial filters:

  • Search by name/rules text.
  • Set.
  • Card type.
  • Affinity/faction.
  • Cost range.
  • Rarity if supported.
  • Genus/tags.
  • Attack type/range.
  • Has AI-assisted asset.

Sorting:

  • Name.
  • Set order.
  • Cost.
  • Card type.
  • Recently added.
  • Rarity if supported.

Interaction requirements:

  • Filter state appears in the URL query string.
  • Active filters show as removable chips.
  • Filter drawer works well on mobile.
  • Search should debounce and feel instant.
  • Empty states should suggest clearing filters.
  • Card preview should be readable before opening detail.

Card Detail

Each card detail page should show:

  • Full card art.
  • Full rules text.
  • Card type and subtype/genus tags.
  • Set and rarity.
  • Stats.
  • Abilities.
  • Related cards.
  • Previous/next tier links for ArchSpirit chains.
  • Lore excerpt or flavor text when available.
  • Origin/memory/world association when available.
  • AI asset disclosure link when the card uses AI-assisted art.
  • Share button/link.

Useful detail tabs:

  • Overview.
  • Abilities.
  • Lore.
  • Related cards.
  • Asset disclosure.

Data Source

Preferred source:

  • Public API backed by the same card definitions used by admin/game systems.

The catalog should not maintain a separate hand-authored card database. If internal cards should remain hidden, card definitions need explicit public visibility fields:

  • Draft.
  • Internal.
  • Preview.
  • Published.
  • Retired.

Leaderboard

The leaderboard should make the current season feel active and tie player victories to the fiction of Channelers creating new stars through conflict.

Default view:

  • Season banner/name with story flavor.
  • Time remaining if seasons are timed.
  • Rank.
  • Display name.
  • Rating/MMR or score.
  • Wins/losses.
  • Win rate.
  • Games played.
  • Rank movement if available.

Filters/tabs:

  • Current season.
  • Previous seasons.
  • Ranked mode.
  • Casual mode only if meaningful.
  • Region only if supported.

Polish:

  • Top 3 treatment with stronger visual presentation.
  • Rank badges/icons.
  • Season constellation visual showing progress or total battles/worlds created if data exists.
  • Player search.
  • Highlight the logged-in player.
  • Sticky table header on desktop.
  • Mobile cards or responsive table layout.

Privacy:

  • Show display name, not email.
  • Avoid internal account IDs.
  • Decide whether hidden/private profiles can appear.
  • Use public player IDs only if intentionally player-facing.

AI Asset Disclosure

The AI pages should be transparent, searchable, and integrated into the rest of the site.

Explanation Page

Route: /ai-assets

Purpose:

  • Explain how AI-assisted assets are used.
  • Distinguish generated, edited, placeholder, and human-created assets.
  • Explain human review and modification.
  • Link to the full report.

Sections:

  • Summary statement.
  • Asset categories that may use AI assistance.
  • Asset categories that do not use AI assistance, if applicable.
  • Human review/editing process.
  • Player-facing impact.
  • Report methodology.
  • Contact/reporting path.

Tone:

  • Plain.
  • Specific.
  • No claims that cannot be backed by report data.

Full Report

Route: /ai-assets/report

Recommended fields:

  • Asset ID.
  • Asset name.
  • Asset type.
  • In-game usage location.
  • Associated card/entity/page.
  • Associated set.
  • Generation/editing tool or source category.
  • Human edits performed.
  • Date created or imported.
  • Current status:
    • Active.
    • Replaced.
    • Placeholder.
    • Deprecated.
  • Notes.

Filters:

  • Asset type.
  • Set.
  • Card/entity.
  • Status.
  • Tool/source category.
  • Date range.

Exports:

  • JSON.
  • CSV.

Linking:

  • Card detail pages link to related AI asset report entries.
  • Report entries link back to affected cards/entities/pages.

Implementation note:

  • The report should come from structured metadata, not a manually maintained webpage.

News And Updates

Recommended route: /news

Use for:

  • Patch notes.
  • New set announcements.
  • Balance updates.
  • Season start/end posts.
  • Maintenance notices.
  • Event announcements.

News matters because it makes the site feel alive and gives returning players a reason to check back outside the webclient.


Lore And Content Metadata

The site should support structured lore content so story can appear across pages without being duplicated manually.

Useful entities:

  • Story chapter.
  • Glossary term.
  • World/star.
  • Archspirit.
  • Set.
  • Card.
  • AI asset.

Glossary terms should include:

  • Channeler.
  • Origin Stone.
  • Archspirit.
  • Terramorpha.
  • Mindscape.
  • Spirit.
  • Ruin.
  • Instinct.
  • Repentance.
  • Fifth Star.

Cards and sets should be able to reference:

  • Lore summary.
  • Associated world/star.
  • Related Archspirits.
  • Related story chapter.
  • Flavor text.

API Needs

Public endpoints:

  • GET /api/public/cards
  • GET /api/public/cards/{slugOrId}
  • GET /api/public/card-sets
  • GET /api/public/leaderboard
  • GET /api/public/seasons
  • GET /api/public/ai-assets
  • GET /api/public/ai-assets/{id}
  • GET /api/public/news
  • GET /api/public/news/{slug}
  • GET /api/public/story
  • GET /api/public/glossary

Auth endpoints:

  • POST /api/auth/register
  • POST /api/auth/login
  • POST /api/auth/logout
  • POST /api/auth/forgot-password
  • POST /api/auth/reset-password
  • POST /api/auth/verify-email

Account endpoints:

  • GET /api/account
  • PATCH /api/account/profile
  • POST /api/account/change-password
  • GET /api/account/game-summary
  • GET /api/account/recent-matches

Data Model Notes

Public Card Metadata

Public-safe fields:

  • ID/slug.
  • Name.
  • Type.
  • Set.
  • Cost.
  • Rules text.
  • Stats.
  • Tags.
  • Art URL.
  • Rarity.
  • Published status.
  • AI asset IDs.
  • Related card IDs.
  • Lore summary.
  • Flavor text.
  • Associated world/star ID.

AI Asset Metadata

Assets need stable IDs referenced by:

  • Cards.
  • NPCs.
  • Tiles.
  • UI art.
  • Marketing/public site assets.
  • News posts if they use AI-assisted imagery.

News Metadata

News posts should include:

  • Slug.
  • Title.
  • Summary.
  • Body.
  • Published date.
  • Category.
  • Hero image.
  • Related cards/sets if applicable.

Lore Metadata

Lore entries should include:

  • Slug.
  • Title.
  • Type.
  • Summary.
  • Body.
  • Related cards.
  • Related sets.
  • Related glossary terms.
  • Hero image.

Performance Standards

The site should feel fast even with image-heavy pages.

Requirements:

  • Responsive image sizes.
  • Lazy-load below-the-fold images.
  • Preload key hero media carefully.
  • Skeleton states for catalog, leaderboard, and account data.
  • Cache public card/set metadata.
  • Avoid blocking the first render with large catalog payloads.
  • Paginate or virtualize large card/report lists.

Targets:

  • Home page usable within 2 seconds on a normal connection.
  • Catalog filter interactions feel immediate.
  • Card detail pages render core text before heavy media finishes.

Security And Privacy

  • Account pages require authentication.
  • Never expose email addresses publicly.
  • Leaderboard uses display names only.
  • Rate-limit registration, login, password reset, public search, and report exports.
  • Add bot protection to registration if abuse appears.
  • Use secure cookies/session configuration.
  • Require HTTPS on aeternalisgames.com.
  • Validate all catalog, leaderboard, and report query parameters server-side.
  • Preserve return URL safely after login; avoid open redirects.

SEO And Sharing

Important pages should have:

  • Title and meta description.
  • Open Graph tags.
  • Canonical URL.
  • Share image.

Card detail pages should have card-specific metadata:

  • Card name in title.
  • Card art as share image where licensing/disclosure allows.
  • Rules summary in description.

News posts should be shareable with strong metadata and preview art.


Accessibility

  • Keyboard navigable nav, filters, dialogs, and account forms.
  • Clear focus states.
  • Form labels and error messages tied to inputs.
  • Sufficient contrast over art backgrounds.
  • Reduced-motion mode respects system preference.
  • Card catalog usable without relying only on color.
  • Leaderboard remains readable on mobile and screen readers.
  • All icons need accessible names or adjacent text.

Implementation Phases

Phase 1: Public Game Shell

  • Home page with real game visual direction.
  • Story page with Origin: Stone of Revival narrative.
  • Navigation with persistent Play.
  • Webclient route/link.
  • How-to skeleton.
  • Terms/privacy/support placeholders.

Phase 2: Auth And Account

  • Registration.
  • Login/logout.
  • Password reset.
  • Email verification.
  • Account overview.
  • Profile/security pages.
  • Return-to-webclient flow.

Phase 3: Card Catalog

  • Public card API.
  • Card grid/list views.
  • Card detail pages.
  • Filters, sorting, and shareable query state.
  • AI asset links from card detail.

Phase 4: Leaderboard And Seasons

  • Leaderboard API.
  • Current season view.
  • Previous season support.
  • Logged-in player highlight.
  • Public privacy rules.

Phase 5: AI Transparency

  • AI asset metadata model.
  • AI explanation page.
  • Full report page.
  • Report filters.
  • JSON/CSV export.
  • Bidirectional links between cards/entities and asset entries.

Phase 6: News And Live Operations

  • News listing.
  • News detail pages.
  • Patch notes/update posts.
  • Homepage latest-news module.
  • Story/lore content update flow if story is managed dynamically.

Phase 7: Polish Pass

  • Responsive image optimization.
  • Motion and hover states.
  • Empty/loading/error states.
  • Accessibility audit.
  • Performance pass.
  • Mobile layout pass.

Page Acceptance Criteria

Home

  • First viewport clearly shows Aeternalis and actual game/key art.
  • Hero copy communicates Channelers, Archspirits, the mindscape, or the fifth star.
  • Play Now is immediately visible.
  • New players can reach how-to and registration without searching.
  • Returning players can reach webclient quickly.

Story

  • Users can understand the premise of Origin: Stone of Revival.
  • The page introduces Channelers, the Origin Stone, Archspirits, Terramorpha, the unknown menace, and the fifth star.
  • Story concepts link to relevant gameplay explanations where possible.

Webclient

  • Authenticated users can launch the client.
  • Unauthenticated users are guided to login/register.
  • Return URL is preserved after auth.

Account

  • Users can register, log in, log out, recover password, and view account information.
  • Account pages expose only authenticated player data.

How-To

  • New players can understand the first-match loop.
  • Rules concepts are scannable and visually supported.
  • Core mechanics are connected to fiction where helpful.

Cards

  • Users can browse cards.
  • Users can filter by set.
  • Users can filter/search by major public card fields.
  • Users can open card detail pages.
  • Card detail pages link to AI asset disclosure when applicable.

Leaderboard

  • Users can view current season rankings.
  • Users can switch seasons if historical data exists.
  • Logged-in users can find their rank quickly.

AI Assets

  • Users can read a plain-language AI asset usage explanation.
  • Users can view the complete AI asset report.
  • Users can filter/export the report.
  • AI-assisted assets can be traced from card/entity usage to report entry.

Open Questions

  • Is the public site a new app, part of the game server, or a separate frontend?
  • Will the webclient live under aeternalisgames.com/play or on a subdomain?
  • Are guest accounts supported?
  • Does registration require email verification before play?
  • What ranking fields are safe and meaningful to expose?
  • Which card fields are public before official release?
  • What exact metadata is already tracked for AI assets?
  • Should replaced/deprecated AI assets stay visible in the public report?
  • Do we have enough real game/key art for a strong first version, or do we need a short asset production pass?
  • Should news/patch notes be managed in admin or as markdown/content files?
  • Should /story be a static authored page for launch, or a structured lore section that can grow over time?
  • What is the final public game title: Aeternalis, Origin: Stone of Revival, or Aeternalis: Origin - Stone of Revival?