Guide: Multiple Parallel Installations of Vintage Story

[Streetwind]

I've written about this multiple times before, in reply to people asking, but I think it's time to give this its own dedicated thread with a cleaned-up how-to guide.

 

The default installation of Vintage Story is fine for most people. It is also convenient in the way that it keeps all of its user data in the user profile, so that a computer that is used by multiple people (in a family for example) will allow every player to have their own savegames, mods, and configs without interfering with anyone else's.

However, sometimes an enthusiast might want to have more than one version of the game in parallel. Perhaps they want to keep an old world around but still play newer versions too. Perhaps they want to test the latest prerelease without risking their saved worlds. Perhaps they want to have a singleplayer instance and a multiplayer instance with different modsets, without having to toggle them all manually everytime they launch the client.

And when this enthusiast then installs two versions of the game into separate folders, they will discover that it doesn't work right. The two game instances can be launched separatedly, but they aren't properly separated. The same savegames and the same mods show up for both.

The reason for this is - you may have guessed it - that the user data is kept in the user profile, as mentioned before. This includes config files, logfiles, saved games, map data, installed mods, and more. Even when there are multiple parallel installations of the game on the disk, launching each one still accesses the same default location for the user data, and therefore loads the same user data.

In order to fully separate two or more parallel instances of the game, each one must be told to use its own unique user data folder. Where these are to be located is fully up to you; they can be placed into the game's install directory if you are the only one who uses this computer, or kept inside the user profile if not, or anywhere else really. The name doesn't matter either. You could even place the data folder on an external storage medium, so long as you ensure that it is mounted when you launch the game.

I'm going to describe this process for Windows users, as that covers 95% of the game's userbase, and Linux users tend to be more tech-savvy anyway and won't need as much help. (And also because I don't have Linux.)

 

Step-by-step guide, to be done separately for each installed version of the game:

• Create the directory where you want your data folder to be located in the future, and copy its full, absolute path. Paste the path into a text file or something similar for later reference. You don't need to recreate the folder structure inside the data folder, the game will do that on its own.
• Go to your VS install directory and create a shortcut to vintagestory.exe. The easiest way to do this in Windows is to select the file, so that it is marked blue. Then, using the right mouse button, click and drag the file to an empty space inside the folder (or some other folder, or even the desktop, wherever you want it). Upon releasing the mouse button, a context menu pops up. Select "create shortcut".
• Rightclick the shortcut, and select "Properties". A small window pops up, with a few editable fields. The topmost one is called "Target". Inside this field, do not delete anything that's already there. Instead, go to the very end, press spacebar once, and then write --dataPath your:\path\here. That's a double dash at the front. You input the absolute path to your desired future data folder that you set aside during the first step.
• If the absolute path to your custom data folder contains spaces, then that path must be encased in double quotes, so that Windows understands it. Do not encase the argument switch (the --dataPath part), just the path itself.
• Some people have reported issues with loading mods from this custom data folder, while for others (like me) it is working without problems. I have no real explanation for why this happens. But in case you suffer from this, or you just want to preempt the possibility of it happening, you can append an additional switch: --addModPath your:\path\here\mods. Again, if that path contains spaces, the path (but not the argument switch) needs to be enclosed in double quotes.
• Press OK to close the properties window. Doubleclick the shortcut in order to launch the game. Pay attention to your desired future data folder; the game should auto-populate it with certain required files and subfolders. If this did not work, you made a mistake with the shortcut somewhere.
• If this worked correctly, you can now close the game again and move your savegames and other user data over from the default data folder (%appdata%\vintagestorydata) to the new one.

 

Examples:

Putting the data folder into the install directory, the path to which includes spaces:
"d:\games\vintage story\1.17\vintagestory.exe" --dataPath "d:\games\vintage story\1.17\data" --addModPath "d:\games\vintage story\1.17\data\mods"
Note how each of the three paths (but not the two argument switches) are encased in double quotes, because all three contain a space.

Keeping the data folder in the user profile, without spaces in the path:
d:\games\vintagestory\1.17\vintagestory.exe --dataPath %appdata%\vintagestory_1_17
Note how there are no double quotes here. It won't break if you add them anyway, but they're not required, as there are no spaces in any of the paths.
This example omits the --addModPath switch, but it could be added just the same as in the first example.

 

A note regarding the new auto-updater!

Since version 1.18, Vintage Story now has a comfortable way to install game updates. You simply click a button inside the client and it downloads and installs everything for you.

