Move modded (Vortex) game to another drive help

[Erke]

Hi,
I'd like to move my modded Fallout 4 game to my new m.2 drive. Been searching the net for suggestions none of them suits me so I thought I'd ask here.

Originally I was planning to copy the whole Steam folder to my new drive and then renaming the "drive letter" to the original one but my steamapps folder is way bigger than I expected.

I can add a new library folder with in steam, then copy the whole F4 to new destination, then tell steam to MOVE the game to that destination and let it "discover" files. But I suspect that would brake my Vortex pathing or may even overwrite some modded replacement files with different sizes.

I don't want to use symbolic links for the rest. I prefer not to use mklinks for this occasion.

Does anyone had a similar experience on this subject?
What are your suggestions?
Let us please brainstorm together...

NOTE: My Vortex's download and staging folders are indipendent from the game folder. But game data folder will be changed, how can I prepare Vortex for this, without disabling all mods and breaking all my conditions?

[Zes]

pain in the .ss thing to do.

i would...

+ disable all mods first
+ go to steam and create a new library path
+ move game to that new steam library 'inside steam' (steam will move it itself)
+ go back to vortex and redefine game's new path
+ enable all mods back on.

..if i were you

[Erke]

Originally posted by Zes:

pain in the .ss thing to do.

i would...

+ disable all mods first
+ go to steam and create a new library path
+ move game to that new steam library 'inside steam' (steam will move it itself)
+ go back to vortex and redefine game's new path
+ enable all mods back on.

..if i were you

Thank you for your response.
It really is a Pita thing to do. I'll avoid the disabling mods part for now, may be someone comes up with a better solution.
Disabling them means I will lose all my conditions (load after that, this requires that, etc) doesn't it? Or was it uninstalling them that clears the conditions?

[Erke]

SIDE QUESTION:

Let's say, I changed my drive letters (A is old drive B is new drive). My new drive to A and my old one to B. And only moved Fallout to the new drive.... Would I then be able to "move" other games to the new drive and let steam discover it, or would steam be unable to locate files to move?

IE. Games are currently on drive A... Lets say I changed that drive's letter to B then told steam to move a game (other games) from A to B... which is phisically already on B, would it work?

[kdodds]

Originally posted by Zes:

pain in the .ss thing to do.

i would...

+ disable all mods first
+ go to steam and create a new library path
+ move game to that new steam library 'inside steam' (steam will move it itself)
+ go back to vortex and redefine game's new path
+ enable all mods back on.

..if i were you

This is your answer. Half @$$ it and you're likely to pay for it in the long run. I did this many moons ago with Steam in its entirety, moving it out from under the default \Program Files (x86) to its own folder under root. With MO2 it's a little easier, but same principles apply. I would not start renaming drives. I would take this opportunity to move Steam if you have not done so already.

[Erke]

Originally posted by kdodds:

Originally posted by Zes:

pain in the .ss thing to do.

i would...

+ disable all mods first
+ go to steam and create a new library path
+ move game to that new steam library 'inside steam' (steam will move it itself)
+ go back to vortex and redefine game's new path
+ enable all mods back on.

..if i were you

This is your answer. Half @$$ it and you're likely to pay for it in the long run. I did this many moons ago with Steam in its entirety, moving it out from under the default \Program Files (x86) to its own folder under root. With MO2 it's a little easier, but same principles apply. I would not start renaming drives. I would take this opportunity to move Steam if you have not done so already.

The thing is, I'll be using both drives as steam library as I mentioned. Honestly, right now, renaming drive letters and either uninstalling all the other games or trying to move them, seems way easier.

I was hoping someone would come up and show how it's done in vortex...

Does anyone know what would happen if I change the game path in Vortex, without disabling the mods first?


The mods will be phisically there, in the new drive. I assume Vortex would be able to delete files, should I ever need to disable any mod...

BTW Official Nexus forums suggest to "Purge" all mods, not disabling them.

[=EGC= kansasterry]

This link will explain an easy way to move the game.

https://help.steampowered.com/en/faqs/view/4BD4-4528-6B2E-8327#exist

The updated vortex should have a way to export its rules and load order that will assist in moving vortex mod files if needed. A simple way may be to use the purge option in vortex mods then deploy option after moving the game.

[tulle040657]

Do what Zes says. Your drive letter rename plan will not work. You will break Vortex

[kdodds]

Don't you just love people who post asking for advice, having already made up their minds to do things exactly the way everyone is telling them NOT to do it, and then try to get you to agree with them? Dude, whatever, do what you want.

[Erke]

Originally posted by kdodds:

Don't you just love people who post asking for advice, having already made up their minds to do things exactly the way everyone is telling them NOT to do it, and then try to get you to agree with them? Dude, whatever, do what you want.

This is not the case... Even it was, there's nothing wrong with looking for "confirmation"....

I didn't change my drive letters.
I ended up "Purging" the mods, despite the suggestions for "disabling" them.

All is fine and the game is working without a problem from the new drive. Vortex is preserved as it is as well...

So all is good.

[kdodds]

LOL. Yeah, go you, "fixed it" "all on your own".

[Erke]

Originally posted by kdodds:

LOL. Yeah, go you, "fixed it" "all on your own".

Wtf is wrong with you?

[kdodds]

Originally posted by kdodds:

LOL. Yeah, go you, "fixed it" "all on your own".

Absolutely nothing, I'm congratulating you for being so great at fixing your own problems that you didn't even really need the input offered here. Go you. Good job.

[Bustoms]

Originally posted by kdodds:

Originally posted by kdodds:

LOL. Yeah, go you, "fixed it" "all on your own".

Absolutely nothing, I'm congratulating you for being so great at fixing your own problems that you didn't even really need the input offered here. Go you. Good job.

i think you should chill, buddy.

[McNaughty]

Originally posted by kdodds:

Originally posted by kdodds:

LOL. Yeah, go you, "fixed it" "all on your own".

Absolutely nothing, I'm congratulating you for being so great at fixing your own problems that you didn't even really need the input offered here. Go you. Good job.

Who the hell hurt you?

[An Heroic Hippo]

Originally posted by Zes:

pain in the .ss thing to do.

i would...

+ disable all mods first
+ go to steam and create a new library path
+ move game to that new steam library 'inside steam' (steam will move it itself)
+ go back to vortex and redefine game's new path
+ enable all mods back on.

..if i were you

This just worked beautifully for me, although with a couple extra steps. Here's what I did.

-Disable all mods
-Move Fallout 4 from drive to drive under game properties in Steam
-In Vortex, Fallout 4's directory should have changed automatically.
-In Vortex, you'll need to change the mod staging folder to match the drive that FO4 is now on. Otherwise, the mods won't deploy. It will prompt you.
-Re-enable all mods
-Re-link F4SE desktop shortcut to the new drive

After this, everything worked for me just as it did before.