After I got the debug menu up and running, I went looking for the next thing the game wasn’t telling me about out of the box - because, of course I would.

It didn’t take too long, since I am writing this post so quickly after the previous one. As it turns out, there’s a bunch of customizations that are only partially exposed through the in-game UI, that you can set through some configuration *.ini files.

Halo: Campaign Evolved has a Difficulty Modifiers screen when you start a campaign mission. It gives you a handful of dropdowns where you can customize damage resistance, shield regeneration, player damage output, melee damage, and ammo, among others. This is actually a really neat feature that allows the player to adjust the game to the level of difficulty they feel like playing under, and I wish more games had this.

While the options in the UI are extensive as-is, digging through the binary and the associated content reveals that there are a few extra settings that can be configured that will make the playthrough a little bit more fun and enjoyable.

The other container

When I went after the debug menu, I only ever touched .pak files - repak pulled DefaultGame.ini straight out of pakchunk0-Windows.pak and that was the unlock. But that’s just a sliver of what the build we have on our hands is capable of.

The configuration file came out clean because .ini files aren’t Unreal assets. They get staged into the .pak as ordinary files rather than cooked packages, so extracting them is somewhat straightforward.

A .uasset, on the other hand, is a completely different animal. Cooked assets live in the IoStore containers - the .utoc and .ucas pairs sitting in the same folder:

...\steamapps\common\Halo Campaign Evolved\Meteorite\Content\Paks\

For those, we will need to use retoc - conveniently, from the same author as repak:

$ retoc unpack pakchunk0-Windows.utoc .\extracted

Unpacking pakchunk0 gives you two roots - Engine/ for engine and plugin content, and Meteorite/ for the game itself. The two assets I care about for this particular experiment both sit under Meteorite/Content/UI/Shared/Settings/ in the extracted data:

  • Widgets/WBP_DifficultyModifierMenu.uasset - the menu widget itself.
  • Data/DA_DifficultyModifierSettingsItems.uasset - the list of options it renders.

The second file is a plain data asset that contains the settings the menu builds its content from. Because the menu is configuration-driven, reading that file gets us quite a bit of context. Running strings over it is enough of a starting point to get what we need (we’re flying blind, after all).

Just to get ahead of folks thinking this is some kind of official asset parsing process that I am standing up - I am not. Reading a cooked Unreal Engine 5 .uasset properly requires the presence of a .usmap mappings file, which this game doesn’t ship. My goal here is to naively run strings over it and hope for the best. For a data asset that mostly contains names and paths - that turns out to be a fairly decent strategy.

The output we’d get from this is not going to be tidy. UE packs its strings back to back with no separators, so everything interesting arrives as a single blob:

$ strings -a DA_DifficultyModifierSettingsItems.uasset | grep VitalityTraits
@/Game/UI/Shared/Settings/Widgets/Buttons/WBP_MetUI_Dropdown_OptionEntrySettingsUI.Settings.PlayerTraits1VitalityTraits.DamageResistancePercentageSettingVitalityTraits.ShieldRechargeRatePercentageSettingWBP_MetUI_Dropdown_OptionEntry_CWeaponTraits.DamageModifierPercentageSettingWeaponTraits.InfiniteAmmoSettingWeaponTraits.MeleeDamageModifierPercentageSettingHaloUIViewItemDataDA_DifficultyModifierSettingsItemsSettingsViewItemDataDropdownEnumSettingsViewItemDataDropdownInt/Game/UI/Shared/Settings/Data/DA_DifficultyModifierSettingsItems

There’s no delimiter to split on because this isn’t really text in the traditional sense - it’s UE’s name table.

A few of the things here are just scaffolding: asset paths, the bare object name DA_DifficultyModifierSettingsItems, the dropdown row template WBP_MetUI_Dropdown_OptionEntry_C, view-item data classes that say how each row is rendered (HaloUIViewItemData, SettingsViewItemDataDropdownEnum, SettingsViewItemDataDropdownInt), a lone Settings, and the gameplay tag UI.Settings.PlayerTraits1 that the whole screen is bound to.

