aethelgard

Aethelgard: The Shattered Crown

Seven nights after the Crown of Aethelgard shattered and its queen died, you wake in the royal ossuary with a shard of that crown grown into your palm — and a city that has already named you her murderer.

A branching, dice-driven fantasy RPG: choose-your-own-adventure prose, visual-novel dialogue, D&D-style d20 skill checks and top-down tactical combat. A tight ~10-hour story built as a string of pearls: anchor scenes every player visits, re-skinned by the choices (and the hidden truth) of each playthrough.

Status: pre-production. Act 1 is complete: the opening chapter (Ossuary → nave escape), the Lantern Market hub, the recruitment of Sable, Doran, Aria and Mirren, the three leads (the Rookery, the Ashen College vault, the Hollow Bells), the Masquerade at Morrow Hall and the Bell Tower climax where the Crown’s truth is locked in. Act 2 is complete: the Waystone Camp, the road out, all three shard sites (the Drowned Abbey, Fort Greywatch, the Thornwood Barrows) with three truth skins each, the trial at the Conclave of Thorns, the Crossroads Night where companions can leave you, and the Shard Thief who takes what you gathered. Act 3 is complete: the Siege of Highspire, the Muster, the Crown Vault with each companion’s finale, and the Reforging, with four endings (rule, give away, destroy, become the lock) and a hook into the follow-up quest, The Thread Beyond, which is now written, with three chapters that depend on the hook you were left with. You choose from five origins and type your own name. It is all written and playable in the terminal and in Godot, with levels, skills, talents, Inspiration rerolls, named injuries, Death’s Door wake-ups, companion help, social duels, trainers, street encounters, a tavern dice game and turn-based skirmish combat (parley + environment actions). The top-down tactical grid comes later.


Quick start

1. Play the story right now (no engine needed)

Requires Python 3 (already on macOS).

python3 tools/story.py play                 # play from New Game
python3 tools/story.py play --seed 7        # same dice every time
python3 tools/story.py play a1_01_ossuary:gallery --set origin=ashen --set crown_truth=sealed_horror

While playing: c = character sheet, f = recent flag changes, s = full state, q = quit.

Try every system (social rolls, a skill trainer, traps, two fights, level-ups) without the story:

python3 tools/story.py play dev_sandbox:setup

2. Run it in Godot

  1. Install Godot 4.7 (the standard build, not .NET).
  2. Open Godot → Import → select game/project.godot.
  3. Press F5 to run. In game: C character sheet · F2 systems sandbox · F5 quicksave · F9 quickload · F1 flag debug panel.

3. Check your work after every writing session

python3 tools/story.py validate        # catches typos, broken links, undeclared flags
python3 tools/story.py fuzz --runs 500 # plays 500 random games: crashes, dead ends, coverage
python3 tools/story.py tracker         # regenerates docs/VARIABLE_TRACKER.md

After changing any .gd file, also run the Godot smoke test:

/Applications/Godot.app/Contents/MacOS/Godot --headless --path game res://tests/smoke_test.tscn

How it’s built

The engine (GDScript) is a player for story data (JSON). It knows nothing about Aria or the Crown; it only knows how to show text, roll dice, apply flag changes and follow links. All the story lives in game/content/:

File What it is
content/flags.json The Variable Tracker. Every story flag (crown_truth, aria_trust, rook_fate…), its type, default and meaning.
content/rules.json Skills, DCs, romance and jealousy numbers.
content/characters.json Speakers and their colours.
content/story/**/*.json Scenes → nodes → text, choices, dice checks, effects.
content/encounters/*.json Fights (who spawns, under which conditions).
content/units.json Monsters, villains and allies: HP, defense, attack, damage dice, XP.

A taste of a story node:

{
  "text": "Read the sigils and find the magisters' door.",
  "check": {
    "skill": "arcana", "dc": 14,
    "bonuses": [{ "if": "clue_chalk_circle", "bonus": 2, "label": "You studied the circle" }],
    "success": "sigil_success",
    "failure": "sigil_fail"
  }
}

Repository layout

docs/
  VARIABLE_TRACKER.md     generated list of every story flag + where it's set/read
  narrative/              the Narrative Bible
    01_premise_and_hook.md
    02_act_structure.md   3-act string-of-pearls flowchart, truth plug-in contract
    03_companions.md      Aria, Doran, Sable, Mirren
    04_sample_scene.md    generated script of the opening chapter
    scenes/               generated readable scripts of every written scene
  design/
    architecture.md       engine/language choices, layers, roadmap
    mechanics.md          d20, fail-forward, morality, romance math, jealousy
    progression.md        levels & XP pacing, HP & Death's Door, skills, combat, balance, interaction ideas
    story_schema.md       how to write scene JSON
tools/story.py            validate · tracker · play · fuzz · script
game/                     the Godot project (open game/project.godot)
  content/                all narrative data
  src/autoload/           GameState, Dice, Skirmish (combat), StoryEngine
  src/ui/                 the visual-novel screen + HUD + character sheet
  src/combat/             tactical grid combat (to build)
  tests/smoke_test.tscn   headless auto-player for the Godot runtime

Why Godot + GDScript + JSON?

Free, lightweight, great 2D/UI and tile-map tools, a Python-like language, and JSON support built in — the gentlest path for a first game that still scales to a full release. The full reasoning and alternatives are in docs/design/architecture.md.

Exporting

JSON isn’t a Godot resource, so add *.json under Export → Resources → Filters to export non-resource files, or your build will start with no story.