Usage
I recommend using a fresh installation of Outward if you want to use Vortex to manage your mods.
I also suggest installing BepInEx and PartialityWrapper with Vortex.
- Download the BepInEx and PartialityWrapper .zip file corresponding to your system.
- Go to the "Mods" tab on the left of Vortex
- Drop the zip file on the bottom of the page
- Install it like you would any other mod
* In case the links above would be outdated, use those from Outward's Official Wiki
How it works
It checks if there is a BepInEx folder at the root of the zip file and if there are files in it or in its sub-folders. Basically, if you follow the current standard for BepInEx mods .zip files, it should work without issues.
If the BepInEx Check is true, it copies the content in the outward folder, basically following the standard guidelines for installing bepinex mods
If the BepInEx Check is false, it check if the zip file contains .dll, .xml or .json files. If it does, it assumes it is a Partiality mod and copies every file in the BepInEx/plugins folder.
if no .dll, .xml or .json files are found it throws an "Incompatible Mod" error.
How the extension manages Partiality mods is a bit janky, but it should work for most of them.
If a partiality mod is not installed properly, you can make a new zip file with the .dll, .xml and .json in the BepInEx/plugins folder and the rest of the files placed correctly. Tthat way it will install it as a bepinex mod and should work.
The source code of my mods can be found here : GitHub
I recommend using a fresh installation of Outward if you want to use Vortex to manage your mods.
I also suggest installing BepInEx and PartialityWrapper with Vortex.
- Download the BepInEx and PartialityWrapper .zip file corresponding to your system.
- Go to the "Mods" tab on the left of Vortex
- Drop the zip file on the bottom of the page
- Install it like you would any other mod
* In case the links above would be outdated, use those from Outward's Official Wiki
How it works
It checks if there is a BepInEx folder at the root of the zip file and if there are files in it or in its sub-folders. Basically, if you follow the current standard for BepInEx mods .zip files, it should work without issues.
If the BepInEx Check is true, it copies the content in the outward folder, basically following the standard guidelines for installing bepinex mods
If the BepInEx Check is false, it check if the zip file contains .dll, .xml or .json files. If it does, it assumes it is a Partiality mod and copies every file in the BepInEx/plugins folder.
if no .dll, .xml or .json files are found it throws an "Incompatible Mod" error.
How the extension manages Partiality mods is a bit janky, but it should work for most of them.
If a partiality mod is not installed properly, you can make a new zip file with the .dll, .xml and .json in the BepInEx/plugins folder and the rest of the files placed correctly. Tthat way it will install it as a bepinex mod and should work.
The source code of my mods can be found here : GitHub