DoubleYou

Just load the IHSS esp after the AOS esp if you want the IHSS footsteps.

Isn't this exactly what fomods do?

EFF = Extensible Follower Framework https://skyrim.nexusmods.com/mods/12933

Marry her. Then she will fear going out with all the guys behind your back. Seriously though, did you try dismissing her and then adding her back?

I do not believe that there is a projectile for soul trap in vanilla at all, but I don't play vanilla ;)

You need to have Acquisitive Soul Gems overwriting USKP in your priority order.

I do not blame Arthmoor. He deals with faulty bug reports all the time. Same thing happens to us with Mod Organizer. The thing to remember is that Mod Organizer and the Unofficial Patches are not at odds with each other, and neither break the game when used. Only when used incorrectly do they break the game. Because most users are not smart enough to understand the whole situation for and against BSAs and how they work, issues will inevitably arise. It's easy for us to bicker because we become frustrated with people and with tools. Modding requires harmony. Harmony can only exist when organized by skilled persons. Skilled persons are created though practice. Failure is an inevitable part of practice. It is when we learn from our faults and correct our mistakes that we can build harmony. The common user out there does not want to practice. They simply want to play. They don't want to fix their mistakes. They believe they have the right to make mistakes and blame the tool or the tool's author. Our difficult task is how to make consonance out of this dissonance, and that is only made possible through rock 'n' roll.

The Unofficial Patch false ESM conversion fixes many problems that previously caused havoc. If you used Unofficial Skyrim Patch (USKP) and Dragonborn and did not use Unofficial Dragonborn Patch (UDBP), you would not be able to absorb dragon souls. That was caused by the dragonactor script from the USKP BSA overriding the dragonactor script from the Dragonborn BSA. With the false ESM conversion, we can now load the USKP patch esp before the Dragonborn esp and avoid this problem. This was fixed in the UDBP by having a fixed script in the UDBP BSA loaded after the USKP. Mod Organizer (MO) added a new dynamic when it came to BSA loading. Now BSAs were capable of being independent of esp load order. Dummy esps became unnecessary. Also, if a novice were to begin using MO and install the Unofficial Patches in a priority order different from the esp loadorder, they would encounter the same problem. The dragonactor script from the USKP installed in a higher priority than the UDBP would cause users to not be able to absorb dragon souls. Inevitably, these users, who will even believe that it was the skimpy body replacer they installed that somehow corrupted their dovahkiin, will complain to Arthmoor about the problem. This, unfortunately, once the problem is solved by the user who does some computer sorcery: reinstalls Windows, and, by the way, stopped using Mod Organizer, will cause Arthmoor to blame Mod Organizer. In reality, it was the simple problem of user error. If the user would simply have changed the priority position of USKP to be less then UDBP, allowing UDBP to overwrite USKP like it is supposed to, we never would have had all these problems. Summary: Computers do what they are told to do. Users do not.

There are no spoiler tags on the wiki as far as I know. There should not be a need for spoilers on the wiki, however, if we format it correctly. Generally speaking, we would answer the question quickly in the first sentence, which should be short and to the point. After that, additional info can be added in subsequent sentences. Most people will never read the entire wiki; it's too large. My goal is for people to be able to find what they need to find in a glance and answer it quickly so they can go back to modding Skyrim. If they find the answer in the first sentence, they needn't read the second sentences. If they do need to read the subsequent sentences, I put big warning signs and notices up to catch their attention.

Did you try editing the plugins.txt when you edited the loadorder.txt? I might have to recreate your situation to figure out a workaround. My suggestion: Edit plugins.txt and loadorder.txt and then recreate the situation where you have to boot into Linux to even think of trying to modify them.

Locking the load order, unfortunately, doesn't work near as well as using BOSS in conjunction with BUM to manage custom load order placements (I have a 9.83 KB userlist myself). This is mostly evidently when using a SkyProc Patcher, as it will generally resort your load order using BOSS, and the locked thing is unrecognized by them, and has caused the patcher to throw a fit for me many times. Of course, this can easily be avoided by turning automatic BOSS sorting in conjunction with SUM during patching.

Last I checked, some of the tutorials did contain outdated information.

We would have to create an actual installer/uninstaller for Mod Organizer to add Start Menu buttons. This is not really too hard to do, and I have done it before, but I don't think the route of an actual installer is one that Tannin really wants to travel down, since one principal advantage of MO is its portable platform supporting multiple games on multiple MO installs.

I guess there must be exceptions to this rule? Because I load More Hotkeys Please, a rather intense scripting mod that relies heavily on SKSE and SkyUI MCM menu, at B8 (the 198th plugin) in my load order and it works perfectly.

Ok, that'd be more work, because the peach doesn't go with the grey buttons. I'd have to change the buttons. I probably ought to change the buttons anyway.

It's rather simple. You'll see code like this: whateverElementThisIsAffecting { background-color: #123456; }Just replace the #123456 with any color from here:https://www.w3schools.com/tags/ref_colorpicker.asp Then save, and you'll see that element change color. The gradients are more difficult. You'll see something like this: qThisElementHasGradient { background-color: QLinearGradient(x1:0, y1:0, x2:0, y2:1, stop:0 #919598, stop:0.5 #757676, stop:1 #919598); } All the #919598 type stuff, replace with other colors like above. Fiddle with the numbers to change how the gradient is applied. Or you can remove the gradient and stick with plain colors.

Something without pink...

I decided it was time I change the skin of Mod Organizer, so I created a qss and this is what I got so far. Any suggestions?

I don't think it would harm you to remove the Dawnguard and Hearthfire esps, but you can leave them in for your current playthrough if you so desire, as it won't harm anything.

@MrT3a That sounds more like a problem to pose to the author. You could try loading up your mods in TES5Edit and finding the conflicts if any. Chances are, however, that it isn't this mod that is causing the CTD.

You do realize that the Even Better Quest Objectives installer tries to install a BetterQuestObjectives.esp with the DLC patches merged in wherever possible? If all you have installed is the DLC and Book Covers Skyrim, you will only get the BetterQuestObjectives.esp, because the author has created a merged file with all those fixes together. For my current setup, the only additional esp I use is the one for Extensible Follower Framework, and that is because I have all DLC, Book Covers Skyrim, and EFF. It still works correctly for me. The red warning triangle is telling however. You do realize that the installer only sees mods that you have installed and activated? A red triangle will indicate that you are missing a master file for that particular esp.

So, what exactly was the problem?

Changelog: 1.0.7 -Fixed packaging error with 1.0.6 update 1.0.6 - nmm importer now also transfers category, endorsement state and latest version information - nmm importer should now always determine the correct nexus id - nmm importer will now correctly restore overwritten files for imported mods - plugin (esp/esm) list is now exposed to plugins (read-only functionality right now) - integrated fomod installer now supports file dependencies - tooltip on download list now contains the file name - directories in data-view are now sorted - the choice to run fnis from the checker can now be stored - bugfix: when refreshing the directory tree conflict information wasn't immediately refreshed (including on start) - bugfix: dataChanged events wasn't emitted when user changed the modlist - bugfix: file patterns in checkfnis plugin weren't completely correct - bugfix: integrated fomod installer crashed if the installer had no options

The problem here was that the ini files contain unknown values that Mod Organizer's Configurator plugin simply cannot understand. Deleting the invalid lines will fix the errors. Deleting the //2048... comment from the skyrim.ini will fix the first error message. Deleting the stray iScreenShotIndex will fix the skyrimprefs.ini. Tested this myself, and it now works. Cheers. Or, Kia ora!