Fallout 4

After a lack of good guides on how to mod Fallout 4 on Ubuntu 20.04, and fighting with Lutris/Vortex Mod Manager for a couple days, I've made this as a reference so that other people don't need to spend days researching this. I make no guarantees that it will work for you, but at this point I'm running custom textures and scripts, so I assume it should scale up from there.

This is aimed at being a complete guide on how to install Mod Organizer 2 (MO2) and get mods working (including scripts) on the Steam version of Fallout 4; ensuring that the mods themselves are functional and compatible is beyond the scope of this tutorial. I will walk through all the steps, but effectively you will need:

  • Fallout 4 on Steam
  • Proton
  • WINE
  • winetricks
  • protontricks
  • Mod Organizer 2 Linux Installer
  • Optionally: F4SE (Fallout 4 Script Extender)

So, without further ado, here's how I got mods to work with the Steam version of Fallout 4 on Ubuntu 20.04:


First, you need to install Fallout 4 through Steam and make sure it will run. Assuming you haven't done so already, here's how you get Fallout 4 on Ubuntu:

  • Install the Steam client and log in.
  • Go into the "Settings" menu (Steam -> Settings).
  • Select the "Steam Play" tab on the left (at the very bottom).
  • In the right panel, under the "Steam Play Settings", select "Enable Steam Play for supported titles".
  • Under the "Advanced" section below, select "Enable Steam Play for all other titles".
  • The Mod Organizer 2 install (below) recommends using Proton 6.3 due to extensive testing, but I ended up running it with Proton Experimental; if you choose to run a newer version of Proton than what's technically supported by MO2, then expect there may be issues.
  • Click "OK" to save your settings.
  • Install Fallout 4 as usual, then launch it and make sure it runs; I would run it at least through until you exit the Vault (also a good position to test mods later).
  • Before continuing, make sure that there are no additional "Launch Options" set for the game (open the game in your library, click on the "gear" icon below the image, select the "Properties", and make sure the "Launch Options" text box is empty).
  • Note that the author of MO2 on Linux indicates that it may not work with any games installed after you install MO2, so make sure you have Fallout 4 ready to go before continuing.


