Skip to content

Mod Managers Comparison

Jump to bottom Edit New page
yggdrasil75 edited this page Feb 11, 2021 · 17 revisions

Comparison to other mod managers

There are many mod managers around these days and it's may be a bit difficult to choose the one you need. This page is designed to highlight key features of known mod managers.

Legend

Features

Kortex MO2 MO1 Vortex NMM Wrye Bash
Supported games TES series starting from Morrowind.
Fallout series starting from Fallout 3.
Sacred 2. 		Morrowind, Oblivion, Fallout 3, Fallout NV, Tale of Two Wastelands (TTW), Skyrim, Skyrim SE, Skyrim VR, Fallout 4, Fallout 4 VR, Enderal (Steam Edition) Oblivion, Skyrim, Fallout 3, Fallout: New Vegas. Supports over 150 games including Cyberpunk 2077, the TES Series, and the Fallout serie. Supports many games including Elder Scrolls (plus Enderal) and Fallout series. Morrowind using Wrye Mash.
Fallout 3/Fallout NV Using Valda's Wrye Flash.
Oblivion, Nehrim, Skyrim (LE, SE, VR), Enderal and Fallout 4 (Regular & VR) Using Wrye Bash.
Importing from other managers Nexus Mod Manager, MO1, MO2.
MO1, MO2, NMM.
Profile management Multiple instances per game, multiple profiles per instance. One instance for one MO installation, multiple profiles per instance. Multiple profiles per game
Assets conflict management
Conflict resolution Using mod priority that can be changed by drag & dropping mods in a specific order
 Using mod priority that can be changed by drag & dropping mods in a specific order.
Per file resolution through hiding of files (renaming with .mohidden). 		Using mod priority that can be changed by drag & dropping mods in a specific order.
Per file resolution through hiding of files (renaming with .mohidden). 		Through definition of order rules between mods, which can be created through drag & drop of the relationship icon. Per file resolution through advanced conflict view (this can be different per-profile) One time popup during installation to decide whether to keep or overwrite other mods files. Using mod priority that can be changed by drag & dropping mods in a specific order.
Conflict visualization
Different conflict flags on modlist for different conflict types (winning/losing/both). Highlighting of mods that have conflict with the currently selected mod. Listing of losing, winning and non-conflicted files for each mod. Ability to preview and cycle alternatives of textures and other file types. Advanced per-mod conflict views with alternatives, sorting, search, etc.
  • Different conflict flags on modlist for different conflict types (winning/losing/both).
  • Highlighting of mods that have conflict with the currently selected mod.
  • Listing of losing, winning and non-conflicted files for each mod.
  • Ability to preview and cycle alternatives of textures and other file types.
  • Single generic flag on modlist for all conflicts types.
  • Only an "active-rule" icon once conflict has been resolved through a rule.
  • Popup when installing mod with conflicts.
  • Simple conflict resolution window (rules) with tooltip of conflicted files. - searchable and filterable as of 1.4
  • Advanced per-mod file tree structure of conflicts with alternatives from other mods.
 No visualization of conflicts as there can't be, just one time popup during mod installation to either overwrite or keep old files.
  • Colored checkboxes indicate conflict.
  • Tabs can be selected to see detailed list of conflicts for both loose files and BSA/BA2 files.
  • The mod archive or package name is shown.
Game archives (BSA) management
  • Extraction
  • Creation
  • Content preview
  • Experimental conflict detection
  • Extraction
  • Conflict detection
  • Loading without plugins
  • Archive version checking builtin as of 1.4
  • Archive version checking
  • Conflict detection