Unfortunately, that function doesn't support multiple parallel installations. It relies on an entry in the Windows Registry to know where VS is installed, and that entry is rewritten everytime you run the installer. That means the auto-updater only works for the installation that you installed last. Even if you launch a client you installed previously, and start the auto-update process from within it, it will not update the client you started it from, but rather the client you installed most recently. Always. There is no workaround for this, other than not using the auto-updater. If you want to maintain multiple installations and keep them all updated, you'll have to do manual updates like in the past.

Edited May 12, 2024 by Streetwind

[breeze108]

So, that works if there are 2 different versions? like if I wanted 1.19.9? I would put d:\games\vintagestory\1.19\vintagestory.exe --dataPath %appdata%\vintagestory_1_19  ?  And when it asks if we want to uninstall the old version (1.18.15) we say "No" and then put the path into the download window that asks where we want the file downloaded?

[Streetwind]

..."download window"? It shouldn't matter where you download something. Are you sure you don't mean "installation window"?

In that case, yes, you need to install each game version into a separate folder. They need to exist independently of each other.

[Thorfinn]

I'd add that the easiest way to accomplish multiple versions is to use the "Update" version of VS. 

Go to wherever you install parallel copies of VS, if, say "D:\VS\119.2", go to just D:\VS. Copy/paste the 119.2 directory. You now have something in that directory like "119.2 - Copy".

Download the update to wherever. Run the update. Select the directory you just created, in this case, "119.2 - Copy". Do not uninstall the old version.

Once done, rename "119.2 - Copy" to "119.9" or whatever. Go into that directory and create a shortcut, then edit the switches per the above description.

[321BoltsOfLightning]

