[WIP] Mator Smash

[Mator]

 

Mator Smash

VIDEO TUTORIAL - For v0.0.7

GamerPoets Video - For v0.4.1

 

 

Mator Smash is now available on Nexus Mods. 

Nexus Mods Mod Page

 

 

As of v1.0.0, Mator Smash has a "Quick Patch" button

As of v0.5.1, Mator Smash will copy records with "errors" in them (such as unresolved/unexpected references)

As of v0.5.0, Mator Smash has new algorithm features and is more stable.

As of v0.4.1, Mator Smash merges redundant plugins properly.

As of v0.4, Mator Smash now produces complete record prototypes

As of v0.3, Mator Smash supports Fallout 4 and Skyrim SE

As of v0.2.2, Mator Smash allows you to modify tags on plugins from within the program.

As of v0.2.1, Mator Smash has Smash Settings for Skyrim for every Bash Tag Wrye Bash offered for Oblivion.

 

Changelog:

 

 

v1.0.0

- No longer cleaning masters (the smashed patch will require all patched plugins as masters)
- Increased saturation of profile panel colors
- Removed unimplemented buttons from the QuickBar
- Removed MO Integration - it's unnecessary
- Added easter egg
- Added "quick patch" button
- Fixed FO3/FNV load order issue
- Added Fallout3 and FalloutNV Smash.All settings  
- Updated FO4 and TES4 Smash.All settings
- Fixed switch smash profile button

 

v0.5.1

- Fixed inactive plugins being enabled for SSE/FO4
- Updated Smash.All so Perk Effect Conditions are treat as single entity
- Fixed case sensitivity when determining if patch destination directory is the game's data path
- Fixed bug with not creating directories when building a patch when user is not using MO
- Now allowing copying of records with "errors" in them
- Improved handling of out of order subrecords

 

v0.5.0
- Added override deletions algorithm feature

- Added force value algorithm feature

- Fixed some SSE/FO4 load order issues

- Added and updated smash settings

- Fixed issue with CTDs due to counter elements being set to 0 when their associated array is not present.

- Fixed issue with cells being deleted incorrectly due to bad ITM/ITPO cleanup code.

 

v0.4.1
- Adjusted the description of the Smash.All setting.
- Fixed merging of redundant plugins.
- Fixed recognition of sorted subrecord arrays.

v0.4

- Added Smash.All setting, a new version of the old "Automatic" setting.
- Dramatically improved record prototyping.  Record prototypes should now be complete and include unions such as BOD2 and BODT.
- Fixed loading the Skyrim load order file for SSE when not using MO.
- Fixed SSE load order DLC positions.
- Added Mod Organizer instancing support.

 

v0.3.1

- Fixed bug with initialization exceptions not being handled properly
- Fixed Fallout 4 BA2 file loading

 

v0.3
- Fixed bug with enabling automatic updating causing catastrophic failure.
- Added some language strings for "Enable", "Disable", and "Autoscroll"
- Fixed bug with setting corruption when combining settings (wasn't cloning the objects properly)
- Fixed bug with being unable to delete patches with unloaded plugins
- Fixed a bug with deleting patches
- Added "Remove unloaded plugins" context menu option to Smashed patches
- Now loading BSAs on initialization so localization strings are available to the program.
- Fixed cancelling plugin selection not closing the program
- Fixed floating point division by zero error when smashing records
- Added search functionality to the records tree
- Added SSE game mode support
- Added FO4 game mode support
- Adjusted how the profile form works.  Now it will always create default profiles for games that don't have profiles.
- Disabled the registration controls on the options form because they aren't working yet (we don't have a backend yet, after all)

 

v0.2.2.2

- Fixed bug with application being unable to create the profiles folder.
- Fixed index out of bounds when trying to set a plugin's smash setting.

 

