Vortex stripped out necessary top level folder during mod install

[IsharaMeradin]

I had been using Mod Organizer 2 pre-Skyrim AE. I stopped playing the game for a while and recently decided to pick it back up. Since many of the mods I had needed to be updated and I was going to start fresh anyway, I opted to give Vortex another go.

 

It has been going okay for the most part. I got the utilities I needed setup, the game runs fine, no major issues with load order, etc...

 

Today, I ran into a little annoying 'bug'. I needed to make a tweak to a script in one of my mods. That script requires source files from another mod to be present. No problem. I went to my MO2 install and opened up the mod folder that contained the necessary PSC files and zipped it up.

 

The contents of the zip file as presented by 7z:

Source > Scripts > PSC files

 

After dragging and dropping into Vortex and being deployed, I still could not compile as those scripts could not be found. Upon investigation, Vortex stripped out the Source folder.

 

Other mods that were dragged and dropped into Vortex were handled correctly. But they all contained either other file types or had both a Source and Scripts folder at the top level. I corrected it locally by creating the Source folder and moving the Scripts folder into it, redeploying and confirming the change. If possible, can Vortex be set up to recognize which directory structure is being used for the PSC files and not strip out folders unnecessarily? Or even better, set to not strip out any folder.

 

In case it needs to be said:

32-bit Skyrim script path defaults:

PEX files -- Data > Scripts

PSC files -- Data > Scripts > Source

 

64-bit Skyrim script path defaults:

PEX files -- Data > Scripts

PSC files -- Data > Source > Scripts

[vortexposer]

Select uninstalled archive in vortex, rt click and choose Unpack (as-is) .

[showler]

Wasn't there some weirdness with Bethesda changing the path for the script source files partway through the SSE era (or was it only during the changeover from LE to SE)? I seem to recall coming across older mods that still had their files on the old path and wouldn't actually work if installed on the new path.

[vortexposer]

Standard install always defaults to first valid data directory. In this case; installer skips atypical \Source and forces \Scripts folder to match up with standard Data path. Unpack (as-is) extracts like it would on desktop, preserving folder structure.

Edited May 25, 2023 by vortexposer

[IsharaMeradin]

Select uninstalled archive in vortex, rt click and choose Unpack (as-is) .

Thank you. While I've used the right click menu on mods after being installed, I never thought to see what the options were when a mod was uninstalled. Still, it would be nice if there were a pop up or something that would ask before stripping out folders.