Version 2.2.1

Version 2.2.0

- Added Fallout 4 support

Version 2.1.3

- Corrected load order bug for FO3/FNV/TES4 when not using MO
- Implemented Extract BSAs option (it did nothing before this update)
- Made documentation on the Resolve Issues Window
- Added Troubleshooting section to documentation
- Updated Merge Statuses section of the documentation
- Fixed Reset Errors being unavailable when a plugin had no errors
- Fixed changing the merge name not always updating its data path
- Fixed merge failure due to an access violation when using the New Records merging method
- Returned the limitation on the fails and files sections of the Merge Details view of 1000 items each
- When the merge destination directory is the data folder Merge Plugins will put merged assets directly into the folder instead of creating a subfolder for each merge
- Merge Plugins no longer breaks due to different regional Decimal Separator characters.
- Fixed the OK button of the Options Form not updating when changing the Merge destination directory

Version 2.1.2

- Hotfix release
- Fixed issue with styles not drawing when plugin selection form initially appears
- Fixed load order being incorrect for FO3/FNV/TES4
- Fixed main application window not repainting when restored sometimes
- Updated the limitation section of the documentation
- Fixed some issues with record renumbering code that could cause issues when renumbering FormIDs, specifically when merging TES4 plugins.
- Fixed issue with merge deletion sometimes causing the program to freeze
- Fixed issue with Dictionary button not enabling when the user downloads a dictionary they didn't have using the Update Button
- Fixed list views on the Main Application window not repainting enough
- Improved non-contiguous plugin handling. Critical non-contiguous issues can no longer be ignored
- Fixed Find Errors checking plugins that have already been checked for errors
- Resolved issue with the merge/ folder not being cleared when rebuilding a merge
- Fixed issue with the Delete Merge confirmation box sometimes being hidden behind the main application window
- The msFailed merge status is now immutable, as it should be.
- Added a note in the documentation about Copy General Assets being on the Integrations tab
- Fixed a critical issue with Merge version in submitted reports having a leading space, which caused the loss of some reports that were submitted over the last few days.

Version 2.1.1

- Fixed TESV_Papyrus_Flags browse filter, added All files (*.*) filter
- Fixed bug with copy general assets using the game's data directory in certain cases
- Created plugin selection form
- Added type-to-search to all list views
- Added help integrations/documentation framework
- Completed documentation
- Added Verify File Access button to merging tab
- Integration-dependent options are now disabled if the integrations they depend on aren't set up
- We now open the Options Form when a new profile has been created
- When editing/creating a merge, a filename missing .esp at the end is now invalid, and entering the TEdit highlights the text before the .esp file extension
- Added -profile target line parameter
- Added -offline target line parameter
- OK button of Options Form is now disabled if the Mod Manager integration is invalid
- Fixed integration detection exception, and the annoying disk prompt that would sometimes come up when detecting integrations
- Balloon hints are now hidden when the user brings up a child form
- Added NMM integration for Nexus Mod Manager v0.60a+
- Changed the TDetailsListEditor into a virtual TStringGrid, allowing for link styling and (nearly) unlimited rows (allowing us to remove the limitation on the Files and Errors sections for merges)
- Heavily refactored the entire project
- Logs now saved to separate folders
- Fixed asset copying being backwards
- Made it so resetting user registration re-registers them if possible
- Fixed script fragment copying targeting the merged plugin instead of the plugins that were merged

DescriptionMerge Plugins Standalone (or just Merge Plugins), is a tool for combining modsfrom Bethesda games which have .ESP/.ESM files. It uses the xEditcodebase asan API, and can be used with Skyrim, Oblivion, Fallout New Vegas, Fallout 3, andFallout 4. Merge Plugins Standalone is the successor to my Merge Plugins xEdit Script.

DocumentationDocumentation for Merge Plugins is provided in the "doc" folder in CHM andPDF format. The provided documentation is extremely thorough, I highlyrecommend you at least skim it so you know what is provided. If you post aquestion that is answered in the documentation, I will not answer it. Instead, I will refer you to the section of the documentation where your question is answered.

Also note that while you're running Merge Plugins you can press F1 and clickon any part of the application to access documentation on it.Additionally, most components in Merge Plugins have mouse-over hints whichvary in length from a single sentence to a full paragraph.

FeaturesMerge Plugins Standalone is a feature rich application that offers numerousadvantages over my Merge Plugins Script, let alone manual merging. Below is alist of some of the most notable features:

MERGE PROFILES:Create profiles to manage different games or load orders. Each profile has itsown settings and merges.

MERGE TRACKING:Merges are tracked. When you update a mod, any merges that mod is a part ofwill be classified as needing to be rebuilt.

INFORMATIVE GUI:A rich, extensive GUI gives you all of the information you need to know to makemerging decisions on the fly.

ASSET HANDLING:Merging manually will break the association of your source plugins with certainassets, leading to bugs. E.g. the grey face bug, voiceless NPCs, and garbledMCMs. Merge Plugins handles all of these assets for you, moving them to correctpaths so they can be found by your new merged plugin, preventing these bugs fromoccurring.

SCRIPT FRAGMENT HANDLING:Papyrus script fragments are used in Bethesda games to handle crucial logic inDialog Topics, Quests, and Scenes. When merging the FormIDs of certain recordshave to be changed due to conflicts, which can break the association betweenscript fragments and their associated records. This leads to bugs such asdialog not triggering events, quests freezing, and broken scenes. Merge PluginsStandalone locates broken script fragments, decompiles them, adjusts theirsource code, renames them, and then recompiles them.

BSA HANDLING:The program detects BSAs associated with plugins being merged, and accesses theassets in them as necessary for asset handling purposes. It can also fullyextract BSAs for plugins being merged, or create a merged BSA from the BSAsassociated with the plugins being merged.

MOD ORGANIZER INTEGRATION:Merge Plugins integrates with Mod Organizer even better than the Merge PluginsScript. Merged mods produced by Merge Plugins become mods in Mod Organizerwithout any post-merge steps. Just merge and go!

USER REPORT SYSTEM:Merge Plugins Standalone connects to a server which has a database of usersubmitted reports on the merge-ability of plugins. Unlike the Merge PluginsScript, you can easily create and submit reports on plugins you've mergeddirectly from the application. Once submitted to the backend, reports will bereviewed and added to the dictionary file if approved. There is a separatedictionary file for each game supported by Merge Plugins. Reports associatedwith plugins are displayed directly in the GUI, allowing you to make decisionson what to merge based on the experiences of other users.

DICTIONARY VIEWERMerge Plugins Standalone has a Dictionary Viewer, which allows you to view thedictionary. The viewer supports both sorting and filtering.

INTEGRATED UPDATES:You can update the dictionary or the program directly from the program itself. Heck, if you want, you can even elect to have the program download and installupdates automatically!

FILTERABLE LOG:Trying to troubleshoot? A filterable log with messages grouped and labeledaccording to what part of the program's functionality they correspond makes iteasy.

INTEGRATED HELP:You can press F1 and click on any component in the program to instantly accessdocumentation on that component.

ABUNDANT DOCUMENTATION:With over 60 pages of documentation, Merge Plugins is one of the best documentedmodding programs currently available. Help yourself by referring to thedocumentation when you have a question.

Setup1. Unpack Merge Plugins somewhere. E.g. C:\Program Files\Merge Plugins.2. Start Merge Plugins.3. If you don't see a profile for your game, right-click in the box and choose"New profile", then specify a profile name, game mode, and game path. You canbrowse for your game path by clicking on the browse icon.4. If your profile is valid, its background color will turn a shade of lightgreen. You can then select the profile by clicking the game icon (or any otherpart of the panel).5. Once you've selected a profile, click "OK".

ConfigurationWhen you first start Merge Plugins you should do some initial configuration.

(1) configure integrationsGo to the Integrations Tab. If you're using Mod Organizer, checkthe "I'm using Mod Organizer" checkbox. Then click DetectIntegrations. If any integrations aren't found, you'll want toinstall them or browse to find them on your system. Make sureyou verify the paths found by Merge Plugins, especially forMod Organizer if you have multiple installations.

(2) set your asset destination directoryGo to the Merging Tab and click the browse icon by the text box.The folder you choose here will be where merges are placed. Ifyou're using Mod Organizer this should be your Mod Organizermods folder.

(3) set merging optionsGo to the Merging Tab and check the boxes corresponding to theoptions you want to use. You'll want to use "Extract BSAs" or"Build Merged BSA" if you aren't using Mod Organizer. You canleave everything else as the defaults.

(4) register a usernameGo to the General Tab and enter a username in the usernametext box. Click "Check" to verify the username is available.Once you have a username that's available, click "Register".This username is put on reports submitted to the backend.A username is required if you want to submit reports onplugins you've merged.

Common Issues- Avast and some other Antiviruses may interfere with Merge Plugins.If you have trouble running the application, you may need to add it as anexception to your antivirus.- If you receive an error message saying "Navigation to the webpage was canceled" when opening the CHM documentation, you need to tell Windowsto unblock it. Find the file at "doc\Merge Plugins Documentation.chm", right-click it, choose properties, and then click Unblock.