v0.2.2
- Refactored project to use decoupled architecture similar to Merge Plugins
- Added a Plugin Selection Window
- Cleaned up the Tree Popup Menu, similar items have been grouped
- Added Tag Manager Form, which allows you to manually clear tags from the plugin, remove specific tags from the plugin, add tags to the plugin, or edit the plugin's description manually.
- If the "Create combined setting" checkbox is ticked when you close the Tag Manager, it will create and apply a virtual combined setting to the plugin for the tags you selected.
- Added a tags submenu for plugins, you can now clear tags on plugins, apply tags to a plugin based on your smash setting, or manage tags from the Tag Manager.
- Fixed various access violations that could sometimes occur when closing the program or when smashing certain records
- Added a feature that tells smash to merge mods that are comprised entirely of override records.  You can enable it from the Patching tab of the Options Window.  You will be notified in the smashing log of any redundant plugins that can be disabled after building your smashed patch.
- Fixed a bug with parsing ungrouped tags on plugins
- Fixed a bug with renaming a setting not updating its name in the Smash Settings List View in the Settings Manager.
- No longer creating duplicate virtual combined settings.
- Fixed bug where resizing the window didn't always update the contents of the form.
- Added a setting which can be manually added to the settings.ini file if the for simple splash display.  This will disable the glow on text in the Splash Form.  If the text on the Splash form looks distorted you should enable this setting.
- Now trimming leading and trailing whitespace when parsing tags.  So the following: `{{BASH: Delev, Relev   }}` will be parsed the same as `{{BASH:Delev,Relev}}`
- Added submenus for smash setting groups in the Plugins Popup Menu -> Add Smash Setting submenu
- Now verifying patch name and filename don't have illegal characters that aren't allowed by Windows.

 

v0.2.1

- Fixed access violation due to a flaw in the for loop when removing ITPOs
- No longer allowing building of patches which have one plugin.  This was causing a floating point division by zero error when performing preliminary calculations for the progress bar.
- Now disables the name, color, description, and tree controls when the msSettingManager is first created
- Now using a release build configuration
- Plugin selection form OK button now enables after Select All or other popup menu actions
- Refactored old log groups from MERGE to PATCH
- Added Bash Tag settings for Skyrim for every Bash tag that exists for Oblivion.
- No longer creating subfolders for smashed patches when the patch destination directory is the data folder
- Changing the smash setting now marks the patch as needing to be rebuilt
- Added groups to the Smash Settings manager.  If a setting's name has a dot in it, the text before the dot will be used as the setting group.  Groups are collapsible, and are reflected in filenames.
- Added special tag group parsing, if a tag starts with some text and then a colon, that text plus a period is prepended to each sub-tag.  E.g. {{Bash:Relev,Delev}} searches for the settings Bash.Relev and Bash.Delev.
- Added more hint information to the Settings Manager Tree view node hints for the Treat as Single and Preserve Deletions flags.

 

v0.1.1

- Added Select Similar Nodes
- Autoset attributes now disables IDLE records because smashing them commonly leads to failure
- Now updates count elements automatically, so no more CTDs from nasty NPC_ records with invalid COCT - Count elements.
- Fixed sorted array index issue for destination element when there were additions at earlier indexes
- Fixed VMAD treat as single not working properly
- Added smash setting hashes
- Added tag recognition for normal tags, extended tags, special extended tags, and multiple tags
- Fixed the combine setting option
- Fixed ITM removal removing non-ITMs
- Smash settings are now stored in game-specific directories.  You'll want to move your smash settings to a directory for your game.  So `.\settings\\`, game being Skyrim, Fallout3, FalloutNV, or Oblivion.
- Fixed a bug that caused the program to freeze while saving plugin errors
- Now conflict resolving with the winning master record
- Fixed loaded ESPs excluded from patch creation still influencing patch contents
- Improved the Edit Patch form to be more like the Edit Merge form from Merge Plugins
- Now saving logs in subfolders as it is done in Merge Plugins
- Changed DetailsListEditor to a virtual StringGrid, as it is in Merge Plugins
- Now offers an option to merge conflicting settings from the msConflictForm
- Fixed issue with autoset attributes not removing flags when disabling a child

 

v0.0.7

- Now copies winning override of overrides in files being smashed, which fixes a bug which caused partial load order smashed patches to often fail
- Fixed record prototype construction, now assigns to empty arrays so the record tree should always be complete now
- Build tree from plugins now targets records instead of top level groups.  You can now access and smash any record type.
- There are no more hardcoded record type exclusions.  You can now smash whatever you want.  Officially distributed settings will skip records that shouldn't be smashed, of course.
- Fixed exception when right clicking not on a node in tvRecords
- Fixed flag drawing bug that would draw flags in the upper left hand corner of tvRecords when expanding a node
- Splash screen now has glow on the loading text so it is always readable
- Now doing a better job of skipping records that don't need to be conflict resolved
- Progress bar is now more accurate when smashing patches.
- Now removing ITM groups when removing ITPOs
- Created Autoset Attributes option
- Created an "Automatic" smash setting which is built using Autoset attributes on a setting built from a full load order of plugins.

 

