Jump to content

incorrectly saying mode are redundant.


MadeUpName92

Recommended Posts

 

No its definitely Mods are redundant.

With the older Version of Vortex it was same for me it say me there is a Conflict and i fix it same as you with rules and all Work fine with this actual Version of Vortex near all Conflict even for Mods im sure they have Conflicts disappear and that with no rules but i get a lot of message that even very important main Mods are Redundant.

Today i Fix some of the redundant Mods but don't know how.I Change only the place from my staging Folder from one folder to another on the same drive.After i reinstall some of the Redundant Mod as see that some of the Message for some Mod are redundant disappear and it Work for most of the Mods now only 5 Mods remain that im not able to Fix.Dont know what is wrong with my Vortex then as i write for me its really buggy hope the next version fix it or i go back to the older Version where all was perfect.

 

 

 

Sounds like if you already have the mods installed, and upgrade, then the news version of Vortex keeps complaining about them being redundant, but if you uninstall and reinstall, then the problem gets fixed, which is why Augusta didn't have the problem when she installed the same mods.

 

I wonder if you just PURGED and then REPLOYED your mods, if Vortex would fix itself.

Link to comment
Share on other sites

Purging shouldn't affect the redundancy message.

 

The way the redundancy detection works isn't too complicated.

After mods have been deployed, vortex goes through all enabled mods and looks at the deployment manifest (which is saved in "<game>\data\vortex.deployment.json" for bethesda games) and checks if there is any file that has this mod as its source.

 

There are two possible explanations, both of which have been mentioned before: Either you have these mods installed and enabled twice so that the newer version overwrites all files of the older one or the mod doesn't actually contain any files in the first place.

Link to comment
Share on other sites

Purging shouldn't affect the redundancy message.

 

The way the redundancy detection works isn't too complicated.

After mods have been deployed, vortex goes through all enabled mods and looks at the deployment manifest (which is saved in "<game>\data\vortex.deployment.json" for bethesda games) and checks if there is any file that has this mod as its source.

 

There are two possible explanations, both of which have been mentioned before: Either you have these mods installed and enabled twice so that the newer version overwrites all files of the older one or the mod doesn't actually contain any files in the first place.

Dont understand how that can be happen if that is the Problem.As i upgrade only Vortex when the new Version come out and i don't change nothing in my Load order or Mods.With the Version before all was really Perfect i work for Days to Fix all my Mods with Vortex as before i was using NMM.Before the Update of Vortex there was no Message or any Problem from Vortex he say me all is Perfect and all Mods Work right ingame.Only one Translation i was not able to let Work ingame but it was not a so great Problem.

 

Try out just now the new test Version from Vortex and all Problems disappear. So it mean it was a Vortex Problem and not a Mod problem as now i don't have any Message that something is redundant and all Mods work again perfect ingame.

Link to comment
Share on other sites

  • 3 weeks later...
Guest deleted34304850

the whole mods are redundant feature is a real pain.

this morning i downloaded several updates after the game and f4se were updated earlier this week. i am replacing mods with updated versions, that should not provoke vortex to tell me mods are redundant as i am replacing, not creating a new version. the replacement should negate any message about mods being redundant as they are being replaced by a newer version of the same mod.

it needs a bit of work because at the minute, it's a hindrance rather than an enhancement.

Link to comment
Share on other sites

  • 8 months later...

Worked for me by manually going into the file directory(seeing my files had not been deleted for some reason, even though I uninstalled), and I deleted them there. Then I just went through a deployment and confirmed deletion in Vortex. Reinstalled the mods and it worked. It's hard to blame Vortex because I love it, but I think in this case, it's due to Vortex we all have this issue. It should be adressed by someone who bother, but Im not going to do it.

Link to comment
Share on other sites

  • 6 months later...

Just got the "Major Update" to vortex. Now I keep getting a message that some mods are reduntant. This message is totally wrong.

 

Most are optional files for their parent mod. One is just a bat file with it's own keybind for taking screenshots.

 

The optional files are supposed to be doing the overwriting, Toxic Raider was broke but I was able to fix by manually re-solving the conflict.

 

Rogue Prototype seems to still be working ok.

 

The Nuka World one is optional file for True storms. I'd have to go there and see if I can change the weather. I'll have to find an old save to do it.

 

And I don't know what would over write the optional bodyslide files for Heather.

 

 

attachicon.gif Capture.JPG

I had the same problem and just individually reinstalled all of my mods because I saw that it was only doing it to mods installed BEFORE the update but I only have a few dozen and I was more than a little annoyed, I couldn't imagine what it would be like if I had over 200 like some people. I know this was posted over a year ago, this is for the people that wound up in this thread through google like I did as a last resort if nothing else works.

Link to comment
Share on other sites

  • 1 month later...

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...