I assume this is due to a difference between file versions, or something. However, looking at the masterlist, I noticed two ITMs listed for hearthfireextended.esp, and this confused me. I am very new to GitHub (and I have zero coding experience), however I did take a look at making a pull request for this. I suggest removing the ITM warning, and perhaps putting a warning in to not clean the mod. This information is slightly incorrect, as LOOT does in fact show one ITM, and recommends cleaning in TES5Edit. This record is required for steward dialogue to function correctly, so I don't recommend you do this.)" (While LOOT recognises that the mod is clean, cleaning with tes5edit actually does remove one record. The mod author states on the Nexus description page ( ): The plugin name is: hearthfireextended.esp Is treated as a localised content data structure.I am using Hearthfire Extended (the "All DLCs - Legendary Edition" version), v1.03. Two plugin cleaning data structures are equal if all their fields are equal. The number of deleted navmeshes reported for the dirty plugin. The number of undeleted records reported for the dirty plugin. A levelled list tailors loot, NPCs and spells to your characters level Wyre Bash will check if mods can be merged with your Bashed Patch to reduce the number of mods. The number of identical-to-master records reported for the dirty plugin. Next, you can scan your mods for dirty edits and clean them using TES5Edit A Bashed Patch can be created that updates your levelled list to allow mods to better co-exist. If undefined, defaults to an empty string. This is only used if the plugin is dirty, and is intended for providing cleaning instructions to the user. If a localised content list is provided, one of the structures must be for English. If a string is provided, it will be interpreted as CommonMark. detailĪ message that will be displayed to the user. The string will be interpreted as CommonMark. If available, the version of the utility used should also be included (e.g. The utility that was used to check the plugin for dirty edits. The 8-character CRC should be preceded by 0x so that it is interpreted correctly.
LOOT displays the CRCs of installed plugins in its report. If the plugin is dirty, this needs to be the CRC of the plugin before before cleaning. Cleaning data is given as a key-value map. This structure holds information on which versions of a plugin are dirty or clean, and if dirty, how many identical-to-master records, deleted records and deleted navmeshes (if applicable) it contains.
0 kommentar(er)
