How to: selective deployment

[megapatato]

Is there a way of telling Vortex to not deploy a subcomponent of a mod in the staging directory? This functionality would be akin to the .gitignore file.

 

Concretely, I would like to not deploy anything in the .vscode directory for a mod I'm developing.

 

[Pickysaurus]

Not per-mod. But this can be defined at the game extension level.

[megapatato]

Hi Pickysaurus, thanks for the response.

 

Just to make sure I'm on the right path, this would mean tinkering with the index.js file, correct? I'm seeing the DaggerfallUnity index.js file has a process to filter out files by extension (line 43), so I'll try that approach (unless you'd suggest something else?)

 

Cheers,

~MP

[Pickysaurus]

It's actually part of the game object. Here's a basic example:

 

https://github.com/Nexus-Mods/vortex-games/blob/master/game-fallout4/index.js#L11

 

https://github.com/Nexus-Mods/vortex-games/blob/master/game-fallout4/index.js#L108

 

Except, instead of ignore conflicts, you'd want ignore deploy like this one: https://github.com/Nexus-Mods/game-valheim/blob/main/index.ts#L308

[Tannin42]

Don't necessarily use the valheim extension as an example.

You don't have to "toLowerCase()" the filenames, the ignore lists are case sensitive.

 

Further, what that extension doesn't show is that you can use glob patterns to maybe have to list fewer items, e.g. you could use something like

ignoreDeploy: [path.join('**', 'readme*')]

to ignore all files starting with readme, no matter in which subdirectory, so it would ignore

• readme.txt
• foobar\readme.md
• multiple\nested\directories\readme

and so on