ARMO records hold information on a piece of armor (has a heavy/light classification and an armor rating).
Subrecords known to occur in an ARMO record include (confirmed):
-
- EDID (required): Editor ID (variable length string)
- FULL (required): Item name (variable length string)
- SCRI (optional): Script form ID (dword)
- BMDT (required?): Flags (dword)
- MODL (optional): Male biped model filename (variable length string)
- MOD2 (optional): Male world model filename (variable length string)
- MOD3 (optional): Female biped model filename (variable length string)
- MOD4 (optional): Female world model filename (variable length string)
- MODB (optional): Unknown, follows a MODL (4 bytes)
- MO2B (optional): Unknown, follows a MOD2 (4 bytes)
- MO3B (optional): Unknown, follows a MOD3 (4 bytes)
- MO4B (optional): Unknown, follows a MOD4 (4 bytes)
- MODT (optional): Unknown, follows a MODT (variable size)
- MO2T (optional): Unknown, follows a MO2T (variable size)
- MO3T (optional): Unknown, follows a MO3T (variable size)
- MO4T (optional): Unknown, follows a MO4T (variable size)
- ICON (optional): Male icon filename (variable length string)
- ICO2 (optional): Female icon filename (variable length string)
- ANAM (optional): Enchantment points (word)
- ENAM (optional): Enchantment form ID (dword)
- DATA (required): Armor data (14 bytes)
DATA Subrecord
This subrecord is always 14 bytes long (confirmed) and holds the armor data.
| Name | Type/Size | Info |
|---|---|---|
| Armor | 2 (word) | Divide by 100 to get the actual in-game value. |
| Value | 4 (dword) | Armor value |
| Health | 4 (dword) | Armor health rating |
| Weight | 4 (float) | Armor weight |
BMDT Subrecord
Holds various armor flags.
- Biped Object Flags -- 0x0001 to 0x8000 (mask 0xFFFF). See Tes4Mod:Biped Object Flags for details
- General Flags
- 0x00010000 = Hide Rings
- 0x00020000 = Hide Amulets
- 0x00400000 = Non-Playable (opposite to checkbox in the CS)
- 0x00800000 = Heavy armor
- 0xCD000000 = Unknown default value
MODB/MO2B/MO3B/M04B Subrecord
These subrecords seem to follow an associated MODL/MOD2/MOD3/MOD4 and are always 4 bytes in size (confirmed). Unknown purpose.
MODT/MO2T/MO3T/M04T Subrecord
These subrecords seem to follow an associated MODB/MO2B/MO3B/M04B and have a variety of sizes: 24, 48, 72, 96, 120, 144, 192 bytes (confirmed).