We've released a new version of the Nexus Mod Manager today that provides official support for an offline mode as well as a few bug fixes. While the old NMM worked while offline it was never officially supported. Version 0.31.2, the latest version, provides support for an offline mode as a button at the login screen. If you don't want to login, or don't have a connection, you can use the "Offline" button to use NMM in offline mode. You won't be able to download files or view latest version information of your already installed mods, but most other features within NMM will continue to work.
0.32.0 as im sure you guys are aware, messed up load order for many people, and will sometimes ask for re-login.
After fixing load order with BOSS and then sorting some manually, I went in-game. Quit. Started up NMM again and load order was RESTORED to what I had before ... which would have been fine the first time, but actually letting BOSS sort them again was better I think, since I had many new mods before the latest BOSS-sorting...
Anyway ... did BOSS, again, sorted manually, again ... and now load order is stuck like it should be.
The old versions are no longer supported for downloading. They were using our old, insecure code and we wanted to switch it off as soon as possible to prevent conflicts.
I am still using an older version of NMM but every time I try to download a file now I get the error message saying the file doesn't exist. Should I upgrade to the latest version? Any help would be most appreciated.
Give Feedback
124 comments
Comments locked
A moderator has closed this comment topic for the time beingAfter fixing load order with BOSS and then sorting some manually, I went in-game. Quit. Started up NMM again and load order was RESTORED to what I had before ... which would have been fine the first time, but actually letting BOSS sort them again was better I think, since I had many new mods before the latest BOSS-sorting...
Anyway ... did BOSS, again, sorted manually, again ... and now load order is stuck like it should be.
Under [Registry], the .omod one should be
Root: HKCR; Subkey: .omod; ValueType: string; ValueName: ; ValueData: OMOD_File_Type; Flags: uninsdeletekey; Tasks: associateOmodFiles
Root: HKCR; Subkey: OMOD_File_Type; ValueType: string; ValueName: ; ValueData: Oblivion Mod Archive; Flags: uninsdeletekey; Tasks: associateOmodFiles
Root: HKCR; Subkey: OMOD_File_Type\DefaultIcon; ValueType: string; ValueName: ; ValueData: {app}\{#MyExeName},0; Tasks: associateOmodFiles
Root: HKCR; Subkey: OMOD_File_Type\shell\open\command; ValueType: string; ValueName: ; ValueData: """{app}\{#MyExeName}"" ""%1"""; Tasks: associateOmodFiles
not “Tasks: associateFomodFiles”.
Not a huge problem but annoying.
I know exactly what you mean. Sadly, though, that would be just too easy.