Feature Request (Extract BSA)

[assasing123]

An option to extract BSA files during mod extraction (up to the user) when staging, as sometimes this can cause issues when some overwrites cannot be done, and some users prefer loose files to BSA deployments.

not to mention this would help fixing issues faster as you can pinpoint single file problems faster.

[Zanderat]

I agree. MO2 can already do something like that.

[Pickysaurus]

Anyone who's willing to take a look at this may want to look at my BSA checker as a starting point.

https://www.nexusmods.com/site/mods/126

[Pacocha23]

Thanks for the information, keep sharing this type of info.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

AlaskasWorld

Edited December 25, 2020 by Pacocha23

[rmm200]

And also - submit Feature Requests through Vortex (upper right three dots).

That will it will be tracked. Requests posted here - tend to age off to oblivion...

[Pickysaurus]

Tannin, BigBizkit and I had a little chat about this and we all pretty much agreed that full BSA extraction isn't a particularly good idea, but having a way to show conflicts/overwrites from BSAs would be handy.

 

Effectively allowing BSA extraction as part of the core Vortex app would make it too easy for inexperienced users to break their games by messing with overwrites where they probably shoudn't. That's not to say this can't be added as a 3rd party, optional extensions though if someone in the community feels up to it. If there's a BSA extractor tool that supports command line interactions it shouldn't be too difficult to add.

[rmm200]

If you implement warnings - and something to do about them - without extracting, I fear you will open a can of worms.

Loose files overwriting - no problem. That is the default now.

Loose files not overwriting - that is where it gets dicey. You also have to undo it if the BSA gets disabled.

[Pickysaurus]

If you implement warnings - and something to do about them - without extracting, I fear you will open a can of worms.

Loose files overwriting - no problem. That is the default now.

Loose files not overwriting - that is where it gets dicey. You also have to undo it if the BSA gets disabled.

 

I'm not sure I follow what you're saying? Perhaps you could explain your thoughts with an example?

[rmm200]

And here I thought my comment was the model of clarity...

 

2 Mods (fictitious).

One is Whiterun Reworked. Contains a BSA, ESP, and 50 texture files. Changes the appearance of major structures and Whiterun guards.

Second is Bunnies of Skyrim. Puts bunny heads on all guards. Loose files.

 

If the OP wants Whiterun guards to have bunny heads, it works fine now. The loose files win out.

If the OP wants Whiterun guards to keep their current heads, the loose file texture for guard heads would have to be disabled, so it does not override the BSA.

Other loose files remain enabled. Pretty straightforward.

 

Next week, the OP disables the Whiterun Reworked mod. Vortex must note that the conflicted file no longer exists, and re-enable the appropriate file(s) from Bunnies of Skyrim.

This is where I see the potential for messing up if not anticipated. Any number of loose file mods could be involved in this roll-back.

[AugustaCalidia]

@rmm200

 

Are you sure? I thought that "Bunnies of Skyrim" put bunny heads on the Draugr. :smile: