Linux vortex meta.ini mod rules cycles. how to delete all mod rules

[axpxion]

Vortex 1.13.7
modding Skyrim SE anniversary addition on steam
Mod list is the Gate to sovngarde

 

So I am running linux, a issue I have seen on occasion and have heard is a linux quirk is that vortex tries to pull rules from the Meta.ini files. I followed the recommended suggestion of setting all to load before and if you end up with cycles set one to load last. This did not fix the issue and I am stuck with like.....hundreds of cyclical rules. Fixing this manually one by one seems overwhelming and I am pretty sure I can just delete the meta.ini files to deploy it. My problem is that I can't seem to delete the rules assigned to the meta.ini stuff?
-I have tried deleting all rules by purging all mods. It fails for some reason? might be issues with vortex getting permissions to the file directories but i am not sure as the error pathing seems to be incomprehensible and is pulling from my heroic install of fallout london for some reason? I am not sure I understand what links its trying to purge here
-I have deleted the userlist.yaml file
-I have deleted the masterlist.yaml file
-I have tried to make a new profile and add the mod collection again through there. it still tries to run these rules on the new profile, won't deploy.
-I kinda don't know to to clear these links, I would like to avoid deleting everything and starting over. it took like 10 hours to download this collection, help would be appreciated. just the file that hold all these links so I can delete it would be nice

Picture of purge failing for example and all the cycles so everyone can laugh at my misfortune.

[Pickysaurus]

The error you've screenshotted seems to be a Linux-related issue, namely that you've created circular links in the file system. As Vortex isn't officially supported on Linux, I can't really advise there. 

The dependency graph one (the big blob of lines) is caused by you setting a circular file dependency (most likely by accident). The video below includes tips on how to untangle this. 

 

[vortexposer]

Idk anything about linux or Steamdeck but this path doesn't make much sense


And Vortex is already told to ignore meta.ini file conflicts by default (albeit are still deployed with one winner, probably based off latest timestamp) - which I guess doesn't apply to linux-based use. Setting rules for those would be ridiculous and imho, MO2 users should be ashamed for bundling in the 1st place... IIRC, this was side-stepped in Vortex a couple weeks after initial public release. My workaround would be open game's global Staging folder, filter/search by meta.ini and delete.

Or via collection draft, individually hide each meta.ini in its own shared subfolder/mod name directory, thereby giving them no ability to conflict since they won't be trying to occupy the same path on deployment. I.e. there can be only one.

Edited May 22 by vortexposer