xEdit Conflict Resolution

[mentaltyranny]

I am just found and used Deorder's custom settings for Mator Smash from a Reddit page linking to Google drive, and I have to say I am impressed (but that is another topic for another forum).  Anyway, I am examining the patch, and I have a concern.  For EnchClothesRobesMageDestruction01 "Novice Robes of Destruction" [ARMO:0010D668], and please note that this record is only affected by STEP mods, my custom patch didn't carry-through the armor template, as shown here on xEdit:

 

 

To be clear, I am NOT asking advice on how to make Mator Smash pickup the subrecord from Mage Outfit Texture Overhaul.esp.  Rather, I am asking if I should forward this subrecord in xEdit to my own conflict resolution patch at the bottom of my load order?  I looked up Armor Template in the Creation Kit wiki, and it says "f filled in, only the Name, Value, and Enchanting fields are used; all of the other values will be inherited from the template."  However for this record, as you can see, Mage Outfit Texture Overhaul.esp has a lot more subrecords than Name, Value, and Enchanting.  So I thinking that the Armor Template values actually aren't used in game, and when you select one in Creation Kit, it just loads the values from the record being used as template directly into the record.  Is my understanding correct?

Edited June 24, 2018 by mentaltyranny

[zilav]

Only you can know what you want in your game. Since you took your time to learn how template inheritence even work in CK (which already is a feature 99.99% mod users completely lack of) you should understand what data will end up winning for this armor in the game. However you understood it a bit wrong - when template is set, all of it's values are used instead of the ones specified in the record, apart from the Name, Value, and Enchanting.

[mentaltyranny]

  On 6/24/2018 at 5:42 AM, zilav said:

Only you can know what you want in your game. Since you took your time to learn how template inheritence even work in CK (which already is a feature 99.99% mod users completely lack of) you should understand what data will end up winning for this armor in the game. However you understood it a bit wrong - when template is set, all of it's values are used instead of the ones specified in the record, apart from the Name, Value, and Enchanting.

Wow... I was hoping that CK just populated the values into the record directly, leaving the template without a gameplay effect.  That really changes things for conflict resolution, both manual through xEdit and automated through Wyre Bash/Mator Smash.  Just to make sure I understand, assume in my example above that I copy the record from CustomSmash.esp to my My xEdits.esp at the bottom of my load order, and then pull over the template armor subrecord from Mage Outfit Texture Overhaul.esp into it.  Will it be the case that the keywords, including "WAF_ProtectiveClothingCCF_10" and a weight of 3 will be ignored in favor of the keywords and weight in the template, but still use the listed amount for value from the record itself?

 

Assuming that I am right... Interestingly, those keywords, including "WAF_ProtectiveClothingCCF_10" ARE in the template, but ARE NOT in the record itself, which means that Mator Smash results here changed little.  Namely it appears to have changed only value and weight (55 and 2 from the template, respectively) using subrecords from CCF, and technically did not change the armor the armor rating (as it is also 10 in template).

[zilav]

Everything is ignored when template is set apart from the Name, Value, and Enchanting. It is similar to NPCs inheritance, someone asked recently why some NPCs have "Fox" race. And the answer is the same - when record is inherited from the other one, it doesn't matter what values it has apart from the listed exceptions.

 

Mator Smash doesn't provide any special handling for templates afaik, it treats them as ordinary data fields like Weight or Value for example. But you'd better speak with Mator about that.

[Mator]

  On 6/25/2018 at 6:15 AM, zilav said:

Mator Smash doesn't provide any special handling for templates afaik, it treats them as ordinary data fields like Weight or Value for example. But you'd better speak with Mator about that.

That is correct.  There is no special handling for template fields in Smash.