Safe Modding

IMPORTANT:
None of the lists that follow are aimed at discrediting the work of certain authors nor direct any hate towards them. The goal is to provide alternatives to mods/tools that have been superseded, and to warn against problematic or placebo ones.

Gaining Independence

Modding past what the guide might include can feel intimidating at first. The purpose of this page is to give you a jump start in that process by highlighting mods and tools you should avoid, along with recommended additions that require minimal work to integrate into most lists (including DBF).

As you install more mods, make sure to get comfortable with the following principles:

  • Read descriptions carefully and check requirements.
  • Do not go overboard with the amount of mods all at once. Doing so is a common recipe for early annoyance that might sour the whole experience going forward, take it slow while you learn!
  • If a mod claims performance improvements, benchmark it.
  • When installing mods with a plugin, use FNVEdit and The Method to check for conflicts between it and the rest of your list.
  • If something breaks, troubleshoot using a binary search: disable mods in groups to isolate the problematic section, then narrow it down by splitting that group into smaller parts.
  • Join modding related communities! Lots of information can be found in conversations that already took place.


All of this is meant to help you build the skills and confidence needed to manage and expand your setup independently.


Mods to Avoid

UI element - Chevron

Bugfix & Optimization Mods

  • ENBoost - ENBoost works around the game's managed memory pool with memory sharing across processes. NVTF changes pool type and fixes the problem at the root, allowing higher VRAM usage. ENBoost also requires configuration based on the user's system and much like ENB, has been abandoned.
  • New Vegas Stutter Remover - Will cause periodic crashes and there is no reason to use it anymore, even on Windows 7. New Vegas Tick Fix replaces NVSR while also doing more. For more information on how to improve game performance, consult the Performance Guide.
  • Zan AutoPurge Crash Protector, PCB Hotkey, and Clear Cache Hotkey - Purging cell buffers is already done by the game during fast travel. Adding these mods will increase the usage of this command for no real benefit, possibly causing stutter.
  • FOOK, New Vegas Enhanced Content and Mission Mojave Ultimate Edition - Massively outdated compared to Yukichigai Unofficial Patch and will introduce bugs of their own.
  • NVAC:
    • It mostly consists of very generic null checks that allow the program to run even when it should not be able to.
    • It can lead to increased instability and save corruption because of the unpredictable behavior after ignoring an error.
    • Crash logging is impossible with NVAC, meaning you will get nonsensical and useless crash logs.
    • NVAC's aggressive inlining and patching can conflict with other NVSE plugins. Due to the closed source nature of NVAC, not every conflict point is known, thus there's always a chance for NVAC to actually cause crashes due to memory corruption.
    • Most engine issues have been fixed in other plugins, meaning that the only use case NVAC has in the modern day is to hide issues of "normal" mods (scripts, meshes etc.).
  • Auto Clean All Fallout New Vegas DLC Ultimate Edition - Running QAC is a minuscule fraction of the changes needed to fix the DLCs. It will not do anything by itself. Use Ultimate Edition ESM Fixes Remastered instead.

