VerifiedBuild 2026.08.11.1121610.2-Rel-i343-Meteorite-2607-CU4

Console commands

Every function the Blam engine inside Halo Campaign Evolved will accept at its console, with the signature it expects and whether this build still carries the code behind it. Read from the function table in the shipped simulation DLL, not from an older Halo.

Functions
1,551
Work in this build
1,127
Compiled out
424
Globals
260 · 43 live

Search console commands

Type part of a name: player_, teleport, cheat

By family

Names share a prefix with the system they belong to. Each family is one page, with every function anchored.

Running them

The game ships the console but nothing feeds it. The MJOLNIRBlamConsole mod in the code-mod set wires the Unreal console to it: type a name with its arguments and the engine compiles and runs the line on its simulation thread. A bare name needs no punctuation; a nested expression takes the blam prefix.

ai_enabled                              = true  (boolean)
player_teleport player0 my_flag
fade_out 0 0 0 30
blam (unit_get_health (player0))        = 1.000000  (real)
help object_                            every name containing "object_"

Answers show on screen and on the UE4SS console. A function marked compiled out is accepted and does nothing: the release build replaced its body with a shared stub, and every cheat_* is among them. A global marked no storage reads as zero and ignores writes.

How the mod works, and what it took to find the console: The Blam console.

Where this comes from

The simulation DLL carries the engine's function table: 1,695 slots, one per overload, each with a name, typed parameters, a return type and the address of its evaluator. The mjolnir console command reads that table and the globals array out of the PE image, and marks the slots whose evaluator is the shared stub. The help strings are the one thing the table no longer has: the release build nulled every one, so the descriptions here are written by hand and cover 84 functions so far.

Where a function is called by the shipped campaign scripts, the page says how often and with how many arguments. That is observed usage, recovered from the compiled scripts, not a declaration.