- C++ 80.2%
- TypeScript 7.5%
- SCSS 6.9%
- Python 3.1%
- JavaScript 2.1%
- Other 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
5c45e2788b
Candidate design from an Imagination pass. One learnable quirk per faction, each tested by the player adjustment it forces, landed on levers the legacy tree has: Faction.Personality read by the existing Minion agent plus the four states the tutorial sketch already needs, Allegiance and product roles for loadouts, station stock and security for resources, signature behaviour and earned HUD identity for visuals, barks and dock stories for hooks. Includes prior art, cross-faction dynamics, a cut list, lore change proposals and the inter-faction relations fork. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
| .epiphany | ||
| .github/workflows | ||
| .obsidian | ||
| .voidbot | ||
| Aetheria | ||
| scripts | ||
| site | ||
| .gitattributes | ||
| .gitignore | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| LICENSE | ||
| README.md | ||
AetheriaLore
Aetheria is an open science-fantasy setting built to hold radically different stories inside one causal world: black-magic hard SF and noir before Elysium, giant mecha and cultivation epics after it, Ratfolk first contact, cockpit action, corporate logistics, and whatever pressure point another writer finds next. Technologies have histories, institutions have incentives, and consequences survive the stories that create them.
Writers do not need custody of the whole universe. Shared notes own their stated constraints; finished stories own their cast, place, depicted sequence, and immediate consequences. Developmental notes, game designs, and brainstorming may test possibilities without silently changing shared physics, faction history, or practice. A local claim becomes shared canon when the relevant owner note explicitly incorporates it.
AetheriaLore is the source vault for aetheria.gamecult.org. It contains setting material, fiction, game design, articles, media, and the Aetheria-specific site overlay.
Start Here
- Readers: begin with
Aetheria/index.md, then browseLore,Worldbuilding, orFiction. - Writers: read
Narrative Themes, the relevant owner notes, and the publicbranch-and-fold process. Finished work lives underFiction;Storiesincludes shorter and developmental work. - Maintainers: site-specific configuration lives under
site/; the shared Quartz engine and build behavior live inGameCult-Quartz.
Repository Map
Aetheria/: source vault content and media; publication is filtered by the site configurationsite/: Aetheria-specific Quartz configuration, layout, components, and stylesscripts/quartz/quartz.ps1: local build and development launcherquartz-site/public/: generated static output.github/workflows/deploy-quartz.yml: deployment workflow using the shared engineAGENTS.md: contribution, continuity, and writing conventions
Internal Brainstorming/ and Inspiration/ branches are excluded from publication. They are working material, not automatic canon.
Local Development
Local builds expect GameCult-Quartz either at the sibling path E:\Projects\GameCult-Quartz or at the path supplied through GAMECULT_QUARTZ_ROOT.
Install the shared engine dependencies first:
cd E:\Projects\GameCult-Quartz
npm ci
Then run from this repository root:
.\scripts\quartz\quartz.ps1 dev
For a one-off production build:
.\scripts\quartz\quartz.ps1 build
The launcher stages the shared engine under .quartz-build/engine and writes the finished site to quartz-site/public.