# Myth II Battle Practices — Local Evidence Digest

**Captured:** 2026-09-16  
**Scope:** Practical command discipline for Myth II map work and study.  
**Status:** Local fan research; not official Bungie balance doctrine.

## Evidence key

- **TESTED / OBSERVED** means the behavior was recorded during controlled Loathing Control repair work and should still be reproduced against the target map/build.
- **UNKNOWN** means the archive does not yet have enough runtime evidence to promote a claim.

## Command ownership

When Movement and Attack are repeatedly assigned to the same group, local tests observed oscillation, unstable pursuit, and visible role confusion. Treat command ownership as a deliberate handoff: let one command control the group’s immediate purpose, then stop or replace it intentionally.

**Evidence:** TESTED / OBSERVED  
**Source:** `C:/Users/roadw/Documents/MythSourceBot/knowledge/evidence_sources/loathing_control/movement_attack_command_ownership.md`  
**Limit:** This is a controlled repair observation, not a universal multiplayer guarantee.

## Attack windows and leashes

Repeated Attack refresh can create visible indecision. A broad, deliberate attack window is safer for role-stable groups; deactivation can act as a practical leash when the fireline must be re-clamped or pursuit must stop.

**Evidence:** TESTED / OBSERVED  
**Source:** `C:/Users/roadw/Documents/MythSourceBot/knowledge/evidence_sources/loathing_control/stable_attack_windows_and_leashes.md`  
**Limit:** Exact timing and behavior remain map- and build-dependent.

## Separate import proof from runtime proof

An editor or parser accepting a map does not prove that the action graph behaves correctly in-game. Preserve the imported specimen, then run a disposable save/reopen and in-game check with a visible expected result and a recorded failure result.

**Evidence:** TESTED / OBSERVED  
**Source:** `C:/Users/roadw/Documents/MythSourceBot/knowledge/evidence_sources/loathing_control/runtime_vs_import_validation.md`  
**Limit:** This workflow does not establish the exact semantics of every action field.

LOCAL STRATEGY-GUIDE CROSS-CHECK
DOCUMENTED, LOCAL PAGE-LEVEL SOURCE. The preserved strategy guide's combat-tactics chapters recommend treating explosives as a spacing problem (pp. 22-27), accounting for weather and terrain when planning bottles and arrows (pp. 27-39), grouping like units for quick control (p. 43), and using formations instead of letting large groups jumble together (pp. 44-45). These are historical tactical recommendations, not measured engine guarantees; the local Loathing observations remain separately labeled.

## What remains open

The archive still needs map/build-specific runtime captures before these observations become measured mechanics. Do not use this digest to claim that Bagrada provides unit coordinates or colored cluster values; that separate idea remains an optional research item.