GrantSP

There currently isn't any advice as to which version of the Enhanced Blood Textures merged plugin to choose. At the moment the instructions simply state: Sadly this will cause errors as the folder "More Gore FWE" contains these sub-folders: More Gore + DLCs + FWEMore Gore + DLCs + FWE + Full Screen Blood Instant RemoveMore Gore + DLCs + FWE + Less Screen Blood TimeMore Gore + DLCs + FWE + No Screen BloodMore Gore + DLCs + FWE + Reduced Dismember ForceMore Gore + DLCs + FWE + Reduced Ragdoll ForceMore Gore + DLCs + FWE + Screen Blood VanillaMore Gore + DLCs + FWE + Smaller Spatters DefaultMore Gore + DLCs + FWE + Smaller Spatters RealisticMore Gore + DLCs + FWE + Smaller Wounds Which are variations on the main plugin and provide blood/gore/splatter detail levels as described. There isn't much information as to what the results are like ingame as far as I can see and it would be nice to have a little suggestion here.

Yet another Gamwich mod gets my vote.

It's a vote for Gamwich's from me also.

It seems the same question can be posed about the .32 pistol as it uses assets from the FNV mod but no references to them that I can see are in the FO3 plugin. I may be just having a "senior moment" but I can't see what we are doing here.

I'll tack this little observation to this thread. In the "Weapons" section we have 3 mods included in 'Millenia's', then a few from 'Zealotlee' and then we're back into 'Millenia's'. I'm assuming this is just a bit of an editing mistake since I see no reason to break up 'Millenia's' into 2 sections.

I'm going through the guide again and I've come to the part of the install wher we install the Millenia Assaultrifle Replacers RH WMK Patch and I just don't see what the necessity is with these steps. The guide, following the instructions from the mod page, tells us to also grab the FalloutNV mod: HK G3SG1, which provides some additional meshes, textures and sounds. Open it and copy into the mod we are installing the meshes, textures and sounds from the FNV mod. That's okay, the instructions are clear, but for the life of me I see no reason to do so. Unless further down the page we are making/installing another plugin that references these meshes/textures/sounds, nothing we just installed is being used in game! Could I get a little insight into what is happening here?

If it does what it says on the box then, definitely, this is a must install. Coming from you I have no reason to doubt that it will work brilliantly. Kudos!

Welcome to STEP @ZarosZeitgeist You haven't specified which version of MO so I'll assume 1.3.11, but truthfully even if it is MO2 the answer will still be applicable. To be blunt MO doesn't have the code in it to delete files in the manner in which you describe. All actions that result in removing files whilst inside the MO UI are initiated by the user and ALL of them use the builtin OS level file actions such as delete/move/copy. To put this another way: MO is not touching your files. The most likely scenario is your AV packages, or some other software, is interfering with the actions MO takes and views those files as needing to be removed or quarantined. Disable your AV or set up an exemption for MO to allow it free reign on your system. If you do not believe your AV or firewall or anything else is causing this please post your ModOrganizer.INI so we can examine how you have MO setup.

Just grabbed the latest MO2 and installed it to test LOOT and it is now handling Skyrim, though admittedly I only tested it with regards to starting it, not actually handling any mods. Also @Tannin will still be interested in any issues that apply to MO 1.3.11, he may just prioritise releasing MO2 before fixing those.

Welcome to STEP @ToughGhost. STEP does not use Frostfall/Campfire in the current guide so either you are adding these as extras or perhaps you are actually following another guide, such as @Neovalen's Skyrim Revisited. In either case try following the instructions in that guide or perhaps asking in the official Frostfall page where @Chesko is very active.

It didn't start out that way, he decided in the last post to give that a try and it worked for him. Why it worked, I don't know.

If it is an issue then it is a very rare and specific one that affects only a handful of users. Keep in mind MO2 is still in active beta development and support for current 32bit games is still a WIP. Primary focus is till on porting the code to 64bit for games such as Fallout4. Nevertheless if it works for you, then use it.

Completely remove the LOOT settings by removing the %AppData%\LOOT\ folder and then re-install LOOT. You may need elevated access to see that hidden system folder. Since the same behaviour is now evident when you install older versions the common denominator in them all is the settings, so let's remove those and start fresh. Could you also advise us whether you are using the archive or installer versions?

I suspect there may have been a Windows update that has interfered with these LOOT installs. I see no reason why 0.9.0 or 0.9.1 should all of a sudden not work for a handful of users but not the rest of us. Nothing has changed with MO or LOOT, other than the obvious, but still it refuses to be called from MO for some. Very odd!

I made one minor edit to @Kelmych's guide very early my time (9 or 10 AM) and the wiki was very responsive, so no, no issues I've seen.

Are still using Windows XP? :O_o: If so it may be time to upgrade your system even if you don't want Skyrim SE.

The best answer I can give you is: FNIS isn't really a 'mod', in the truest sense of the definition, rather it is a tool that accesses the Data folder. Since STEP recommends Mod Organizer I could advise you to switch, but that probably isn't the answer you're after. Please note the sticky post on the FNIS forum is wrong, FNIS works perfectly well with MO. Now specifically the error message occurs because NMM is trying to access the tool that is found in the temporary folder used during the installation, this is wrong and I have no specific answer for that other than following @Gamerpoet's video exactly.

Not really a big fan of the DLC Retexture files as they are hosted on Mediafire, I site that I don't rate very highly. I'm curious to know where you first found out about them and whether there might be an alternate site to store them.

Oh there are Star Trek fans around, it's just that Star Trek games have been notoriously bad and the whole VR thing hasn't grabbed me. I did enjoy seeing Jeri Ryan again.

If by that statement you have a working LOOT called from MO, then go with that. I can't see anywhere the system OS specified so I'm assuming Win 10, that being the case we have seen a few oddities with access differences compared to Win 7 so maybe you are seeing that too. It really wasn't a straight-forward upgrade by MS, despite what they say. The way you describe your setup, I too can't see any reason why there is an issue.

You should wait until July 4th because that's INIpendence Day!

Check your AV package, the change of version number may have triggered a different response from it and it could become blocked when MO tries to initiate it. Many AV software packages view the 'hooking' by MO as malicious as it is very similar to the way nefarious applications gain access to system files. Whatever AV you have either temporarily disable it or if you know how, setup an exclusion for MO so it isn't checked.

Could you open the Modorganizer.INI and copy in here just the section that defines the LOOT entries? It will look something like this: 9\title=LOOT 9\custom=true 9\toolbar=true 9\ownicon=true 9\binary=D:/Games/Utils/LOOT/LOOT.exe 9\arguments="--game=Skyrim" 9\workingDirectory= 9\closeOnStart=false 9\steamAppID= Here I have LOOT installed into a folder outside any UAC folders and also away from Steam or game controlled folders, LOOT gets all it needs to know about your game from registry entries and can be installed anywhere. I also have the Skyrim specific game switch, since I use the same executable for all my Bethesda games and this way I don't have to manually switch it using the builtin menu LOOT has. Since it works just fine outside of MO there shouldn't be any issues with Steam updates breaking the registry entries but just incase run the game launcher from the desktop to ensure those are correctly set.

Hmm... I'm just starting another install of this, largely to see where @JUNKdeLUXE was having so many issues, and I've just seen this myself. The link is to the file directly but considering Gamefront is now shut down we're going to have to source this file elsewhere. Starting my search now. EDIT: The alternate link in the guide seems to be the only other source at the moment, just go with that.

Does LOOT start outside of MO? If it does then there is an issue with your entries in MO's settings for it.