Instant Crash with any mod *Fixed*

yeah happened to me last night after installing remastered in vortex and installing some mods, i suspected it was the loadorder config because of the way the handler worked in Vortex, found the plugins.txt and i had no point of reference so i copied it, then went to verify (Xbox App informs you it'll wipe out your saves and configs, which i didn't want, so i had to find the local cache location of the saves which are obfuscated, but once i had the directory i just zipped the whole thing, ran verify, checked the plugins.txt and lo, the Oblivion Remastered config for Vortex had munched my load order. sigh... In the last 12 months I鈥檝e had zero success with Vortex being coherent with new games, its always a cascade of red alerts every time and big unhandled exceptions on just basic behaviour like _installing the thing_ behaviour - which sounds like its not even been tested.聽 Does Nexus audit the configurations before sending them live? you'd hope that's where the money goes right? stability was kinda the goal we all signed on for.聽 Be great if you could make sure nexus creates a staging config before breaking everything and on try-catch of the inevitable exception it rolls back its changes.聽 Any change in fact, touching load order is pretty awful without a way to revert. What happened to the new NMM (or whatever you guys were gonna call it), the last you guys spoke on it a year or 2 ago Vortex was being thrown away in favour of some new NMM, i think Vortex was a node app or something and the devs didn't like that and preferred something else. is that still happening? Am i just a big silly idiot for continuing to use Vortex? Or are y'all just on some fabulous new Vortex/NMM with the very best exception handlers and whistle bells n bell whistles? (XboxApp didn't kill the saves btw, perhaps because i had previously asked it not to use cloudsaves and it actually listened, a miracle)