diff --git a/docs/BOSS Metadata Syntax.html b/docs/BOSS Metadata Syntax.html index ffb76d9b..dcec61a3 100644 --- a/docs/BOSS Metadata Syntax.html +++ b/docs/BOSS Metadata Syntax.html @@ -79,8 +79,9 @@ h3{
  • Tag Data Structure
  • File Data Structure
  • Message Data Structure -
  • Plugin Data Structure
  • Location Data Structure +
  • Dirty Info Data Structure +
  • Plugin Data Structure
  • URL Hyperlinking
  • Condition Strings @@ -196,11 +197,11 @@ display: OBSE v18+

    Message Data Structure

    Messages are given as key-value maps. - -
    Key NameRequiredNotes +
    Key NameData TypeRequiredNotes
    typeThe type string can be one of three keywords, see the table below for their semantics. -
    contentEither simply a string, or a list of localised content data structures. If the latter, one of the structures must be for English. -
    conditionA condition string that is evaluated to determine whether the message should be displayed: if it evaluates to true, the message is displayed, otherwise it is not. See Condition Strings for details. +
    typestringThe type string can be one of three keywords, see the table below for their semantics. +
    contentstring or localised content listEither simply a string, or a list of localised content data structures. If the latter, one of the structures must be for English. +
    conditionstringA condition string that is evaluated to determine whether the message should be displayed: if it evaluates to true, the message is displayed, otherwise it is not. See Condition Strings for details.

    There are three message types: @@ -250,6 +251,48 @@ would be displayed as отмечать: An alternative example link, with no translations. + +

    Location Data Structure

    +

    This data structure is used to hold information on where a plugin is hosted online. It is not currently used by BOSS, but it was suggested that since the BOSS team receives a considerable number of plugin URLs, they should be recorded in a standard format, as there is no existing store of such information and it could prove useful in the future. +

    The data structure has two forms: the first is a simple string, and the second is a key-value map. The first form should be used for a URL without any associated version data, such as when it is not clear which version is found there, or when it is the only known hosting location for the plugin and as such hosts all available versions. The second form should be used when version data can be associated with the URL, such as when the URL only hosts a subset of the available versions of the plugin. +

    The simple form: +URL +

    where URL is a URL at which the plugin may be found. +

    The map form: + + +
    Key NameData TypeRequiredNotes +
    linkstringA URL at which the plugin may be found. +
    verstring listA list of versions that can be found at the URL. +
    +

    Examples: +http://skyrim.nexusmods.com/mods/19/ +or +link: http://steamcommunity.com/sharedfiles/filedetails/?id=87144366 +ver: + - 1.3.2c + + +

    Dirty Info Data Structure

    +

    This structure holds information on which versions of a plugin are dirty, and how many identical-to-master records, deleted records and deleted navmeshes (if applicable) it contains. Dirty info is given as a key-value map. + + +
    Key NameData TypeRequiredNotes +
    crchexadecimal integerThe CRC checksum of the dirty plugin, before cleaning. BOSS displays the CRCs of installed plugins in its report. The 8-character CRC should be preceded by 0x so that it is correctly interpreted. +
    utilstringThe utility that should be used to clean the plugin. This field supports URL Hyperlinking, and it is recommended that a URL to the game's cleaning guide is supplied. +
    itmintegerThe number of identical-to-master records reported for the dirty plugin. If the number is unknown, this field should not be supplied. If the number is known and zero, this field should be supplied. +
    udrintegerThe number of undeleted records reported for the dirty plugin. If the number is unknown, this field should not be supplied. If the number is known and zero, this field should be supplied. +
    navintegerThe number of deleted navmeshes reported for the dirty plugin. If the number is unknown, this field should not be supplied. If the number is known and zero, this field should be supplied. +
    +

    Examples: +crc: 0x3DF62AB +util: "http://www.creationkit.com/TES5Edit_Cleaning_Guide_-_TES5Edit TES5Edit" +itm: 4 +udr: 160 +nav: 0 + + +

    Plugin Data Structure

    This is the structure that brings all the others together, and forms the main component of a metadata file. It is a key-value map. @@ -263,7 +306,8 @@ would be displayed as
    incfile listAn unordered list of files that this plugin is incompatible with. If any of these files are present, an error message will be displayed.
    msgmessage listThe messages attached to this plugin. The messages will be displayed in the order that they are listed.
    tagtag listAn unordered list of Bash Tags suggested for this plugin. If a Bash Tag is suggested for both addition and removal, the latter will override the former when the list is evaluated. -
    urllocation listAn unordered list of location data structures (see below) for this plugin. If the same version can be found at multiple locations, only one location should be recorded. This metadata is not currently used by BOSS. +
    urllocation listAn unordered list of locations for this plugin. If the same version can be found at multiple locations, only one location should be recorded. This metadata is not currently used by BOSS. +
    dirtydirty info listAn unordered list of dirty info structures for this plugin.

    Example: name: "Oscuro's_Oblivion_Overhaul.esm" @@ -286,26 +330,6 @@ msg: content: 'Do not clean. "Dirty" edits are intentional and required for the mod to function.' -

    Location Data Structure

    -

    This data structure is used to hold information on where plugins are hosted online. It is not currently used by BOSS, but it was suggested that since the BOSS team receives a considerable number of plugin URLs, they should be recorded in a standard format, as there is no existing store of such information and it could prove useful in the future. -

    The data structure has two forms: the first is a simple string, and the second is a key-value map. The first form should be used for a URL without any associated version data, such as when it is not clear which version is found there, or when it is the only known hosting location for the plugin and as such hosts all available versions. The second form should be used when version data can be associated with the URL, such as when the URL only hosts a subset of the available versions of the plugin. -

    The simple form: -URL -

    where URL is a URL at which the plugin may be found. -

    The map form: - - -
    Key NameData TypeRequiredNotes -
    linkstringA URL at which the plugin may be found. -
    verstring listA list of versions that can be found at the URL. -
    -

    Examples: -http://skyrim.nexusmods.com/mods/19/ -or -link: http://steamcommunity.com/sharedfiles/filedetails/?id=87144366 -ver: - - 1.3.2c -

    File display strings and message content strings (including the strings in localised content structures) that contain recognised URLs have them displayed as hyperlinks in the BOSS report. Recognised URLs are those that are enclosed in double quotes and that begin with file:, http: or https:.