LOCAL ARTIFACTS

Use the preserved records directly.

These downloads keep the route, character, unit, and practical guidance available even when an external source is unavailable.

Campaign route

Structured 27-entry Prologue-through-Epilogue sequence, labeled transcript cross-check.

Open route JSON ↗

Unit identity ledger

Sixteen unit roles, visible plate captions, and the provisional Ghast boundary.

Open unit JSON ↗

Battle practices

Local tested/observed command-discipline notes with source paths and limits.

Open battle digest ↗

Cluster-map option

Future battlefield density-map concept, with Bagrada’s missing telemetry and evidence requirements stated plainly.

Open design note ↗

MYTH II · LOCAL SOURCE LIBRARY

Source digests.

Useful information from the manuals, technical references, campaign records, and community services is summarized here in Jesse’s own reading library. You can learn the working facts without leaving the site; the original source remains available for attribution, page-level checking, or live status.

How to read this page. These are original summaries, not copied manuals. “Documented” means the source states it directly. “Community technical” means a maintained tool or service reference. “Fan cross-check” is useful context that still needs a primary journal or runtime capture before it becomes canon.

01 · SOURCE DIGESTS

What each source contributes.

Every digest answers the practical question: what did we retain locally, and why would you still open the original?

PRIMARY GAME SOURCES

The game’s own reference layer.

DocumentedManual

Myth II: Soulblighter manual

Local digest: the manual establishes the campaign frame, the Great War’s aftermath, Alric and Soulblighter, the glossary, unit roles, default controls, formations, special abilities, and the structure of multiplayer setup.

  • Select units by click, band selection, double-click type selection, or Shift-click additions.
  • Use Hold, Stop, Scatter, Retreat, formations, and Special as distinct orders; defaults can be changed in Preferences.
  • The tutorial is the recommended first practice map; F8 displays the key reference in-game.

We retain the factual outline and control table locally; we do not reproduce the manual’s pages or dialogue.

DocumentedEarlier campaign

Myth: The Fallen Lords manual

Local digest: the first manual supplies the lead-in to Soulblighter—the Light’s war against the Fallen Lords, the role of Alric, the older Connacht/Balor identity, and the locations that return in later history.

  • Use it to anchor Connacht, the Trow, the Myrkridia, the Nine, Rhi’Anon, and the Great Devoid.
  • Keep its campaign history separate from later fan chronology and transcript wording.

The local archive connects these terms to the Myth II chronology without treating a fan retelling as a new primary source.

TECHNICAL PRESERVATION

Tools, maps, and safe boundaries.

Community technicalLoathing

Project Magma Loathing documentation

Local digest: Loathing is the terrain and mesh workspace for Myth II maps. A color map defines visible terrain; a displacement map defines height; terrain/passability, shadow, reflection, media, and scenery layers are separate concerns.

  • Color-map dimensions must be divisible by 256 for the documented workflow.
  • Good maps require iteration: establish the mesh, import layers, inspect passability and lighting, then test the result in the game.
  • Editor acceptance is not the same as a Myth-runtime or multiplayer pass.
Community technicalFear

Project Magma Fear documentation

Local digest: Fear edits tag-level data and map references. Meshes contain references to landscape, media, lighting, weather, and strings; major terrain, unit, and scenery changes belong in Loathing rather than being forced into the tag editor.

  • Use Fear for controlled tag edits and Loathing for major mesh work.
  • Map actions are safer to learn by studying working examples before inventing new scripts.
  • Keep a disposable copy, record hashes, and mark any untested runtime behavior as unknown.
PreservationVersion notes

Project Magma release documentation

Local digest: maintained releases document modern compatibility, updated mapmaking tools, and changes in the 1.7–1.8.5 line. These notes explain the preservation layer around the original game; they do not rewrite campaign canon.

  • Use version notes to identify which tool behavior belongs to which release.
  • Record the exact build before comparing a map, plugin, or save.

CAMPAIGN CROSS-CHECKS

Useful chronology, clearly labeled.

Fan cross-check25 entries

Myth Journals · The Fallen Lords

Local digest: the indexed route runs from Crow’s Bridge through Bagrada, Forest Heart, the Tain, the Great Devoid, and Rhi’Anon. We use it as a dated reading order that connects locations; exact wording and dates remain secondary until matching in-game journal pages are captured.

The Field Archive already contains the route locally, so readers can follow the historical sequence without depending on the external index.

Fan cross-check27 entries

Myth Journals · Soulblighter

Local digest: the Prologue-through-Epilogue index provides a convenient mission reading order, including Willow Creek, the Baron, Relic, The Summoner, and the late Soulblighter arc. We retain the factual sequence and label transcript wording as fan-hosted until runtime capture confirms it.

The local archive includes all 27 mission links and concise summaries; opening the original is optional verification, not the only way to learn the sequence.

Secondary sourceHandbook

The Myth II Handbook

