[WIP] Mator Smash - The Conflict Resolution Revolution

[matortheeternal]

Thanks. I finally understand how "Treat as single entity" should be used. Testing it out right now. I still have some questions.

1. Did you add all those smash settings for the bash tags yourself or is there a way to get them automatically, and
2. How can I do what I showed inside the image I included in my previous post?

1. Yes, I added them myself through the Settings Manager
2. That's what my previous post answers.

[machuidel]

 

Thanks. I finally understand how "Treat as single entity" should be used. Testing it out right now. I still have some questions.

1. Did you add all those smash settings for the bash tags yourself or is there a way to get them automatically, and
2. How can I do what I showed inside the image I included in my previous post?

1. Yes, I added them myself through the Settings Manager
2. That's what my previous post answers.

 

 

Ah yes of course, thank you. I asked 2 questions both having the same answer.

[kociol21]

I used Mator Smash for the first time today. I just used Smash.All on my entire modlist as a noob I am. Firstly I did it out of curiosity but after comparing it in SSEEdit to my Bashed Patch and Merged Patch, I'm amazed. I had no clue that my Bashed Patch was missing so many things... Smash picked up like 25% more leveled lists entries. Also did far better job on conflict resolution than SSEEdit merged patch. I'm just gonna use it from now on. If anything, it went little too extensive in some places, like it restored some things in Perks from USSEP that Ordinator removed and I'm pretty sure that it was wrong to do. But other than that, for just smashing entire list like there's no tomorrow, it did amazing job.

[delgathar]

Hello Mator,

 

I've got a mod that places some NPCs, so it reverts some of the Sub-block info. I could place this mod high in my list so ELFX overwrites, but is there a way to make Mator Smash specifically ignore entries?

 

If don't add it to the patch, then whatever is lower will win. I used the build option, and the only record it populated was the CELL, but the CELL record is one I specifically don't want it to smash.

 

I was thinking an "Ignore" toggle would be useful for people who are constantly rebuilding their load order, or for later when people start trading their smash rules, because an ignore toggle could reduce the impact of load order, and the need to enter manual rules in loot.

 

The functionality of an "ignore" toggle would specifically utilize the higher mod's settings. Thus, where a skip option, or not adding a mod to patch, or simply not checking a field, might result in the lower mod overwriting since the records will be empty in the smash patch. The ignore toggle would tell the patcher to add the previous mod's (or the vanilla) records to the smash patch, so that the ignored mods settings are overwritten, regardless of it's place in the load order. This is also useful in the event that only the ignored mod changes the vanilla settings. For example, a npc replacer mod changes the lighting, but the player has no lighting mods.

 

A lot of mods go beyond their scope, and the ignore option also would manually correct the scope so that a player wouldn't need to go around deleting records, which doesn't work with added objects to CELL records anyway. And because the ignore option would persist across updates, where deleting a spurious record in tes5edit would be reset when the mod is updated, or reinstalled, this would make things easier in the long run.

[IMxAWESOMEx5678]

Hi man, if I add smash.all as the settings tag to all the mods in my smash, how badly will it screw up my game?

[Deleted30920795User]

Hello Mator, I would like to configure MatorSmash so it behaves as follows.

1. Compare plugins records to master file.
a. If a record is equal to the record in the master file, copy the master file record into patch.
b. Else If records differ from master file.
I. If only one plugin has a differing record
*. Copy the plugin's record into patch.
II. If more than one plugin have differing records
*. Copy the last loaded plugin's record into the patch.

By record I don't mean whole records but each individual category of each sub-record, like "Skill Values" from DNAM and PRKR from perks.
I attach two images to try to illustrate my point (of MatorSmash not behaving like I described)

Thank you very much for this great tool.
Kudos.

Edited April 28, 2017 by Guest

[Deleted30920795User]

Hello Mator, I would like to configure MatorSmash so it behaves as follows.

 

1. Compare plugins records to master file.

a. If a record is equal to the record in the master file, copy the master file record into patch.

b. Else If records differ from master file.

I. If only one plugin has a differing record

*. Copy the plugin's record into patch.

II. If more than one plugin have differing records

*. Copy the last loaded plugin's record into the patch.

 

By record I don't mean whole records but each individual category of each sub-record, like "Skill Values" from DNAM and PRKR from perks.

I attach two images to try to illustrate my point.

 

Thank you very much for this great tool.

Kudos.

 

Second Image:

[Deleted30920795User]

Hello Mator, I would like to configure MatorSmash so it behaves as follows.

 

1. Compare plugins records to master file.

a. If a record is equal to the record in the master file, copy the master file record into patch.

b. Else If records differ from master file.

I. If only one plugin has a differing record

*. Copy the plugin's record into patch.

II. If more than one plugin have differing records

*. Copy the last loaded plugin's record into the patch.

 

By record I don't mean whole records but each individual category of each sub-record, like "Skill Values" from DNAM and PRKR from perks.

I attach two images to try to illustrate my point (of MatorSmash not behaving like I described)

 

Thank you very much for this great tool.

Kudos.

Another example:

[matortheeternal]

Seninel199:

You should be able to do this by creating a Mator Smash setting which sets each record as "Treat as Single Entity". I'd start by making an automatic setting per the video tutorial in the OP, prune records from the right-click menu, then select all records, right-click, toggle -> treat as single entity.

[Richardo11]

Hi Mator

.

Just downloaded vs 0.4

.

Installed and in using MO2 -- When deted integrations = mpOpt_ModOrganizer not found

.

Don't really know what it is missing and how i can get/install it.

.

I already have and working fine - Merge Standalone in the same App

.

Thanks

Edited May 6, 2017 by Richardo11