Welcome! In order to get started with NV:MP while it is still in beta, you will need to download either the installer (which will automatically install NV:MP to your Fallout: New Vegas folder), or alternatively, you can download the raw client files and extract them to your FO:NV folder.
This will install NV:MP as an automatically updating program on your system.
¶ Client Files
If you'd prefer to download NV:MP as a ZIP, you can download the latest release from here and extract it to your New Vegas folder.
If there's something that isn't listed to help answer your question, feel free to ask in our Discord.
Yes. With the most current version of the NV:MP client, it is possible to host your own private CO:OP server. Simply open the client, and select the “Launch Local Sever” button. For instructions, look here.
Yes and no. In general, it is recommended to have a fresh, unmodded game installation before installing NV:MP and use that to play, but there are mods that work with the mod after installing it. NV:SE mods are currently being tested as of 3.82. On the main server (Ring-A-Ding-Ding), NVSE mods are not permitted and will be blocked when you attempt to jon.
This troubleshooting list is incomplete, and could potentially be outdated. If you are stuck for solutions, please use our #nvmp-support channel in Discord.
Uninstall the game using Steam, then check the Steamapps/Common folder and delete the Fallout New Vegas folder if it remains. After installing the game again, launch it and load up an existing save file or start a new game up until pressing “No” on the Hardcore prompt at the end of the Doc Mitchell intro, be sure to save afterwards to have a clean unmodded save file for any future fresh installs. This process will create the fresh .ini files. Install NV:MP again and it should work right away.
If you would like to keep a separate installation of Fallout New Vegas for modded singleplayer purposes, rename the game's directory in the Steamapps/Common folder. An example would be “Fallout New Vegas Singleplayer”. This should also be done in the Documents/My Games folder for the “FalloutNV” folder. From there, you can uninstall and reinstall the game via Steam. Launch the newly installed New Vegas in a similar fashion as stated above to create a new FalloutNV folder. You will now have a second, fresh install of the game that can be used to install NV:MP without any worry of needing to remove any pre-existing mods.
This is an issue caused by your translated game having a different FalloutNV.esm than the server's copy, which is an English FalloutNV.esm copy. Any translation changes FalloutNV.esm's integrity. The fix for this is to change your game's language through Steam itself.
To do this, go into Steam, click on Library and find Fallout New Vegas and right click on it, click on properties and select the Language tab, then select English as your language. If you're doing this whilst you have the game already installed, it will basically act as an update to the game and you should be able to download the other two dependencies and play NV:MP. If this doesn't work, uninstall the game, set the language to English and install it with the language set like that.
If you're on GOG, you will have to either change language through there or get another English GOG copy.
For Fallout New Vegas RU players: after switching the language to English, be sure to go into your game's Data folder and deleting FalloutNV.lang file, which is completely useless on the English version and in fact will actually make the loading longer because it doubles the entries that FalloutNV.esm has, making them load again for another unecessary time. When you're done with playing NV:MP, switch to your preferred language (RU, CZ, PL) and verify integrity to get FalloutNV.lang back, as it is required for the Russian/Czech/Polish main menu translations, primarily fonts.
This is a seemingly rare issue that crops up, but after some trial and error I have found an incredibly simple fix: simply run New Vegas in windowed mode. This has worked for those that have encountered it. If it does not work, then change your game resolution until it does work.
Fallout New Vegas is infamous for its random crashes, and by extension this applies to any and all modifications to the game. NVMP is still in development, so it's likely you'll experience crashing. If you do crash, it is recommended to submit your crash via the automatic bug reporter that opens after a crash occurs.
Some players have experienced more crashing happening with the 4GB installation of NV:MP (as of 3.82+). Please see if removing this, and making sure New Vegas Heap Replacer is not enabled. It is also recommended that you install New Vegas Anti-Crash (NVAC). The number of crashes you experience may be reduced if you are using NVAC.
This is because the Mod Dependencies prompt is only made to detect dependencies within the default Steam Fallout New Vegas filepath that it was set to detect, even if the Steam version isn't installed. This filepath is C:/Program Files (x86)/Steam/steamapps/common/Fallout New Vegas/Data. Chances are if you own the GOG version, you don't have this filepath anywhere in your PC. The fix is to create it.
First, go into your GOG installation's Data folder and copy FalloutNV.esm. Go into C:/Program Files (x86), create a Steam folder, then a steamapps folder inside it, then a common folder inside the steamapps folder, then a Fallout New Vegas folder into common and a Data folder into the Fallout New Vegas folder. Inside this data folder you will paste the FalloutNV.esm file that you copied. With this, you should be able to download the two other dependencies. However, this process isn't done yet.
Once the two dependencies have downloaded, cancel the authorization process completely and go back to your “Steam” Data folder. You should have two .ESP files named NVMP Q Patch and NVMP Rebalance. Copy them and paste them into your GOG installation's data folder and then you can properly authorize and NV:MP will work like normal.
If the process above doesn't work, you can create the entire Steam Fallout New Vegas filepath, however this time you don't create the Fallout New Vegas folder, but instead you dump the entire GOG game installation folder (with the folder name set to Fallout New Vegas) into that steamapps/common folder. Once you've done that, Edit Game Directory and set it to your GOG copy now located inside your fake steamapps/common folder.
If this process doesn't work either, then the only course of action would be buying the game on Steam or waiting on GOG support to be completely fixed.
This issue can be fixed in 3 ways, depending on whether you have the 4GB Patch or not. Without 4GB Patch, see if you have any other NVSE mods other than NVAC and delete those. If that doesn't work, delete all NVSE-related files and mods and it should work.
With the 4GB Patch, simply removing all NVSE-related files and mods will only make the game crash on the Bethesda and Obsidian logos, as the 4GB Patched .exe still tries to start up the NVSELoader that is no longer in your game installation folder, requiring you to uninstall the 4GB Patch aswell, by renaming the FalloutNV_backup.exe to FalloutNV.exe, replacing the patched one.
If none of those options work, you will have to do a completely fresh install. This process is explained at the top of the Troubleshooting section.
Unfortunately, even with MO2's virtual folders function, the game installation directory isn't saved from major changes that affect NV:MP. You can either do a fresh install (instructions at the top of Troubleshooting), or using two game directories.
The easiest way to do this that I've heard from another experienced player is to find the Fallout New Vegas folder in Steamapps/Common and rename it into anything you want, then go into Steam and uninstall New Vegas. Because Steam doesn't detect anything, it doesn't uninstall anything either, but it recognizes New Vegas as uninstalled. Afterwards, download and install New Vegas again, then launch the game and load a clean save file or start a new game and get to the part where you say “No” to the Hardcore prompt, then exit the game, so that the new .ini files get created. With this, you should be able to install NV:MP into the clean Fallout New Vegas folder and play.
If you want to continue playing TTW, rename Fallout New Vegas (the one with NV:MP installed) into something else then rename your TTW game installation back into Fallout New Vegas, then use MO2 to start it all up, and it should work. As a warning: do not boot up MO2 if you haven't renamed the Fallout New Vegas folder with NV:MP installed, as it will break it. The same can be said about the other way around: NV:MP will not work with a renamed Fallout New Vegas NV:MP directory.
This can also apply with other mods of such a magnitude like The Frontier and New California, however DUST runs off of one .ESP file so this process isn't required, as the server you're playing on will disable it.
If you've received an MOTD error, it means that you successfully made a connection to the server as a player - but your client didn't follow up with the first “Message of the Day” packet in time (maximum time allowed in CO:OP servers is 1 minute 30 seconds until the player is kicked). This packet tells the server you're ready to be synchronized.
There are a few potential solutions, the first is seeing if removing a 4GB patch to FalloutNV helps. There is a temporary issue with the 4GB patch that may cause NV:SE to prevent NV:MP from sending communications to the server. If this doesn't help, then the next point of call is to make sure you don't have an NV:SE plugin that is interfering. The last solution we can offer is seeing if you have too many mods being loaded for your CPU to handle. Again, if you take longer than 90 seconds - then the server thinks you're unresponsive and disconnect you.
Please make sure you have run the game after installing at least once; trying to run NV:MP without having first run Fallout: New Vegas can present some issues that make the mod unplayable.
Yes. The Lonesome Road and Gun Runner's Arsenal (GRA) DLCs have been implemented into the main server (Ring-a-Ding-Ding Server). As of the 3.82 update, these are the only two required. However, more of the DLCs may possibly be implemented into the server in the future.
This is a common issue that usually happens when New Vegas is not installed in the correct place. The game needs to be installed on the same drive that Steam is on. For example, this is what your directory should look like for New Vegas - C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas
Also be sure that your NVMP Client/Launcher is installed within the Fallout New Vegas directory.
Translations of the ‘Getting Started’ guide are made by members of the community and don't play an active part in moderation or development for New Vegas Multiplayer unless stated, in the same vain as this is an English speaking community these guides cannot be properly fact checked and tested so please be advised that these may become out dated and not in support as these aren't actively moderated or ran by the moderation nor development team and are upon the community and members to keep update.
Español/Spanish - insert link
Author - Arko Piktuviry#8843