Nexus-Mods / Vortex

Vortex Development
GNU General Public License v3.0
920 stars 135 forks source link

Visibility into loose file rules #16671

Closed hakasapl closed 3 days ago

hakasapl commented 4 days ago

Is your feature request related to a problem? Please describe. N/A

Describe the solution you'd like I am developing an application for Skyrim which would benefit from knowing about the loose file rules in vortex. I can already get data for which files belong to which mods from the vortex deployment file, but it would be great to have a similar way to know whether one mod is set to load after another mod.

Describe alternatives you've considered For now I have a system where the user can specify their priority in my application, but it ends up being extra work for the user, so it would be great to have visibility into this in Vortex.

Additional context N/A

IDCs commented 4 days ago

Hey @hakasapl, I'm afraid the conflict detection for loose files runs on a per session basis so you won't be able to extract that information. But you can still extract the details of which mod depends on which using the persistent state if that helps.

You'll have to go to your settings page -> workarounds tab -> create state backup button. The branch you're interested in is persistent.mods.skyrim each entry there represents a mod entry, and some entries may have dependency information/rules defined in relation to a different mod (and its files by extension).

hakasapl commented 4 days ago

@IDCs thanks for your response.

Ideally I wouldn't have to ask the user to export anything specifically for this app. If there is no other way for external apps to know about which mods depends/loads after which I will continue with my workaround.

I was hoping that info could be added to the deployment file or saved elsewhere in some parseable plain text.

IDCs commented 3 days ago

Adding more information to the deployment file at this stage of development might be troublesome and may affect performance.

You could use the state backups that are done hourly and/or on startup. They're located inside %appdata%\vortex\temp\state_backups_full\

Alternatively you could always use Vortex's CLI parameters directly (but it has to be closed) ./vortex.exe --get persistent.mods.skyrim

hakasapl commented 3 days ago

Got it, thanks. I will look into both