Introduction
In this article we will explore the process of manually modding Fallout New Vegas on Linux. While the steps are somewhat similar to those for modding Fallout 4, there are important differences we need to keep in mind.
It’s clear there’s a growing interest in manual modding for various Fallout games on Linux. I’ve received numerous requests for general modding guidelines, especially concerning Fallout New Vegas. The spike in interest might relate to the ongoing second season of the Fallout show, which is set in the same Mojave environment as the game.
Having recently finished Fallout New Vegas, which I bought during a Steam sale that included all its DLC, I’m excited to dive into modding it. However, I’ve encountered various tutorials that sometimes provide conflicting information, making this exploration all the more intriguing.
As with any modding endeavor, being mindful of your hardware and operating system setup is crucial, as these factors can significantly impact your experience. I suspect that the discrepancies in tutorials stem from individual setups, much like what I observed with Fallout 4.
Some have asked why I prefer manual modding. It’s a fair question! While I’ve tried different mod managers on Linux, they haven’t proven to be stable and often create more issues than they solve. So, manual modding has become my go-to approach.
Now, let’s get started!
My Current Setup
I’m currently running Fedora 43 on an MSI Raider GE76 laptop. Initially, I used Windows until the warranty expired, at which point I decided to do a complete flush of the system. I started with Arch Linux, but I wanted to challenge myself by using Fedora for an extended period, mainly because my past experiences with it were less than stellar.
Here are the key specifications of my setup:
- RAM: 64 GB
- Storage: 3 TB
- Processor: Intel i9-12900H
- Graphics: Integrated Intel Iris Graphics and a discrete GeForce RTX 3060 GPU
I’ve been using this laptop for about four years now and tend to go all-in on it, as I haven’t had a dedicated desktop for eight or nine years.My desktop environment is KDE Plasma 6.5.4. I have installed Steam via the Discover package manager (the package version, not Flatpak or Snap), and I’m currently using Proton Experimental as my compatibility layer for gaming.
I believe that covers all the important details about my setup!
Clean Install
Lets start things off with a clean install of Fallout new Vegas for this video, just to make sure we are all on the same page.
I am installing from Steam with all the Down Loadable Content (DLC).
I have gone through and deleted all reference to Fallout new Vegas after uninstalling it. So this install should be totally clean. This basically involves making sure the following two directories are deleted;
/home/rt/.local/share/Steam/steamapps/common/Fallout New Vegas/
/home/rt/.local/share/Steam/steamapps/compatdata/22380/I am installing from Steam with all the Down Loadable Content (DLC).
Once installed, We need to run the game to activate the DLC and create several files that don’t currently exist.
Before jumping into modding lets look at the layout of important directories across the file system. I will be referring back to these directories.
The first folder we need to find is the SteamApps folder. To do this select any game in your library, we will use Fallout New Vegas in our example. Right click and select properties. Then click on installed files. Finally click on Browse. The Steam Apps folder will be two levels up from your game folder.
Within the SteamApps folder is a folder called “common”. This is where Fallout New Vegas game folder resides. When mods talk about the “Data” folder, it resides in the Fallout New Vegas game folder.
In addition there is a “compatdata” folder, which contains the compatibility layers. Directories here are given numbers. For example Fallout 4 is “377160” and fallout New Vegas is “22380”. In the “22380” directory we find a “pfx” directory. And within the “pfx” directory we will find “drive_c”.
This is where your user data will reside for the game just like in windows; “drive_c/users/steamusers/Documents/My Games”. The path should look somewhat familiar to any Windows user.
Within the My Games Directory is a “FalloutNV” directory. This is where the files Fallout.ini and FalloutPrefs.ini reside. Remember these. When mods talk about modifying INI files, these are the ones they are usually talking about.
A final folder of interest on drive_c is /users/steamuser/AppData/Local/FalloutNV/. Here we find the plugins.txt and NVDLCList.txt files. These will become important when we look at Fallout New Vegas Script Extender.
Evaluating Mod Requirements
Yes, evaluating a mod before installation is essential. Let’s look at a few mods for Fallout New Vegas from Nexus Mods.
Weapon Mods Expanded – WMX. This mod enhances the game by adding various weapon modifications. The first step is to check the requirements section, which indicates there are no additional dependencies. This is ideal, as it allows for easy installation.
Next, let’s examine NMC’s Texture Pack for New Vegas. Similar to WMX, this mod has no additional requirements. However, there are multiple large files for download, which introduces a bit of complexity.
Now, take a look at Nevada Skies – Weather Effects. This is where things get complicated. Checking its requirements reveals four Nexus Mods dependencies, along with one off-site requirement. Some of these dependencies may have their own requirements, adding layers of complexity.
The key takeaway here is the importance of reviewing mod requirements prior to downloading. Failing to do so may lead you into what Linux users like to refer to as “Dependency Hell.”
Installing Tidier Prospector Saloon Mod
Since this is a fresh play through, I will start with a few mods that are present at the start, and also have limited requirements (mainly the DLC). Tidier Prospector Saloon makes some adjustments to the front of one of the first buildings you will run across when entering the game. We will do a before and after look.
Looking at the front entrance we see a few chairs, a couple of motorcycles with one knocked over. Remember this scene.
Opening the mod archive, we extract it to our staging folder. We use a mod staging folder in case we need to reinstall New Vegas, it is a simple matter just to drag and drop all the files from the stagging folder instead of extracting and copying them individually.
We copy the esp file (one of Bethesda’s archive formats) to the Fallout New Vegas Data Folder located in SteamApps/Common/Fallout New Vegas. Remember the Steam Apps folder form earlier in the video?
Once that is done we start the game. From the launcher window we select Data Files. You should see the mod listed but unchecked. To activate it we simply check the box and then select OK.
Once we enter the game we can see the changes. All the motorcycles are upright on the left side. There is some type of matting in front of the Saloon. Some tables and a floor mat have also been added.
Okay not an impressive mod, but it does show then process works.
Installing Boom Stick Mod
Lets install a second mod. This one is for a shotgun called the boom stick (nod to Bruce Campbell’s Ash character in the evil dead trilogy). This one is somewhat different in that it includes several loose files.
Note when extracting this one it will extract to its own folder. You will need to move everything to the main Mod Staging folder, and delete the parent Boostick folder.
After that it is a similar procedure with dragging and dropping to the New Vegas Data folder. If you drag the entire mod staging folder content over you will have to decide to overwrite the previous mod, since it is in there also.
Then the same process of opening the Data Files window form the Launcher and checking the box.
Once we are in the game we need to go to the old gas station on the hill. I am going to skip a few spoilers for the New Vegas story line. We find the new gun on the back shelf, sitting there waiting for us to pick it up. It is a double barrel twelve gauge that does double the damage of the Sturdy Caravan 20 gauge shotgun. Now if I just had some twelve gauge shotgun shells.
Fallout New Vegas Script Extender
Next we are going to do something a little different, installing the new Vegas Script Extender. The install is slightly more complex than the previous mods, but this mod is a requirement for a lot of other mods. Installing this mod also has a downside in that activating any new mods becomes more complex.
There are versions of this file on nexus mods, and a few other places. I suggest downloading it from its home page rather than a third party source.
As with the last mod we will extract to our staging folder, but we will leave everything in its original folder, mainly because the installation process is different.
We want to enter the NVSE folder and copy the contents over to the New Vegas folder, not the Data folder, but the main folder. We will get a widow about writing into the data folder, go ahead and allow this.
Now the tricky part, but this is the quickest and most reliable way I have found to get the script extender working.
In the main Fallout New Vegas folder find the FalloutNVlauncher.exe file. Rename it by adding a “.bak”.
Now find the nvse_laoder.exe file and rename it to FalloutNVlauncher.exe. This will make Steam run the file in the proper Proton environment.
There is probably a better way to do this, but I have not found it yet.
I am also assuming you have seen the issue this cases. Not running the FalloutNVlauncher.exe file means no Data Files Option, with no way to add mods or loose files. Well at leas through the program. Lets test it first, then tackle the adding mods issue latter
We start the game and use the tildent key in the upper left corner of an American English keyboard to open the terminal. We should see the NVSE version number. We can also run the command GetNVSEVersion, which should return the major version number. This shows the script extender is working.
Fallout New Vegas Script Extender Work Arounds
When using the Fallout New Vegas Script Extender (NVSE), you lose access to the Data Files option in the FONV loader. However, you can manually replicate some of its functionality. I’ve tested these steps with limited success, but I haven’t explored every possible scenario or the full range of mods like I have with Fallout 4. Please approach this with caution, as outcomes can vary. Also note file locaitons are for my system. Interpolation may be needed for other Linux Distributions and different install methods (like flatpak).
To add mods we need to go to;
/home/rt/.local/share/Steam/steamapps/compatdata/22380/pfx/drive_c/users/steamuser/AppData/Local/FalloutNV/Here, you will need to edit a file named plugins.txt. This file lists all DLCs and mods. To activate a mod added to the Data Folder, include its archive files in this list. Keep in mind that you may need to rearrange the lines if you encounter load order issues.
To load Loose files we need to go to;
/home/rt/.local/share/Steam/steamapps/compatdata/22380/pfx/drive_c/users/steamuser/Documents/My Games/FalloutNV/Next, modify the Fallout.ini file in the [Archives] section. The line bInvalidateOlderFiles=1 should already be present; if not, ensure it’s set to 1. Additionally, you’ll need to add the line sResourceDataDirsFinal=. Note that the Fallout.ini file may not be writable by default, so you may need to change its permissions to make edits.
Epilogue
In this video we have looked at some methods for installing mods to the Fallout New Vegas game.
Be aware modding can cause issues and unique challenges. So mod at your own risk. Always backup good saves, and be prepared to start from ground zero if needed. I highly recommend doing at least one play though without mods.
While initially modding Fallout New Vegas might appear easy, many mods are dependent on other mods and requirements. So it is important to read the full mod description, any additional requirements, and any reported issues.
That being said, modding can enhance the game environment and play, bringing new life to multiple replays.
There is nothing really hard about manual modding Fallout New Vegas on Linux. And in many cases manual modding will give you more precise control than a mod manager will. And having an increased understanding of what is installed and how can help you troubleshoot any problems that arise.
Manual modding is not for everyone, but it is worth giving it a try.