JJStylez05

Yeah that's the frustrating part. The hard push. You make a conscious decision to avoid the rat race because of the uncertainty that comes with big patches and you get torched regardless. So many people dump on Vortex and I've defended them because I personally think the app is quite streamlined and solid, but this force feed and the lack of response after clearly messing up has been a real turn off.

So for clarity, manually exporting/deploying and rolling back to v.112.0 which can be found on github is what you did? Once you revert Vortex you're saying the extension will automatically revert as well?

"Potentially ruining loads of other players games by not having their extensions update automatically." . I cant even dignify this. Aight bud Im bored now, if your game is set go and enjoy it, this thread for people looking for any word on a fix.

No s#*! sherlock. Still not gonna stop me from giving voice to a fresh issue that could've easily been avoided by instituting choice.

You're aware that's 5 now with the same issue and counting so its not just "my" game. The nature of modding is not hard forcing an update clearly without testing on patch 6 saves then not affording means (as of now) to revert to the last extension that worked. Your patch 7 game with 5 working mods must be fine though so I guess you're good.

The last extension before the 1.51 one vortex wont even let me install to see if my mods would at least work with that one. Its saying "Archive not recognized as a vortex extension".

Having the same issue as mainline. Not everyone is jumping headfirst into the stress that is patch 7. I was just playing the game on my working patch 6 modded save, logged out for a bit only to find vortex hard update (without my input) and leaving me now with a save that cant load mods. Its strange because this is a game where many hours go into a save, so to disregard this fact completely and in effect bork patch 6 modded saves is wild.