0.25.3

[thashepherd]

[0.25.3]

Changes

• mod.json and AuroraLoader now support changelog files (there's a Changelog button next to the Config File button in the mod manager now)
• AuroraLoader now has a changelog as well, and there's a button for accessing it
• Aurora version targeted by the currently loaded game is shown in parenthesis (and only mods compatible with the loaded game's version are shown - but that was already the case)
• Additional message after updating Aurora telling user to create a new game in order to use the new version
• Got rid of modal dialogs prompting user to update Aurora/the loader on launch (there are a lot of cases where people want to hang back at 1.9.5 and I don't want to annoy them - IMHO the snazzy new update icons are obvious enough). This also means that the dialogs aren't re-shown every time RefreshInstallData() is called.
• Behavior when creating new save games is a bit more intuitive (the 'new game' button is disabled when it can't be clicked, and the user is presented with a confirmation dialog before creating a fresh DB that tells them the version of Aurora that the new game will target - in later Loader versions, we may allow them to select this manually)
• Selected executable mod is no longer reset after checking or unchecking 'Enable Poweruser Mods'
• Lists of available mods are now updated after making changes in the Mod Manager window

Bugfixes

• Buttons for opening a mod's config & changelog files are disabled if the mod hasn't actually been installed yet
• Fixed typo in Aurora & loader update confirmation dialogs
• Confirmation dialogs are now shown when the user decides to manually update either Aurora or the loader (previously behavior was inconsistent)
• Removed an unused click handler & fixed some typos in the codebase
• Mod manager is now modal

Builds

• Build action updated to build loader on the LTS version of .NET Core 3.1
• Build action produces a self-contained executable (i.e. the ~55mb executables typically updated with @01010100b's releases, and expected by the Loader's auto-update functionality). We are still working to debug a few reports of the loader not launching due to compatibility issues - please get in touch if you're experiencing issues!
• Commit SHA appended to name of artifact uploaded by build action

Release candidate download: https://github.com/Aurora-Modders/AuroraLoader/releases/tag/0.25.3-rc2

[01010100b]

As for the modal dialog on launch, can you check the behaviour in airplane mode? That dialog was there because if there was no internet it would take the loader 10 seconds to time-out on it, which would appear to the user as the loader not having started.

[thashepherd]

Great catch, I forgot that's why you added it - will revert

[thashepherd]

• ~Freshly installed mods don't immediately show up in lists if they're installed when the 'Enable Mods' / 'Enable Poweruser Mods' checkboxes are already checked. User needs to toggle one of them in order to refresh.~
• AuroraLoader_new.exe and newly downloaded mod.json are not being cleaned up automatically (auto-update broke, for whatever reason). We should probably download directly to the mod directory and only then copy the .exe/readme/mirrors/bat file to root. (and honestly, the batfile likely doesn't need to be outside of the standalone exe)
• MS Defender flags update_loader.bat (as well as the .exe, for what it's worth)
• ~Enabling poweruser mods should not reset exe selection~