vortexposer

Timestamp of their files - which makes it circumstantial and quite arbitrary to base a decision off what should win or not.
 

https://github.com/Nexus-Mods/Vortex/releases/tag/v1.11.3
 
collections: Added comparison of patches, installer choices, hashes when installing. (#15396)

Sounds like they've set Fallout4's Staging to be the same folder as Enderal (which has merged their content).
 

Oof. I think I can visualize what kind of situation you're describing... and know that pain all too well but without getting into details - I've never found an efficient way to recover from an orphaned Staging folder (which has lost the install/metadata connectivity) - except to be mindful to not break, again. All I can add is; I've learned to build each profile that's important to me into their own draft collection, so I can always revert Staging folder to an uninstalled state and automate their entire restoration.

Currently, I'm sitting here dropping 5578 archive into a new fallout new vegas set up...
but thankfully, I've got 7 highly curated drafts ready to install stuff, once they're added
 

Correct. Once conflicts are resolved (in mods tab), their "deploy order" makes no difference whatsoever.
There's really no point in keeping the column enabled either (disable/enable columns in upper right cog).

Although generally irrelevant for most users; the only practical use for deployment order that I've ever seen (in BGS games) is when making one Ini Tweak deploy after another Ini Tweak that don't share the same name (not in direct conflict), where both edit the same ini values = deploy after rule enforces the value changes in the override Ini Tweak file.
 

Does the Apply button get grayed out after confirming new downloads folder path?

On Profile tab there's an independent button (lower, middle) to Add "<game>" profile which starts user off with no existing mods enabled but you could clone, hold ctrl+A to select all and disable as well.

To maybe help clarify further; all profiles share its staging folder, so if collection uses any of your existing mods it'll simply enable them for that new profile. However, if collection sets specific install instruction on an existing install that differs in any way from current install, it will prompt to either replace or make a variant - which will install a 2nd copy of the same mod with their different configuration - preserving your other profiles copy of that specific mod. This is why I personally create local draft collection that can reinstall the entire thing in case anything unforeseen gets broken. Permanently preserving that profile's dependencies.

E.g. I often uninstall everything (for various reasons) and rely on drafts to reproduce a profile's state at a moment's notice
This also includes custom bundle and anything else that profile may need or dump in game folder (filegen, ini tweaks etc)
 

Go to downloads tab, open skyrimse downloads folder and delete Immersive--Adult-145943-80-1694195700.7z - it's corrupt/incomplete.

An .esl master can't be set to load after .esp

Check if that .exe is set up on Dashboard tab as a tool, remove it from tools and reboot Vortex to confirm.

Deleting vortex.deployment.json in game folder would likely force reset.

Delete the FNIS tool path on Vortex Dashboard tab > Tools in above pic. It was set to expect that tool and is missing = error being displayed.
 

There was temporary site outage yesterday, so those are just failed attempts by Vortex to connect. Can x out their notifications.

Do you have a Collection tab?

Can add intended download "manually" from backup or direct link, then drop/paste the .7z or URL to Vortex like any other custom source.
E.g. Grab direct link (rt click, copy link from pages Add button), go to Vortex downloads tab and paste its URL into lower drop-box window.
 

Gamebryo Plugin Management is for BGS games.
It is unlikely that Mechwarrior3 even uses plugins.
 

Remove theme in UI has never worked. I've always had to go to themes install folder to manually delete various throwaways.

Although I'm not familiar with that game specifically, "deploy after" is for all intents and purposes useless regarding conflict resolution or their load order management. The only practical use of "deploy after" I've ever seen (in BGS games) is when making one game config ini file deploy after another copy of the same game config ini file that don't share the same name (not in direct conflict), which both edit the same values = deploy after enforces these value changes in one game ini config file over another.

It's a problem with that specific archive (corruption).

Close Vortex (to release the process) and delete archive, then open Vortex and try redownloading.

 

Anything "combined" gets merged to that targeted output folder, then uninstalled (since their contents are cut from source folder to output folder). You could also target update folder instead for final output (with load after rules in place), which'll pass update checks - rather than fail with only Main file (being technically out of date).

Have you managed a game yet? From picture it doesn't look like it.

Starfield doesn't have a Plugins tab yet.

Your assumption is correct and that is how it is meant to work.

Only a collection should ever override this toggle.

Tools that generate files can be redirected to their own custom output directory (user-made folder) in Vortex staging.