Now you can install Mod Organizer 2:

  • Everything listed here is outlined on the Mod Organizer 2 Linux Installer github located here: https://github.com/rockerbacon/modorganizer2-linux-installer
  • If the above link doesn't work, it's a github repository by rockerbacon called modorganizer2-linux-installer. Note that I am not the author of this repo, but going this route has made it stupidly quick and easy to get back into Fallout 4.
  • I will outline the main points below, but everything is covered in the README on the above repository.
  • I had WINE, winetricks, and 7z installed before doing the following steps, but you will need to install those first if you don't have them. On Ubuntu, they can be installed using "sudo apt install".
  • First, you will need to install protontricks, which can be found here: https://github.com/Matoking/protontricks. If the link doesn't work, it's a github repository by Matoking called protontricks. The github recommends using Flatpak (which you will have to install if you don't already have it), although I installed it manually using the terminal. If you'd like to install it manually, I used these instructions (https://simpler-website.pages.dev/html/2021/1/protontricks/), although essentially you will need to go into your terminal and type:

    1 sudo apt install python3-pip python3-setuptools python3-venv
    2 python3 -m pip install --user pipx
    3 python3 -m pipx ensurepath

    Then close and reopen the terminal and install protontricks using:

    1 pipx install protontricks
    And that should install it.
  • Download the latest stable release of the Mod Organizer 2 Linux Installer from rockerbacon's github and extract it.
  • Open the extracted folder and run "./install.sh", then follow the installation instructions (I did this through the terminal).
  • Once installation completes, you'll want to launch Fallout 4 from Steam, and it should launch directly into MO2.
  • At this point, you will be provided with a series of options; I chose to install separate instances (portable instead of global), as I've read previously that there may be issues with getting mods to work properly using a global install. If you're only modding Fallout 4, there's no real reason to do a global install anyway, so no sense risking it.
  • I kept all of the other defaults, with the exception of adding my API key for Nexus Mods (although you can do that later if needed, and it's likely not required).
  • I've read that launching webpages from MO2 on Linux can cause crashes, so I selected "No" for the tutorial (as it forces you to navigate to the web at one point).
  • Once MO2 loads up, launch Fallout 4 from within it to make sure everything launches properly; if all works, then you can quit out from the game and return to MO2.
At this point, the Steam launcher should load MO2 instead of Fallout 4, and you should be able to launch Fallout 4 from within MO2 without issues. If you're not able to do this, then take a step back and make sure you've followed everything correctly. At worst, you may have to remove and reinstall Fallout 4 entirely, then reinstall MO2.


Manually loading and installing mods in MO2:

  • I haven't tried automatically downloading and installing mods from Nexus using MO2, so it may or may not work. I get my mods from other sources as well, and already had most of them downloaded, so I chose to manually install them.
  • Note that this will not work for installing F4SE (Fallout 4 Script Extender)! Installation of F4SE is covered in the next section.

  • Download the mods you want.
  • Open a file explorer window and navigate to your main "Downloads" directory (or wherever your mod is stored).
  • Open a second file explorer window and navigate to the MO2 download directory; mine was located at:

    ~/Games/mod-organizer2-fallout4/modorganizer2/downloads
    If you can't find the correct directory, you can locate it by launching MO2 from Steam, clicking on the "open folder" icon above the mod pane, selecting "Open Downloads folder" from the drop-down menu, and working your way up through the directories to figure out where it is
  • Move or copy the mod file from your main "Downloads" directory to the MO2 "Downloads" directory. You might be able to drag it directly from your main "Downloads" directory into the "Downloads" pane in MO2, or the folder itself within MO2, but I found it easier to go between the two folders directly.
  • If MO2 isn't running yet, launch it and you should see the mods appear in the "Downloads" pane on the lower right of the window (make sure to select the "Downloads" tab if needed).
  • At this point, you should modify the fallout4custom.ini file. On my computer, this file was located at:

    ~/Games/mod-organizer2-fallout4/modorganizer2/profiles/Default/fallout4custom.ini
    This file appeared after launching Fallout 4 from MO2, but if it's not there then you will have to create it.
  • In the fallout4custom.ini file, add the following lines:
    [Launcher]
    bEnableFileSelection=1

    [Archive]
    bInvalidateOlderFiles=1
    sResourceDataDirsFinal=

    Then save and close the file.
  • At this point, you can create separate profiles for your mod lists; if you modified the default fallout4custom.ini file as above, you can either copy the Default profile and rename it, or select the "Default Game INI Settings" when making a new profile. Otherwise, you will have to modify the fallout4custom.ini file for each profile.
  • Install the mods you want from the "Downloads" pane (double-click or right click -> "install"). You will need to choose the appropriate options and maintain compatibility yourself.
  • Enable the mods in the main mod pane.
  • Launch Fallout 4 from MO2 and check that your mods are showing up and active.


Installing F4SE (Fallout 4 Script Extender):

  • F4SE needs to be installed directly into the main Fallout 4 directory in order to work; MO2 does not like the F4SE directory structure and will not install it properly for you.

  • Download the current version of F4SE from silverlock.org: http://f4se.silverlock.org/
  • Open a file explorer window, navigate to your main "Downloads" directory, and unpack the archive.
  • Open a second file explorer window and navigate to your main Fallout 4 installation directory. The main Fallout 4 installation directory will contain "Fallout4.exe" and "Fallout4Launcher.exe"; mine was located at:

    ~/.steam/debian-installation/steamapps/common/Fallout 4
    Note that ".steam" indicates a hidden directory/file, so you will need to enable "Show hidden files" in your file explorer window to get there.
  • Move (or copy) everything from the F4SE archive you unpacked into the main Fallout 4 installation directory; this should include "Data" and "src" directories, as well as 5 files (all named "f4se_...").
  • At the beginning of the file transfer, you should get a popup asking you to merge the "Data" directory; you want to make sure you merge the directories, as that will transfer the needed F4SE files from the archive to the "Data" directory without overwriting/removing needed files.
  • Launch MO2 and select "F4SE" from the drop-down menu on the upper right (next to the "Run" button), then click "Run".

If all has gone well, at this point Fallout 4 should launch and your scripts should be working. If not, make sure you've followed all of the steps correctly and your fallout4custom.ini file has the correct lines in it; otherwise, it could be an issue with the mod itself, or you may need to try a complete reinstall of MO2 (or Fallout 4).

Happy modding!

Article information

Added on

Edited on

Written by

popeface

7 comments

  1. agiletek
    agiletek
    • member
    • 0 kudos
    Seems to have worked. Any XEdit on Linux guides?

    edit: Just load it via ModOrganizer (after synaptic link for ini?).
  2. leumas9969
    leumas9969
    • member
    • 0 kudos
    This seems to work fine with one addition.
    I needed to restore the steam launch options that were removed from step 9 of the installation.
    The audio in game was not present or so broken that it was unusable.  Also the video would hesitate/stutter while moving.

    This is what worked in my case (mostly from protondb): 
    WINEDLLOVERRIDES="xaudio2_7=n,b" PULSE_LATENCY_MSEC=90 PROTON_NO_ESYNC=1 %command%

    Using Proton 6.3.8
    Ubuntu 22.04.3 LTS
    Kernel 5.15.0.89 generic
    Gnome 42.9
    CPU  Core i7 4770K 3.5 GHz
    RAM  16 GiB
    GPU  GeForce GTX-1080
  3. k5d
    k5d
    • member
    • 0 kudos
    Thank you very much for taking the time to write this :)
    Much appreciated :D

    (MO2 installed Ubuntu 22.04)
  4. mhawaro
    mhawaro
    • member
    • 2 kudos
    I made a video about FO4 Linux experiences here : https://www.youtube.com/watch?v=jnCjKiND-x8
  5. KingCobra007
    KingCobra007
    • member
    • 0 kudos
    Hello! I'm stuck on step 3 of installing MO2. "./install.sh" isn't working. I just get a error code saying: "ERROR: Redirector binaries not found" Any clue of how I can solve this?

    Pop!_OS 22.04 LTS
  6. Razorek94
    Razorek94
    • member
    • 0 kudos
    I have problem with model/ texture mods. Firstly I dont see any folders which I need for modding in main game Data folder. I have installed mods anyway, but MO2 did it in own data directory (paradoxally game was reacting on mod) but i had transparent/bugged character. I wanted to install unique body + wonder body.
  7. BlackSun1784
    BlackSun1784
    • member
    • 0 kudos
    This guide worked beautifully for me, thanks for posting this! I appreciate the detail for each step, and the ELI5 breakdown.

    Pop!_OS 22.04 LTS

    I had been using a flatpak version of steam, occasionally running lutris for some games that like to misbehave, and had trouble at first getting this to work. MO2 really didn't seem to want to launch from the flatpak steam install, I could get the game to run from MO2 by launching from the command line but it didn't seem to want to run more than 5 fps that way. Launching from the flatpak version of steam failed to launch MO2 or recognize any mods, though it would still give me an error message about mods being missing when loading my saves. A scorched earth approach switching to the Debian version of steam using the native app shop, reinstalling FO4 and running the MO2 install again seems to have worked, along with the install steps in this guide. I'm not sure why any of that would matter, but maybe because the flatpak steam runs sandboxed? I don't know enough about Linux to make a good guess.