Object lists

Reach ships a folder of plain-text object lists beside the Megalo scripts. In a default Halo Reach Editing Kit (HREK) install they live at:

data/multiplayer/megalo/object_lists/

(for example …/HREK/data/multiplayer/megalo/object_lists/ under Steam).

Bungie's Megalo editor (MegaloEdit) loads these files for autocomplete, syntax help, and the Help menu reference lists. The game engine uses the same tables to turn symbolic names in scripts into numeric indices when a gametype or custom variant is compiled.

These lists correspond to data in the loadout_globals_definition (lgtd), megalo_string_id_table (msit), and multiplayer_object_type_list (motl) tags.

Custom maps

Everything in the object lists corresponds to data in your tags. That lets you author Megalo scripts for custom maps with custom objects, weapons, vehicles, and other map-specific entries — not just stock Reach content.

Format

Each file is a simple lookup table:

• One entry per line — a snake_case identifier with no punctuation.
• Line order is the index — the first line is index 0 (or id 1 where noted below). Blank lines in some lists (notably incidents.txt) still consume an index slot in the engine.
• Names are stable vocabulary — you type them literally in Megalo source (action create_object warthog …, submit_incident kill, and so on).

These lists are not Megalo script elements. They are engine data that scripts reference by name.

What each file is for

File	Entries	Used for
objects.txt	~220	Master object type table. Weapons, vehicles, equipment, scenery, spawn points, Forge objects, and special markers. Referenced by create_object, set_pickup_filter, set_respawn_filter, object_matches_filter, respawn/vehicle actions, and map_object type fields.
weapons.txt	24	Player trait primary/secondary weapons. Subset of objects.txt in a fixed order. Used in player_traits blocks (primary_weapon, secondary_weapon). Indices are resolved against which object types the gametype actually uses.
equipment.txt	10	Player trait equipment slot. Armor abilities and equipment (sprint_equipment, jet_pack_equipment, …). Same absolute-index rules as weapons.
vehicles.txt	34	Vehicle names for trait and filter operands where the editor offers a vehicle picker (subset of entries from objects.txt).
grenades.txt	4	Grenade types in player_traits initial_grenades (frag_grenade, plasma_grenade, spike_grenade, firebomb_grenade).
incidents.txt	~470	Game incidents for submit_incident and submit_incident_with_custom_value. Covers kills, medals, mode events (CTF, KOTH, Infection, …), survival, achievements, and announcer triggers. Incident ids are 1-based (first line = incident 1).
loadout_palettes.txt	15	Loadout palette presets for set_loadout_palette and override loadout_palette (slayer_loadouts, objective_loadouts, firefight palettes, …).
loadouts.txt	~80	Loadout display names (loadout_name_carter, loadout_name_ninja, …). Used by the editor and UI when presenting loadout choices, not as action opcodes.
weapon_sets.txt	16	Weapon restriction presets for override weapon_set in game_options. See Weapon Set for sentinel tokens (none, default, random) and the full preset list.
vehicle_sets.txt	14	Vehicle restriction presets for override vehicle_set (mongoose_only, no_aircraft, all_vehicles, …). See Vehicle Set for sentinel tokens and indices.
hud_widget_icons.txt	33	HUD widget icons for hud_widget_set_icon (slayer, ctf, koth, generic_icon_2, …).
strings.txt	~58	Device animation / string tokens for device_animate_position and related device actions (map-specific animation names like mp_boneyard_a_fly_in, plus generic entries such as default and none).

Relationship to objects.txt

Most specialized lists are subsets or views of the master objects.txt table:

• weapons.txt and equipment.txt list names that also appear in objects.txt, but player traits encode them using a compressed absolute index that depends on which object types the gametype marks as used.
• vehicles.txt is a convenience list for vehicle pickers; vehicle types still resolve through objects.txt indices in compiled data.

When in doubt, check whether a name exists in objects.txt — that is the authoritative object-type namespace for spawn and filter actions.

See also

• Megalo language overview — map_object, player_traits, and actions that consume these names
• Megalo Versions — action opcodes per Reach build