-
Notifications
You must be signed in to change notification settings - Fork 2
2.1 Deploy Restore
When you have added your mods, You will need to press deploy on the top bar. This will move all the modded files to their target location. For smaller mod lists, this should be near instant. For larger modlists it will take a few seconds.
Whenever you make a change to a mod such as adding a new mod, disabling a mod or moving a mods position. You will need to deploy again
Deploy will silently run restore first, This ensures the game is put into it's vanilla state before anything moves over.
Restore simply reverts the game to it's vanilla state,
For some games, mods will create config files within the game folder. The manager can detect these files and when we run restore they will be moved to the overwrite folder. Then when deploying they are moved back to the game folder so the mod can read from it again.
Normally to run a modded bethesda game, you must run the game via script extender instead of the normal launcher. You can still do this but the manager makes it easier by renaming the script extender to the same name as the original launcher. The original launcher is backed up.
This way when we deploy, we can just launch the game via the original launcher via the manager or on steam. This is especially useful for the steam deck in gaming mode as we can just deploy then launch the game normally without having to open the manager each time we want to play the game or having to set up a non steam game to point to the script extender.
The shader cache folder for community shaders doesn't seem to work if it is hardlinked or symlinked. For this reason the shadercache folder is instead copied to the Data folder when deploying and copied back when restoring to ensure that the version in the overwrite folder is always in sync.
Since all of mewgenics files exist within a single gpak file, deploying works slightly differently. We don't need to move any of the files, instead we can use a command to point the game to those files. When deploying you will get 2 options, a steam command and a repack option. The steam command points to a script that contains the location of the modded files. It has to be a script as adding many mods will cause the command to be too long for steam.
The repack option will physically unpack the gpak file > replace/place the modded files > repack the gpak file. This is not fast but does mean we don't need a command. Any replaced vanilla files in this gpak file will also be backed up.