Local digest: the handbook is used for secondary explanations of units, maps, and play patterns. It can suggest a research lead, but manual text, a reproducible experiment, or a captured game result outranks it.

  • Use it to find questions worth testing, not to silently upgrade an interpretation to fact.
  • Keep the source label visible when a page depends on it.

COMMUNITY RECORDS

Live services and measured evidence.

Community serviceFAQ

Bagrada metaserver and FAQ

Local digest: Bagrada documents the modern lobby, room categories, ranking context, and Discord connection points. Its status is time-sensitive, so the archive records the date of each browser check rather than claiming a permanent census.

  • Live status is a point-in-time observation, not proof that every player or room is visible.
  • Room, ranking, and connection notices are retained with their limitations.
Community statisticsMethod note

Myth Tournament Stats

Local digest: replayed films and uploaded matches can produce map, player, unit, damage, kill/loss, and derived command statistics. Those metrics are analytical records, not a complete census; command counts may overcount repeated or interpreted actions.

  • Use the data to compare a defined sample or investigate a question.
  • Do not turn a derived statistic into a universal gameplay rule.
Local evidenceJesse archive

Our research index and evidence log

Local digest: this is the control layer for the project. Each entry records what is documented, observed, tested, or unknown; a source URL, date checked, and the page or experiment it changes.

  • Reference book: a readable offline narrative.
  • Research index: structured entries and open queue.
  • Knowledge log: dated changes and evidence boundaries.
  • Archive manifest: SHA-256 integrity records for the captured library files.
  • Bagrada snapshot: privacy-sanitized room and game metadata with capture time.

LOCAL READING ROUTES

Start inside the library.

These routes are now the default way to learn. External sources are kept as citations and freshness checks, not as required reading.

History first

Read the Great War, the earlier campaign, Soulblighter’s return, and the mission-by-mission route.

Open history ↗

Play and battle

Use the local controls, formation notes, terrain guidance, and battle checklist before opening a match.

Open play guide ↗

Build and preserve

Follow the local technical tutorial, then use the source digests to understand which tool behavior is documented.

Open technical route ↗

Reviewed 2026-09-16. Summaries are original notes for this fan project. Myth II, Myth: The Fallen Lords, Bungie, Project Magma, Bagrada, and the referenced archives belong to their respective owners.

OFFICIAL GUIDE DIGEST

Use the period guide as a map, not a shortcut.

This local digest records the preserved 1999 strategy guide’s chapter structure across units, combat, campaign, multiplayer, and development history. It keeps the guide’s advice useful while marking secondary, runtime-needed, and unknown claims.

Open official guide digest ↗

HISTORY DIGEST

Start with the locally preserved frame.

Our downloadable history digest keeps documented orientation separate from draft community context, so readers can learn the story without treating every community summary as canon.

Open history digest ↗

STORY ARC READER

Follow the campaign as five movements.

This local guide turns the 27-mission route into a readable story arc without reproducing journal text or hiding the evidence limits.

Open the story arc reader ↗

UNIT DIGEST

Read the role notes directly.

The Unit Foundations digest explains ten local role summaries and records the observed presentation corrections: WIGHT label → Soulless study, prior Ghoul label → Myrk/Myrkridia study, and Thrall label → Ghast study.

Open unit digest ↗

CHARACTER DIGEST

Meet the named figures.

The Character Foundations digest gives readable records for the central figures, the Nine, and the Fallen while keeping transcript-only details visibly provisional.

Open character digest ↗

CHARACTER RELATIONSHIPS

See the connections at a glance.

This local map links the named figures and groups while keeping cross-checks and runtime-needed claims visible.

Open the relationship map ↗

COMMUNITY PULSE

See the dated live observation.

The privacy-safe Community Pulse digest explains what the latest Bagrada metadata showed—and what it cannot prove.

Open community digest ↗

LOCAL COMMUNITY LEDGER

Compare the captures here.

The four Bagrada observations are preserved and compared locally, so the external service is optional verification rather than the only place to learn what changed.

Open the capture ledger ↗ Submit a Scout/BigC capture ↗

CLAIM REGISTER

See what is known—and what is not.

The claim register gives every major statement a plain evidence label and points to the local record behind it. Unknowns stay visible until a stronger capture or runtime test supports promotion.

Open the claim register ↗

OPEN EVIDENCE QUEUE

See what needs proof next.

Use the queue to understand which journal captures, canonical unit pairings, community records, and cluster-map inputs are still open.

Open the research queue ↗ Capture a journal page ↗

LOCAL GLOSSARY

Get the names straight.

The local glossary explains campaign terms, unit names, and the supplied visual-label corrections without hiding what remains unproven.

Open the glossary ↗

LOCAL INGEST LEDGER

See how evidence enters the library.

This ledger shows which private notes were promoted, held back, or routed to the research queue.

Open the ingest ledger ↗

MULTIPLAYER + CO-OP NOTES

Practice the decisions that keep a force alive.

This local checklist covers scouting, spacing, explosive-unit handoffs, veteran safety, and co-op control without pretending draft guidance is engine proof.

Open multiplayer notes ↗