Skyrim Special Edition

Legacy of the Dragonborn Full Guide
This document is the 'end-all be-all' of Legacy information.  Everything you need to know about mod installation, support, troubleshooting or otherwise is contained within this single doc. All relevant outside information is linked directly in this document for ease of access. All other resources of information found on the Legacy Nexus page or the Discord community will reference this document. You are REQUIRED to read (not skim) through this document prior to seeking any help on the comment page or on the Discord support channels. If the answer to any inquiry is found within this doc or the linked articles, you will be told to read this manual which will be linked EVERYWHERE.

Important Note for Xbox Users
All support is provided by Rhaella, the xbox version coordinator on the Icecreamassassin Mods Discord, Xbox support channel ONLY, and no support will be given here on the Nexus page.  Bring any questions to that support channel.

Important Resources
FAQ : Find answers to commonly asked questions here first.
Wiki : Community run resource for all in game information about Legacy.
Skyrim Classic Version : Skyrim LE version (support limited).
Mod Blog : Icecreamassassin's modding article blog with updates, insights, guides and more.
Patreon : Support Icecreamassassin and the senior developer team.
Discord : General community and support discord for Icecreamassassin's mods (review rules channel first).
Patch Central : Official patch page curated by SirJesto. All support issues for patches should be referred here. There is also a complete list of patches available for further information.
Creation Club Patches : CC patches curated by Jelidity. No official support is offered for CC patches. Direct all questions to the CC patches Nexus comment page. You must download these if you use any CC content.
WryeBash - core modding tool, used to create the bashed patch.
SSEdit - core modding tool, used for conflict resolution.
LOOT - core modding tool, used to sort load orders.
More Informative Console - tool used in conjunction with the console to gather information on things in the game. - website used to allow users to share load order lists. Useful for troubleshooting.


  • Download the mod (manually is REQUIRED, downloading massive mods from inside your mod management program can damage the ZIP or BSA).
  • Download the Patch FOMOD installer from Legacy Patch Central and read the patches FAQ.  You may also wish to read review the Patch List for more details.
  • Download.  If you use any Creation Club content (including those 4 CC packages included for free in the Skyrim SE 1.6 upgrade), you need to download the Creation Club Patches FOMOD installer as well.
  • Download.  If you use The Curator's Companion (TCC), you will need to download that FOMOD installer as well.
  • Install Legacy’s core package using your mod management program, like MO2 or Vortex.  Do NOT unzip the archive to install it; either drag it into the manager or use the File menu option "Install From File" and navigate to where you downloaded the zip file.  (NMM, WyreBash, or manual installs are neither supported nor recommended).
  • Install ALL your other mods (exception: TCC, which comes in a few steps) and make sure they are activated in your load order BEFORE running the official Legacy FOMOD patch pack.  This includes any mods that (erroneously) say to install after starting a game.
  • Install the Legacy Patch FOMOD through your mod manager, it will auto detect almost all activated supported mods (see the patches docs for more information) and recommend patches to install.  Note: Patches are to get individual mods to work with Legacy and they do not address any potential issues with one another. You may still need other patches provided by other mod pages to resolve issues between those mods.  You may also need to resolve conflicts between various Legacy patches, depending on the content you install.  Always double-check your patches after installation to make sure they are present and activated!
  • Install. If you are using any CC content, run the Legacy-CC FOMOD installer.  Make sure to run it after installing and activating Legacy patches. After installation double-check the installed patches and activate any that aren't.
  • Install.  If you are using TCC, run it after all the other pieces are installed and activated.  After installation double-check the installed patches and activate any that aren't.
  • DO NOT use any Legacy patch provided from another mod page unless it was built after 12/16/19 and there is no official Legacy patch for it.
  • Create any leveled list (bash) patch and/or custom conflict resolution patch you may need (technically optional, but pretty much essential on most load orders).
  • Start a NEW GAME using the NEW GAME button (not an "early post character creation save"). Your game MUST be new with your new load order; no previous save games.
  • Should you wish to add or remove mods from your load order, do new conflict resolution and start another NEW GAME.  Otherwise, save such changes for the next game!

Additional information

BSA Extraction

Extraction of the BSA is only supported under MO2 and Vortex installations since they utilize a virtual folder structure. Loose files overwrite BSA's and the likelihood of file version issues later down the road are inevitable if files are not easily accessible and removable. It will require greater care on your part to manage conflicts on a file by file basis if you extract the BSA, so just be warned that support may be limited if you choose to extract BSAs.

