Wickedness/heros
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Ruxu river line scenario

Browse Source
This commit is contained in:
Wickedness
2026-06-18 01:10:20 +09:00
parent c69dbc6c2b
commit 43fe7be4b0
5 changed files with 378 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/DATA_MODEL.md
View File

@@ -53,6 +53,7 @@ data/scenarios/039_hanzhong_approach.json
data/scenarios/040_hanzhong_gate.json
data/scenarios/041_hanzhong_settlement.json
data/scenarios/042_ruxu_advance.json
data/scenarios/043_ruxu_river_line.json
```
## Campaign
@@ -107,7 +108,8 @@ The campaign file defines scenario order, resource paths, and officers who are a
{ "id": "039_hanzhong_approach", "title": "Hanzhong Approach", "path": "res://data/scenarios/039_hanzhong_approach.json" },
{ "id": "040_hanzhong_gate", "title": "Hanzhong Gate", "path": "res://data/scenarios/040_hanzhong_gate.json" },
{ "id": "041_hanzhong_settlement", "title": "Hanzhong Settlement", "path": "res://data/scenarios/041_hanzhong_settlement.json" },
{ "id": "042_ruxu_advance", "title": "Ruxu Advance", "path": "res://data/scenarios/042_ruxu_advance.json" }
{ "id": "042_ruxu_advance", "title": "Ruxu Advance", "path": "res://data/scenarios/042_ruxu_advance.json" },
{ "id": "043_ruxu_river_line", "title": "Ruxu River Line", "path": "res://data/scenarios/043_ruxu_river_line.json" }
]
}
```
@@ -239,6 +241,8 @@ Scenario `formation.cells` controls the highlighted starting cells available dur
Scenarios should use deployments rather than full inline unit stat blocks. `DataCatalog` will resolve officer, class, and item references into runtime unit dictionaries. Scenarios may also define briefing text, visible objective text, battle conditions, and victory rewards.
Scenario deployments may override `move_type` for special units. For example, a river boat can keep an existing combat class but set `"move_type": "water"` so it can deploy and path on `W` water tiles while normal foot, mounted, and archer units treat those cells as impassable.
```json
{
"id": "001_yellow_turbans",

5
docs/ROADMAP.md
View File

@@ -21,7 +21,7 @@
- Destination victory conditions and objective map markers exist.
- Turn-limit conditions and HUD turn-limit display exist.
- Victory reward summary is visible.
- Next-battle flow exists across the current forty-two-scenario campaign.
- Next-battle flow exists across the current forty-three-scenario campaign.
- Campaign completion and new-campaign reset exist.
- Reward inventory can be brought into the next battle.
@@ -52,7 +52,7 @@
- Party roster persistence has a first save-file skeleton.
- Level, experience, and equipment persistence.
- Chapter selection and save/load.
- Linear forty-two-scenario campaign order exists.
- Linear forty-three-scenario campaign order exists.
- Save reset exists.
- Victory rewards, consumable counts, equipment stock, and equipped gear persist.
- A basic pre-battle shop with scenario-specific stock exists. Sell-back and richer item management are still planned.
@@ -102,6 +102,7 @@
- Fortieth-scenario content exists with Hanzhong gate pressure, Zhang Lu's mountain guard, pass-road siege stakes, 039 branch reactions, and submission or pacification follow-up flags.
- Forty-first-scenario content exists with Hanzhong basin settlement, storehouse pressure, Zhang Lu submission or pacification branch reactions, and Hanzhong garrison or Ruxu pivot follow-up flags.
- Forty-second-scenario content exists with Ruxu riverbank pressure, Wu vanguard resistance, Hanzhong garrison or Ruxu pivot branch reactions, and Ruxu bank or Sun Quan river-line follow-up flags.
- Forty-third-scenario content exists with Ruxu river-line pressure, water-move enemy boats, Ruxu bank or Sun Quan line branch reactions, and Ruxu camp or crossing follow-up flags.
## Milestone 5: Presentation