Skip to content

4.1 Root folder building

Chris edited this page Aug 5, 2026 · 3 revisions

Root Folder Building

The manager supports root folder building,

This can be a way to add certain frameworks to the game without having to keep them in the game's install directory all the time.

To do this:

  • Right click the Root folder separator found at the bottom of the modlist panel
image
  • Click open folder, This folder is in the staging directory for the configured game.

  • Add the files you wish to move the the games root folder

image
  • In this example I've added the BepInEx files for subnautica

  • Now when we deploy those files will be transfered to the games root folder and removed when we restore

  • If any of these files already existed in the games root folder, they will be replaced and backed up in the staging folder

Option 2 - Right click menu

There is now a much easier method than shown above, Simply right click a mod and enable root folder install, This will flag the mod to be installed to the root folder. The above method can still be used

image

Option 2 - Mod Files tab

For some games you might not want to send an entire mod to the root folder and instead just some of the files within it. the mod files tab contains a column for this case

image

This mod has its enb files/folders set to go to the root folder. The other ones not marked will be sent to their usual location

Note that for a game like Cyberpunk, this option will not appear as it is a root deployed game. So all files go to the root folder already

Option 4 - Do nothing

A lot of mods for games may be automatically flagged as root folder installed. For example Script extender and the SSE engine fixes preloader will automatically be flagged and sent to the root folder without any input needed.

Collection authors can also set mods that need to flagged as root folder installs, Amethyst will apply this flag to any of these mods too.

Clone this wiki locally