Add Ruxu river line scenario
This commit is contained in:
@@ -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",
|
||||
|
||||
Reference in New Issue
Block a user