Game archives (BSA) management
Extraction, Creation, Content preview, Experimental conflict detection. Extraction, Conflict detection, Loading without plugins.
Game archives (BSA) Conflicts
Only experimental WIP conflict visualization of archives through BSA specific conflict flags. BSA order is decided by plugin order like normal. Change of how the game handles BSAs to allow BSA files to be loaded without plugins, in a different order, and allow BSA contents to overwrite loose files. Order is decided through mod priority and conflicts are shown as part of the normal loose assets conflicts. Cons: some mods and programs relayed on the previous game behavior.
Saves management Virtualization per profile and dedicated tab to visualize them.
The Saves Tab allows you to switch between different 'save profiles'.
Change master name in header of save game from save game manager
List plugins used in a save game
Through tooltip. Warning icon if current load order is missing files for them.
Config (INI) management Virtualization per profile and advanced editor. Virtualization per profile and editor. Virtualization per profile.
The INI Edits Tab allows applying and undoing 'INI Edits', small INI files that can be installed via BAIN and then applied to INIs. Comes packaged with many default INI tweaks that have been tested and verified.
Load order management scheme Drag and Drop for mods and plugins. Based on LOOT and its own rules system. Drag and Drop for plugins. For mods it's the install order. Drag and Drop for mods and plugins. Allows locking load order to prevent external applications from making changes.
Add or remove plugin flags from plugin list
ESL flag.
ESM and ESL flags. Also generates correct ONAM data when adding/removing ESM flags.
Change master name in header of plugin from plugin list
Integrated LOOT support
One click sort, detailed loot report, visualization of loot info on pluginlist through flags and tooltips. One click sort, detailed loot report. (! severely outdated version of integrated Loot) 
		<td id="Vortex" class="text-left">
			<ul>
			<li>Drag & drop dependency icon for specific "load after" rules.</li>
			<li>Full features native to LOOT.</li>
			<li>Group management including:	adding and removing groups, changing a plugins groups, order of groups.</li>
			<li>LOOT defaults</li>
			<li>Automatic LOOT updates</li>
			<li>Plugin details visible by double clicking plugin.</li>
			<li>Visualization of info through flags.</li>
			</ul>
		</td>
		<td id="NMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="WB">
			Visualization of dirty plugins via underlining on the plugin list, automatic retrieval of LOOT's Bash Tag suggestions.
			Allows you to export your applied tags for contribution to the LOOT masterlist.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Backup features</td>
		<td id="KMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="MO2.MO1" colspan="2">
			Modlist order,
			Plugin order,
			Individual mod folder backup.
		</td>
		<td id="Vortex">
			Via Extension only:
			https://github.com/Garethp/Vortex-Modlist-Backup
		</td>
		<td id="NMM">
			<ul>
				<li>Import Export Load Order</li>
				<li>Backup and Restore Mod Installation</li>
			</ul>
		</td>
		<td id="WB">
			<a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#tools-settings">Backs up all the parts of Wrye Bash that can be changed by the user to a location of the user's choosing</a>.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Program list</td>
		<td id="KMM">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="MO2">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="MO1">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="Vortex">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="NMM">
			<ul>
				<li>No method to add custom launcher and you must choose from a predetermined list.</li>
				<li>Program List varies depending on selected game mode.</li>
			</ul>
		</td>
		<td id="WB">
			<div class="cmp-yes" />
		</td>
	</tr>
	<tr>
		<td class="feature-name">Mod package creator</td>
		<td id="KMM">
			FOMod (XML), KMP.
		</td>
		<td id="MO2">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="MO1">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="Vortex">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="NMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="WB">
			Only BAIN wizards, and only via simple text editors.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Supported mod package formats</td>
		<td id="KMM">
			FOMod (XML), KMP.
		</td>
		<td id="MO2.MO1" colspan="2">
			FOMod (XML, C#), BAIN Package, freeform<sup>1</sup>, simple<sup>2</sup>.
		</td>
		<td id="Vortex">
			FOMod (XML, C#), simple<sup>2</sup>.
		</td>
		<td id="NMM">
			FOMod (XML, C#), OMOD, simple<sup>2</sup>.
		</td>
		<td id="WB">
			FOMod (XML), OMOD (by repackaging to BAIN), BAIN Wizard, BAIN Package, simple<sup>2</sup>.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Event Logging</td>
		<td id="kmm">
			external logs
		</td>
		<td id="mo2.mo1" colspan="2">
			logs viewable within program
		</td>
		<td id="Vortex">
			external logging,
			internal event viewer for order of recently install/enabled/disabled mods
		</td>
		<td id="NMM">
			<div class="cmp-unknown" />
		</td>
		<td id="WB">
			External logs
		</td>
	</tr>
	<tr>
		<td class="feature-name">Mod Merging</td>
		<td id="KMM">
			<div class="cmp-no" />
		</td>
		<td id="mo2.mo1" colspan="2">
			Merge "mods" (assets) from the same mod page during install
		</td>
		<td id="Vortex">
			merge "mods" (assets) from the same mod page during install and any mods after install
			merge plugins via extension
		</td>
		<td id="NMM">
			<div class="cmp-no" />
		</td>
		<td id="WB">
			merge overwrite-only plugins for certain games during patch creation
		</td>
	</tr>
	<tr>
		<td class="feature-name">Virtualization scheme</td>
		<td id="KMM">
			<b><a href="https://github.com/KerberX/KxVirtualFileSystem">KxVFS</a></b> - based on <b><a href="https://github.com/dokan-dev/dokany">Dokany</a></b> - kernel-mode file system driver.
		</td>
		<td id="MO2">
			<b><a href="https://github.com/ModOrganizer2/usvfs">USVFS</a></b> - user-mode WinAPI hooks, a successor to the <b>hook.dll to support 64bit</b>.
		</td>
		<td id="MO1">
			<b>Hook.dll</b> - a user-mode WinAPI hooks (32bit only).
		</td>
		<td id="Vortex">
			Hardlinks by default,
			Symlinks or move deployment as an option on specific games,
			<b>USVFS</b> as an experimental extension (no new file support for now).
		</td>
		<td id="NMM">
			Symbolic links (symlinks).
		</td>
		<td id="WB">
			No virtualization, files are installed in the Data folder.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Virtualization Pros and Cons</td>
		<td id="KMM">
				   
			<ul><b>Pros:</b>
				<li class="li-pro">Game folder remains clean all the time as exclusively hooked programs see the mods.</li>
				<li class="li-pro">Zero overhead when installing/enabling mods or switching profiles.</li>
				<li class="li-pro">Mounter VFS visible to all processes on the system (it's kind of a con too).</li>
				<li class="li-pro">Can link mods across different drives.</li>
				<li class="li-pro">Allows top-level virtualization.</li>
			</ul>
				   
			<ul><b>Cons:</b>
				<li class="li-con">Slower than alternatives.</li>
				<li class="li-con">Requires target folder to be empty.</li>
				<li class="li-con">Huge memory consumption on large mod setups (~5 GB for 975k files).</li>
				<li class="li-con">Program startup overhead for VFS initialization.</li>
				<li class="li-con">Kernel-mode driver, requires administrator privileges to install.</li>
			</ul>
		</td>
		<td id="MO2">
				   
			<ul><b>Pros:</b>
				<li class="li-pro">Supports 64bit programs.</li>
				<li class="li-pro">Game folder remains clean all the time as exclusively hooked programs see the mods.</li>
				<li class="li-pro">Zero overhead when installing/enabling mods or switching profiles.</li>
				<li class="li-pro">Doesn't require write access to destination.</li>
				<li class="li-pro">Sources and target can be linked across different drives.</li>
				<li class="li-pro">Intercepts creation of new files in overwrite, keeping game folder clean</li>
			</ul>
				   
			<ul><b>Cons:</b>
				<li class="li-con">Can be less intuitive to users since only the programs can see the mods.</li>
				<li class="li-con">Can often be flagged by antiviruses.</li>
				<li class="li-con">Can't virtualize some top level files like load-time linked .dll.</li>
				<li class="li-con">Can lead to hard to diagnose issues in case there is a bug.</li>
				<li class="li-con">Small memory and computation overhead at runtime.</li>
				<li class="li-con">Program startup overhead for VFS initialization.</li>
				<li class="li-con">Can potentially break if Windows changes something.</li>
				<li class="li-con">Uses Overwrite folder that can require some user cleanup and management</li>
			</ul>
		</td>
		<td id="MO1">
				   
			<ul><b>Pros:</b>
				<li class="li-pro">Game folder remains clean all the time as exclusively hooked programs see the mods.</li>
				<li class="li-pro">Zero overhead when installing/enabling mods or switching profiles.</li>
				<li class="li-pro">Doesn't require write access to destination.</li>
				<li class="li-pro">Sources and target can be linked across different drives.</li>
				<li class="li-pro">Intercepts creation of new files in overwrite, keeping game folder clean</li>
			</ul>
				   
			<ul><b>Cons:</b>
				<li class="li-con">Can't be used for 64 bit programs.</li>
				<li class="li-con">Can be less intuitive to users since only the programs can see the mods.</li>
				<li class="li-con">Can often be flagged by antiviruses.</li>
				<li class="li-con">Can't virtualize some top level files like load-time linked .dll.</li>
				<li class="li-con">Can lead to hard to diagnose issues in case there is a bug.</li>
				<li class="li-con">Small memory and computation overhead at runtime.</li>
				<li class="li-con">Program startup overhead for VFS initialization.</li>
    			<li class="li-con">Can potentially break if Windows changes something</li>
				<li class="li-con">Uses Overwrite folder that can require some user cleanup and management</li>
			</ul>
		</td>
		<td id="Vortex">
				   
			<ul><b>Pros:</b>
				<li class="li-pro">Remains even when the program is not running</li>
				<li class="li-pro">Faster than alternatives because NTFS handles hardlinks directly instead of indirectly when using KxVFS or USVFS</li>
				<li class="li-pro">Deployment only necessary when adding/removing mods "set and forget"</li>
				<li class="li-pro">Windows updates shouldn't break it.</li>
			</ul>
				   
			<ul><b>Cons:</b>
				<li class="li-con">Improper removal of mod will cause mods to remain</li>
				<li class="li-con">"Dirty" data folder</li>
				<li class="li-con">Some applications may see the hardlinks as duplicates and count them as used disk space</li>
				<li class="li-con">Requires deployment</li>
				<li class="li-con">Requires full write/read access to target folder</li>
				<li class="li-con">Takes time (based on file count) to switch profiles and enable/disable mods</li>
				<li class="li-con">Can't link across drives</li>
				<li class="li-con">Can be less convenient to use for mod authors messing with mod files</li>
			</ul>
		</td>
		<td id="NMM">
				   
			<ul><b>Pros:</b>
				<li class="li-pro">Can link across partitions.</li>
				<li class="li-pro">Mostly same as Hardlinks (assuming good implementation)</li>
			</ul>
				   
			<ul><b>Cons:</b>
				<li class="li-con">Requires Admin Rights to create Symlinks.</li>
				<li class="li-con">Can leave the game folder with mess in case stuff goes wrong</li>
				<li class="li-con">Mostly the same cons as Hardlinks</li>
			</ul>
		</td>
		<td id="WB">
			<ul>
				<b>Pros:</b>
				<li class="li-pro">Does not add complexity and potential failure points with virtualization, hardlinks, or symbolic links and uses a simple and reliable file copy.</li>
				<li class="li-pro">100% Reliable with 0% chance for issues installing files into the Data folder. No problems with leftover/broken links and other inconsistencies, just normal files (that are all kept track of).</li>
				<li class="li-pro">Allows you to have your Game and downloaded mods on different drives.</li>
			</ul>
			<ul>
				<b>Cons:</b>
				<li class="li-con">Depending on the amount and size of files copying files to the Data folder may take a reasonable amount of time to an extended amount of time.</li>
				<li class="li-con">Installing 3 GB mods like Interesting NPCs can take a very extended amount of time.</li>
				<li class="li-con">Changing order, enabling/disabling mods, clearing to vanilla, requires file transfers to update Data tab contents (user decides when to apply changes so multiple ones can be applied in one step).</li>
				<li class="li-con">Requires full write/read access to target folder</li>
				<li class="li-con">Requires more space as mod archives can't be deleted (source of files to be copied in Data)</li>
			</ul>
		</td>
	</tr>
	<tr>
		<td class="feature-name">Game root directory virtualization</td>
		<td id="KMM">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="MO2">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="MO1">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="Vortex">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="NMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		<td id="WB">
			<div class="cmp-no" tooltip="Not applicable, WB does no virtualization." />
		</td>
	</tr>
	<tr>
		<td class="feature-name">New files handling (overwrite) and file changes</td>
		<td id="KMM">
			All new files end up in profile specific Overwrite.
			All changes to existing virtual files are transparently executed on the correct mod files.
		</td>
		<td id="MO2">
			All new files end up in overwrite folder.
			Ability to Drag & Drop files to existing mod, create a new mod, delete the files, leave the files there.
			Allows specifying a mod to use as overwrite for a particular program.
			All changes to existing virtual files are transparently executed on the correct mod files.
		</td>
		<td id="MO1">
			All new files end up in overwrite folder.
			Ability to Drag & Drop files to existing mod, create a new mod, delete the files, leave the files there.
			Changes to existing virtual files can sometimes lead to deleted mod files and new files in Overwrite.
		</td>
		<td id="Vortex">
			No handling of completely new files, those end up in the game folder.
			File changes without deletion are executed transparently on mod files.
			Deleted/recreated files don't automatically reflect on mod files.
			A popup for deleted/recreated files will ask user whether to use mod version or game version.
		</td>
		<td id="NMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="WB" style="width: 150px;">
			Files added or altered in the Data folder are tracked.
			New files become orphaned files.
			Orphaned files can be captured and/or removed using <a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#bain-CleanData">Clean Data</a>.
			Changed files that belong to an installer can be easily synced with the installer (e.g. to copy the cleaned version of a plugin back into its archive).
			<a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#bain-monitor">Monitor External Installation</a> tracks changes in the data folder. Wrye Bash creates an installer from both new and altered files. This can be used to track instalation from other mod managers such as OBMM, FOMM, NMM. It can also be used to manage the changes made by the CK or other tools such as FNIS or BodySlide through BAIN.
		</td>
	</tr>
	<tr>
		<td class="feature-name">VFS persistence</td>
		<td id="KMM">
			Manager runtime.
		</td>
		<td id="MO2.MO1" colspan="2">
			Only present for programs started through the manager and their child applications.
		</td>
		<td id="Vortex">
			For hardlinks, move, and symlinks it persists until purged.
			For USVFS - same as MO2/MO1.
		</td>
		<td id="NMM">
			Symlinks - persists until purged.
		</td>
		<td id="WB">
			N/A - WB uses direct file copies, so no persistence issues are possible.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Game (virtual) folder layout visualization</td>
		<td id="KMM">
			Using any file explorer (when VFS is enabled) or with dedicated Data tab.
		</td>
		<td id="MO2">
			Through dedicated Data tab, or running Explorer++ and similar programs through Mo2.
		</td>
		<td id="MO1">
			Through dedicated Data tab.
		</td>
		<td id="Vortex.NMM.WB" colspan="3">
			Not needed as Explorer already shows the correct final result.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Websites-integrations</td>
		<td id="KMM"><b>NexusMods</b>, partially <b>LoversLab</b> and <b>tesall.ru</b></td>
		<td id="MO2.MO1.Vortex.NMM" colspan="4">
			<b>NexusMods</b>
		</td>
		<td id="WB">
			Opening mod pages on NexusMods.
			Searching on Google for mods.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Nexus Mods Integration features</td>
		<td id="KMM">
			Account login,
			Download with manager,
			Mod update check
		</td>
		<td id="MO2">
			Account login, 
			Download with manager, 
			Mod update check,
			Mod endorsements,
			Mod tracking,
			Mod meta info like categories etc,
			Browser for mod description,
		</td>
		<td id="MO1">
			Integration no longer works since Nexus API update.
		</td>
		<td id="Vortex">
			<ul>
				<li>Account login</li>
				<li>Download with manager</li>
				<li>Mod update check</li>
				<li>Automatic mod update for premium users</li>
				<li>Mod endorsements</li>
				<li>Mod tracking</li>
				<li>Mod meta info like categories etc</li>
				<li>Browser for mod description</li>
				<li>New mods list</li>
				<li>download rate limiter</li>
				<li>mod tracking</li>
			</ul>
		</td>
		<td id="NMM">
			Account login, 
			Download with manager, 
			Mod endorsements,
			Mod meta info like categories etc.
		</td>
		<td id="WB">
			Opening mod pages
		</td>
	</tr>
	<tr>
		<td class="feature-name">Web-integration extent</td>
		<td id="KMM">
			<b>NexusMods</b>: Account, mod updates, mod source, downloads.
			<br>
			<b>LoversLab</b>: mod source.
			<b>TESALL.RU</b>: mod source.
		</td>
		<td id="MO2.MO1.Vortex.NMM" colspan="4">
			Account, mod updates, mod source, metadata query, downloads, endorsements.
		</td>
		<td id="WB">
			Mod source, searching on Google.
		</td>
	</tr>
	<tr>
		<td class="feature-name">
			Auto-update check
		</td>
		<td id="KMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="MO2">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="MO1">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="Vortex">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="NMM">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="WB">
			<div class="cmp-no" />
		</td>
	</tr>
	<tr>
		<td class="feature-name"><span flow="right" tooltip="Integrated download manager meaning the mod manager has internal download capabilities and uses can see the files being downloaded">Integrated download manager</span></td>
		<td id="KMM">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="MO2">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="MO1">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="Vortex">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
			Download rate limiter available
		</td>
		<td id="NMM">
			<div class="cmp-yes" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203989803204630/tick.png"/>
		</td>
		<td id="WB">
			<div class="cmp-no" />
		</td>
	</tr>
	<tr>
		<td class="feature-name">Mod Categories</td>
		<td id="KMM">
			Custom tag system.
		</td>
		<td id="MO2">
			Import from Nexus, support for custom categories.
		</td>
		<td id="MO1">
			Broken import from Nexus, support for custom categories.
		</td>
		<td id="Vortex">
			Import from Nexus, support for custom categories.
		</td>
		<td id="NMM">
			Import from nexus, custom categories?
		</td>
		<td id="WB">
			<a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#bainAddMarker">Customizable marker system</a> for archives,
			<a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#mods-commands">customizable groups system</a> for plugins.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Problem detection</td>
		<td id="KMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="MO2">
			<ul>
				<li>Plugins with missing masters</li>
				<li>Files in overwrite</li>
				<li>Form 43 plugins for Skyrim SE</li>
				<li>Script Extender plugin load failure</li>
				<li>Need to run FNIS</li>
				<li>Presence of files with attributes that the game can't handle</li>
			</ul>
		</td>
		<td id="MO1">
			<ul>
				<li>Plugins with missing masters</li>
				<li>Files in overwrite</li>
				<li>Need to run FNIS</li>
			</ul>
		</td>
		<td id="Vortex">
			<ul>
				<li>Bug report automation in menu</li>
				<li>Notifications in the bell icon including xSE error notifications.</li>
				<li>Plugins with missing masters</li>
				<li>Form 43 plugins for Skyrim SE</li>
				<li>Incompatible BSA/BA2 detection</li>
				<li>Generate Report option to generate shareable report about mods installed, including details of selected mod</li>
			</ul>
		</td>
		<td id="NMM">
			<ul>
				<li>Missing masters</li>
			</ul>
		</td>
		<td id="WB">
			<ul>
				<li>Missing masters</li>
				<li>Out of order masters</li>
				<li>Missing strings files</li>
				<li>Form 43 plugins for Skyrim SE</li>
				<li>ESL verification</li>
				<li>File timestamp conflicts</li>
				<li>Ghosted plugin verification</li>
				<li>Dirty edits</li>
				<li>Deactivate and NoMerge verification</li>
				<li>Mismatched BSA versions</li>
				<li>Directory thrashing in Oblivion</li>
				<li>Encoding problems</li>
				<li>Load order verification & sanitization</li>
				<li>Unrecognized save and plugin headers</li>
			</ul>
		</td>
	</tr>
	<tr>
		<td class="feature-name">GUI customization</td>
		<td id="KMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/> 
		</td>
		<td id="MO2">
			Comes with 15+ built in styles, more available on Nexus.
			Styles created through QSS files, with CSS like syntax.
			Very limited color customization for highlights and separators from menu.
		</td>
		<td id="MO1">
			Comes with some built in styles, more available on Nexus.
			Styles created through QSS files, with CSS like syntax.
		</td>
		<td id="Vortex">
			Comes with 3 built in styles, several on nexus, customizable via CSS/SASS.
			Change colors and fonts via a setting menu.
			MO-esque extension available to make your vortex appear as if it was mo2
		</td>
		<td id="NMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>?
		</td>
		<td id="WB">
			<a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#tools-colors">Change colors via a settings menu</a>.
		
		</td>
	</tr>
	<tr>
		<td class="feature-name">Exporting modlist/pluginlist</td>
		<td id="KMM">
			Non-customizable export of modlist to HTML file.
			Import and export of plugins list.
		</td>
		<td id="MO2">
			Customizable modlist export to CSV file.
			Otherwise only simple copy of loadorder.txt and modlist.txt.
		</td>
		<td id="MO1">
			Less customizable modlist export to CSV file.
		</td>
		<td id="Vortex">
			Generate Report option generates a online document with list of plugins
			extension automatically uploads to modwatch				   
		</td>
		<td id="NMM">
			
			Export plugin and mod list to clipboard or text file.
		</td>
		<td id="WB">
			Export plugin and/or mod list to clipboard.
			Export of various other lists (e.g. applied tags) to clipboard, text files or CSV files.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Modlist features</td>
		<td id="KMM">
			Color-coding of each mod,
			collapsible separators (using tag system).
		  
			<b>Mod metadata:</b>
			name,
			priority,
			version,
			author,
			tags,
			sources,
			date installed,
			date uninstalled,
			folder,
			install package,
			signature
		</td>
		<td id="MO2">
			Grouping by Category or Nexus Id.
			Filtering with advanced filters and regex search.
			Colored separators.
			Avanced mod counters.
			Conflict highlighting on selection.
			Plugin Highlighting on selection.
			Full refresh from disk.
			Backup, export as CSV.
			Update check.
			Various Keyboard shortcuts and support for multi selection operations.
	 
			<b>Mod metadata:</b>
			Conflits,
			Catagories,
			Contents,
			Version,
			Target Game,
			Custom Notes,
			Install time,
			Nexus ID,
			Flags: Endorsed,Tracked,hiddenFiles,valid
		</td>
		<td id="MO1">
			Mostly same as Mo2, but somethings are missing like separators and notes.
		</td>
		<td id="Vortex">
			<ul>
			<li>Advanced mod counters.</li>
			<li>Update check.</li>
			<li>Grouping by state, category, content, author, version, source.</li>
			<li>Filter by state, name, version, install time, category, endorsed state, content, dependency resolution.</li>
			<li>collapsible separators</li>
			<li>Update check, install from file, manage rules.</li>
			<li>Various Keyboard shortcuts and support for multi selection operations.</li>
			<li><ul><b>Mod metadata:</b>
			<li>mod name,</li>
			<li>version number,</li>
			<li>author,</li>
			<li>install time,</li>
			<li>source (nexus or not),</li>
			<li>category,</li>
			<li>endorsed,</li>
			<li>content,</li>
			<li>priority,</li>
			<li>dependencies,</li>
			<li>highlight</li></ul></li>
			</ul>
		</td>
	
		<td id="NMM">
			<ul>
				<li>Filter by category</li>
				<li>Sort mod list by Name, Cetegory, Install Date, Download Data, Endorsment, Download ID, Mod version, Author</li>
				<li>List plugin dependencies (Plugin Tab)</li>
			</ul>
			<ul>
				<b>Mod metadata</b>
				<li>Name, Version, Author, Website, Description</li>
			</ul>
		</td>
		<td id="WB">
			<ul>
				<b><a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#mods">Mod context menu</a></b>
				<li>Duplicate, Hide, Rename, Backup, Create Snapshot, Revert to Backup or Snapshot for plugins from the Mods tab.</li>
				<li>List Bash Tags</li>
				<li>Mod Info Report of plugin name, installer, modified date, file size, author, CRC</li>
				<li>List file dependencies</li>
				<li>Jump to assigned Installer from Mods List</li>
				<li>Check ESL Qualifications for ESL enabled games</li>
				<li>Export/import various subrecords to/from .csv files</li>
				<li>List LOOT Cleaning Information</li>
				<li>Copy .esp to .esm file (Creates file in Data Folder)</li>
				<li>Add Remove ESL or ESM flags</li>
				<li>Add ESM Flag to Masters (ESM flag(s) must be manually removed)</li>
				<li>Create empty plugins for missing masters</li>
			</ul>
			<ul>
				<b>Mod metadata</b>
				<li>Import, Export, Edit, Assign to group</li>
				<li>List ObjectIDs with Editor ID by record type</li>
				<li>View, Edit, or Assign Readme Files</li>
			</ul>
		</td>
	</tr>
	<tr>
		<td class="feature-name">Game files preview</td>
		<td id="KMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="MO2">
			.DDS Textures complete preview support.
			BSA/BA2 content preview.
			Normal images and text (.txt, .ini, .cfg, .log, .json) files.
		</td>
		<td id="MO1">
			.DDS Textures partial preview support
			Normal images and .txt files.
		</td>
		<td id="Vortex">
			Will attempt to open in default program for the file type
			ie: nif in bodyslide, dds in gimp or WTV, txt in notepad
		</td>
		<td id="NMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="WB">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
	</tr>
	<tr>
		<td class="feature-name">
			Available translations
			<br>
			<i>(default distribution)</i>
		</td>
		<td id="KMM">
			<ul>
				<li>English</li>
				<li>Russian</li>
			</ul>
		</td>
		<td id="MO2">
			<ul>
				<li>English</li>
				<li>French</li>
				<li>Dutch</li>
				<li>Polish</li>
				<li>Italian</li>
				<li>Spanish</li>
				<li>Russian</li>
				<li>Portuguese</li>
				<li>Chinese</li>
				<li>Japanese</li>
			</ul>
		</td>
		<td id="MO1">
			<ul>
				<li>English</li>
				<li>..?</li>
			</ul>
		</td>
		<td id="Vortex">
			many available via extensions
		</td>
		<td id="NMM">
			<ul>
				<li>English</li>
				<li>German</li>
			</ul>
		</td>
		<td id="WB">
			<ul>
				<li>English</li>
				<li>Chinese (Simplified)</li>
				<li>Chinese (Traditional)</li>
				<li>German</li>
				<li>Italian</li>
				<li>Japanese</li>
				<li>Portuguese</li>
				<li>Russian</li>
			</ul>
			<br/>
			Non-English languages are <b>very</b> outdated, and further localization efforts are currently postponed until Wrye Bash has been ported to Python 3.
			<a href="https://wrye-bash.github.io/docs/Wrye%20Bash%20Advanced%20Readme.html#international">Localization can be easily exported</a> and edited with Notepad++ or Poedit.
		</td>
	</tr>
	<tr>
		<td class="feature-name">Extensions</td>
		<td id="KMM">
			<div class="cmp-no"/>
		</td>
		<td id="MO2.MO1" colspan="2">
			Bundled with some extensions, additional are available at <b>NexusMods</b> and <b>GitHub</b>.
			Supports C++ and Python extensions.
		</td>
		<td id="Vortex">
			Additional extensions are available at <b>NexusMods</b>.
			Supports JavaScript, C++, and various other electron extensions.
			Extensions are available to install from within the program.
		</td>
		<td id="NMM">
			<div class="cmp-no" />
			<img src="https://cdn.discordapp.com/attachments/347329036084707330/680203972564484176/cross.png"/>
		</td>
		<td id="WB">
			<div class="cmp-no" />
		</td>
	</tr>
	<tr>
  
		<td class="feature-name">Current development state and maintainers</td>
		<td id="KMM">
			Open Source, fully released.
			Maintained and not so much actively developed on by Kerber (non-paid developer), with highly irregular feature updates.
		</td>
		<td id="MO2">
			Open Source, fully released.
			Maintained and actively developed on by MO2 Team (community non-paid developers), with regular feature updates.
		</td>
		<td id="MO1">
			Open Source, fully released.
			No longer maintained or updated.
		</td>
		<td id="Vortex">
			Open Source, fully released.
			Maintained and actively developed by NexusMods (paid professionals), with frequent feature updates and fixes.
		</td>
		<td id="NMM">
			Open Source, beta release.
			Discontinued by NexusMods in favor of Vortex.
			Currently maintained by a few members of the community.
		</td>
		<td id="WB">
			Open Source, fully released.
			Maintained and actively developed by <span tooltip="Made up of Utumno, Ganda, Infernio. Record decoding by Sharlikran. Rare updates by Lojack. Documentation updates by Felis and Wrye Bash team">Wrye Bash Team</span> (community non-paid developers) with regular feature updates.
		</td>
	</tr>
</tbody>

Supplementary information

  1. Any content inside the mod archive. This installation mode usually requires user input to some extent.
  2. Just some files such as .esm/.esp and/or Data folder inside the mod archive.

Page contributors

Add a custom footer
Add a custom sidebar
Clone this wiki locally