Note for people who run servers, the same flags worked great for me on the server exe, using both --dataPath and --addModPath. But you'll want to make a backup of all your old data stuff just in case, and double check that the server's mods are loaded once you run the server. Also, if you copy over your serverconfig.json you'll want to make sure the save file location still makes sense, because if not the server won't load (I spent some time trying to figure that out why mine wasn't loading haha).

Thanks for writing this up!

[Thorfinn]

Since this came up in another thread, and none of us could remember exactly how to do the second part of this...

 

1. Install new version. Do not remove the old version. Add a desktop shortcut. Do not start game.

2. Rename shortcut to something appropriate, so it does not get overwritten next update. I use VS [version], so VS120 p7 for version 1.20 pre-7.

3. Right-click on the shortcut, select Properties.

4. Make sure the Start in: is where you installed.

5. Put your cursor on the end of the Target: box.

6. Add  --dataPath .\[save location] --addModPath [mods location] There must be a space before the --dataPath, and note that is a double dash. This nests your saves in your install directory, so relocating to another computer is easy. In my case, my first playthroughs are all vanilla, so I want them in the directory v for vanilla. My Target: reads, 

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\v --addModPath \\THORFINN-PC\Inbox\vs120

Substitute whatever is appropriate for your setup.

7. Play.

 

When you want to use a different modlist, and don't want to have to go through the mod manager and try to remember which modlists go to which worlds,

1. Copy-paste the Shortcut on the desktop.

2. Rename it. Maybe VS120-p7 PS for Primitive Survival. Or VS120-p7 V+ for a very lightly modded game.

3. Edit the Target: to change the --dataPath, in this case, maybe something like 

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\PS --addModPath \\THORFINN-PC\Inbox\vs120

or

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\vplus --addModPath \\THORFINN-PC\Inbox\vs120

4. Play.

 

Now if only @Tyron would add an --addMacroPath switch so you don't have to copy your macro files manually...  

[StCatharines]

On 10/26/2024 at 2:30 PM, Thorfinn said:

Since this came up in another thread, and none of us could remember exactly how to do the second part of this...

 

1. Install new version. Do not remove the old version. Add a desktop shortcut. Do not start game.

2. Rename shortcut to something appropriate, so it does not get overwritten next update. I use VS [version], so VS120 p7 for version 1.20 pre-7.

3. Right-click on the shortcut, select Properties.

4. Make sure the Start in: is where you installed.

5. Put your cursor on the end of the Target: box.

6. Add  --dataPath .\[save location] --addModPath [mods location] There must be a space before the --dataPath, and note that is a double dash. This nests your saves in your install directory, so relocating to another computer is easy. In my case, my first playthroughs are all vanilla, so I want them in the directory v for vanilla. My Target: reads, 

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\v --addModPath \\THORFINN-PC\Inbox\vs120

Substitute whatever is appropriate for your setup.

7. Play.

 

When you want to use a different modlist, and don't want to have to go through the mod manager and try to remember which modlists go to which worlds,

1. Copy-paste the Shortcut on the desktop.

2. Rename it. Maybe VS120-p7 PS for Primitive Survival. Or VS120-p7 V+ for a very lightly modded game.

3. Edit the Target: to change the --dataPath, in this case, maybe something like 

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\PS --addModPath \\THORFINN-PC\Inbox\vs120

or

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\vplus --addModPath \\THORFINN-PC\Inbox\vs120

4. Play.

 

Now if only @Tyron would add an --addMacroPath switch so you don't have to copy your macro files manually...  

Excellent guide, it helped me ensure I wouldn't break anything when installing a 1.20-pre.9 copy.

[Dilan Rona]

I keep mine in the VS directory, under a profiles sub directory. And I would recommend keeping the datapath, and modpath inside the same profiles directory. As per the example below. My system being Fedora. Just adjust the path as needed.

./Vintagestory --dataPath "./Profiles/1_20/Data/" --addModPath "./Profiles/1_20/Data/Mods/"
 

[Thorfinn]

That is a good way to do it. The only downside is when a mod is updated, you will need to update it in all Profiles. It might not be obvious, but the way I did it, I only have to keep mods updated on one machine on the LAN. It's marginally slower loading the mods, but there's no more hassle with trying to make sure everyone is running the correct versions.

[Thorfinn]

Incidentally, if you keep multiple installs, DO NOT INSTALL THE UPDATE FROM THE IN-GAME PROMPT.

Maybe it chooses the right directory, maybe it doesn't. Not worth it. Download it and install it as usual, even/especially if you just want to update an existing instance.

[JAGIELSKI]

I wish this sort of guide wasn't needed and it was a simple option switch to keep all the data (mods, saves, etc.) in the "main" directory (i.e. the one where VS was installed/unpacked to). I mean, the other block game figured a way to do it a long time ago (at least for Java version) so why not VS?

[Thorfinn]

You can absolutely do that, @JAGIELSKI. Easy peasy.

It's just not a great answer, as you have to keep your mods updated in every instance. If you want a copy to run on a server still on 1.18, you have to make sure none of the updated mods get in there. This is just a way of maintaining separate instances without having to know all that much about your directory structure. Click on Mod Manager, make sure everything is copacetic, and you are off to the races.

[CatNine]

Can anyone here please clarify how to properly update one of the versions if not through the in-game updater? I've read the thread and I am still very confused. 

If Thorfinn's explanation is for that (which I am not sure if it is) then I am stuck on the first step. "Install new version. Do not remove the old version."

Where does the new version get installed? And how do you avoid removing the old version?

I have successfully followed the steps to get a 1.20.3 folder up and running. But I'm stuck on how to do the same thing for a 1.20.4, if not using the auto updater.

Do you use the installer downloaded off the website? But then, where are you to install that? In the 1.20.4 folder that I made (that is currently unpopulated)?

Edit: Tried my best to figure it out but ended up scrapping everything and starting again, still super confused about how to have 2 different versions.

Edit: Have scrapped and retried multiple times closely scouring every post on this thread, following every step to the letter and still I can't seem to update any version (not even the original install) manually. When installing the manual update from the website, I selected the copied over directory I made from the working 1.20.3 directory I had made (not the original), so that should be the right one shouldn't it? Then once installed, I renamed the directory to something I'd recognise I made a shortcut of the launch exe from that and edited it's target to match the new directory location. Yet, when I launch that shortcut it's still version 1.20.3, not 1.20.4. And neither the separate 1.20.3 install nor the original install got updated either, so I don't know what did. And yes, I've double, triple, quadruple, lost count checked the target IS right.

Edit: Turns out, the update did take effect I just can't get the shortcut to properly target it, even though the Start in: leads to the vintagestory folder inside the newly copied directory (where the update went), and target: correctly points to the copied directory.

If I'm slow to reply apologies I may be napping, got a headache.

Got this figured out, was missing the \data\ part of the path.

Edited February 17, 2025 by CatNine

[JAGIELSKI]

16 hours ago, Thorfinn said:

You can absolutely do that, @JAGIELSKI. Easy peasy.

It's just not a great answer, as you have to keep your mods updated in every instance. If you want a copy to run on a server still on 1.18, you have to make sure none of the updated mods get in there. This is just a way of maintaining separate instances without having to know all that much about your directory structure. Click on Mod Manager, make sure everything is copacetic, and you are off to the races.

No, I meant each installation would have separate "mods" and "saves" folders next to the EXE instead of keeping them in user profile. Would also make the game fully portable and possible to put on a pen drive.

[Thorfinn]

You absolutely can do that. The base directory has a Mods directory that has only the core three, but you can (or at least could) put all your mods in there. Saves is a little more difficult since they have tried to abide by Microsoft's standard for protected status based on directory structure, i.e., you can do almost anything with stuff in your own user directory, but very little in Program Files. So for saves, yes, you have to use the command line switch. 

[EDIT]

You aren't considering running the game from the stick, are you? Database access at the speed of USB...

Edited February 17, 2025 by Thorfinn

[Voldemort]

On 10/26/2024 at 10:30 PM, Thorfinn said:

Since this came up in another thread, and none of us could remember exactly how to do the second part of this...

 

1. Install new version. Do not remove the old version. Add a desktop shortcut. Do not start game.

2. Rename shortcut to something appropriate, so it does not get overwritten next update. I use VS [version], so VS120 p7 for version 1.20 pre-7.

3. Right-click on the shortcut, select Properties.

4. Make sure the Start in: is where you installed.

5. Put your cursor on the end of the Target: box.

6. Add  --dataPath .\[save location] --addModPath [mods location] There must be a space before the --dataPath, and note that is a double dash. This nests your saves in your install directory, so relocating to another computer is easy. In my case, my first playthroughs are all vanilla, so I want them in the directory v for vanilla. My Target: reads, 

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\v --addModPath \\THORFINN-PC\Inbox\vs120

Substitute whatever is appropriate for your setup.

7. Play.

 

When you want to use a different modlist, and don't want to have to go through the mod manager and try to remember which modlists go to which worlds,

1. Copy-paste the Shortcut on the desktop.

2. Rename it. Maybe VS120-p7 PS for Primitive Survival. Or VS120-p7 V+ for a very lightly modded game.

3. Edit the Target: to change the --dataPath, in this case, maybe something like 

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\PS --addModPath \\THORFINN-PC\Inbox\vs120

or

C:\Games\vs120-p7\Vintagestory.exe --dataPath .\vplus --addModPath \\THORFINN-PC\Inbox\vs120

4. Play.

 

Now if only @Tyron would add an --addMacroPath switch so you don't have to copy your macro files manually...  

Is possible launch 2 different account on same PC and connect them on one server?

[xXx_Ape_xXx]

35 minutes ago, Adnyeus said:

Is possible launch 2 different account on same PC and connect them on one server?

I guess, if you run one of the instances in a VM, then I believe you should be able to run two accounts. The question tho, why would you want to do that?

[Voldemort]

29 minutes ago, xXx_Ape_xXx said:

I guess, if you run one of the instances in a VM, then I believe you should be able to run two accounts. The question tho, why would you want to do that?

I want create youtube videos. i dont have actor so i will use myself  and record with main 

[idiomcritter]

4 hours ago, Adnyeus said:

Is possible launch 2 different account on same PC and connect them on one server?

running under windows, its possible to to run 2 VS clients (2 different accounts) under 2 different windows login accounts.  windows can swap between the 2 accounts without closing/signing off either. 

not aware of how both accounts could be displayed at the same time though.  so while viewing/playing the 1st account, things could be occurring on the live 2nd account that could need quick attention

[Thorfinn]

So maybe it's a solution to the stuff that dribbles out of your machinery when the chunk gets unloaded? Might be worth it. 

[Voldemort]

I wish there is some camera mod like in minecraft when you building for exmaple house and you have one spot that recording different corners and move around

[Chiaro]

Don't know if this video is step-by-step the same as your guide here, but without having seen it completely it looks kinda similar.
 

 

[Thorfinn]

Welcome to the forums, @Chiaro

Yep, same thing. Useful for those who tend to be more of a video than text person.

One thing I'd note, though, is you should consider the --addModPath switch. Though the Mod Manager leaves something to be desired in terms of listing what game version each rev of each mod is good for,  trying to keep your mods updated in all instances of VS is non-trivial, and bound to cause problems somewhere down the line, particularly as you start migrating saves. It's probably no big deal if you only play SP, but add a few servers to the mix and you will be pulling your hair out looking for why it's doing what it is.

[AnniPicto]

Just recently I deleted the new version and installed the old version of the game just to enter the old world. And then I deleted the old version and installed the current one again.
Next time I will use your method!

[flackstacks]

I'm about to attempt to follow this guide but on a Mac Mini M4 and while being a life long Windows user now- brand new to Mac. Wish me luck! (hopefully this might help a mac user down the line if it comes to that.)