Collections and Guides
The Legacy team does not support load orders based on collections and/or guides.  If you are using one and are looking for support, please contact the maker of your collection/guide for more assistance, rather then the Legacy team.

Patch Merging
Legacy's official patches are provided as ESL flagged ESP plugins and they do not take up space in your load order. We do not support any user who has merged the ESL patches. If you choose to make a merged pack for patches or any other mods in your load order DO NOT under any circumstances upgrade any of those mods and rebuild your merges, this will break your save in progress which is the main reason we do not support this practice. Merging general mods that are NOT patched or support Legacy of course can be done at your own discretion and may be necessary with extensive load orders.

New game VS Game in progress
While it is possible to install Legacy to a game in progress, there are too many variables that cannot be modified if a plugin is added after a game has already begun. Plus adding a mod mid game will shift the load order of all plugins that load after it which will cause instability issues. It is always advised to establish a load order, resolve conflicts, test and THEN start a new game and never touch the load order again until you are ready to review your setup and start over again on a new game.  As touched on in the Support Guide section below, we cannot support games where Legacy is installed on a game that was already in progress.

There is also a widespread misconception that making a save right after character creation is a "clean save" (it isn't) and is the same thing as a new game. It is not. As soon as you hit the NEW GAME button, the game starts building data that cannot be updated in your save. If any mod is added after which alters any of those values, they will not be able to do so after having started the game. How far you go in the game and where you have been doesn't matter. New game = baked game; make sure you are finished working on your load order before starting a game and then do not touch it again.


V5 has the following versioning convention: (Generational version).(Major patch).(Minor Patch) ex: 5.1.6

All updates for Legacy of the Dragonborn V5 will be provided as complete core packages and we will not be providing any updates in the form of patches on the official page. Some optional add-ons and 3rd party fix patches may be available on their own page but for ease of installation and preventing any mistakes and confusion with upgrading, we are only providing full package updates. So remove completely your existing version of Legacy and install the version you are updating to (one step regardless of how many versions might lie in between), then follow any instructions below.  We realize this can be difficult for people with slow, poor, or metered internet service, but repeated occurrences of people failing to follow upgrade directions properly has resulted in this measure and we will not entertain any appeal to host torrents, or incremental update patches of any kind. We appreciate your understanding.

Generational Versions: These CANNOT be upgraded to from previous generations of the mod. These updates REQUIRE a new game and have security measures to prevent users from trying to update a save in progress since upgrading to these new versions will break saves. (ex: V4.16 to V5.0.24)

Major Patches: These versions may require some script cleaning (see below) or special console commands after updating a game in progress from another major version. Download the new version and replace the old one, then follow any instructions in the changelogs. (ex: Upgrading from 5.1.2 to 5.2)

Minor Patches: You can update to these minor version changes within the same major version number without any special actions in most cases. Just download and install (ex: upgrading from 5.1.4 to 5.1.7). Review the changelogs for any special instructions (rare cases).

Note:  In all instances, please review the changelogs of ALL versions that have been released after your current version up to and including the new version you are updating to. You should follow any instructions for EACH changelog in ascending order to ensure a proper upgrade, as all updates to the mod are cumulative.  As you are working through the ascending order, if a given version has no instructions listed, it means there are no further actions required for that version.

If you are starting a new game after an update, obviously all update instructions can be ignored since you're starting fresh.

Cleaning Scripts
Some updates (when instructed in the changelog) will require the use of Fallrim Tools (ReSaver). Simply follow the steps below. Usually the instructions in the changelogs will just involve cleaning a specific instance or a specific script from your save game and this will help you do so:

IMPORTANT: Script cleaning on a broad scale will almost certainly destroy your save game if not immediately, then certainly in the long run. Even cleaning specific scripts as we sometimes indicate as being required for upgrading, have the potential to alter or damage unrelated records in your save file. It has been anecdotally indicated that even cleaning a single script may cause some kind of alteration or damage to unforeseen properties elsewhere in your save file which cannot be predicted, traced, or corrected easily. For best practices and long term stability of your save game it is always advised that you maintain your load order AS IS during your playthrough and only update when you intend to start a new game. If you choose to upgrade mid game and follow our cleaning recommendations, you do so at your own risk. We will offer support, but may not be able to offer solutions in every case, as the effects of cleaning are somewhat unpredictable on unrelated elements.

  • Run ReSaver.exe
  • Open your save game
  • Click "clear filters" button
  • Enter the name of the script or the form ID for the script instance needing to be cleaned into the top left box. (Instances will be labeled as XX893A85 for example where XX is the load index of Legacy. When in doubt open the console in game and click on the museum building to see it's reference ID, the first two numbers will be what you enter in place of XX).
  • If cleaning an instance, open the "Script Instances", find the entry that matches the search, click it and press DELETE on your keyboard.
  • If cleaning a base script (ex: DBM_DisplayScript) open the "Scripts" tree, find the listed entry that matches the search, click it and press DELETE on your keyboard.
  • Note that if your instruction is to clean a script or script instance that is not present in your save game, it means you have not triggered the conditions that would populate that entry in your save - you can safely ignore that particular item.
  • Save the changes and exit.
  • When you launch the game, do NOT select 'Continue' from the main menu, since this will load the old save and not the one you just edited.  Select 'Load' and pick the save you just created.

Keep in mind that if you clean the base script it will clean EVERY instance of that script from your save, so if you are asked to only clean a specific instance, be careful not to clean the "SCRIPTS" entry rather than a "SCRIPT INSTANCE", this avoids needless script cleaning which could lead to instability.

Simply uninstall using your mod program and/or delete the Legacy ESM and BSA files as well as the LegacyCredits.bik file from the Data/Video folder. DO NOT uninstall and continue your existing save. Your save will break. This is modding rule #1. 

Support Guide
Support given by the Legacy team will be limited so that we can focus on development. We ask that the community work together to solve their issues using this guide and the linked resources at the start of this guide as tools. We will try and help when able and address new concerns, but for our own sanity and maximization of our time, we ask that you help one another as much as possible.

We offer support on the Legacy of the Dragonborn Nexus page comments section and via our Discord server. We provide channels on the Discord for Legacy LE and Legacy SE as well as a general community operated general modding help channel. If your issues relate to another mod or modding tool, please limit your posts to the general support channel or visit the mod page or discord for the other mods/tools (some links provided below).

Support has a few simple requirements:
  • Be polite. Believe me, I know it gets frustrating when things don't work, but remember that hundreds of thousands of people have played this mod with relatively few issues, so most problems are either user error or conflict issues and we're MUCH more willing to help people who are sincere. Coming off as entitled or accusatory is a fast pass to the exit.
  • Thoroughly read through this Legacy Full Guide (which should happen before you even download and install the mod) and freshly review the FAQ to ensure your question is not already addressed before posting/commenting. (Skimming through the comment forum on Nexus or searching for terms related to your issue is also recommended but not required.)
  • All your mod content is hosted on Nexus.  We do not offer support for mods (or versions of mods) hosted on other sites.
  • You started a new game after installing Legacy.
  • All supported mods in your load order were all installed and activated then patched (and activated) prior to starting your game (this includes Helgen Reborn).
  • You have NOT added or removed any mods, or resorted your load order, during play.
  • You have not used console commands other than for troubleshooting issues and then have reverted to a previous save or have only used them when advised by the dev team.
  • Check the stickies on the Legacy Nexus comment page. Notable issues posted here and links to the FAQ are your first line of support before asking for help.
  • We do not offer support for versions of Legacy prior to V5. Feel free to post in the proper ICA Discord channel (Legacy-LE-Support) asking help from the community, but the developers will offer no support for Legacy LE since the SSE version has been out for over 6 years at the time of this editing.
  • We DO NOT offer support for any load order that contains LoversLab/Sexlab content due to the proprietary nature of their setups which are very system intensive and cause more variables of conflict than we are willing to look into.
  • BE AWARE: If your question is addressed in the FAQ or the mod page sticky the dev team will not respond to your question. Only if it's obvious that you have seen these and tried the fixes and are still having issues will we chime in and try to help. No longer will we hold hands and point out the trees in the forest.

Other elements to consider before asking for support:

If your issue pertains to another mod working with Legacy, have you read the Patch/CC patch page descriptions completely, as well as any stickies or articles that may be relevant?
Many common questions can be answered right on those pages. It saves the team typing the same thing over and over.

Can you reproduce the issue with just Legacy (and if patch related, the mod involved and its patch) installed?
9 times out of 10, issues are caused by mods unrelated to Legacy or it's associated mods and patches. Unfortunately we can't fix everything, or your entire load order.

Are you on PC?
Legacy is ONLY supported on PC. If you're using a console, switch, Steam Deck, etc... Please don't ask us for help. We don't offer a version for anything but a Windows PC and can't help you troubleshoot those other platforms. Any oddness with the mod on these systems will not be looked at for this reason. There is a third party Xbox port, and there is a dedicated channel on our Discord server provided as a convenience, but all support will be handled by the port author.

Are you on VR?
None of the team have or use it, and as such do not support it.

Have you sorted your Load Order with LOOT (or mindfully by hand)?
Many issues can be resolved by a load order change. (remember that any shift in load order during play may require a new game since changing your load order during play can cause issues.)

Have you generated a bashed or smashed patch, or otherwise performed conflict resolution on your load order?
Unfortunately Skyrim is not the type of game you can just "plug and play" mods with. Conflict resolution with SSEdit or a similar tool will be absolutely required. If you generate bashed/smashed patches we strongly suggest checking to make sure the resolution is correct to your satisfaction and not just trusting the automation.

Are you using a modpack or guide?
Please direct all questions to the modpack or guide's author. This includes Lexy.

Discord Support:
The best way to get faster help is on the ICA discord (link above), in the appropriate support channel. When you've gone through all the steps above please:

  • Use the Discord search function. It's very possible someone has had this issue before (or maybe several people even!). Take a quick gander through some keyword searches and see if we've already answered your question/resolved your issue.
  • Take a few minutes to think about how you write up your issue so it's easy for someone without the context of your entire game to understand. If you've read these guidelines, it would really help to indicate that you've done so at the start so we can save a lot of pointless questions you've already looked at.
  • If the issue is visual, have one or two screenshots handy.
  • If the issue is with a specific item try installing More Informative Console and getting the Base ID of the item. This will also let you check out which plugin last modified that item and may be helpful for tracking down conflicts.
  • Be patient. The team provides help in their free time, for free. We're not always around. Feel free to state your question again if you feel like it was missed, but try to remember we're doing the best we can here. Out of courtesy, please do not ping or DM anyone with a color-tagged role about support issues unless they have asked you to do so.
  • Follow instructions. It's really frustrating when we ask for specific information and can't get it. Take a deep breath, read documentation twice and ask questions if you're not sure. Better to be safe than sorry.

Nexus Comment Page Support:
Posting in the comments of the Nexus page will usually get a response within a day or two. The same basic guidelines above apply when communicating your issue and troubleshooting it ahead of time. 
  • If your post has not been answered within a day or two, make sure you are looking back up to 3 pages on the comments since they can get buried on a busy day to make sure you didn't just miss the response or we didn't miss seeing it initially.
  • Look for your original comment on the Posts tab and reply there.  Do not make another post to re-state the issue if you have not gotten an answer the first time around.
  • Please do not contact the author for support questions unless asked to in the comments by the author or another support person.

Bug Reports:

We have purposefully disabled bug reporting on the Nexus mod page because the vast majority of issues are caused by mod conflicts or user error. All bug reports should be made as a support request and if the issue is determined to be a bug we need to look into, we'll log it into our GitLab issue tracker and note in the upcoming version changelog any fixes that are applied.

Any typo, spelling, punctuation or grammatical error reports should be made to TheNoobyDuelist on Nexus or posted to his typo patch page for Legacy.  Note: any requests to change the actual syntax will likely not be honored, since that would involve a great deal more work and would not be practical.

General Troubleshooting Guide:

This portion of the guide is primarily for informational purposes and education and not necessarily required (though suggested) to get the most out of technical support. We may ask you to do these things anyways, so it's better if you do them beforehand and potentially solve your problem, or have the resulting data to share with us when you do seek assistance.

When you experience problems with your game, the first thing to do is to thoroughly review the description page, this Full Guide, the FAQ page and any updates in the comment section main sticky. You can also use the Nexus forum search to try and find answers from previous posts.  Many times, your issue will have been discussed and solutions provided.  If you still haven't found an answer, the following process can help you narrow down the issue and produce more meaningful data.  It will not work for every kind of issue, but it is a good sequence to undertake for many common problems, which in turn will help the support staff if you are still stumped. 
A few reminders before we begin:
  • Console usage here is for testing purposes only.  Please do not use the console on your regular game unless directed to by a Dev.
  • The Legacy Dev team does not support manual installations or any version of NMM, so these steps are geared for Mod Organizer 2 or Vortex.
  • Quit the game and restart to see if the issue is resolved.  If it is not, try rebooting the computer. 
  • Try stepping back several saves to see if the problem still exists.  If it goes away, you may wish to revert to this earlier save.
  • All isolation testing is intended to be done on a new test profile, which should be a clone of the profile you have been playing under.  That way you can leave your load order and installed mods intact for your regular game.
  • Do NOT simply uninstall/install mods during testing as this will break your regular game. Just deactivate/activate them (the whole mod, not just the plugin) on the test profile.
  • Always use an alternate start mod, both in play and testing.  This will allow the script-heavy part of creating a new save to settle down.  The most common one, and most recommended, is "Alternate Start - Live Another Life".  This will be referred to as LAL going forward.
  • Any time you discover during your testing that you will need to update/add/remove/reorder mods (including patches) during a game, you will need to start a new game – from the New button.  The exception to this is the Legacy mod and patches updates for minor revisions (unless told otherwise).
  • For test on the test profile, do NOT have a save in-game that you use each time, ALWAYS start a new game.  There is no such thing as a clean save!
  • It’s assumed when you ran LOOT that you paid attention to any warnings and resolved them as need be.  If you do run it again to see the messages, do so on the test profile.
  • It is also assumed and expected that you have at least run SSEEdit (xEdit) with the quickautoclean parameter on your mods, one at time, to clean them while you were building your load order.
  • ALWAYS use a smashed/bashed patch unless you are very experienced at patching your own conflicts and leveled lists.
  • SKSE may not be required, but there is no good reason for not using it, so the assumption is that you are using it.  Make sure the version, and the version of the address library, match the SkyrimSE.exe version you are running.
  • For purposes of brevity, DynDOLOD will refer to DynDOLOD and/or SSELODGen.  Similarly bashed patch will refer to smashed and/or bashed patches.  If you don't use LOD generation, just ignore where it's mentioned.
  • Official DLCs is shorthand for the official expansions: Dawnguard, Dragonborn, and Hearthfires.  Update will be considered part of this group but not the creation club content.
  • If directed to re-download the game, do not forget to reinstall any ENBs, Creation Kit and ini files (if you use the CK), and SKSE.  Note: it is a very bad idea to install Steam and any of it's games in C:\Program Files (x86), due to Windows UAC.  If this applies to you, and if you do have to re-download the game, consider uninstalling Steam and reinstalling to a different location (preferably a different drive) before re-downloading the game.  Since any other Steam games you have would also have to be reinstalled, use discretion.
  • If directed to start a new (non-test) game, take the time to do the things you would do before any new play-through: check for updates, remove mods (and their patches) you no longer desire, add mods (and their patches) you had flagged for the next game, generate your bashed patch, check for errors in xEdit and do conflict resolution, etc.

Sequence to test (broader to more granular):
Note: it is assumed that restarting the game and/or rebooting the computer has already been done and the error persists.

1. Make sure your Legacy main mod and patches are up-to-date.  If not, read the changelogs, update and test on your active save.
  • If you are no longer having the problem, and did not add any new patches (only updated existing ones), you are done and can return to your game.  Note: if you added new patches, you may have to start a new game, use discretion.
  • If you are up-to-date and still having the issue, continue on. 

2. On the test profile (full load order), start a brand new game.  You may use the console to navigate to where you experienced the issue.
  • If you cannot reproduce the problem, the issue is with your save and you will most likely need to start over, since your save is already experiencing corruption.
  • If the problem persists, continue on.
3. If your issue cannot be pinpointed to Legacy specifically, create a Minimal Test Bed.  Load only SkyrimSE, the Official DLCs, USSEP, SKSE, SkyUI, and LAL and launch a new game.  You may use the console to navigate to where you experienced the issue.
  • If there are still problems with this minimal load order, make sure SKSE is installed correctly, that the game and SKSE version are in synch, and that the USSEP, SkyUI, and LAL files are not corrupt (re-download).  If this doesn't help, you may need to delete the game folder and chose verify on Steam to have it cleanly install.  Don’t forget to reinstall SKSE.  If that was the problem but now it’s fixed, retest with your full load order on first your test profile, then your regular profile.  If the problem does not occur on a new game but does on your save game, then the issues you fixed are unfortunately baked into your save game.  You are done but you will need to start a new game.  If the problem does not occur on either profile, you are finished and can return to your game.  If the problem still happens with your full order, switch back to your test profile and continue on.
  • If no issues occurred on this minimal load order at all, re-enable all your mods on the test profile and continue on.
4. If your issue deals with CTDs (seemingly random or reproducible), open your whole load order in xEdit, select all the plugins, right-click and run the script “Apply Filter to Show Deleted Navmeshes”.  Take note of any mods reported and deactivate them, and any associated patches, on the test profile.  Check the mod(s) pages for any comments about the issue(s). Start a new game and see if you can reproduce the issue. Since this is a test only, you may use the console to move around to the location where the problem occurred. After testing, you can either fix the mod(s) if you have the skill, or you can delete them (and any patches). 
  • If the problem goes away, move back to your playing profile, resolve the issues, and start a new game.  You are done.
  • If the problem persists, re-enable all the mods in your test profile (including any flagged earlier) and continue on.  Note: if there winds up being a reason to start over from further troubleshooting, take the time to resolve any mods/patches identified as having deleted navmeshes at that time.
5. If your issue deals with a particular asset in the game, such as a texture or item, it is highly recommended that you use More Informative Console to help figure out which mod it is coming from (due to MIC's nature, it is relatively safe to install mid-game; just don't re-sort your load order).  Deselect the offending mod(s), and test to see if your issue has gone away.  For items, you may also use the console command help “item name” to identify if there is more than one version of the item.  If there are multiple versions, check to see if any v5 patches exist or if not you may need to make one for yourself.  You may also try changing the sequence of where the offending mod(s) loads in relation to the mod(s) in conflict.  Test to determine if your fixes have resolved the issue.
  • If this was your issue, since you will have altered your load order by moving/removing/patching a mod, start a new game.  You are done.
  • If this is not your issue, continue on.
6. Create a Minimal Test Bed.  Load only SkyrimSE, the Official DLCs, USSEP, SKSE, SkyUI, LAL and Legacy and launch a new game.  You may use the console to navigate to where you experienced the issue. 
  • If your problem is still happening, download Legacy again (large downloads like Legacy can occasionally corrupt).  Retest to see if the problem is gone.  If the problem is not gone, and if you did not follow step 3, delete the Skyrim Special Edition game folder and chose verify on Steam to have it cleanly install.  Don’t forget to reinstall SKSE.  Test again.  If the problem persists, post in the comments with as many details about the steps you took and the issue as you can. 
  • If there is no problem, continue on.
7. Load SkyrimSE, the Official DLCs, USSEP, SKSE, SkyUI, LAL, Legacy, and all your mods except DynDOLOD and the bashed patch.  You may use the console to navigate to where you experienced the issue.
  • If the problem is gone, skip to Step 10.
  • If the issue is still happening, continue on.
8. Load SkyrimSE, the Official DLCs, USSEP, SKSE, SkyUI, LAL, Legacy, and half the mods in your load order and launch a new game.  Generally make the first half you will test base mods themselves, only include patches if the mods they patch are included.  Do NOT enable DynDOLOD or the bashed patch during any of step 8 testing.  You may use the console to navigate to where you experienced the issue.
  • If your problem doesn’t happen, switch to the other half – being mindful you may need to activate some of the mods from the first half to work with patches in the second half – and test again.
  • If the problem does happen, use the 'divide and conquer' technique by halving down until you have identified the culprit(s), each time starting a new game.  In case its simple file corruption try re-downloading the mod(s), choosing replace, for the existing mod(s), and test again to see if the problem is gone.  Since you are using the test profile, you may sort with LOOT.  If the problem persists, you may have file corruption in those downloads, or leftover/conflicting files in your game folder.  First, try re-downloading again to see if it resolves the issue.  If you still have the problem, delete the game directory and use Steam’s function Verify to re-download the game.  Remember to reinstall SKSE.  Make sure to test the problem mod(s) with both Legacy active and not active.
    • If it only happens with Legacy active, post the abbreviated list of mods you narrowed down to the conflict in spoiler tags or a modwatch link, with any extra details, in the Legacy posts section.
    • If the problem happens with Legacy not active, then there is a problem with the mod(s) which you will need to fix or delete. Then retest.
    • If the problem is gone, continue on.

9. Re-enable all your mods except DynDOLOD and the bashed patch, and sort with LOOT (don’t worry; it will affect your test profile only).  Retest.  You may use the console to navigate to where you experienced the issue. 
  • If the problem is not gone, you will need to repeat step 8 again (using different testing batches, or going one-by-one, to try and catch any interactions you may have missed before) to look for other conflicts. 
  • If the problem is gone, continue on.
10. Enable the bashed patch and test again.  You may use the console to navigate to where you experienced the issue.
  • If you have made no changes to anything in your load order from the preceding steps to this point, and the problem doesn't happen, skip to step 11.
  • If the problem does happen, or you made changes from the preceding steps, sort with LOOT, rebuild the bashed patch and test again.  If the problem persists after re-making the bashed patch, open xEdit (SSEEdit) with your whole load order and check the bashed patch for errors (note: you may have to edit the bashed patch or make your own conflict resolution patch to load after the bashed patch at this point).  Retest.  If the problem is gone, continue on.
11. Regenerate LOD(s) and test again.  Make sure your version of DynDOLOD is 2.76 or higher.  You may use the console to navigate to where you experienced the issue.
  • If the problem is not gone, re-download the latest version of DynDOLOD (and/or SSELODGen if you use it) and make sure it is installed correctly.  Regenerate LOD(s) and retest.
  • If the problem is gone, you are ready to start a new game.  You should have a more stable load order.

Reference Appendix 

The following information is for testing purposes ONLY and should never be used to advance your game progress or manipulate things with console. It is here for perspective, troubleshooting purpose and should only be applied with the help of the development staff. Any use of this information in your save game is at your own risk and we highly recommend making backup saves before utilizing any of this content for testing purposes.

Story Manager controlled quests:The following quests start via Story Manager as long as the conditions are met.
Much Ado About Snow Elves (DBM_MuchAdoAboutSnowElves)
  • Quest not completed - DBM_MuchAdoAboutSnowElves
  • Quest completed - dunNchuandZelQst (Lost Expedition)

Night at the Museum (DBM_HauntedMuseumQuest)
  • Global Value HauntBlock = 0 (Set in MCM)
  • Global Value DBM_DisplayMax >= 300 (Display Count)
  • Player is not in interior
  • Player has not moved into Location "Museum Exterior"
  • Player has not moved into a Location that you can teleport to with the Curator's Guide
  • Quest not completed DBM_HauntedMuseumQuest
  • DBM_ExplorerGuildHouse (A Room with a View) is not at stage 15 or 20
  • DBM_MuseumHeist is not currently running or is completed

Shadows of One's Past (DBM_MuseumHeist)
  • Global Value DBM_DisplayMax >= 400 (Display Count)
  • Player is not in interior
  • Player has not moved into Location "Museum Exterior"
  • Player has not moved into a Location that you can teleport to with the Curator's Guide
  • Quest not completed DBM_MuseumHeist
  • DBM_ExplorerGuildHouse (A Room with a View) is not at stage 15 or 20
  • DBM_HauntedMuseum is not currently running or is completed

Airship Handler (Hidden quest - controls airship travel) DBM_AirshipQuest
  • Quest completed - DBM_ExplorerGuildHouse (A Room with a View)
  • Quest completed - DBM_MuseumIndarysQuest (The Staff of Indarys)
  • DBM_AirshipQuest is not currently running
  • Player is in the Tamriel worldspace (main Skyrim world)

The Visage (DBM_Excavation03Prelude) - Spawns the snow elf ghost at the fort
  • Quest completed - DBM_MuchAdoAboutSnowElves
  • Quest completed - DBM_Excavation02
  • DBM_Excavation02Cleanup is not running
  • Player is in a village or city

Safehouse Key delivery - Hidden quest, delivers the safehouse key via courier (DBM_SafehouseKeyDelivery)
  • Global Safehouse access = 0
  • Global Value DBM_DisplayCount >= 50 (Display Count)
  • Quest not running DBM_RelicHunterQST (Solitude docks start)
  • Player has not moved into a Location that you can teleport to with the Curator's Guide
  • Player is not in Solitude
  • Player is not indoors

Article information

Added on

Edited on

Written by