The ones that we really care about, though, are the following:

VitalityTraits.DamageResistancePercentageSetting
VitalityTraits.ShieldRechargeRatePercentageSetting
WeaponTraits.DamageModifierPercentageSetting
WeaponTraits.InfiniteAmmoSetting
WeaponTraits.MeleeDamageModifierPercentageSetting

Running strings over the aforementioned WBP_DifficultyModifierMenu.uasset turns up the same five trait paths. Seems like we’re on the right path.

Building out the shape

Notice that the paths are prefixed with VitalityTraits. and WeaponTraits., which means they are fields on some larger structure. To see it in a real, written-to-disk world, open this file:

%LOCALAPPDATA%\Meteorite\Saved\Config\<YourSteamID64>\HaloGlobalGameUserSettings.ini

Under [HaloUserSettings], the file’s only section,1 there are four preset slots. They start out empty:

ModifierPreset=None
PlayerTraits1=(VitalityTraits=(),WeaponTraits=(),MovementTraits=(),AppearanceTraits=())
PlayerTraits2=(VitalityTraits=(),WeaponTraits=(),MovementTraits=(),AppearanceTraits=())
PlayerTraits3=(VitalityTraits=(),WeaponTraits=(),MovementTraits=(),AppearanceTraits=())
PlayerTraits4=(VitalityTraits=(),WeaponTraits=(),MovementTraits=(),AppearanceTraits=())

Unreal writes out the four nested category structs even when every field inside them is carrying only its default value. The individual fields get omitted, which is why you get four sets of empty parentheses. This doesn’t give you the field names you need to modify, but it does hand you the shape for experimentation, and we will experiment here.

For the actual properties we need to modify for each trait, we need to go back to the executable. Because we are tinkering with PlayerTraits, it’s natural to use this as a search term - also with strings (or Select-String if you are on Windows).

Run the following against the Halo: Campaign Evolved executable in the game folder:

Select-String -Path "HaloCampaignEvolved.exe" -Pattern "\w*PlayerTraits\w*" -Encoding ascii -AllMatches |
  ForEach-Object { $_.Matches.Value } | Sort-Object -Unique

Or, if you have Windows Subsystem for Linux (WSL), Git Bash, or you’re actually on Linux or macOS like myself:

$ strings -a HaloCampaignEvolved.exe | grep -oE '\w*PlayerTraits\w*' | sort -u

Either way, you will see the following output:

BlamGameEnginePlayerTraits
GetPerPlayerTraits
HasModifiedPlayerTraits
PerPlayerTraits
PlayerTraits
PlayerTraits1
PlayerTraits2
PlayerTraits3
PlayerTraits4
SetPerPlayerTraits

The winning choice for us is BlamGameEnginePlayerTraits. Assuming that Blam-related items are prefixed with, well, Blam, we can take this a step further and see if we can find references to the player traits which are labeled the same way:

Select-String -Path "HaloCampaignEvolved.exe" -Pattern "BlamPlayerTrait\w+" -Encoding ascii -AllMatches |
  ForEach-Object { $_.Matches.Value } | Sort-Object -Unique

Or, for bash aficionados:

$ strings -a HaloCampaignEvolved.exe | grep -oE 'BlamPlayerTrait\w+' | sort -u

This will yield us the following list:

BlamPlayerTraitAppearance
BlamPlayerTraitMovement
BlamPlayerTraitVitality
BlamPlayerTraitWeapons

Well isn’t this a coincidence - it matches what we saw earlier in the config file.

The individual fields follow the convention too. Their enum types are prefixed EBlam, which is a far cleaner thing to search for (I can only assume E stands for Enum, duh!):

Select-String -Path "HaloCampaignEvolved.exe" -Pattern "EBlam\w*Setting" -Encoding ascii -AllMatches |
  ForEach-Object { $_.Matches.Value } | Sort-Object -Unique

And, in bash:

$ strings -a HaloCampaignEvolved.exe | grep -oE 'EBlam[A-Za-z]*Setting' | sort -u

We will now be in possession of a list like this:

EBlamActiveCamoSetting
EBlamDamageModifierPercentageSetting
EBlamDamageResistancePercentageSetting
EBlamInfiniteAmmoSetting
EBlamPlayerGravitySetting
EBlamPlayerSpeedSetting
EBlamRechargeRatePercentageSetting
EBlamRenderSetting

Ignore EBlamRenderSetting - it’s the regex biting a prefix off EBlamRenderSettingsChangeType, but the rest are types behind trait fields, and three of them describe things the Difficulty Modifiers menu has never once offered you:

  • EBlamPlayerSpeedSetting
  • EBlamPlayerGravitySetting
  • EBlamActiveCamoSetting

That regex doesn’t catch everything, though. Three fields (DeathlessSetting, WeaponPickupSetting, RechargingGrenadesSetting) share a single type called EBlamBooleanTrait, and ModifierPreset uses EModifierPresetSetting with no Blam prefix at all. We treat the convention is a useful lead rather than a generic rule.

Types are only half of it. We need the enumerators, and to the surprise of nobody we can extract them from the binary too, in Type::Value form:

Select-String -Path "HaloCampaignEvolved.exe" -Pattern "EBlamPlayerSpeedSetting::\w+" -Encoding ascii -AllMatches |
  ForEach-Object { $_.Matches.Value } | Sort-Object -Unique

For our bash friends:

$ strings -a HaloCampaignEvolved.exe | grep -oE 'EBlamPlayerSpeedSetting::[A-Za-z0-9]+' | sort -u

Now take a look here:

EBlamPlayerSpeedSetting::Num
EBlamPlayerSpeedSetting::Percent0
EBlamPlayerSpeedSetting::Percent100
EBlamPlayerSpeedSetting::Percent110
EBlamPlayerSpeedSetting::Percent120
EBlamPlayerSpeedSetting::Percent130
EBlamPlayerSpeedSetting::Percent140
EBlamPlayerSpeedSetting::Percent150
EBlamPlayerSpeedSetting::Percent160
EBlamPlayerSpeedSetting::Percent170
EBlamPlayerSpeedSetting::Percent180
EBlamPlayerSpeedSetting::Percent190
EBlamPlayerSpeedSetting::Percent200
EBlamPlayerSpeedSetting::Percent25
EBlamPlayerSpeedSetting::Percent300
EBlamPlayerSpeedSetting::Percent50
EBlamPlayerSpeedSetting::Percent75
EBlamPlayerSpeedSetting::Percent90
EBlamPlayerSpeedSetting::Unchanged

There are twelve trait fields in total. There are seven with no option to set from the menu:

ActiveCamoSetting
BodyRechargeRatePercentageSetting
DeathlessSetting
GravitySetting
RechargingGrenadesSetting
SpeedSetting
WeaponPickupSetting

So MovementTraits holds SpeedSetting and GravitySetting, and AppearanceTraits holds ActiveCamoSetting. Neither category has a dropdown anywhere in the game. Within the two categories the menu does show, it skips DeathlessSetting, BodyRechargeRatePercentageSetting, WeaponPickupSetting, and RechargingGrenadesSetting. But this, of course, doesn’t mean we can’t set these properties.

Secret traits not so secret anymore

Back in HaloGlobalGameUserSettings.ini, we can now start adding some of the things that we just discovered.

Our payload will touch only fields with no dropdown. We need to close the game first, since it rewrites this file on exit and will stomp whatever we typed. Then, we will replace the ModifierPreset and PlayerTraits1 lines in place with this blob:

ModifierPreset=Preset01
PlayerTraits1=(VitalityTraits=(DeathlessSetting=On,BodyRechargeRatePercentageSetting=Percent200),WeaponTraits=(WeaponPickupSetting=On,RechargingGrenadesSetting=On),MovementTraits=(SpeedSetting=Percent300,GravitySetting=Percent50),AppearanceTraits=(ActiveCamoSetting=Invisible))

