8. Workshop Exporting and Importing - ChrisDKN/Amethyst-Mod-Manager GitHub Wiki

Workshop / Exporting and Importing

In the collections window there is a workshop and Import manifest button. You will need to be logged into nexus to see and use these. The workshop is a feature that allows you to export your modlist as a zip file. The zip file contains a manifest that is used to rebuild the modlist in a similar manner to installing a collection. It also contains our profile state and load order files.

This means we can save our modlist and import it again later or share it with someone else so they can install the exact same modlist, similar to a wabbajack file.

Note that this is not quite the same as the workshop feature in Vortex, the idea is the same but we cannot upload it to nexus as a collection which would require building the manifest in the same way that Vortex does.

What it does

• Copies the modid and fileid of every mod in the profile and adds them to the manifest
• You can add a fileid to any mod that does not have one.
• Copies fomod settings for any mods in the profile that used fomod
• Adds the Overwrite folder, and load order settings to the output .amethyst file
• Importing via the inport manifest button will install the .amethyst file exactly like a collection and auto apply any saved fomod settings

Mod Source

The source button will give these 4 options, this is what they do

• Nexus - Downloads from nexus, Requires the modid and fileid to be set
• Direct URL - For mods not found on nexus you can add the url to them here, They will show up as off site mods in the install window
• Bundle - These mods will be copied straight to the .amethyst file. If the mod doesn't have a download link you should use this. This is useful if your modlist has something like a dyndolod output that you want to keep
• Ignore - The mod won't be added to the exported file at all