This page was last updated on 16 January 2025, 8:56AM
Changelogs
Version 1.0.2
Fixes a weird issue with the load order when unmanaging games (https://github.com/Nexus-Mods/Vortex/issues/13342)
Version 1.0.1
Set a hard requirement of Vortex 1.2.0 and above.
Fixed "log is not defined" that may occur in some cases.
Version 1.0.0
Swapped out the custom load order page for the generic one included with Vortex. This will allow for all future UI/UX improvements to be applied without updating the extension.
New load ordering page supports only PAK mods and can be toggled to show the mods in ascending or descending order.
New load ordering page allows you to toggle the images on or off (requires Vortex 1.3.0+)
When installing a mod with multiple PAK files, Vortex will now ask you to confirm which ones you want to install.
Mods now have a numerical index rather than using AAA, AAB, etc (although the folders are still named this way in the ~mods folder for compatibility).
Vortex now supports non-PAK mods. By default, these will be installed to the game folder, so it is recommended that mod authors include empty folders to make up the desired path.
The game can now be detected when installed with Steam, Origin or Epic Games. (Thanks bleedn)
If a mod installed multiple PAK files, the load order entry will include a count to remind you.
Version 0.1.4
Cleaned up the info.json file to prevent problems installing manually.
Version 0.1.3
Fixed a bug where Vortex would crash if you somehow enabled a mod without any mods in the Vortex DB. https://github.com/Nexus-Mods/Vortex/issues/6933
Version 0.1.2
Fixed possible error from an undefined mod (https://github.com/Nexus-Mods/Vortex/issues/6550)
Version 0.1.1
Moved the API registrations into context.once() as they don't work correctly in main().
