Vortex scripts issue workaround

This batch file tool temporarily fixes an annoying issue with mods that use the folder name "Scripts" instead of "scripts".

If they do, Vortex does NOT install the scripts from the staging folder into the game. The functionality is missing.

Vortex does NOT show ANY error message, so you can not even notice the problem.

This batch file renames recursively all "Scripts" folders in the mod staging directory to "scripts".

It uses the standard folder location Vortex uses in Windows 10 (I don't know if it runs correctly in 7 out-of-the-box!).

This is the batch file content:

setlocal enabledelayedexpansion

set "modstagingfolder=%programdata%\Vortex\Starfield\mods"

for /d /r "%modstagingfolder%" %%A in (*) do (

if /I "%%~nxA"=="Scripts" (

set "newname=scripts"

ren "%%A" "!newname!"

echo Renaming finished.

IF you use a different mod staging folder, because your OS has not a %programdata% folder or you changed it manually, look it up in "Settings"-"Mods" (copy the folder name and replace it in the batch file after the =).

INSTALLATION

There is no installation needed. Download the file and extract the .bat file to wherever you want.

Since you need it whenever you (re-)installed new mods or updated them, this is essentially necessary every time, when mods are newly deployed.

Therefore, I installed them as a tool in Vortex' Dashboard.

Please look up Vortex' documentation about this. It's easy and takes just a minute to do.

Afterwards you can start it with one click.

Whenever you installed or updated mods:

Start the batch file by double-clicking it. (Or click them from inside Vortex, see above under INSTALL.)

Use Vortex "Deploy" function under "Mods" or "Loadorder".

The script files now have been copied to the correct folder.

MODS AFFECTED BY THE ISSUE:

I noticed it on some SKK mods and informed the author.

GENERALLY it is VERY easily possible that mod authors are NOT aware of this issue.

I am sure there are plenty of mods out there, that have this issue with Vortex. Therefore, I wrote this batch file.

I got aware of it today, and I have been modding Starfield since it was released. It is SO easy to not notice the problem cause.

If you manually install the mod, everything is fine, because Windows explorer functions and batch functions simply merge "Scripts" and "scripts" folders in the same location, using the existing folder (which is "scripts").

HOWEVER: The original folder name IS "scripts" and therefore should be used by mod authors.

A big Thank YOU for being part of the modding community, without discussions about the issue in posts here on Nexus