Difference between revisions of "Modding The Witcher 3 with Vortex"

From Nexus Mods Wiki
Jump to: navigation, search
 
(12 intermediate revisions by the same user not shown)
Line 10: Line 10:
 
|nxm= https://www.nexusmods.com/witcher3
 
|nxm= https://www.nexusmods.com/witcher3
 
}} <!--https://staticdelivery.nexusmods.com/Images/games/cover_2763.jpg --> This guide is designed to help you set up Vortex to install and manage mods for The Witcher 3: Wild Hunt. &nbsp;
 
}} <!--https://staticdelivery.nexusmods.com/Images/games/cover_2763.jpg --> This guide is designed to help you set up Vortex to install and manage mods for The Witcher 3: Wild Hunt. &nbsp;
 +
 +
&nbsp;
  
 
&nbsp;
 
&nbsp;
Line 16: Line 18:
  
 
Before we get started, this guide assumes that you have installed The Witcher 3&nbsp;and [https://www.nexusmods.com/about/vortex/ Vortex] at their default locations. You will also need to be [[Logging_in_via_Vortex|logged in to your Nexus Mods account]] in Vortex.&nbsp;Other than that, if you are planning to use more than 3-5 mods, it is recommended to set up the [[Tool_Setup:_Witcher_3_Script_Merger|Witcher 3 Script Merger]].
 
Before we get started, this guide assumes that you have installed The Witcher 3&nbsp;and [https://www.nexusmods.com/about/vortex/ Vortex] at their default locations. You will also need to be [[Logging_in_via_Vortex|logged in to your Nexus Mods account]] in Vortex.&nbsp;Other than that, if you are planning to use more than 3-5 mods, it is recommended to set up the [[Tool_Setup:_Witcher_3_Script_Merger|Witcher 3 Script Merger]].
 
&nbsp;
 
  
 
== Getting Set Up ==
 
== Getting Set Up ==
Line 26: Line 26:
  
 
If you can’t see Witcher 3, you can [[Adding_a_new_game_to_Vortex|scan for it or define it manually]].
 
If you can’t see Witcher 3, you can [[Adding_a_new_game_to_Vortex|scan for it or define it manually]].
 +
 +
 +
  
 
== Managing your W3 Load Order ==
 
== Managing your W3 Load Order ==
Line 37: Line 40:
 
*"Merges" generated by the [[Tool_Setup:_Witcher_3_Script_Merger|Witcher 3 Script Merger]] have to load first and are automatically locked to the first slot in the load order.  
 
*"Merges" generated by the [[Tool_Setup:_Witcher_3_Script_Merger|Witcher 3 Script Merger]] have to load first and are automatically locked to the first slot in the load order.  
 
*Vortex will only pick up on mods that you have installed via Vortex. If you have manually installed some of your mods, you need to add them by either editing your mods.settings file, or by reinstalling them with Vortex. Both options are explained below.  
 
*Vortex will only pick up on mods that you have installed via Vortex. If you have manually installed some of your mods, you need to add them by either editing your mods.settings file, or by reinstalling them with Vortex. Both options are explained below.  
 +
 +
[[File:W3LoadOrderExample.png|1050px|Witcher 3 Example Load Order including a Script Merge and a manually added mod.]]
  
 
&nbsp;
 
&nbsp;
Line 42: Line 47:
 
=== Adding manually installed mods ===
 
=== Adding manually installed mods ===
  
If you have previously installed mods manually by unpacking them into the Witcher 3 mods folder, Vortex (nor any other mod manager) does not know about them and they will not be loaded by the game.
+
If you have previously installed mods manually by unpacking them into the Witcher 3 mods folder, Vortex (or any other mod manager) does not know about them and they will not be loaded by the game.
  
 
However, there are two simple ways to add manually installed mods so they show up in the load order tab within Vortex:
 
However, there are two simple ways to add manually installed mods so they show up in the load order tab within Vortex:
Line 50: Line 55:
 
&nbsp;
 
&nbsp;
  
==== Adding mods to the mod.settings file ====
+
==== Adding mods to the mod settings file ====
  
 
For our example, we will take a look at what your Vortex/mods setup would look like if you had two mods. One installed with Vortex, and one installed manually (by dropping the contents of an archive into the Witcher 3 mods folder).
 
For our example, we will take a look at what your Vortex/mods setup would look like if you had two mods. One installed with Vortex, and one installed manually (by dropping the contents of an archive into the Witcher 3 mods folder).
Line 113: Line 118:
 
[[File:ModZippedDropped.JPG|900px|ModZippedDropped.JPG]]
 
[[File:ModZippedDropped.JPG|900px|ModZippedDropped.JPG]]
  
=== For Vortex version 1.1.15 or lower ===
+
=== For older versions of Vortex ===
 +
 
 +
IMPORTANT NOTICE: Managing your load order is only supported in '''Vortex 1.2.0''' and above. If you are using an older version of Vortex, please update as you are missing out on the most powerful features of the Witcher 3 game extension.
 +
 
 +
 
  
IMPORTANT NOTICE: Managing your load order is only supported in Vortex 1.2.0 and above.
 
  
 
== Troubleshooting ==
 
== Troubleshooting ==
Line 121: Line 129:
 
=== My mod does not work/is not recognised by the game. Why is that? ===
 
=== My mod does not work/is not recognised by the game. Why is that? ===
  
Monster Hunter: World is a game that is still actively supported by the developers (Capcom). While this is good because new content is added on an almost monthly basis, this also means that the essential tool "Stracker's Loader" needs to be tweaked each time the game is updated. Please ensure that your version of Stracker's Loader is up to date and allow for some time for the author of the loader to make necessary changes after each game update.
+
If your mod is seemingly ignored by the game, make sure it actually shows up in your load order. A mod that does not show in the load order tab in Vortex will not be loaded by the game. Make sure it is actually installed and enabled. If it is a mod that you have installed manually, you will need to add it to the mod.settings file or reinstall it via Vortex (see above). '''Don't forget to hit "Refresh" on the Load Order tab in Vortex, and deploy your changes thereafter.'''
  
 
&nbsp;
 
&nbsp;
  
=== I'm getting a security prompt each time I install a mod, can I stop that? ===
 
  
Depending on your settings, Vortex may select "[[Deployment_Methods#Symlink_Deployment|Symlink Deployment (Run as Administrator)]]" as the default deployment methos. This is perfectly fine to use but will require you to accept a security prompt from Windows each time you deploy or change your mods.
+
=== Mod issue Troubleshooting Checklist ===
 +
 
 +
*Make sure the mod you are using is for the right version of the game. Witcher 3 mods that were made for older versions or for different versions (Game of the Year Edition vs. Standard edition etc.), may prevent the game from starting, or may cause unintended issues. Often outdated mods have since been superseded by new mods with the same functionality, but designed to work with more recent versions of the game.
 +
*Make sure you have created a script merge using the Witcher 3 Script Merger.
 +
*Ensure that you have correctly installed the [https://www.nexusmods.com/witcher3/mods/2134 Unification Patch] which is highly recommended and a prerequisite for many mods. An alternative for the Unification Patch is the [https://www.nexusmods.com/witcher3/mods/3652 Community Patch - Base].
 +
*Ensure that you have also downloaded and installed any requirements for the mods you are using. Some mods may require you to install any of the following:&nbsp;[https://www.nexusmods.com/witcher3/mods/3652 Community Patch - Base], [https://www.nexusmods.com/witcher3/mods/2110 Community Patch - Shared Imports], [https://www.nexusmods.com/witcher3/mods/2109 Community Patch - Bootstrap and Utilities]
 +
*If your mod is not preventing the game from starting, but you are missing e.g. special effects or other content, you can try moving it further up (lower index number = higher priority in Witcher 3) in your load order tab in Vortex.
 +
 
 +
&nbsp;
 +
 
 +
=== How do I remove a manually added mod? ===
 +
 
 +
If you have manually added a mod to the mod.settings file, you will need to delete its entry there to remove it from your game. Changing "Enabled=1" to "Enabled=0" will not disable the mod. To properly remove/disable a manually added mod, navigate to your mod.settings file typicall found in "''C:\Users\YourUsername\Documents\The Witcher 3''". Find the mod you want to remove/disable and delete the entry between brackets for example "[modManuallyInstalledExample]". Go back to Vortex and hit "Refresh" in the Load Order tab. The mod should now disappear from the load order. Don't forget to deploy your changes to ensure the leftover entries in the mod.settings file are removed by Vortex.
 +
 
 +
&nbsp;
  
To avoid this, you may want to go to Settings > Mods and change the deployment method to "[[Deployment_Methods#Hardlink_Deployment_(Default)|Hardlink deployment]]", then click "Apply". This will require one final security prompt to save the change.
+
=== No deployment option is available. Why is that? ===
  
''See also: [[Deployment_Methods|Deployment Methods]]''<br/> &nbsp;
+
This typically affects users who 1) were using hardlink deployment and 2) do not have system permission to use symlink deployment. As of 1.2.15, we have added support for mods that add menus. Because these mods require Vortex to deploy files to the My Documents folder, this means in order to continue using hardlinks the game, the mod staging folder, and the My Documents folder would need to be on the same drive. If this is not the case, Vortex will need to switch to symlink deployment. While this is fine for the vast majority of users, some users might not have the correct system permissions to create symlinks and thus use symlink deployment. To fix this, please ensure that your Windows user account has the appropriate permissions for symbolic link creation to become available.
  
[[Category:Vortex]] [[Category:Getting Started]] [[Category:Monster Hunter World]]
+
[[Category:Vortex]] [[Category:Getting Started]] [[Category:The Witcher 3]] [[Category:Modding Guides]]

Latest revision as of 10:53, 10 July 2020

Witcher3.jpg
The Witcher 3: Wild Hunt

The Witcher 3: Wild Hunt is a 2015 action role-playing game developed and published by CD Projekt.

Released: 2015

Genre: Action RPG

Engine: REDEngine

Nexus Mods

 This guide is designed to help you set up Vortex to install and manage mods for The Witcher 3: Wild Hunt.  

 

 

Requirements

Before we get started, this guide assumes that you have installed The Witcher 3 and Vortex at their default locations. You will also need to be logged in to your Nexus Mods account in Vortex. Other than that, if you are planning to use more than 3-5 mods, it is recommended to set up the Witcher 3 Script Merger.

Getting Set Up

To begin, open up Vortex and navigate to the games section. If you don’t already see Witcher 3 under the “Managed” tab, check the “Discovered” section. Use the “Manage” button on the game tile to add it to your managed games.

xImage Witcher 3 unmanaged

If you can’t see Witcher 3, you can scan for it or define it manually.



Managing your W3 Load Order

VortexLogoSmall.png This content applies to Vortex 1.2.0 and above.


As of Vortex version 1.2.0, you can manage your Witcher 3 load order directly in Vortex via the "Load Order" tab.

  • You can drag and drop mods anywhere in the list to create the load order you want.
  • For Witcher 3 (this may be different for other games) the topmost mod overrides the other mods (only if there are conflicts). In other words, the mod with the lower index number will override a mod with a higher one (a mod that is further down the list). In Witcher 3 the first mod to load wins the conflict. This is important when deciding on which mod to sort before another if they both do the same or similar things (e.g. texture replacers which affect the same things in the game).
  • "Merges" generated by the Witcher 3 Script Merger have to load first and are automatically locked to the first slot in the load order.
  • Vortex will only pick up on mods that you have installed via Vortex. If you have manually installed some of your mods, you need to add them by either editing your mods.settings file, or by reinstalling them with Vortex. Both options are explained below.

Witcher 3 Example Load Order including a Script Merge and a manually added mod.

 

Adding manually installed mods

If you have previously installed mods manually by unpacking them into the Witcher 3 mods folder, Vortex (or any other mod manager) does not know about them and they will not be loaded by the game.

However, there are two simple ways to add manually installed mods so they show up in the load order tab within Vortex:

 

 

Adding mods to the mod settings file

For our example, we will take a look at what your Vortex/mods setup would look like if you had two mods. One installed with Vortex, and one installed manually (by dropping the contents of an archive into the Witcher 3 mods folder).

RTENOTITLE

The above is what the contents of your mods folder would be. However, since only one of these mods is installed with Vortex, only that one would show up in the mod list in Vortex:

VortexModList.JPG

 

Likewise, only this one mod would show up in the "Load Order" tab:

LoadOrder1.JPG

The mod we had installed manually "modManuallyAddedExample" needs to be added to the "mod.settings" file which is a file that can be found in C:\Users\YourUsername\Documents\The Witcher 3:

RTENOTITLE

 

Open that file and insert the exact name of the mod you want to add as it appears in the Witcher 3 mods folder in square brackets. In our example it would look like this:

RTENOTITLE

You DO NOT have to add or worry about "Enabled, Priority, or VK" - Vortex will apply those parameters automatically the next time you deploy.

Now, go back to your Vortex Load Order tab and click "Refresh" as shown in the image:

HitRefresh.JPG

This should bring up the recently added mod:

ModAdded.JPG

 

Make sure to hit the "Deploy Mods" button once you are done so Vortex can update the mod.settings file to add the needed parameters.

RTENOTITLE

Optional: You can double-check that everything went smoothly by checking your mod.settings file again (after refreshing and deploying). It should have added the Enabled, Priority, and VK parameters for the mod we just added:

RTENOTITLE

 

Reinstalling mods via Vortex

The other option is to simply zip up the mod/mods you have installed manually and install them again via Vortex.

  • Navigate to your Witcher 3 mods folder (typically this would be in: C:\Program Files (x86)\Steam\steamapps\common\The Witcher 3\mods
  • zip up the mod you want to reinstall with Vortex
  • Important: Make sure to delete the manually installed mod from the Witcher 3 mods folder.
  • Drag and drop the zip archive into the Vortex drop zone (at the bottom of the mods tab)

Vortex Drop zone.PNG

The mod will now be added and can be installed with Vortex:

ModZippedDropped.JPG

For older versions of Vortex

IMPORTANT NOTICE: Managing your load order is only supported in Vortex 1.2.0 and above. If you are using an older version of Vortex, please update as you are missing out on the most powerful features of the Witcher 3 game extension.



Troubleshooting

My mod does not work/is not recognised by the game. Why is that?

If your mod is seemingly ignored by the game, make sure it actually shows up in your load order. A mod that does not show in the load order tab in Vortex will not be loaded by the game. Make sure it is actually installed and enabled. If it is a mod that you have installed manually, you will need to add it to the mod.settings file or reinstall it via Vortex (see above). Don't forget to hit "Refresh" on the Load Order tab in Vortex, and deploy your changes thereafter.

 


Mod issue Troubleshooting Checklist

  • Make sure the mod you are using is for the right version of the game. Witcher 3 mods that were made for older versions or for different versions (Game of the Year Edition vs. Standard edition etc.), may prevent the game from starting, or may cause unintended issues. Often outdated mods have since been superseded by new mods with the same functionality, but designed to work with more recent versions of the game.
  • Make sure you have created a script merge using the Witcher 3 Script Merger.
  • Ensure that you have correctly installed the Unification Patch which is highly recommended and a prerequisite for many mods. An alternative for the Unification Patch is the Community Patch - Base.
  • Ensure that you have also downloaded and installed any requirements for the mods you are using. Some mods may require you to install any of the following: Community Patch - Base, Community Patch - Shared Imports, Community Patch - Bootstrap and Utilities
  • If your mod is not preventing the game from starting, but you are missing e.g. special effects or other content, you can try moving it further up (lower index number = higher priority in Witcher 3) in your load order tab in Vortex.

 

How do I remove a manually added mod?

If you have manually added a mod to the mod.settings file, you will need to delete its entry there to remove it from your game. Changing "Enabled=1" to "Enabled=0" will not disable the mod. To properly remove/disable a manually added mod, navigate to your mod.settings file typicall found in "C:\Users\YourUsername\Documents\The Witcher 3". Find the mod you want to remove/disable and delete the entry between brackets for example "[modManuallyInstalledExample]". Go back to Vortex and hit "Refresh" in the Load Order tab. The mod should now disappear from the load order. Don't forget to deploy your changes to ensure the leftover entries in the mod.settings file are removed by Vortex.

 

No deployment option is available. Why is that?

This typically affects users who 1) were using hardlink deployment and 2) do not have system permission to use symlink deployment. As of 1.2.15, we have added support for mods that add menus. Because these mods require Vortex to deploy files to the My Documents folder, this means in order to continue using hardlinks the game, the mod staging folder, and the My Documents folder would need to be on the same drive. If this is not the case, Vortex will need to switch to symlink deployment. While this is fine for the vast majority of users, some users might not have the correct system permissions to create symlinks and thus use symlink deployment. To fix this, please ensure that your Windows user account has the appropriate permissions for symbolic link creation to become available.