vortexposer

Possibly suppressed. Check Settings tab\interface. Can confirm if did by checking whether or not .bsa are backdated to whatever stupid date it designates.

All that would do is open all their mods page en masse.

Wouldn't matter even if it were the old tabletop version Battletech.

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

Those don't look like plugin or group rules added by GTS collection, which means they were added manually or by another collection and need removed. Quickest way to ensure you're getting what a collection gives and only what that collection gives, is reset to default and then rerun collection to enforce just its own set of rules/groups. To reset to their default state; go to plugins tab "Manage Groups" tool, rt click and choose "reset". Then go to plugins tab "Manage Rules" and individually delete plugin specific rule, rerun collection (to check dependencies), and it should reapply its own set of rules required for what it adds (without needing to uninstall/reinstall entire collection).

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

You'll probably need to tag a moderator to remove that unnecessary attachment distributing your mod.

I can confirm that it is related specifically to the __double_underscore at the start of the archive name. After fixing that on your local downloaded archive outside of Vortex, you'll want to manually delete the dropped mod in Staging folder bc it doesn't actually get removed. Maybe Vortex doesn't jive with double underscore bc that's what __vortex_staging_folder uses or something.

Update to your exact issue recently got fixed!

I think what they're saying is that by default, Vortex should display min. 226 supported games, not 84. I could see that being bc Vortex itself is out of date or some key registry is being quarantined by AV, etc. Can you confirm in Extension tab whether or not any "bundled" extensions are disabled or in a failed state? If nothing than is likely some anti-virus app chewing on critical Vortex files.

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.

Three of those four mods listed don't have plugins, so they will never show up in the in-game mods menu (which is exclusive to only plugins), except for Settlement Supplies Expanded - which should show SSEX.esp in Vortex Plugins tab and could be disabled (preventing it from being loaded). The other 3 are dependent on f4se being installed correctly and requires launching the game with f4se and is likely the issue.

Yeah, I don't really use rule overrides often as it gets quite messy to manage but that issue sounds more like it was an unforeseen outcome to the mod type conflict fix - which most users wouldn't have been aware of as its failure wasn't obvious and happened behind the scenes when deploying (creating false external changes) and made it difficult to maintain mod folder integrity.

Well, that one should work fine assuming that you have ISControl Enbabler and its dependencies installed and deployed.