vortexposer

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

The content column is usually updated often enough that shouldn't be necessary but can rt click mod, select refresh content and it'll display what it registers in staging folder(s), if you've been mucking around with its contents manually, etc. Use same drop-down menu and open in file manager to visually confirm expected content matches up

Someone likely informed Microsoft that they didn't want their assets to be legally redistributable/patched anywhere other than on bnet, where it can be more easily moderated by owner vs some random 3rd party website (from MS perspective) And legal dept have now taken appropriate steps to ensure those protections

Regarding Vortex/LOOT supported games: if auto-sort is disabled Vortex can't update your local plugins.txt... so that incorrect state should be expected as you're forcing it to rely solely on some other 3rd party app to manage its own plugins.txt - which is absolutely unnecessary and easily avoidable. Although it is apparently not so easy to understand if you've never used LOOT or its various built-in functions that it has to control load order (by overriding the default sort with your own personal preference). You'd be best served by creating your own post and providing a direct example of or at the very least, a few more details on what in the load order isn't being set where (with default auto-sorting on). Once understood, there are built-in functions that can and will let you do almost anything you could ever want vs complicating stuff by using another manager (including standalone LOOT App) which is imho, inherently incompatible with Vortex and dramatically less effective.

Those look like Groups. Go to "Manage Groups" tool in Plugins tab and either undo cycle or rt click (in manage groups) and choose "reset".

Same for Vortex. As long as downgraded/FOLON "output" files are sequestered in Staging, it will override game folders original copy in Steam, with hardlink to copy of modified vanilla file when deployed (replacing physical up-to-date copies in Steam). Then either set up custom game settings per profile and manually edit or create custom Ini Tweaks file to automatically apply required ini edit when FOLON profile is enabled.

Correction: extension sets primary before it even installs obse (via prompt) and doesn't need rebooted per se but won't fully register until UI is forced to refresh. E.g. Mods tab, rt click > refresh will allow dashboard/tools bar to display updated status. Personally, I disable the extension and use local collection drafts to auto-install script extenders for all my BGS games Versus manual set up - which requires using unpack (as-is) install and setting mod type every time it gets re-installed And reminds me... Extension sets incorrect metadata by forcing nexus ID copy to register as github page (breaks collection source)

I can and have reproduced this behaviour (and even reported a few times) since before script extender ext. was added to its bundled extension. Is very easy to confirm; uninstall/delete xobse, reboot to follow auto-install ext. process, reboot again and it'll force xobse to be "set as primary". Then user is forced to take extra steps to have to unset xobse as primary in order to use the Oblivion.exe or oblivionlauncher.exe (custom).

The Vortex Script Extender extension doesn't treat Oblivion any different than their other BGS games and definitely sets as primary launcher (registers after 1st reboot), so users will have to specifically "unset as primary" in order to launch standard launcher - which obse has always stated as its intended "loader" for Steam vs obse_loader.exe

This path would imply that the game is installed to C:\*

Okay, so start filtering for mods that don't crash... as I pointed out the only obvious err your manager shows - to a passive observer.

They were culprits, no doubt but you should confirm game works on an empty profile and then do the standard checks for balance off of that.

The missing master on those 3 plugins (marked with caution), would be likely source.

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

Just be mindful of the state in Staging and confirm if any random links got orphaned, etc.