Greg

I think Gyldenhul Barrow in Solstheim has one room that is loaded with piles of gold coins on the floor. You may also find a pile of coins in a few other places, but I don't remember specifically where these are offhand.

If @DoubleYou and @TechAngel85 agree, I suggest changing the instructions to so that skse_loader.exe creates files in a new SKSE Output mod. If my Fallout 4 profile, it looks as if may be only MCM/Settings/FO4FixesAndTweaksByAurelianis.ini at the time I setup this profile. I think the current method is too confusing and is error-prone since it requires moving e.g. SKSE\Plugins\Fuz Ro D'oh.ini to one mod and SKSE\Plugins\SkyrimUncapper.ini to another mod.

I just setup the skse64_loader.exe executable configuration to create new files in a mod named SKSE Output and setup the SSEEdit.exe executable to create new files in a mod named SSEEdit Output. This way pretty much everything goes into an appropriate output mod without having to fiddle with the files in Overwrite. Technically it's not as clean as @z929669 recommends, but it's easier and serves mostly the same purpose.

It sounds as if you may be missing a mod required by the L&W patch. Look through the plugin list in the right pane to see if any plugins have a red triangle icon. This indicates a missing master and you can hover over the plugin name to see a tip that shows which masters are missing.

When you install and first run Mod Organizer, you are given a choice of modes to use: Portable installed the Mods, Downloads, and Profiles folder directly in the Mod Organizer folder. Although this works, Portable mode is discouraged because it requires installing a new copy of Mod Organizer for every game you play and keeping all of these updated to the latest version is a grand pain. Don't do it. Instanced mode is the most flexible option because you use one and only copy of Mod Organizer to managed all your games and all your profiles within these games. This is the (highly) recommended option. The contention I have with Mod Organizer is that Instanced mode defaults to storing your profiles, mods and downloads folders in C:\Users\[username]\AppData\Local\ModOrganizer and most people (myself including) are using smaller system drives (C:) with larger data/game drives (D: ... Z:). Most people just select Instance mode, select the appropriate game, and click OK without realizing the game data is stored in a hidden folder on the system drive. The alternative is to select Instance mode and somewhere before finalizing the selection you can set the base directory to something more appropriate (say D:\Modding\Instances or whatever). From here on out, the D:\Modding\Instances folder will contain one folder for each of your instances and these folders contain your downloads and mods. I'm assuming this doesn't really help answer your direct question though. The bottom line is that if you had not set base directory to something explicit, all your downloads and mods were on the C: drive and this doesn't help if everything on that drive is gone.

If you used Instance mode without setting custom paths, the mods and downloads were all stored in C:\Users\[username]\AppData\Local\ModOrganizer.

You're right that is not nearly as easy as pressing Backspace or Alt+Left Arrow to go back through history, but I find it's better than nothing. Oops! Sorry, I indeed missed this in the "wall of text."

xEdit Overview 2.8.5 - Navigation Treeview Ctr + 1 through 5 to set a bookmark Alt + 1 through 5 to jump to a bookmark Basically set a bookmark before you Ctrl+Click to jump to the FormId. When you're finished, jump to the bookmark to return where you were. If I understand correctly, the leveled list also has LVLD - Chance None that specifies the chance for getting nothing. LItemMiscVendorArmor has this set to 25 so if I'm not mistaken, each time it attempts to select an item from this list it has 25% chance of selecting nothing.

FAlloutNV is never visible in the left pane so you can ignore it. Just verify the DLCs are ordered correctly in the left pane. You should see FalloutNV.esm in the right pane and LOOT should sort the game and DLC masters correctly.

You have piqued my interest as well and I certainly see why you are so fond of this one. If I can ever find the time to get back into Skyrim, I want to experiment with this one as well.

I recommend hopping over to the xEdit Discord and downloading/installing the latest xEdit 5.1.5c that was just released earlier today. This contains a number of fixes and improvements, such as recognizing Unknown 14 as the Partial Form flag on Quest, Cell, and I think Worldspace records. You can find the xEdit Discord link in the Tome of xEdit.

I think using LOOT groups to categories plugins makes the most sense given plugins are ordered into these groups. I think using the separators in the left pane (or even Nexus categories) as the grouping for the plugins seems problematic to me because the plugins are not necessarily sorted by this order. Looking my Step Skyrim SE 2.0 setup as an example, plugins in the Foundation and Models & Textures sections are scattered throughout the right pane. There's also the issue with ESMs and ESLs at the top followed by the ESPs and ESP+FEs so you get an immediate split with Realistic Water Two - Resources.esm at the top and Realistic Water Two.esp close to the bottom.

