Oblivion Mod:Save File Format/Enabled

This page summarizes the Enabled, Disabled, and Enabled/Disabled subrecord which is common to ACHR, ACRE, and REFR change records. The page is designed to be included in those pages, but the information has been collected in one place to ensure that future updates are added to all appropriate places.

Enabled/Disabled

This value is true when byte 30 (0x80000000) is set in an ACHR/ACRE/REFR record's overall Flags. No subrecords or data are added to the record when this flag is set.

It is unclear, however, what this flag means. In text file dumps, this flag is described as "Enabled", "Disabled", or "Enabled/Disabled"; "Enabled/Disabled" is only used on NOT LOADED records. One logical explanation would be that this flag means the item's default status has been reversed: that objects which are initially enabled are disabled when this flag has been set, and vice versa. However, it does not seem to be that straightforward. For example, statistics from one save file show that:

• This flag appeared 450 times for objects identified in Oblivion.esm as being "disabled by default" (byte 19 set in the flags1 field).
  • 46 of these objects were "Disabled" according to the text file dump.
  • 404 of these objects were "Enabled" according to the text file dump.
• This flag appeared 932 times for objects identified in Oblivion.esm as being initially enabled (byte 19 was not set in the flags1 field).
  • 190 of these objects were "Disabled" according to the text file dump.
  • 742 of these objects were "Enabled" according to the text file dump.

In other words, in the majority of cases, this flag means that the object is Enabled, regardless of the object's initial status. It is unknown how savefile parsers are supposed to determine the correct meaning of this flag.

In a small number of cases (7 in the previous example), a property identified as meaning "Disabled" was also set.

Name	Type/Size	Info
N/A	0	No data is added to the record