A Redundant question about redundant mods?

[JamesRook]

I've been looking through posts on the forum to get a handle on why mods are marked redundant. Some things I understand, like installing the same mod twice or an updated version of a mod and not clearing out the first, but I don't understand why some Hot fixes or updates register as redundant. For example, I have Riften Docks Overhaul 2.0 installed and then the update 2.3. Vortex complains 2.3 is redundant. 2.3 should overwrite 2.0 and is not redundant. Very confusing to me.

[showler]

Redundant usually means that one mods files are being completely overwritten by another.

 

If it is showing 2.3 as redundant due to 2.0 it would mean that they are installed as separate mods rather than as an update and that the files in 2.3 are being overwritten by the files in 2.0.

 

You should be able to go into the Rules list and set the 2.3 files to "load after" the 2.0 files and that will fix it.

[Petty7]

This is my (bad) experience with the "Some mods are redundant" problem, which I have often:

Mod A contains file1, file2, file3. It was installed correctly.
Mod B contains a different file2, I want it overwrites file2 from Mod A, so I simply install Mod B and then I get:

"There are unresolved file conflicts"
"Some mods are redundant"

To solve the conflicts I select load Mod B "after (suggested)" Mod A, then click on "Save" and the conflict message is gone, but the "Some mods are redundant" message is still there so I check it and it says:

---
Mod name: Mod B

Deployed files (0)
None

Files overwritten by other mod (1)
file2 (Hash not calculated) - Mod A

Files not deployed (0)
None

Files that are supposed to be deployed but weren't found (0)
None

Files that are present but couldn't be read (0)
None
---

Conclusion: Mod B was not installed. To this day, I couldn't find a solution for this problem.

Edited January 3 by Petty7

[showler]

You can choose individual files to overwrite, not just entire mods.

[Petty7]

Clarification: Mod B only contains file2, nothing else.

[Zanderat]

Not sure I completely understand the issue.  But redundant means that one mod entirely overwrites another mod.  So the overwritten one, since nothing of it is being loaded, is not needed.

[showler]

They're saying that mod A, with files x, y and z should be partly overwritten by mod B, which only has file y.  For some reason that does not appear to be happening.

We'd probably need some images of their settings since the behaviour they are describing is entirely contrary to how things are supposed to work.

[Pickysaurus]

Quote

Mod name: Mod B

Deployed files (0)
None

Files overwritten by other mod (1)
file2 (Hash not calculated) - Mod A

Files not deployed (0)
None

Files that are supposed to be deployed but weren't found (0)
None

Files that are present but couldn't be read (0)
None

This seems to indicate that Mod B only contains a single file. 

[showler]

Yes, but the question is why that file is being overwritten by Mod A given that they chose "load Mod B "after (suggested)" Mod A,"?

[Pickysaurus]

It might simply be that you didn't deploy after making the rule change. Vortex only re-checks redundant mods at the end of a deploy if I recall.