v1.0.3 Release of Relink Mod Manager
Visit the GitHub Wiki for detailed instructions and more information.
Note: Relink Mod Manager is built on .NET 8. If you encounter issues, ensure you have the .NET Desktop Runtime 8 installed.
To use Relink Mod Manager download the Relink.Mod.Manager.zip below, extract the exe to anywhere on your PC, such as the Desktop, and run it.
Reminder that directly importing Reloaded II Mods is supported. Please read the Wiki page for more information.
Changes
- The Mod Option Bindings filter for Unreferenced Files will highlight the last selected filter option during that window session.
- Mod Details have the scrollbar adjusted to be within the tab contents instead of scrolling the entire panel when there is a lot of content displayed at once.
- When selecting the "I Restored My Files" option during the Mods Already Installed error the stale "data_volatile_backups" directory will be cleaned out to avoid keeping old irrelevant mod data.
- Mods are now stored via their Mod Name when put into Mod Archive Storage instead of retaining their original Archive Filename.
- This allows mods that have had their archive renamed, such as those uploaded to Nexus Mods, to still be eligible for in-place updating rather than needing to delete the previously installed Mod manually.
- Nearly any Mod previously created with Relink Mod Manager already used the same archive name as the Mod's name so this will have effectively zero user-facing impact.
Fixes
- When creating a new Mod and using a Mod directory that contains more than just a
ModConfig.jsonin the root directory will no longer result in a crash during Mod Option Bindings.- It is still recommended to always store Mod files in a sub directory such as a
datafolder to keep them more organized.
- It is still recommended to always store Mod files in a sub directory such as a
- Fixed a crash when updating a duplicate Mod but no existing Mod was selected in the Imported Mods browser list.