As bad as this may sound, it's nice to see confirmation that Steam may mysteriously update itself and games even while allegedly in offline mode. I'm a bit behind at this point, but I currently have backup copies of Skyrim Special Edition 1.5.97, 1.6.318, 1.6.353, and 1.6.640. It looks as if I missed the 1.6.1130 update.

If you follow the steps to install Complex Item Sorter, you should not need to edit anything in Binary, Start In or Arguments. Steps 1 - 4 create Complex Sorter as an executable with the correct Binary and Arguments already set. Steps 5 - 7 set Start In by selecting the appropriate folder. Step 8 sets Create files in... by selecting the Step Fallout 4 - Complex Sorter Output from the list. One potentially confusing point is that the box shows Binary set to e.g. C:\Windows\system32\cmd.exe and Arguments set to e.g. /C "D:\Games\Mods\M8r98a4f2's Complex Item Sorter\Complex Sorter.bat". If you have Binary set to e.g. "D:\Games\Mods\M8r98a4f2's Complex Item Sorter\Complex Sorter.bat" and Arguments is empty, this is fine. Just note that I am using the paths on my system so your paths may be slightly different.

Please bear in mind that what I am writing here should approximate correctness as a high level overview, although it is based on my understanding of the implementations and direction Intel was heading up through the Pentium processor in real mode (with an actual memory management unit and flat address space). It's the latter. Modern processors have an internal memory management unit (MMU) that maps logical memory allocations to physical memory and tracks which areas of memory are allocated to a process and the actions that are allowed in each memory block (execute and read/write). Modern languages like C/C++ and several others also have the concept of a null pointer (0x0) that is used to trap illegal memory accesses (typically because the pointer was never initialized or assigned a valid address). The 64-bit address space is so large (0x0000 0000 0000 0000 - 0xFFFF FFFF FFFF FFFF) and physical memory is so comparatively small (0x0000 0000 0000 0000 - 0x0000 003F FFFF FFFF for 256GB) that this works in our favor. Note the instruction pointer in the crash is (expanded out to 64 bits) 0x0000 7FF6 DACC C4B3 and (if my math is correct) this is in the 127 terabyte block of logical memory space. I won't go into the details of how the MMU works because I'll probably be wrong at worst and outdated at best. The high level is that when the processor needs to access a logical memory address, it consults the MMU to get the physical memory address in RAM1. If the logical memory address is not mapped in the MMU, the process raises an access violation exception. This may be naive on my part and is based on observation of a small sample of debugging sessions, but I've never seen a legitimate allocation in the lower logical address space. I believe this is intentional and works to the advantage of address randomization (in which Windows loads executables and DLLs into random addresses to minimize predictable load patterns). 1This is a very simplified because it does not account for mapping logical address blocks to the page file. The MMU also tracks whether the process is allowed to execute, read or write to this logical address space and throws an exception if you attempt to execute in a non-executable block or write to a non-writable block.

If you are referring to to the probably call stack, these are processor instructions. The mov instruction is typically used to move data from memory to a register or vice versa (from a register to memory). It's been too many decades since I fiddled with x86 assembly so I don't remember if mov supports register to register or memory to memory. PROBABLE CALL STACK: [0] 0x7FF6DACCC4B3 SkyrimSE.exe+01CC4B3 -> 15507+0x333 test byte ptr [rcx+0x0C], 0x01 [1] 0x7FF6DACC923C SkyrimSE.exe+01C923C -> 15469+0x5C movzx r9d, byte ptr [0x00007FF6DC9465B0] [2] 0x7FF6DAC7C648 SkyrimSE.exe+017C648 -> 13760+0x78 mov [r13+0xDAA], r15b [3] 0x7FF6DAC7AC58 SkyrimSE.exe+017AC58 -> 13753+0x328 xor dil, dil [4] 0x7FF6DB0E92C6 SkyrimSE.exe+05E92C6 -> 36553+0x346 call 0x00007FF6DACC92A0 [5] 0x7FF6DB0F285C SkyrimSE.exe+05F285C -> 36644+0x1C xor eax, eax [6] 0x7FF6DB745E4D SkyrimSE.exe+0C45E4D -> 68445+0x3D mov rcx, [0x00007FF6DDB06898] What i can say is that (looking at very top of the stack and the registers), it looks is if the game is attempting to read the English string files (perhaps for a BGSStoryManagerBranchNode a bit further down the stack) and this caused an unhandled access violation exception at 0x7FF6DACCC4B3 (test byte ptr [rcx+0x0C], 0x01). This is getting the address in RCX, adds 0x0C to this address, and then tests whether the byte at this memory address has the 0x01 bit set. The issue here is that in REGISTERS, i see that RCX is 0x0 (a null pointer). This basically means RCX+0x0C is pointing into unallocated memory space and this is why the game crashed. I also see EngineFixes.dll and tbbmalloc.dll in the stack trace, so I'm inclined to think it's remotely possible something in Engine Fixes or you are correct that the vanilla game files may be at fault. Take this with a grain of salt because the honest answer is that I don't see anything in this crash log that definitively points to the culprit. I haven't tinkered with assembly since just after the the 80386 was released, and I have zero RE skills with game engines.

