BD Armor and Clothing Collection -> ESP Update...

[grw]

So, there is a problem with this mod (V 1.0) and it's ESP update (V 1.4).

 

https://www.nexusmods.com/skyrimspecialedition/mods/25705

 

Vortex want's always deaktivate the 1.4 ESP update, but I think it is needed, like it says... it is an update of ESP only.

Discarding doesn't work. On every new opportunity (event) Vortext wants to deactivate the ESP update again.

[HadToRegister]

When you installed the update, did you pick REPLACE or NEW VARIANT?

[grw]

When you installed the update, did you pick REPLACE or NEW VARIANT?

 

 

That's the problem. It is a standalone mod installation and not a replacement! So this option does not appear either! Is will only replace the ESP.

Maybe the mod author should change this?

 

Is there any way to force Vortex to keep this always active as a file conflict?

[HadToRegister]

 

When you installed the update, did you pick REPLACE or NEW VARIANT?

 

 

That's the problem. It is a standalone mod installation and not a replacement! So this option does not appear either! Is will only replace the ESP.

Maybe the mod author should change this?

 

Is there any way to force Vortex to keep this always active as a file conflict?

 

 

The mod author doesn't need to change anything.

I just looked at it, the Update, has the same named ESP in the file as the original, so what should be happening, is when you install the UPDATE, Vortex should either be asking for a NEW VARIANT, or REPLACE, or, you should get a conflict notification, where you can tell the 1.4 to LOAD AFTER the 1.0 version.

 

That's how Vortex handles that.

 

Did you try and install the update by having Vortex search for the Mod Update, and install it from the VERSION column?

 

I don't update that way, I find it 'finicky'

 

I would uninstall the 1.4 mod, and the 1.0 mod, then Reinstall the 1.0 mod, and then reinstall the 1.4 mod FROM THE MODS TAB, not the VERSION COLUMN, because then, Vortex will say there's a Conflict, and then you can tell Vortex that version 1.4 should LOAD AFTER 1.0

 

 

[grw]

I think the mod author could easily fix the problem.
In Vortext V 1.0 appears as "BD Armor and Clothing Collection" and the ESP update as "BD Armor and Clothing Collection ESP Update". Vortex seems to think they are two different mods and always wants to install 1.4 before 1.0 and therefore disable it.
If the 1.4 update were also simply called "BD Armor and Clothing Collection", both would appear together in the version column as one mod and not as two different mods!
How else should Vortext determine that it is one mod?
Unfortunately many mod authors make such a name mix that there is hardly any reasonable logic behind it.

 

In Vortex, however, I now lack the ability to force the installation from V1.4 after V1.0. Or I can't find the right place to do it. But I can't change the loading order in Vortex as it seems.

 

Edit:

Strange... after your hint to re-install it again (V1.4) a conflict message came up and I could position it after V1.0. This did not appear so far...

 

Can be a fix in latest Vortext update?

[HadToRegister]

I think the mod author could easily fix the problem.

In Vortext V 1.0 appears as "BD Armor and Clothing Collection" and the ESP update as "BD Armor and Clothing Collection ESP Update". Vortex seems to think they are two different mods and always wants to install 1.4 before 1.0 and therefore disable it.

If the 1.4 update were also simply called "BD Armor and Clothing Collection", both would appear together in the version column as one mod and not as two different mods!

How else should Vortext determine that it is one mod?

Unfortunately many mod authors make such a name mix that there is hardly any reasonable logic behind it.

 

In Vortex, however, I now lack the ability to force the installation from V1.4 after V1.0. Or I can't find the right place to do it. But I can't change the loading order in Vortex as it seems.

 

Edit:

Strange... after your hint to re-install it again (V1.4) a conflict message came up and I could position it after V1.0. This did not appear so far...

 

Can be a fix in latest Vortext update?

 

That is exactly how the install should've worked in Vortex.

 

You install Version 1.0

 

the Mod Author uploads an updated ESP ONLY, so you install the newer esp and vortex says, there's a file conflict, then you tell vortex to load the newer esp (1.4) AFTER the older one.

 

This is exactly how it should work, it's not a fault of the mod or mod author.

[grw]

You install Version 1.0

the Mod Author uploads an updated ESP ONLY, so you install the newer esp and vortex says, there's a file conflict, then you tell vortex to load the newer esp (1.4) AFTER the older one.

 

This is exactly how it should work, it's not a fault of the mod or mod author.

 

Yes, I understood that and I know that too. But how does Vortex identify or know that it is an update if the mod name is different?

During the first installation Vortex apparently didn't recognize this, otherwise I would have received a conflict message immediately.

Only after the re-installation of the V1.4 ESP update Vortex recognized that a conflict (update) exists.

 

In any case, it seems to work properly now, even though I still don't quite understand why Vortext has now brought the conflict message... :teehee: :ermm:

[AugustaCalidia]

@grw

 

 

But how does Vortex identify or know that it is an update if the mod name is different?

 

The Nexus Mod ID's are the same, and the .esp names are identical.

[grw]

@grw

 

 

But how does Vortex identify or know that it is an update if the mod name is different?

 

The Nexus Mod ID's are the same, and the .esp names are identical.

Okay, I guess that was my mistake. I thought it was identified by its name.

Thanks for the info!