MYTH II · TUTORIAL PATH
Learn from evidence. Test the rest.
These lessons make each process explicit: what it is, why it matters, how to do it, common mistakes, evidence status, and the next lesson.
01 · Story and timeline
What / why: Build a dated sequence from primary references. Steps: identify a source, record scope and date, compare a second reference, and flag disagreement. Status: method verified; entries pending review.
02 · Light and Dark factions
What / why: Connect faction identity to battlefield roles. Steps: classify the claim, cite it, test it in a controlled scenario, and separate mod behavior. Mistake: turning a balance preference into canon.
03 · Unit field guide
What / why: Document role, strengths, and counters with provenance. Steps: register the asset filename and dimensions, attach approval, write evidence-backed notes, and list unknowns.
04 · Combat and formations
Choose one question, capture a baseline, hold context constant, run three trials, compare, and archive the evidence. Do not generalize from one map, difficulty, or mod.
05 · Terrain, weather, explosives, and magic
Change one environmental factor at a time while holding unit and objective constant. Preserve screenshots and logs, and label visual interpretation separately from engine behavior.
06 · Fear, Loathing, mapmaking, and recovery
Keep originals immutable, document conversions, inspect alpha and color plates separately, and render derivatives for review. Evidence is not automatically runtime proof.
07 · Canon versus community
Label every claim as official/canonical, community reference, non-canonical/mod content, or inference. Link and attribute; do not copy protected text or images.