dwstiffler Posted June 14, 2019 Share Posted June 14, 2019 With Nmm you could add a mod to the manager from a file and it would get all the info about the mod from nexus including updates, but with Vortex it won't do this, you have to redownload the file to get it to be recognised for info and available updates. Am I doing something wrong or looking in the wrong area? Link to comment Share on other sites More sharing options...
rmm200 Posted June 14, 2019 Share Posted June 14, 2019 That is very interesting. A downloaded mod is just an archive; a zip file or a rar. It includes no information about the mod name, version, or download site.All that information is only available as part of the download process from nexusmods.So how does NMM create all that information from nothing with a downloaded archive? Link to comment Share on other sites More sharing options...
HadToRegister Posted June 14, 2019 Share Posted June 14, 2019 With Nmm you could add a mod to the manager from a file and it would get all the info about the mod from nexus including updates, but with Vortex it won't do this, you have to redownload the file to get it to be recognised for info and available updates. Am I doing something wrong or looking in the wrong area?NMM creates it the same way Vortex does, by the ID Number in the URL No you don't, you don't need to download the mod again. All you need to do is double click on the Mod in the MOD TAB, a panel opens up on the the right, then change the SOURCE to NEXUS MODS, then click the GUESS button.(Edited for focus) Link to comment Share on other sites More sharing options...
Rattledagger Posted June 14, 2019 Share Posted June 14, 2019 That is very interesting. A downloaded mod is just an archive; a zip file or a rar. It includes no information about the mod name, version, or download site.All that information is only available as part of the download process from nexusmods. If mod archive includes FOMOD\info.xml Vortex will change the current name displayed on mods-tab with the name included in this file, even if mod not downloaded from Nexus.This happens even if mod isn't installed. As part of the new Nexus API, Vortex sends a hash to a Nexus-server and if Nexus recognizes the mod, the mods information about mod id etc. will be filled-out in Vortex. Not sure if this happens automatically after mod has been added, or if Vortex only asks for this information then you install the mod. If Nexus does not recognize the mod, or you've not yet installed the mod, you can use HadToRegister method to get information. Note, if not mistaken, Vortex won't check for updates for mods that isn't installed. Link to comment Share on other sites More sharing options...
dwstiffler Posted June 14, 2019 Author Share Posted June 14, 2019 Ahhhhhh!!! Thank you ever so much, got it. and didn't think about this.. :cool: :cool: :smile: Link to comment Share on other sites More sharing options...
dizietemblesssma Posted June 14, 2019 Share Posted June 14, 2019 If mod archive includes FOMOD\info.xml Vortex will change the current name displayed on mods-tab with the name included in this file, even if mod not downloaded from Nexus.This happens even if mod isn't installed. This topic is exactly what I tried to discuss elsewhere, I found while modding morrowind that a fomod folder with just info.xml in it resulted in vortex naming a manually added mod accordingly, but with the moduleconfig.xml as well, it didn't, In the first case it also left the fomod folder in the staging area along with esps etc.In troubleshooting this I acknowledged that the fomods in question were mine, built using Fomod Creation Tool 1.7.0.37. I pasted a pair of info/moduleconfig xml files to see if anyone could point out any errors but no-one could.I am therefore very interested in other peoples experiences of manually adding fomod installed mods in vortex with regard to mod naming etc. Link to comment Share on other sites More sharing options...
HadToRegister Posted June 14, 2019 Share Posted June 14, 2019 If mod archive includes FOMOD\info.xml Vortex will change the current name displayed on mods-tab with the name included in this file, even if mod not downloaded from Nexus.This happens even if mod isn't installed. This topic is exactly what I tried to discuss elsewhere, I found while modding morrowind that a fomod folder with just info.xml in it resulted in vortex naming a manually added mod accordingly, but with the moduleconfig.xml as well, it didn't, In the first case it also left the fomod folder in the staging area along with esps etc.In troubleshooting this I acknowledged that the fomods in question were mine, built using Fomod Creation Tool 1.7.0.37. I pasted a pair of info/moduleconfig xml files to see if anyone could point out any errors but no-one could.I am therefore very interested in other peoples experiences of manually adding fomod installed mods in vortex with regard to mod naming etc. Well, having spent a couple of weeks downloading and converting Oblivion mods to work with Vortex, I ended up with a bunch of mods with my nickname in the front part, so I could tell quickly which mods I had converted,It wasn't until I got about 20 mods converted, and was manually adding the mod info with the right hand panel, that it dawned on me to start naming the Mods I had converted, THIS WAY: 'My Nickname' Mod Name - MOD ID.7z So something like "CK Realistic Leveling - 13879.7z" Putting the MOD ID at the end, allowed me to quickly double click on my Converted mod, open the right hand panel, tell Vortex the source is NEXUS MODS, then I could type the MOD ID, at the end of the archive name, into the Nexus MOD ID entry, and Vortex would look up the actual mod info, even though the mod was completely repackaged differently, and named differently.This also enabled the ability to Endorse the mods right from Vortex It was a good self tutorial on how to manipulate Vortex, and the Nexus Info for a custom/repackaged/renamed mod Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.