v0.0.6

- Preserve deletions in top-level elements (subrecords) now works

- Some improvements to logging

- Linking elements fixed

- Single entity element copying fixed

- Array identification conditions fixed

- Did away with the old building trees methodology. You can now right-click on the records node of a setting and use the Add submenu to create definitions for records.

- Added a new build tree option, which can be used from the right click popup menu.

 

 

v0.0.5

- Added code so you can now toggle multiple nodes in the tree using the space bar.

- Fixed Treat As Single Entity never being triggered because children nodes were always disabled and couldn't be toggle without removing the flag.

- Fixed chain nodes linking nodes at different levels, which also led to access violations when trying to remove the links.

- Failed smashed patch status now retains after smashing completes.

- Smashing is now cancelable.

- Now storing element definition type information in setting trees.  NOTE: Elements in old setting trees will have the "Unknown" type.  You'll need to rebuild your settings to get type information.

- Made prune nodes option more user friendly and added an auto-prune option to the popup menu for fast and simple pruning.
- Fixed bug with deleting a smash setting not removing it from disk.  They now get sent to the recycle bin when deleted.

- Fixed issue with processing records when they were set to not be processed in the setting (which created ITPOs).

- Distinguishes between arrays better.  Unsorted dtArray elements will now be treated as arrays, as intended.

- Removes ITPOs after smashing.

 

v0.0.4

- Added -profile param handling
- Algorithm now supports multi-linking (chaining) elements
- Added option to chain nodes in the Settings Manager
- Hardcoded excluded groups are now only RACE, NAVI, and NAVM
- Cloning settings will no longer create an infinite loop
- Plugin selection form now has a popup menu with Select all, Select none, and Invert selection options
- Plugin selection form now has extra options for targetting/skipping records
- Fixed issue with building tree not assigned TElementData for the rootNode, causing an access violation when checking anything in the tree

 

v0.0.3.14

- Core functionality is complete

- The UX for smashing and the algorithm are both more-or-less complete, may be updated

- Most of what needs to be done now is the creation of smash settings, which can be done by anyone with some knowledge of patching

- I'll try to make some documentation/tutorial resources for creating smash settings so you guys can get started on them

 

 

 

 

Purpose
Mator Smash is an application built on the xEdit framework developed to replace the primary functionality of Wyre Bash - the creation of patch files to combine (or merge) conflicting overrides to overcome Bethesda's "Rule of One". Wyre Bash used to provide this functionality in the days of Oblivion through the usage of bash tags, keywords that would be put in the description of the mod that would then tell Wyre Bash what types of records it should try patching. However, the current status is that Wyre Bash only provides this for a handful of record types for Skyrim, and this has been the case for quite a while now. There are several users (most notably Sharlikran) who have been working to update Wyre Bash's codebase to work with Skyrim, but it's been an uphill battle. As of now, it's not certain whether Wyre Bash will ever offer the same functionality it did in the days of Oblivion for Skyrim mods. That's where Mator Smash comes in.

 

Why is this necessary?
As per Skyrim's "Rule of One", any two mods that modify the same record but in different ways will conflict with each other in a way that can't be resolved asides from the creation of a compatibility patch. Because the number of Skyrim mods exceeds 40,000, there is no conceivable way to manually build enough compatibility patches to make every possible load order (or even a small fraction of them) work with each mod operating as intended. Mator Smash automates the most important part of the task of compatibility patch creation - the combining of conflicting edits. This is something that we've been needing for a very, very long time.

 

How does it work?
Warning: technical jargon ahead. Where Wyre Bash has separate procedures for the patching of individual record types, Mator Smash has a few generic procedures for the patching of ALL record types. This means that Mator Smash has, with very little development effort, achieved the capacity to patch more records than Wyre Bash has ever been capable of patching. This is achieved through a recursive traversal method which traverses override record structure, comparing subrecords between a master record, a source override record, and a destination override record. Upon the basis of this comparison, certain subrecords are written to the destination record while others are skipped and others are deleted from it.

 