We can now launch the game and start a new mission. You will know things are taking effect if you go into the Difficulty Modifiers view and see Preset 01 as the selected preset.

You are now moving at triple speed, jumping in half gravity, and fully invisible. Every one of those is as far as its enum goes. Percent300 tops the speed ladder, Invisible tops the camo one, and Percent50 is the floatiest gravity we can get.

The payload also sets DeathlessSetting, BodyRechargeRatePercentageSetting, WeaponPickupSetting and RechargingGrenadesSetting, because why not.

Values with no menu entry

Most typical dropdown options are enumerated in the same UI data asset. Those are the values the menu can produce and we can see them in-game.

The underlying enums, however, go further:

Setting Menu limit Extra value
DamageResistancePercentageSetting Percent2000 Invulnerable
DamageModifierPercentageSetting Percent300 Fatality
ActiveCamoSetting No menu entry Up to Invisible

Which lets you write this:

ModifierPreset=Preset01
PlayerTraits1=(VitalityTraits=(DamageResistancePercentageSetting=Invulnerable,ShieldRechargeRatePercentageSetting=Percent200,BodyRechargeRatePercentageSetting=Percent200,DeathlessSetting=On),WeaponTraits=(DamageModifierPercentageSetting=Fatality,MeleeDamageModifierPercentageSetting=Fatality,InfiniteAmmoSetting=BottomlessClip,WeaponPickupSetting=On,RechargingGrenadesSetting=On),MovementTraits=(SpeedSetting=Percent300,GravitySetting=Percent50),AppearanceTraits=(ActiveCamoSetting=Invisible))

Who wouldn’t want to play with triple speed, half gravity, invisible, invulnerable, one-shot kills and bottomless magazines!

Two limits to keep in mind:

  • Percent300 is the top speed. The ladder tops out at that value, at least from what I can tell looking at existing reverse-engineered values.
  • Percent50 is the lowest gravity. Unfortunately, it doesn’t seem like there is another lever for hang time.

The Halo engine underneath all of this ships as its own DLL, HaloSimulation_tag_release.dll, sitting in the same Binaries\Win64 folder. Blam tags describe their own fields, so those descriptions survive into the binary as plain strings - name, a #, then the help text:

$ strings -a HaloSimulation_tag_release.dll | grep -i 'unable to jump'
jump multiplier#use -1 for 'unchanged.'  0 will make the player unable to jump. 100 is default.

So a jump trait exists, it is separate from gravity, and 100 is its baseline - which also confirms these multipliers read the way you’d hope, with Percent50 gravity meaning floatier rather than heavier. The same dump has speed multiplier and gravity multiplier as sibling labels, and no jump multiplier equivalent anywhere in BlamPlayerTraitMovement, which exposes only SpeedSetting and GravitySetting.

The extracted asset package confirms what SpeedSetting actually drives. Under Meteorite/Content/Tags/multiplayer/game_variant_settings/player_traits_template/ the movement traits ship as four separate tags:

  • traits_movement_walking_speed
  • traits_movement_personal_gravity
  • traits_movement_jump_height
  • traits_movement_vehicle_useage

Walking speed and jump height are distinct traits. So SpeedSetting buys us horizontal movement, and the trait that would buy hang time is not wired up to anything we can set. Alas, maybe I am just missing some obvious option - do tag me in the comments if you find one. Let’s get back to testing, though.

The easiest way to test is to just launch the game. I know, very obvious - but you will instantly see the effect. I use Truth and Reconciliation as a test mission and you will see that I am camo-d up right from the start, with absurd speed, taking zero damage, and floating in the air.

Permanent camo mod in a Halo: Campaign Evolved mission.
Permanent camo mod in a Halo: Campaign Evolved mission.

See it in action:

Full value reference

Now that you know the basics, I thought I’d also provide a dump of all the values that you can set yourself. Use this at your leisure.

Preset selector