Visual Mods

  • Oversized textures - Based on the object size and how the texture is wrapped around it, you should pick textures with a reasonable resolution and avoid the very big ones also based on your display resolution. Keep in mind that the textures will not be displayed with their full resolution at all times, in fact they will be scaled down because of mipmaps based on distance and other factors, as shown with these sliders. Just for reference, a maximum of 2K at 1080p is a pretty safe bet in terms of balance.
  • AI-upscaled texture packs - Mods upscaled with AI or other automated techniques generally are not worth the higher VRAM usage.
  • ENB - Fallout 3 and New Vegas ENBs were never fully developed and have been abandoned by the author. This means they are left with some issues, like transparent and glowing objects (which can be somewhat mitigated with ENB Glowing Objects Overhaul).

    Due to its post-process and deferred nature, ENBs require MSAA to be disabled which introduces visual issues with alpha textures, that are not solvable with post-process anti-aliasing solutions.

    Additionally, ENB's integration with the game is pretty high level and detection based, which means that mods modifying graphical features in-engine can easily break ENB by changing something as simple as a resolution of a rendered texture, or replacing a shader.

    Many popular ENB features like LUTs, lens flares or god rays can be replicated with ReShade. There's also New Vegas Reloaded, which while still in development, offers similar feature set, while adding graphical features such as PBR or real global shadows.
  • Fallout Character Overhaul:
    • Multiple broken file paths which cause missing mesh triangles and pink textures.
    • The installer auto-selects patches for mods you don't have installed.
    • It doesn't cover every NPC in the game.
    • The ghoul file and the bLoadFaceGenHeadEGTFiles INI setting both reduce performance.
    • Reverts many YUP fixes.
    Use Simple Character Expansions instead.
  • Handheld Pip-Boys, such as the 2500 - All hand-held Pip-Boys share the same common visual bugs that occur if you enter/exit your Pip-Boy too fast. The methods these mods use to hide the Pip-Boy in third person are also quite janky, as they were made before NVSE extensions like JIP LN. These bugs and quirks have mostly been removed with Handheld Fixes though. Either 2500a or 2000 Mk VI are recommended.
  • Electro City - Contains unnecessary bloat and leftover features from a planned quest. Use A Little More Lamplight instead.
  • Vault 22 Flora Overhaul - Has tons of unnecessary bloat such as new weapons, enemies, poison effects, skill books and more. Use Vault 22 Flora Overhaul Remastered instead. Be aware that the mod is still pretty performance-intensive and should be avoided on weaker systems.
  • New Vegas Landscape Overhaul Remastered - Has broken navmeshes, many misplaced objects and bad balance. Use Mojave Scenery Overhaul instead. Be aware that it can lower performance on lower-end systems due to the amount of objects added to scenes.
  • Project Reality - Will cause massive performance issues and save bloat due to bad scripting.
  • Dragbody 10 Year Anniversary Pack and Ragdolls - Broken meshes prone to crashing.
  • Interior Lighting Overhaul - Nothing inherently wrong with it but needs proper patching for it to work as intended. Use Simple Interior Lighting Overhaul instead for a plug and play solution.
  • Weapon Animation Replacer WAR - Might cause crashing.
  • Borderlands Inspired Numeric Damage - Has a bug that can cause NPCs to teleport directly to you upon entering an interior.

Content & Gameplay Mods

  • Project Nevada - Outdated, inefficient, bloated, and some features either don't work or break the game (chargeable weapons, lethal headshots and the stealth/AI changes).

    Although it may seem counterproductive to install a bunch of small mods to replace one big mod, these alternatives are all more functional and performance friendly:

    Core Module

    Cyberware Module

    Rebalance Module

    Equipment Module

  • Unlimited Companions - Unlimited Companions re-compiles every script in the game and will break many mods. Use JIP Companions Command and Control if you want unlimited companions at the same time or other companion-related features like equipment managing, infinite ammo, combat-ready companions and much more.

    Before installing any mods that edit companion behavior, you should check if JIP CCC already does it.
  • Populated Casinos - Poorly made mod with many dirty edits, ITMs, and UDRs. It will also severely reduce performance due to the amount of new NPCs. Use Casino Crowds instead.
  • Freeside & Strip Open - Same performance issue as Populated Casinos. Adds many new NPCs and pieces of unpolished restored content that cause many bugs and performance drops and lacks any sort of performance optimization. Use Simple Open Freeside and Simple Open Strip instead.
  • Increased Wasteland Spawns - Causes save bloat due to using the PlaceAtMe function. Use The Living Desert and/or Mojave Wildlife instead.
  • True Wasteland Economy - Incredibly script-heavy, will cause save bloat and deteriorate performance over time. Use Economy Overhaul or Harder Barter Faster Stronger instead.
  • DUST - Contains tons of errors of all kinds. If you do insist on playing it, DUST Tweaks, DUSTed DUST, and DUST -Additional Fixes are a must, optionally alongside DUST Expansion Project.
  • Weapon Mods Expanded/Extended - Needs careful patching, mostly for YUP. Some bugs may remain as the mod is abandoned and very old.
  • More Perks - Made in 2010 without the use of any script extenders, so many of the perks are broken or have poor implementation. Use More Perks Reimagined instead.
  • CAGE - Continue After Games Ending - Broken, use Functional Post Game Ending instead.
  • NV Interiors Project - Replaced by NV Interiors Remastered.
  • Classic Fallout Weapons - Countless broken meshes and leveled lists that will cause crashes. Use Classic Fallout Weapons Remastered instead.
  • Honest Hearts Reborn - Re-compiles every script in the game and still has many bugs after cleaning.
  • Killable children mods - Might break quests.
  • Weapons of the Wasteland - Causes crashes.
  • Leave Conversation - Force closes dialogues, breaking scripts and possibly locking you out of dialogue choices.
  • Monster Mod (MoMod) - Has broken meshes that cause crashing and broken levelled lists.
  • Enhanced NPC Awareness - Causes random NPCs and companions after firing to become hostile to the player, among other issues.
  • The Storyteller Companion - Contains dirty edits.

