Struct BattleSetup 

pub struct BattleSetup { /* private fields */ }

The resolved battle configuration: record directories, field mapping and the type chart. Built lazily on the first startBattle (projects without a battle section never pay for it, and projects that never battle never fail on a broken section).

Implementations

impl BattleSetup

pub fn from_project(project: &LoadedProject) -> Result<Self>

Resolve the manifest’s battle section against the project’s data tables and rules file.

Errors

Fails when the section is absent, a referenced table id names no declared data table, or the rules file exists but does not parse.

pub fn start(&self, enemy_id: &str, rng: Box<dyn BattleRng>) -> Result<Battle>

Build a battle with a FRESH party state (every member at full HP/MP, no status) and the manifest’s starting inventory. Convenience for tests and tools; the runner calls start_with.

Errors

Fails when the party table holds no readable record.

pub fn start_with( &self, enemy_id: &str, rng: Box<dyn BattleRng>, party_state: Option<&[PartyMemberState]>, inventory: Option<&HashMap<String, u32>>, ) -> Result<Battle>

Build a battle: the WHOLE party table (sorted by record id) against enemy_id. Resolution order (v2-d): when the manifest has an encounters block AND enemy_id names an encounter record, the enemy side is that record’s ordered enemy party (a queue) with its trainer flag and money reward; otherwise enemy_id names an enemy record (a single implicitly-wild enemy); an id in NEITHER table falls back to the first enemy record with a warning. party_state (runner-owned, from the previous battle or a save) re-applies current HP/MP/status per member id — base stats always come fresh from the records; inventory overrides the manifest’s items.starting counts. The first LIVING member leads; a party with no living member arms an immediate loss.

Errors

Fails when the party table holds no readable record, or when the encounter record is malformed (no enemies list, or an enemy id in it that names no enemy record).