Development Status
I began development of Mator Smash as a standalone application built on top of the xEdit API 10/18/2015. Here's the GitHub repository. Check out the design folder in the repository for various files relating to my design process. I'll be live streaming most of my development on livecoding.tv. I'll be streaming mainly on weekends 9:00AM-9:00PM PST. Because of major code reuse from merge plugins standalone, smash will be entering public beta very soon.

Mator Smash is currently available as a proof of concept script (which is slow and lacking in features/a clean user experience). You can download v0.9.4 of that script here. This script can currently correctly patch a massive number of different types of records. FAR MORE than Wyre Bash or any other currently available solution, and more than any solution that has ever existed for Skyrim or any other game.

 

Implemented Features

• Dynamic, flexible settings: Smash settings are comprised of a tree which has information on how records/subrecords should be handled. This will allow users to control how a patch is created on a per-subrecord basis. This will make smash relevant regardless of the nature of the mods being patched, or the game the mods come from. Each node (record/subrecord) will have the following data associated with it-
  • Process: Whether or not smash should process this node and perform conflict resolution for it if a conflict is found.
  • Preserve Deletions: If a mod deletes an element inside of this node, that deletion will be preserved in the generated patch.
  • Treat as single entity: If a mod overrides any subrecord in this node, the entire node will be replaced with that mod's version of it.
  • Chaining: Linking allows you to copy multiple side-by-side elements when any one of those elements changes.
  • Override Deletions: Allows a plugin to restore deleted elements.
  • Force Value: Forces values from a particular plugin to be used, and only allows plugins which require this plugin to perform further conflict resolution on affected records.
• Tags: As of v0.2.1, all Bash tags that were offered with Wrye Bash for Oblivion are now available for Skyrim.  Smash will automatically detect tags and apply smash settings to the plugins that have them, assuming you have smash settings that correspond to the tags.
• Managed smashed patches: Patches you build will be tracked in the program, so you can quickly and easily rebuild them when your load order changes. You can also have multiple patches for your load order, if you feel that is desirable.
• Multi-language support: I built a really clean, extensible, and easy to use language system when I developed Merge Plugins Standalone. Smash will use the same language system to support multiple languages out-of-the-box. As a translator, all you have to do is make a text file to create a translation and have users install it in their lang folder. The rest is handled by the program.
• Fast and easy setting creation: Select some plugins to build a setting to specifically handle the conflicts they are capable of creating in a load order.  Toggle or set flags for multiple nodes at once.  Select similar nodes in a setting tree.  Conflict resolution has never been quite so powerful, flexible, and easy.

 

Planned Features

Smash is now pretty much feature complete.  Further development energy will be spent on porting it to a zEdit application mode, zSmash, which will include a new, streamlined workflow.

[thommaal]

I have seen Mator's general plan but does anyone know if he has a timeline published somewhere to tell us when to inform him about bugs/curiosities? Usually, there is a deadline for any input prior to the release of the next version, so .. any idea?

[Mator]

I have seen Mator's general plan but does anyone know if he has a timeline published somewhere to tell us when to inform him about bugs/curiosities? Usually, there is a deadline for any input prior to the release of the next version, so .. any idea?

All development has been pushed back.  Focus has shifted to developing merge plugins as a standalone application using the TES5Edit API which will serve as a precursor/sample codebase for developing Mator Smash as a standalone application.

[Octopuss]

So what's the new ETA then? I thought Smash would be significantly bigger deal then special program to merge plugins, considering the current version works just fine.

[hishutup]

The application is pretty neat and does significantly more than the script.

To give you an idea of the timeline, its near the end of pre alpha.

 

Its up to mator on what info he is willing to release.

[thommaal]

Its up to mator on what info he is willing to release.

Of course; and just in case someone got the wrong idea: My question was not meant to push Mator but to find out when it's time to give what kind of feedback and when it's time to let him work in peace.

 

Looks like it's time for the latter. When a focus shifts, feedback on previous plans is more likely pointless and the time he spends to answer it a time-consuming distraction.

 

 

