MJOLNIR Research
Technical documentation
Curated findings for Halo Campaign Evolved's UE5 and Blam architecture. Claims are separated from hypotheses so each result can be checked and revised as the game changes.
Active research
Tag definitions
Field-level reference for all 101 tag groups: 11,216 fields with names, types, byte offsets, and enum options, generated from the shipped game data.
Read researchConsole commands
Every Blam console function in the game: 1,551 names with signatures and return types, 1,127 of them live in this build, plus 260 engine globals. Read from the simulation DLL.
Read researchBlam tag data
12,328 real Blam tag files ship inside Unreal packages across 101 classic tag groups. Container format, inventory, and the simulation-versus-rendering split.
Read researchSelf-describing tag layout
Every tag carries its own field definitions. The blay layout section ships real Guerilla field names, type names, and enum options for all 101 groups.
Read researchMultiplayer viability
Inventory of retained multiplayer systems, packed content, campaign worlds, and the shortest route to a CTF prototype.
Read researchHaloSimulation_tag_release.dll
Build fingerprint, factory ABI, shell object layout, interface tables, and the UE5 loader call path.
Read researchGuides
View allFollow one start to finish and you will have done the thing. New here? Start with your first tag edit.
Getting Started: Your First Tag Edit
This walks the whole path, from a clean install to a value you changed showing up on the HUD. It
Making Your First Mod
mjolnircore.com account (Discord sign-in) if you want to publish
Getting Started: Editing Halo Campaign Evolved Tags
A practical guide to reading and changing Blam tags, with the mjolnir command line
Swapping a Texture
mjolnir command line
Making a custom level
The MJOLNIR level pipeline is this game's answer to the old Halo Editing Kit:
Driving the Game From Outside
2026.06.26.1097863.1-Rel-i343-Meteorite-2606-CU2 (Steam).
Research notes
View allRaw investigation logs rendered from the repository, including reproduction commands and superseded conclusions. The curated pages above summarize what these established.
Build Lock
Every finding in docs/ is only true of the build it was measured on, and the game updates without
Game Update Pipeline
Steam updates the game in place. The moment a patch lands, the previous build is gone, and with
Blam Tag Data in Halo Campaign Evolved
Does Halo Campaign Evolved run on real Blam tag data like the classic games, or are bipeds,
Blam Tag Body Format (`blay` Layout Section)
Verified: the Blam tag body that follows the 0x4C-byte container header is
Getting an Edited Tag Into the Game
with the P patch suffix mounts, wins the chunk lookup, and its Blam payload is what the
Cooked Texture2D / Virtual Texture Format in Halo Campaign Evolved
A shipped Texture2D in this build cooks one of two ways, and both are common:
Where the Audio Lives in Halo Campaign Evolved
Almost none of the game's audio is reachable through the IoStore reader. The
HaloSimulation_tag_release.dll Analysis
| Property | Value |
The Blam console
Halo Campaign Evolved's simulation DLL still carries the classic Blam
MJOLNIR Multiplayer Investigation — Session Notes
| What | Path |
The `.mjolnir` Release Archive
A .mjolnir file is a plain zip with a manifest at the root and IoStore
MJOLNIR Hub — Mod Distribution Architecture
deviations each phase note records. Phase 4 has not started. Section headings note what is live.
Mod Authoring: Design
distribution are future phases.
The MJOLNIR level format (`.level.json`)
The interchange format of the level authoring pipeline: what the Blender exporter writes, what
Mod Signing and Attribution: Design
0005 carries the key registry and per-release attribution. Rollout step 2
Contributing a Code Mod
mods — tags, textures, maps, sounds — you don't need any of this: upload a
Security advisory: the `arrayref` 0.3.10 supply-chain attack
On 2026-08-20 a malicious version of the widely used Rust crate arrayref
Evidence model
Reproduced by an executable check or direct decompilation.
Present in an artifact, but runtime reachability is not proven.
A testable interpretation of current evidence.
Proposed behavior that still needs a discriminating test.