Plugins List Doesn't Jive?

[michaelrz167]

Alright... so I moved my FO4 install to a different drive. Went through the whole process of moving my setup from one drive to another. I went through the standard procedure of purging mods, moving the install, pointing everything in vortex over to the new locations, moving the staging folder... redeploy. Play. Everything works.

 

Well... it seemed like everything worked. I've been playing the game and making changes to my setup and everything. But now I have a mess on my hands. Don't wanna be that guy, but it seems like everything I touch in Vortex breaks and frankly it is getting me down. It's the best modding software ever until something simple and dumb screws up and adds this whole new layer of complexity to modding these already rocky games... one that wasn't there in times before Vortex. That sucks! Looks like my problem is tied to everyone's favorite feature, loot force-feeding :tongue:

 

I'm seeing something pretty weird and annoying. My plugins list is all screwed up. It's like it hasn't updated since the move. So I've got plugins listed there for mods that aren't even installed anymore. And somehow they're enabled! Other times, I see esp's for mods that are 'installed' in vortex but disabled active. Figure that one out.

 

Is there a way to just wipe the plugins list and get vortex to build it again based off of the mods I actually have installed? I can't figure out where it keeps the loot data and everything.

 

I'm trying to troubleshoot a different mod (though THIS may actually be why things aren't stable.) But even in FO4edit, it's got the wrong plugins listed, I supposed because it's going by the list vortex deploys. Really annoying when I'm trying to work out conflicts and it is factoring-in plugins that shouldn't even be there! I didn't know I was running multiple lighting overhauls... I only have one activated. You can see how that might be problematic.

 

EDIT: UGH... it's worse. Something is going on with the deployment data... when I purge, the vast majority of my mods stay in the game folder. All of the plugins, textures, everything... those plugins for uninstalled mods still showing up on the list... they're always in the game folder!

 

So what can I do? I was thinking with the mods deployed, I'll first delete the mods that aren't supposed to be there at all. From there, purge. Wipe the install folder and redeploy. I'm thinking maybe I only thought my game folder was purged when I moved it. So now all of the stuff from before I moved it is being left behind. Does that make sense?

[HadToRegister]

How did you move the staging folder?

Using Windows, or within Vortex like this?

[michaelrz167]

How did you move the staging folder?

 

Using Windows, or within Vortex like this?

 

 

From within vortex.

[michaelrz167]

Well... at any rate, it seems I found my answer. For whatever reason I wound up with a 'dirty' game folder during the move. Any mods I had installed/activated before the move weren't getting purged, even though new mods were deploying fine. After purging mods and manually restoring the game folder to a fresh install by deleting the lingering mod files (minus bodyslide data, looksmenu, F4SE, etc...) everything looks right. When I deploy, it drops all of the mods/plugins as listed. When I purge, they all come up.

 

Was definitely causing problems! Some of the mods clogged in the game folder can't be run next to what I installed after. Explains a lot, for sure...

 

I just wonder how. I would've thought it wouldn't let me move anything with mods deployed... or at least would have warned me to purge my mods before moving the staging folder.

 

I would be curious if anyone knew... is there anything that gets installed via FOMOD in vortex that sticks around after purging? I was wary of deleting the bodyslide/CBBE stuff from my 'purged' game folder just in case there's anything there that Vortex doesn't directly manage past installation. I thought because that stuff is accessed with a tool maybe it wouldn't be. Same with def_ui stuff in the "Interface" folder. Left them be, thinking if I ever open bodyslide or the def_ui editor, it's working from what's in the game folder

[HadToRegister]

Well... at any rate, it seems I found my answer. For whatever reason I wound up with a 'dirty' game folder during the move. Any mods I had installed/activated before the move weren't getting purged, even though new mods were deploying fine. After purging mods and restoring the game folder to a fresh install (minus bodyslide data, looksmenu, F4SE, etc...) everything looks right.

 

Was definitely causing problems! Some of the mods clogged in the game folder can't be run next to what I installed after. Explains a lot, for sure...

 

I just wonder how. I would've thought it wouldn't let me move anything with mods deployed... or at least would have warned me to purge my mods before moving the staging folder.

 

 

So how did you move the mod staging folder?

 

With Windows, or Vortex as I asked in the post above?

[michaelrz167]

 

Well... at any rate, it seems I found my answer. For whatever reason I wound up with a 'dirty' game folder during the move. Any mods I had installed/activated before the move weren't getting purged, even though new mods were deploying fine. After purging mods and restoring the game folder to a fresh install (minus bodyslide data, looksmenu, F4SE, etc...) everything looks right.

 

Was definitely causing problems! Some of the mods clogged in the game folder can't be run next to what I installed after. Explains a lot, for sure...

 

I just wonder how. I would've thought it wouldn't let me move anything with mods deployed... or at least would have warned me to purge my mods before moving the staging folder.

 

 

So how did you move the mod staging folder?

 

With Windows, or Vortex as I asked in the post above?

 

I already told you, I used Vortex to move it. :P That's why I was surprised it didn't bug me about doing it if my mods were still deployed. I would have figured it would pick up on that and want me to purge mods first.