All development has been pushed back.  Focus has shifted to developing merge plugins as a standalone application using the TES5Edit API which will serve as a precursor/sample codebase for developing Mator Smash as a standalone application.

Thanks for the update, Mator. Smash is already quite the useful tool.

 

[Mator]

So what's the new ETA then? I thought Smash would be significantly bigger deal then special program to merge plugins, considering the current version works just fine.

 

The ETA is largely dependent on the amount of time I can put in now that I have a full-time summer job.  It's not a situation I've been in before, so I can't really say much with certainty.

Smash is a big deal, but prior to developing something new that I don't fully understand, I decided to make something that I already understand.  The transition from script to standalone application is not trivial.  Attempting to do Mator Smash as a standalone application right from the get-go would be a far more inefficient way of doing things than the way I'm doing them now.  Code reuse will be high, so in a way I am working on Mator Smash right now, just not directly.

 

Also, the Merge Plugins standalone application is kind of a big deal.

 

Thanks for the update, Mator. Smash is already quite the useful tool.

 

I'm doing my best to get things done as fast and efficiently as possible.  Please bear with me - I'm a single programmer trying to redefine the way we all play and mod the bethesda games.  That's no easy feat!

 

 

Regards,

-Mator

Edited June 2, 2015 by Mator

[afonik]

...  That's no easy feat!

 

 

And I guess that's why we all love you!!!

[Descivii]

Error in unit 'smash' on line 895 : Undeclared Identifier 'ebi'

This is the error I got while trying Smash. I am using xEdit 3.1 NOT 3.1.1 As mentioned in my thread in the xEdit forum, I am currently unable to use the newest xEdit. Would this be the reason for this error? Forgive my ignorance, I am only user aware of xEdit and haven't any real knowledge of the programs rhymes or reasons.

[Mator]

Error in unit 'smash' on line 895 : Undeclared Identifier 'ebi'

 

This is the error I got while trying Smash. I am using xEdit 3.1 NOT 3.1.1 As mentioned in my thread in the xEdit forum, I am currently unable to use the newest xEdit. Would this be the reason for this error? Forgive my ignorance, I am only user aware of xEdit and haven't any real knowledge of the programs rhymes or reasons.

 

You didn't install the version of mteFunctions included with the download for Mator Smash or you replaced it with a different version.  Redownload the archive from the OP and make sure to replace your mteFunctions.pas file with the one from the archive (in your Edit Scripts folder).

[kranazoli]

Hi,

 

I've been using and know (able to use, ...) Tes5Merged Patch as a pre Bashed Patch plugin (deleted Leveled Items, Cleaned Masters) + Wrye Bash ReBuild Bashed patch, ... so the well known method. (but Tes5Merged Patch still a little bit new for me). But this whole process took me just some minutes and after makeing other SkyProc plugins...

 

I have heard about Mator Smash before, but didn't read topics and more infos about it.

 

1.) Is it good to load my whole plugin list via Tes5Edit and run Mator Smash script? Enabled every plugins, leave everything by default in Mator settings, and creating the Mator Smash patch file?

 

(I've done it, but to be honest I am do not really understand that tool yet, as how I know Tes5Edit and Wrye Bash)

 

 

 

 

 

 

I am not sure at all, wheter it is okay or not like that way? Or this is a little bit more complicated than how I think about that? :)

 

If not, so it is good, it is how should we use I have some other question:

 

2.) Still needed, good, better to make a Tes5Merged Patch before Mator ones? Or this is absolutely unnecessary?

 

3.) I guess in this case, I can disable any plugins which was created after Bashed Patch? (ASIS; Dual Sheat Redux)

 

4.) After the patch is created I can run those Patches the same as before?

 

5.) Does it matter what title I give this Mator patch .esp? (Mator; MatorSmash, etc...)

 

Sry, as I said I do not really know that tool yet!

I'm sure it is must be very useful, and more clever than Wrye Bash and we will use this tool later, ... but do not really found as much infos about it, then the other ones.

 

I use STEP Extended + REGS + SR-LE. I know I guess tools which are mentioned and required by STEP and Skyrim Legendary. At this moment I don't really know why should we use that tool instead of Wrye Bash, but I am sure it has sense, etc, etc, ...

 