Field Accepted values
ModifierPreset None, Preset01, Preset02, Preset03, Preset04

None is the shipped default - it means that nothing is applied.

VitalityTraits

Field In menu Accepted values
DamageResistancePercentageSetting Yes Unchanged, Percent10, Percent50, Percent90, Percent100, Percent110, Percent150, Percent200, Percent300, Percent500, Percent1000, Percent2000, Invulnerable
ShieldRechargeRatePercentageSetting Yes Unchanged, PercentNegative25, PercentNegative10, PercentNegative5, Percent0, Percent10, Percent25, Percent50, Percent75, Percent90, Percent100, Percent110, Percent125, Percent150, Percent200
BodyRechargeRatePercentageSetting No Unchanged, PercentNegative25, PercentNegative10, PercentNegative5, Percent0, Percent10, Percent25, Percent50, Percent75, Percent90, Percent100, Percent110, Percent125, Percent150, Percent200
DeathlessSetting No Unchanged, Off, On

Less. The field is resistance, not damage taken, so higher is tougher - the menu tops out at Percent2000, and Invulnerable is one rung above it.

BodyRechargeRatePercentageSetting is health regeneration as opposed to shields.

DeathlessSetting is a plain boolean, and the engine’s trait variable table groups it with player headshot immunity, player assassination immunity and player vampirism, with a matching cheat_deathless_player debug command sitting nearby - so it should stop you dying.

WeaponTraits

Field In menu Accepted values
DamageModifierPercentageSetting Yes Unchanged, Percent0, Percent25, Percent50, Percent75, Percent90, Percent100, Percent110, Percent125, Percent150, Percent200, Percent300, Fatality
MeleeDamageModifierPercentageSetting Yes Unchanged, Percent0, Percent25, Percent50, Percent75, Percent90, Percent100, Percent110, Percent125, Percent150, Percent200, Percent300, Fatality
InfiniteAmmoSetting Yes Unchanged, Off, On, BottomlessClip
WeaponPickupSetting No Unchanged, Off, On
RechargingGrenadesSetting No Unchanged, Off, On

The damage menus stop at Percent300. For ammo, On stops it draining and BottomlessClip also removes reloading.

RechargingGrenadesSetting refills grenades over time.

WeaponPickupSetting is the one field here I can’t tell you the effect of. The older Blam tag definitions inside HaloSimulation_tag_release.dll carry it as a plain weapon pickup field in player_trait_weapons_block, and the engine has a player_disable_weapon_pickup script call sitting next to things like player_disable_movement - which reads like a permission toggle for whether you can pick weapons up at all, rather than a buff.

MovementTraits

Field In menu Accepted values
SpeedSetting No Unchanged, Percent0, Percent25, Percent50, Percent75, Percent90, Percent100, Percent110, Percent120, Percent130, Percent140, Percent150, Percent160, Percent170, Percent180, Percent190, Percent200, Percent300
GravitySetting No Unchanged, Percent50, Percent75, Percent100, Percent110, Percent120, Percent130, Percent140, Percent150, Percent160, Percent170, Percent180, Percent190, Percent200

AppearanceTraits

Field In menu Accepted values
ActiveCamoSetting No Unchanged, Off, Poor, Good, Excellent, Invisible

And just as a final note, PlayerTraits2 through PlayerTraits4 are preset slots 2 to 4, selected with ModifierPreset=Preset02, ModifierPreset=Preset03 and ModifierPreset=Preset04 respectively, if you want to have some supersoldier custom setups that you want to use on other missions.

Conclusion

Because this is the first public build, I am not certain that what you see above will last. At the same time, I am excited to continue digging and see what other settings I will find. I am sure there is more hiding in plain sight.


  1. This is an exception to something I said last time. The debug menu post claimed a config class’s section header must be [/Script/<Module>.<Class>], and this one is plainly [HaloUserSettings]. Some classes override the section name, and this is one of them - the rule holds everywhere it isn’t overridden, which is nearly everywhere. ↩︎