dungeon

`nodes` is a list of already-shaped DungeonNode dicts ({"id", "type", "data"}) — this first-pass module doesn't add guided per-node-type defaults beyond registering the whole graph as one record; a later version could offer node-builder helpers the way weapon() offers tier resolution. The FIRST entry in `nodes` is where a run starts (see bot/engine_bridge.py's `dungeon["nodes"][0]["id"]`) — no separate `isStart` flag needed here the way the one-node-per- file `.resource` convention (modules/dungeon_node/v1) needs one, since this module's own node order is never ambiguous the way file discovery order across several separate files would be. `name`/`difficulty`/`image_id` are pure display/selection data, same "never read by the engine" spirit as an item's `icon_id` — added 2026-10-14 alongside this module finally getting a COMMUNITY_SCHEMA, for a `.resource`-authored dungeon's own outer block to carry something real beyond just `id`/`description`. `image_id` picks this dungeon's own cover art from assets/dungeons/<image_id>.png — no UI currently reads it (no "pick a dungeon" art surface exists yet, the same "accepted now, rendered later" situation several dungeon NODE fields were already in) — accepted anyway so the content model doesn't need a second migration once that surface exists.

Example Usage

This real example file builds more than one record — dungeon is one of several blocks (or a nested sub-block) in it, shown together because they reference each other.

resource "goblin_watch" {
  source: modules/dungeon/v1
  id: "goblin_watch"
  name: "Goblin Watch"
  description: "A sentry outpost goblins built out of salvaged watchtower stone, strike fast before their numbers call for backup."
  difficulty: 1.5
  image_id: "goblin_watch"

  combat_node {
    id: "watch_entry"
    enemy_group_id: catalog.goblin_pack
    next_node_id: "watch_fork"
    description: "Goblins posted at the gate scramble to meet you."
  }

  choice_node {
    id: "watch_fork"
    description: "Two paths lead deeper - a straight charge, or a careful search for weak stonework."
    fork{
      label: "Push straight through the courtyard."
      next_node_id: "watch_ambush"
    }
    fork{
    label: "Search for a weak point in the wall."
    stat_check {
      stat_check_stat_id: "luck"
      stat_check_difficulty: 3
    }
    on_pass {
      next_node_id: "watch_treasure"
    }
    on_fail {
      next_node_id: "watch_ambush"
    }
    }
  }

  combat_node {
    id: "watch_ambush"
    enemy_group_id: catalog.goblin_ambush
    next_node_id: "watch_treasure"
    description: "The goblins you passed catch up from behind."
  }

  reward_node {
    id: "watch_treasure"
    next_node_id: "watch_end"
    gold_given: 15
    essence_given_type_id: catalog.mana
    essence_given_amount: 5
    stat_exp_stat_id: "luck"
    stat_exp_amount: 2
  }

  terminal_node {
    id: "watch_end"
  }
}

Arguments Reference

The following arguments are supported:

• id - (Required) The unique id this record is registered and referenced under — what a `.resource` file's own filename-independent identity is, and what any other content's foreign-key-style field (a dungeon node's `next`, a skill node's `parent_id`, and so on) points at. community
• nodes - (Required) `nodes` is a list of already-shaped DungeonNode dicts ({"id", "type", "data"}) — this first-pass module doesn't add guided per-node-type defaults beyond registering the whole graph as one record; a later version could offer node-builder helpers the way weapon() offers tier resolution. developer
• name - (Optional) `name`/`difficulty`/`image_id` are pure display/selection data, same "never read by the engine" spirit as an item's `icon_id` — added 2026-10-14 alongside this module finally getting a COMMUNITY_SCHEMA, for a `.resource`-authored dungeon's own outer block to carry something real beyond just `id`/`description`. community
• description - (Optional) Flavor text shown to players — pure display data with no effect on game mechanics. community
• difficulty - (Optional) Defaults to 0.0. community
• image_id - (Optional) `image_id` picks this dungeon's own cover art from assets/dungeons/<image_id>.png — no UI currently reads it (no "pick a dungeon" art surface exists yet, the same "accepted now, rendered later" situation several dungeon NODE fields were already in) — accepted anyway so the content model doesn't need a second migration once that surface exists. community

Nested Blocks

These can't be set as flat key: value fields — write them as their own block_type { ... } inside this module's block instead (see the Example Usage above).