Thank you for any support! And sorry!

Edited September 17, 2015 by kranazoli

[Mator]

1.) Is it good to load my whole plugin list via Tes5Edit and run Mator Smash script? Enabled every plugins, leave everything by default in Mator settings, and creating the Mator Smash patch file?

 

(I've done it, but to be honest I am do not really understand that tool yet, as how I know Tes5Edit and Wrye Bash)

 

I am not sure at all, wheter it is okay or not like that way? Or this is a little bit more complicated than how I think about that? :)

 

If not, so it is good, it is how should we use I have some other question:

Depends on who you talk to. I think it's fine, but hishutup thinks it's a bad idea because you'll get records patching that you don't want to be patching. Smash is blind - if it sees a conflict in a record/subrecord that is not excluded, it will resolve it.

 

2.) Still needed, good, better to make a Tes5Merged Patch before Mator ones? Or this is absolutely unnecessary?

Unnecessary and harmful because the TES5Merged Patch makes mistakes that smash doesn't. Same with a bashed patch.

 

3.) I guess in this case, I can disable any plugins which was created after Bashed Patch? (ASIS; Dual Sheat Redux)

You should use smash as you'd use a Bashed patch, so replacing the bashed patch. You should use neither a Bashed patch nor a TES5Edit Merged patch.

 

4.) After the patch is created I can run those Patches the same as before?

Yes. Treat a smashed patch the same way you'd treat a bashed patch.

 

5.) Does it matter what title I give this Mator patch .esp? (Mator; MatorSmash, etc...)

No, it doesn't matter at all. The script recognizes the Mator Smash ESP by its author field, so the filename is irrelevant.

 

Sry, as I said I do not really know that tool yet!

I'm sure it is must be very useful, and more clever than Wrye Bash and we will use this tool later, ... but do not really found as much infos about it, then the other ones.

 

I use STEP Extended + REGS + SR-LE. I know I guess tools which are mentioned and required by STEP and Skyrim Legendary. At this moment I don't really know why should we use that tool instead of Wrye Bash, but I am sure it has sense, etc, etc, ...

 

Thank you for any support! And sorry!

Development of Smash has been put on hold until a standalone application for it can be made. The speed of development when using smash as a script (interpretted code) was too slow to iterate effectively, so I decided to drop it until I had completed Merge Plugins Standalone so I could then make a standalone application for it similar to Merge Plugins Standalone. Mator Smash Standalone will be up to 360x as fast as the script (based on benchmark comparison of a similar recursive traversal method for GetChildRecords). If it ends up being as fast as I expect, it should complete in around 10 seconds regardless of the size of your load order.

 

The script can be used for certain things, and you can talk to hishutup to get his thoughts on this. He uses STEP as well, so he should be able to provide you with some very relevant thoughts and advice on using smash with your load order.

Edited September 17, 2015 by Mator

[kranazoli]

Hi,

 

"Depends on who you talk to. I think it's fine, but hishutup thinks it's a bad idea because you'll get records patching that you don't want to be patching.

Smash is blind - if it sees a conflict in a record/subrecord that is not excluded, it will resolve it."

 

First and foremost, thank you, your read my "stupid" and long questions and also thank you for the answer.

Be sure, I am not a half God Skyrim Guru like you guys. :)

 

So far, os could I could understand what is the issue, problem with Tes5Edit Merged Patch (as a pre Wrye Bash patch) and Wrye Bash.

 

But for me, using Wrye Bash at this time, with its lots guide, every guide use that tool yet (STEP; Skyrim Legendary) plus extra YT video guides and so on, made me that I can use WB easily, can manage my mods, etc... And I really love that I almost do not have to do anything. Just run it, read the STEP or Legendary WB guide, some click and my Wrye Bash patch has done, or rebuild again within 1 minutes, without I should care everything. I mean that, so called some kind of user friendly, automated, ... Easy to use.

 

As easy to use Mator Smash just how I tried to describe. Load my whole plugin list, click apply script, waiting, patching done, and everyone is happy.

 

But if it is require more manual procedure, so I must say I would need more user guide + videos to understand how should I properly use Mator Smash tool and forget Wrye Bash. Change to Mator from Wrye Bash.

 

A little bit polishing my knowledge:

:)

 

