Aoikani Posted December 26, 2017 Share Posted December 26, 2017 (edited) How many of you have discovered your game won't start and you can't figure out what mod is preventing your startup? You might say it was fine yesterday! Then you find out there was an update. Well there's nothing you can do but update your Script Extender if it's available and update the mods that use SE. However, discovering which mod can be problematic as well. You can simplify this for yourself by noting which mods you have downloaded that use SE. I bet most players don't keep track of that though, yes?I see topics time to time with players asking for help with that problem. So I thought I might just add a small piece of advice on how they can help themselves. There is a way you can keep track with little effort without writing down, trying to remember the mods you have to find that is preventing you from playing. This is my way of doing it, since I do use NMM, I create a category folder named... "Scripted Mods". By doing this you can now narrow your search for scripted mods that haven't been updated yet within that folder. If you use MO or just prefer manual DLs and placing your mods in the appropriate directories yourself, then at least Rename your archive and add a "Scripted-" prefix to it or while using MO rename the folders with a "SE" prefix. (you MO users should know what that means) All in all, this will help your search for the mod that is preventing your game play (that was scripted) so that you can check on updates. Simple. Edited December 26, 2017 by Aoikani Link to comment Share on other sites More sharing options...
Recommended Posts