Integrating Tool Mods with Mod Organizer 2 for Fallout 4

It appears you’re encountering some confusion while trying to integrate external tools, specifically FO4CT (Fallout 4 Configuration Tool), with Mod Organizer 2 (MO2) for Fallout 4. Many users, especially those transitioning from other mod managers, sometimes find the nuances of MO2’s virtual file system a bit tricky when it comes to running tools. Let’s clarify how to ensure your Tool Mods, like FO4CT, are correctly recognized and function within your MO2 environment.

Understanding Mod Organizer 2 and Tool Execution

Mod Organizer 2 operates using a virtual file system. This means that when you run a game or tool through MO2, it creates a virtual environment where mods are layered on top of the base game files. Tools launched outside of MO2 will not see this virtualized mod setup, leading to potential discrepancies in settings and file access. Therefore, to have tools like FO4CT recognize your MO2 mod setup, you need to launch them through Mod Organizer 2.

Setting up FO4CT (or Similar Tool Mods) in MO2

To ensure FO4CT reads your Fallout 4 settings correctly when launched via MO2, follow these steps:

1. Adding FO4CT to MO2: First, you need to add FO4CT as an executable within Mod Organizer 2.

   • Open Mod Organizer 2.
   • Click the executables dropdown menu (it looks like a gear icon, often labeled “Executables”).
   • Select “Edit…”
   • Click the “+” button and select “Add from file…”.
   • Browse to the FO4CT executable (FO4CT.exe or similar) and select it.
   • Give it a descriptive name in MO2, like “Fallout 4 Configuration Tool”.
   • Click “Apply” and then “OK”.

2. Running FO4CT through MO2: Now, instead of launching FO4CT directly, launch it through MO2.

   • Open Mod Organizer 2.
   • Ensure your desired MO2 profile is selected.
   • Click the executables dropdown menu again.
   • Select “Fallout 4 Configuration Tool” (or whatever name you gave it).
   • Click “Run”.

By launching FO4CT this way, it will run within MO2’s virtual environment and correctly see the INI files and game settings as configured by your MO2 profile and mods.

Addressing INI File Discrepancies and “Local Game Settings”

You mentioned issues with INI files and the “Local Game Settings” option in MO2 profiles. Let’s address these:

• “Local Game Settings” in Profiles: When “Local Game Settings” is ticked in your MO2 profile settings, MO2 will manage separate INI files per profile. This is generally recommended for keeping profiles isolated and preventing conflicts.

  • When ticked, MO2 creates profile-specific INI files in ModOrganizerprofiles<YourProfileName>Fallout 4.
  • When unticked, MO2 uses the INI files located in My GamesFallout4.

• Missing Fallout4.ini in INI Editor: If you’re missing Fallout4.ini in MO2’s INI Editor when “Local Game Settings” is unticked, this is unusual. Fallout4.ini, Fallout4Prefs.ini, and Fallout4Custom.ini should generally be visible regardless of this setting, as MO2 should still be able to access and display the base game INI files. However, ensure that:

  • You are looking at the correct INI Editor within MO2 (accessible via the puzzle piece icon, then “INI Editor”).
  • Your MO2 is correctly set up for Fallout 4 and pointing to the correct game installation directory.

• BethINI and MO2 Paths: BethINI is a useful tool for configuring INI settings. While BethINI can detect MO2 paths, it’s crucial to ensure that when you make changes with BethINI, and then launch the game or tools, you are doing so through MO2 to ensure those changes are actually applied within the virtual environment. Changing the “INI Default path” in BethINI might not directly solve your MO2 integration issue, as MO2 manages INI files independently when “Local Game Settings” is enabled.

Conclusion

To effectively use tool mods like FO4CT with Mod Organizer 2, the key is to launch these tools directly through MO2. This ensures they operate within MO2’s virtual file system and recognize your mod configurations and INI settings correctly. By adding FO4CT as an executable in MO2 and running it from there, you should be able to manage your Fallout 4 settings seamlessly within your modded environment. If you continue to experience issues, double-check your MO2 setup, profile settings, and ensure you are consistently launching all tools and the game itself through Mod Organizer 2.