Is that order fine? (if I choose Mator Smash)

 

0.) Deactivate my Tes5Merged patch and Bashed Patch

1.) Deactivate any plugins which were created after Bashed Patch, every single SkyProc plugin

2.) Use Mator Smash, how I can handle at this moment yet and creating patch file

3.) Activate Mator Smash patch file and continue to finish my other patches

 

And use that Mator Smash patch instead of Wrye Bash patch.

 

If it is more or less okay, there's immediately one thing I miss:

 

- Wrye Bash merge plugin feature.

 

If I use Mator ones as I described above, I didn't notice Mator Smash merged unnecessary plugins and save my load order. Reducing my esp files, ...

 

In conclusion, what do you recommend for me:

 

1.) I still continue using Wrye Bash how I've been doing it for a long time; or

2.) Change Mator Smash

 

Ps: I guess, from what I wrote more or less you know about my Skyrim modding knowledge.

The most important thing for me, stability and reliability.

 

Edit: How long the Mator Smash process take does not matter for me. It is nothing compare to DynDOLOD. ;)

 

Thank you!

Edited September 17, 2015 by kranazoli

[Octopuss]

There's still no rough estimate when the standalone version could be available?

[Mator]

First and foremost, thank you, your read my "stupid" and long questions and also thank you for the answer.

Be sure, I am not a half God Skyrim Guru like you guys. :)

No question is stupid!  :)

I'm nowhere near as good as people make me out to be.  I just work really hard and pretty much never play the game itself.  (which seems fairly common in modding) :P

 

As easy to use Mator Smash just how I tried to describe. Load my whole plugin list, click apply script, waiting, patching done, and everyone is happy.

 

But if it is require more manual procedure, so I must say I would need more user guide + videos to understand how should I properly use Mator Smash tool and forget Wrye Bash. Change to Mator from Wrye Bash.

Yeah, it's not really there yet for "one-click and done" to be a valid procedure to follow.  You could do it, but it might not resolve things the way you want it to.  It's a beta project for a reason.  ;)

 

I'd recommend experimenting with it, but not using it on a full large load order with a single button click like Wrye Bash.  It's not quite polished enough for that yet.

 

0.) Deactivate my Tes5Merged patch and Bashed Patch

1.) Deactivate any plugins which were created after Bashed Patch, every single SkyProc plugin

2.) Use Mator Smash, how I can handle at this moment yet and creating patch file

3.) Activate Mator Smash patch file and continue to finish my other patches

 

And use that Mator Smash patch instead of Wrye Bash patch.

Sounds fine by me.  Again, results may vary, it's beta.  ;)

 

- Wrye Bash merge plugin feature.

 

If I use Mator ones as I described above, I didn't notice Mator Smash merged unnecessary plugins and save my load order. Reducing my esp files, ...

 

In conclusion, what do you recommend for me:

 

1.) I still continue using Wrye Bash how I've been doing it for a long time; or

2.) Change Mator Smash

In terms of merging plugins, I'd recommend using my Merge Plugins script (or Merge Plugins Standalone, which is in alpha) for that.  Smash may eliminate unnecessary plugins at some point in time in the near future, but it doesn't do that yet.

 

Ps: I guess, from what I wrote more or less you know about my Skyrim modding knowledge.

The most important thing for me, stability and reliability.

 

Edit: How long the Mator Smash process take does not matter for me. It is nothing compare to DynDOLOD. ;)

 

Thank you!

If stability and reliability are your top priorities, I wouldn't recommend using smash in its current state.  Just be a bit patient, it'll be in standalone application form before you know it!  :)

 

 

There's still no rough estimate when the standalone version could be available?

You want a rough estimate?  Ok, I'll give you a very rough timeline of some events:

 

Merge Plugins Standalone Public Beta - September 22

MXPF Release - October 2

Merge Plugins Standalone Release - October 9

mteFunctions refactor - October 9

Mator Smash Standalone Alpha - October 16

Mator Smash Standalone Public Beta - November 6

FO4Edit Work Begins - November 10

Mator Smash Standalone Release - November 20

Edited September 19, 2015 by Mator

[GrantSP]

As rough estimates go, they're pretty specific. 

 

I'm always looking forward to what you bring to the gaming table, some of the best tools around are because of your work.