DoubleYou

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!

https://en.wikipedia.org/wiki/Kia_ora

Okay, under the Display section of your skyrimprefs.ini you have a stray iScreenShotIndex with no value attached. If you delete this, the error will go away.

I was wondering if anyone else noticed the esp conflict between Smooth Blade Draws and Sheath and USKP. I didn't change it because I wasn't sure what it did. What does it do?

Could you post your skyrimprefs.ini. Both files you have pasted refer to the same skyrim.ini, unless they truly are identical.

Under the Display section, change iShadowMapResolutionPrimary=4096 //2048 for better performanceto iShadowMapResolutionPrimary=4096and see if that doesn't fix the issue.

Could you do the following for me? 1. Click Puzzle icon 2. Select Ini Editor 3. Look for any line that has a value of 4096 in it 4. Report here Or you could copy and paste the contents of you ini files to somewhere like Pastebin so I can examine it.

For what game are you using Mod Organizer?

You shouldn't need to delete NCC. As far as I know, the only thing that Mod Organizer writes to registry is how to handle nxm links, which has nothing to do with NCC.