MYTH II FIELD PLAYBOOK — LOCAL FOUNDATIONS
Recorded: 2026-09-16
Purpose: A practical, self-contained starting point for learning Myth II without importing assumptions from other real-time strategy games.

WHAT THE PLAYER IS MANAGING — DOCUMENTED
A normal Myth II battle gives the player a limited force rather than a base-building economy. There is no routine mining, production queue, or replacement-unit loop to fall back on. The durable skills are movement, spacing, formation control, range, terrain use, and preserving experienced units.

FIRST-BATTLE CHECKLIST — PRACTICAL GUIDANCE
1. Read hills, water, crossings, walls, and routes before committing.
2. Keep a front line between enemies and fragile ranged or support units.
3. Separate explosive specialists from the main group before they attack.
4. Give fast units a target and exit route; do not let a chase become an isolated fight.
5. Re-form after contact instead of allowing one uncontrolled blob.
6. Preserve veterans when a retreat is possible.

ROLE-BASED DECISIONS — DOCUMENTED ROLE MODEL
Melee holds space after contact; ranged pressures before contact; demolitions and area damage break groups but risk friendly fire; spellcasters and support change timing and shape; fast assault units reach exposed targets but can overextend; durable front-line units buy time but can still be outmaneuvered.

CO-OP — DRAFT
Assign explosive-unit control, movement calls, and objective watch. Avoid conflicting orders, call out ambushes, protect healers and veterans, and do not rush while the force is split.

MULTIPLAYER — DRAFT
Scout first, learn routes, protect ranged and explosive units, use terrain, communicate, and avoid clumping when the opponent can punish it. This is guidance, not a current ladder claim.

OPEN RUNTIME TESTS — UNKNOWN
Current bindings, formation behavior on slopes, projectile/friendly-fire edge cases, veteran persistence, and mission-specific scripted exceptions still need dated runtime captures.

PROVENANCE
Consolidated from C:\Myth2Bot\knowledge\gameplay\beginner_guide.md, unit_roles.md, coop_basics.md, multiplayer_basics.md, plus the local gameplay and battle-practice digests. Runtime proof is tracked separately in the evidence matrix and capture template.