Miscellaneous

  • Sinitar's Modlists - This document goes into detail on why Sintar's lists should be avoided.
  • Game Settings Tuner - GST - Bad scripting that causes save bloat and corruption. Use Stewie Tweaks' GMST override feature instead.
  • DSOAL - Can break audio or make it lag.

Tools to Avoid

UI element - Chevron
  • Nexus Mod Manager and Mod Organizer 1 - No reason to use them over Mod Organizer 2.
  • LOOT - LOOT doesn't really have any idea about your mods and their inner structure - it just orders them based on tags in a masterlist managed by volunteers, meaning that it's impossible to account for every single mod and combination of them.
    The main issue regarding LOOT in most Bethesda games is that its masterlists are often outdated or incomplete, leading to broken load orders that will cause mods to misbehave. Oblivion is an exception where LOOT tends to work more reliably.
  • Crash log readers - Crash logs require a plethora of knowledge to read, and in a lot of cases, the ability to confirm findings by reverse engineering the game's code. Automated solutions work through assumptions and by turning this further into a game of guessing. If the crash log contains enough named information (not always the case), a tool of this kind can turn useful as a way to narrow down possible causes, but at that point it just becomes a way to sort lines by frequency.

    As large language models (AI) become more common, it might be tempting to use one to demystify a crash. In practice, though, their scarce knowledge of modding and engine-specific behavior often leads to incorrect conclusions, making them a big source of misinformation.

    What then? Well, ideally, you never want to end up dealing with a crash log that offers no clear direction to begin with. The best prevention is to vet the mods you install and stay informed about any known issues. But if you do find yourself needing to interpret a crash, take the time to understand the game systems it references; that alone can often give an idea of the type of mod responsible.

    If all else fails, many modding communities include people experienced in reverse engineering and, by extension, skilled at reading crash logs. Reaching out to them is often the most reliable way to get an accurate diagnosis. Keep in mind that crash logs are a tool; they merely take a snapshot of what happened during the crash, not why. Keep expectations in check, as in some cases they might not help to find a solution.
  • Bashed Patches - These patches have their use cases and in skilled hands can save a tremendous amount of time. It's not that they should be completely avoided period.
    However, as it is often the case, automation without careful supervision can lead to errors. For this reason, it's only recommended to use them if you are both capable and willing to comb over the resulting patch.
    LOOT and Bash tags are unused by majority of the SSE modding community, leading to complete breakage of the automated behavior of these mods.
  • Mator Smash - Outdated and produces broken patches. The only viable method of automated patching (keeping in mind what was said above) available is through a properly utilized Bashed Patch thanks to its sophisticated tagging system, which allows the user to customize how the generated patch handles individual records.
  • zEdit/zClean - Neither have any real advantages over SSEEdit and lack some essential features due to their outdated codebase. Support for zEdit/zClean is also limited.
  • Merge Plugins Standalone/zMerge - Automated merging can potentially cause major breakage in mods, especially complex ones that require careful handling of their internal references.
  • Ordenador/DDSopt - Breaks textures by needlessly converting/adding/resizing alpha channels, cubemaps and mipmaps. Use BSArch Pro or CAO instead.

Recommendations

UI element - Chevron