vortexposer

Okay, I see it now... If I take 3 non-conflicting folders (sorted by deploy order), they deploy 0/1/2 alphanumerically and then if I introduce an artificial file conflict for 2 to "load after" 0 - it'll readjust "deploy order", overriding defaults sort assignment. Guess I never bothered to pay attention to that detail (or sort by deploy order priority), which led me to ignore the correlation to conflict resolution rather than simply being arbitrarily linked to the defaults state alphanumeric sort. Also interesting that install status plays a part in where the UI display shifts it too. Thank goodness for collapsible custom category because I'd go insane trying to sort by anything else. *Actually, I can't figure out what sorts by default to determine initial deploy order. No wonder I ignored

Yeah, is plausible that my cognitive dissonance resolution had a cyclic error moment in regard to conflict and deployment because I generally don't consider conflicts as part of the equation when I deploy, since Unless you're a mod type conflict

I guess I must not understand the context of what the term "deployment order" is meant to represent in Vortex for an end user - besides what order its deploying files to game folder in, which is irrelevant to its LO. The main issue I've seen is users thinking that deploy order is somehow indicative to MO "priority index".

DynDOLOD?

Unpack outside of fomm to confirm archive isn't broken and then maybe just manually import extracted content to a custom fomm folder.

Really? How does deploy order matter when at the end of the process, what is there is there and what loses isn't? Like, I get the loose file vs bsa reasoning but in terms of where one or the other is in deploy order, how would its specific indices matter? This might make me rethink the significance of using deploy after rules, which until now I thought only applied to Ini Tweaks (BGS). Also, hi Tannin! Hope you're doing well

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.

I forgot to come back to this thread and report but eventually mine got fixed by rerunning the listed .NET 6.1+ link in required files off Vortex page. Can only speculate as to what broke it (unofficial copy of MO2) but .NET registered as needing repaired and issue went away for good.

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

My guess is that it's an unavailable/archived (out-of-date) version of Mojave Wildlife - TTW Patch off of Trooper's Patch Page mod. If you're looking for it bc of Wasteland Supplemental Guide loadorder.txt, use newer version. It's only listed as an index placeholder.

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)

Switching a profile already purges all relative hardlinks. E.g. When creating a new profile with no mods enabled nothing is actively deployed and everything is already purged (check game folder for unmanaged leftovers and either import to custom mod or delete files). My only real concern would be wanting to make sure to choose to make a variant if/when collection installs certain mods differently than your existing set up has them (vs replace). Personally, I'd make a draft collection of each profile with its specific settings to maintain their integrity indefinitely.

For now I've found the part that I can edit locally So at least I can reset and repopulate from there "persistent": { "categories": { "game name": { Cheers

Regarding how to redirect output, go to extensions tab > find more and grab "Add custom mod button" and create new folder in Staging. Then in BS, go to advanced settings and target custom mod in its Output Path.

Thanks for the quick fix! Is there anywhere else other than Settings > Workaround > Backup that stores custom categories metadata? It's such a slog to make 100's of categories and not be able to easily restore, swap or share my own configs.