This just changes the tile that appears into the executables dropdown to something a bit cleaner and is cosmetic. The title can be anything you want, but we suggest using "xLODGen64" so it clearly represents the name of the executable this runs.

I use and recommend Mod Organizer 2 for pretty much all Bethesda games. I know it works well with Fallout 3, Fallout New Vegas, Fallout 4, Oblivion, Skyrim and Starfield.Mod Organizer 2 also makes it easier to follow guides. Vortex probably works, but you'll have to jump through hoops with manual LOOT rules to keep mods and plugins sorted in the correct order. One point to bear in mind is that Clear and Present Danger for Fallout 3 and Fear and Loathing in New Vegas for Fallout New Vegas have not been maintained for a long time so you may have to do some investigating and troubleshooting to get these up to date. I know Compiled Fixes for Fallout 3 is no longer available and the darnified.net site was taken down a while back, although I think Darnified UI may be available on alternate sites still.

If you click on the plugin missing the master in the right pane to select it, Mod Organizer will highlight the mod containing this plugin in the left pane. This should tell you which mod needs to reinstalled correctly.

The Start In field can be left empty for most executables since these (SKSE, xEdit/SSEEdit, LOOT, DynDOLOD, TexGen, etc.) find and use the game data folder themselves. I think the Force Load Libraries libraries checkbox is checked by default, but I doubt it really matters. If i remember correctly, you have to click Configure Libraries and manually add a list of library to force loading. This isn't configured by default so the checkbox has no effect.

This may be confusing for a while because Bethesda released Skyrim 1.6.659 on GOG and this is not the same executable as Skyrim 1.6.659 on Steam. The downside is that some folks may mistakenly install the 1.6.659 version of the plugins on the GOG version of the game and SKSE, Bug Fixes, etc. may detect this as the Steam version of the game and likely CTD without a compatibility warning.

The wiki z929669 linked is owned by Nexus so you'll need to report this issue to them. As you mentioned, I can't find a clickable element to collapse the left pane and the and the right pane containing all of the useful information flows off the right side of the browser window and can't be scrolled into view. I did find that if you click the Print button and cancel without printing, the left pane magically collapses so this gives the right pane a bit more space. If you still can't read everything in the table, you might try clicking Print, select Microsoft XPS Document Writer, change orientation to Landscape. It's not exactly a perfect solution, but but at least I can read the entire table this way.

I think most of us were using profiles the days prior to instances because the only options were to use profiles or install multiple copies of Mod Organizer. I still have multiple copies of Mod Organizer floating around (pretty much one for each Bethesda game from Fallout3/Oblivion to Starfield) that I need to migrate to instances at some point Multiple portable instances were my preference in the days of old, but it's also a pain having to update multiple copies of Mod Organizer. At some point I want to migrate all of my portable installs to instances. The pain point with instances is that Mod Organizers defaults instances to %AppData% or %LocalAppData% (on the sacred boot drive) and many people have small boot drives. I'll just need to spend some time to move the instance folder to my game drive.

It's funny you say that because I ate my two cookies while reading this and had to laugh out loud when I read this sentence. I may have mistaken that screenshot, but I'm interpreting this as SKSE saying it detected Skyrim version 1.6.640 and is why I posted instructions to get this version of SKSE. I hadn't looked at that Wabbajack list, but it does seem to be a bit dated based on your findings.

I agree with @z929669 that profiles are too fiddly to bother using. Profiles are great in that mods are shared in both profiles so it uses significantly less disk space, but this is also it's major sore point. This essentially means you can install the STEP guide, get it working correctly, and easily create a new profile containing an exact copy of your existing profile. If you then install let's say JK's Skyrim and redo TextGen, DynDOLOD, etc. you just clobbered Texgen Output and DynDOLOD Output in your STEP profile. Instances uses more disk space because none of the mods are shared between instances, but this also means you can make all the changes you want to this instance without affecting any other instances.