-
Notifications
You must be signed in to change notification settings - Fork 38
3.01 Mod Files Tab
Sometimes mod authors package their mods in a way the managers game handler does not expect or we just want to disable files or folders from being deployed without deleting them from the staging folder
We can also use the mod files tab to change which folder or file is considered top-level. This is in case a mod author has included an extra folder that the manager did not remove.
In the screenshot is lennys mod loader for RDR2, When we install it, it comes with a bunch of stuff we don't need. I have disabled every folder except for the Modloader folder.
I have then removed Modloader as a top level folder by selecting one of the files within it. When the manager sees this mod, it will now only see the enabled files within the modloader folder and will treat them as if they are in the root of the mod folder.
The mod itself in the staging folder doesn't change
I have then set this mod to root folder deploy, By default mods for RDR2 go to the LML folder but we want this mod to go to the game's root, so we right click the mod and enable root folder deploy. Now the files mentioned in the screenshot above will land in the games root folder on deploy. Techincally this is not actually needed as Lennys mod loader files are hard coded to always go to the root folder regardless of this setting but this is just an example of what it does
Getting started
Managing mods
- Installing a mod
- Mod Files Tab
- Updating a Mod
- Installing a collection
- Creating and uploading a collection
- Installing VNV and TTW
- Mods not working
- Profile Specific Saves
Load order and conflicts
Deploying and playing
Tools and advanced
Reference