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 SSEEdit 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

  • DXVK - On Windows, DXVK can often bring a massive improvement to older games. Most notably the ones that use a very old graphics API such as D3D9, which has a large CPU performance overhead. But in the case of more modern games such as Skyrim Special Edition, which utilizes D3D11, this is no longer the case, while possibly introducing bugs from the translation and limited compatibility.
  • Unofficial Skyrim Modder's Patch - USMP SE - Contains many changes that are out of scope, making it hard to track down random features/changes in your game.
  • Skyrim Landscape and Water Fixes - Landscape edits are not simple to do conflict resolution for, and SLaWF has a history of intentionally making its conflict profile more annoying.
  • Grass FPS Booster - Includes out of scope changes and does not improve performance at all, as tested here. Grass performance depends on the grass mod used and the density setting; results for this are also on the benchmarks page.
  • eFPS - Often adds way too many occlusion planes, which can cause performance issues due to the higher CPU load from occlusion checks. This higher load would be fine only if the amount of draws lowered was significant, which it is not in the vast majority of cases. The mod also needs extensive patching with location overhauls, which most of the time have proper occlusion built in.
  • Skyrim Crash Guard - Fundamentally flawed idea in the same way as NVAC. In short, it will lead to more problems down the line by letting the game run in an unsafe state.

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.
  • ELFX and ELFX Shadows - Both are unsupported and far less patches are available for them compared to Lux.
  • HDT-SMP - Completely replaced and superseded Faster HDT-SMP.

Miscellaneous

  • Sinitar's Modlists - This document goes into detail on why Sintar's lists should be avoided.
  • Achievements Mods Enabler - Achievements are already enabled by Engine Fixes.
  • Skyrim's Environmental Audio Enhancer:
    • It may negative affect the game's audio dynamic range and compatibility with other audio mods.
    • Skyrim does not support true 5.1 or 7.1 surround sound. Proper multi-channel surround mixing is not present, which would require extensive changes to even make possible.
    • Any surround sound effect in Skyrim is simulated rather than genuine, and often just results in louder audio.
    • Skyrim does not support advance audio formats like Dolby Atmos.
  • Binaural 3D Surround Sound for Headphones - HRTF - Will cause crashes.

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.
  • FallrimTools Cleaning - This should be used only for debugging and in very specific situations, such as when dealing with scripting. Using it on active saves is a band-aid fix at best, and a source of future breakage at worst.
  • Ordenador/DDSopt - Breaks textures by needlessly converting/adding/resizing alpha channels, cubemaps and mipmaps. Use BSArch Pro or CAO instead.
  • Fores New Idles (FNIS) and Nemesis - Both have been replaced by Pandora Behaviour Engine Plus, which has more features and is easier to use. It also processes animations much faster and brings a series of fixes.

Recommendations

UI element - Chevron

Animation Mods

Visual Mods

Content Mods

Gameplay Mods

Miscellaneous