Migrate to new settings file to avoid compat issues#26
Merged
Conversation
Holt59
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While the settings did upgrade smoothly, backward compatibility is a bigger issue that I first considered.
Running old nxmhandlers will break the MODL settings and can cause the launch args to transfer to the NXM handler settings.
This breaks the NXM link forwarding between MO2 installs as the args no longer start with the nxm:\ schema.
Now we copy the old nxmhandler.ini to a new downloadhandler.ini (if it doesn't exist) and use that for new nxmhandler.exe versions.
This effectively segments the settings between new and old handlers, preventing mixups when users have multiple differing MO2 versions.