LOOTDebugLog.txt. Is this a problem?plugins.txt and loadorder.txt. Won't this break something?Users can supply metadata themselves to alter the order LOOT gives. There are two types of metadata that can be supplied to change load order:
Be sure to read LOOT's documentation for more information on these.
LOOTDebugLog.txt. Is this a problem?If you are running LOOT on a Steam Deck, the easiest way is to use Steam to move the game in question to a microSD card that has been formatted by Steam (as described on this page).
Otherwise, assuming you are using Linux, you can manually create a partition or disk image and format it with a case-insensitive filesystem, mount the filesystem, and then move the game to that filesystem. Case-insensitive filesystems include ext4 (with the casefold option), F2FS (with the casefold option), exFAT and NTFS. Here is an example of the steps needed to prepare a case-insensitive ext4 disk image before a game can be moved to it:
IMAGE_LOCATION=~/Downloads/casefolded.img
MOUNT_POINT=~/Downloads/casefolded
truncate --size=15G "$IMAGE_LOCATION"
mkfs.ext4 -O casefold "$IMAGE_LOCATION"
echo "$IMAGE_LOCATION $MOUNT_POINT ext4 defaults 0 0" | sudo tee -a /etc/fstab > /dev/null
mkdir -p "$MOUNT_POINT"
sudo mount "$IMAGE_LOCATION" "$MOUNT_POINT"
sudo chown "$USER" "$MOUNT_POINT"
mkdir "$MOUNT_POINT/SteamLibrary"
chattr +F "$MOUNT_POINT/SteamLibrary"Running LOOT through Mod Organiser is unsupported. If you're experiencing an issue while running LOOT through Mod Organiser, try replicating the issue while running LOOT independently of Mod Organiser. If the issue persists, please report it.
Some users have reported that antivirus software can interfere with LOOT, so, if you are experiencing issues, try checking if your antivirus software is involved and whitelist or exclude LOOT.
Make sure any firewalls or security software you have installed aren't stopping LOOT from reaching the online masterlist.
If LOOT still can't update its masterlist, it's likely due to connectivity issues that are beyond our control (e.g., a temporary outage or your ISP blocking the domain the masterlists are downloaded from). You can attempt to update it manually by downloading this file (or this ZIP if you can't access the previous site, just extract the prelude.yaml file from it), selecting "Open LOOT Data Folder" within LOOT's File menu and placing prelude.yaml in the prelude folder.
Then, using the following table, download the masterlist.yaml file for your game from the masterlist link (or extract it from the alternative ZIP) and place it in the corresponding game folder. Finally, disable the "Update masterlist before sorting" option in LOOT's settings until your connectivity issues have been resolved.
| Game | Links | Game Folder |
|---|---|---|
| Morrowind | Masterlist, ZIP | games\Morrowind |
| OpenMW | Masterlist, ZIP | games\OpenMW |
| Oblivion | Masterlist, ZIP | games\Oblivion |
| Oblivion Remastered | Masterlist, ZIP | games\Oblivion Remastered |
| Skyrim | Masterlist, ZIP | games\Skyrim |
| Skyrim Special Edition | Masterlist, ZIP | games\Skyrim Special Edition |
| Skyrim VR | Masterlist, ZIP | games\Skyrim VR |
| Fallout 3 | Masterlist, ZIP | games\Fallout3 |
| Fallout: New Vegas | Masterlist, ZIP | games\FalloutNV |
| Fallout 4 | Masterlist, ZIP | games\Fallout4 |
| Fallout 4 VR | Masterlist, ZIP | games\Fallout4VR |
| Nehrim | Masterlist, ZIP | games\Nehrim |
| Enderal | Masterlist, ZIP | games\Enderal |
| Enderal Special Edition | Masterlist, ZIP | games\Enderal Special Edition |
| Starfield | Masterlist, ZIP | games\Starfield |
Steam removes the game's Registry entry when the game is updated or its cache is verified. Run the game's launcher to add the Registry entry back again. LOOT will then be able to detect the game. If you've manually moved your game, make sure to properly migrate it so that Steam recognizes it.
Another cause may be that the game is installed in a location where you do not have read permissions. In this case, LOOT cannot read your plugins and treats the game as undetected. Try checking the permissions of the game's path and ensuring you have read access.
You can also set your game's install path manually in LOOT's settings menu. In the menu, select your game's settings profile in the left-hand panel (if it's not there, select "Open LOOT Data Folder" within LOOT's File menu and delete settings.toml to restore your settings to default, or make a new profile for your game) and enter your install path in the "Install Path" field.
If you have multiple installations of a game, you will need to manually set your install path depending on which installation you'd like to manage (LOOT can only automatically find whichever one is set in your registry). For convience, you may want to create LOOT shortcuts for each installation with the --game-path command-line parameter.
plugins.txt and loadorder.txt. Won't this break something?CR LF line breaks with LF line breaks. It doesn't make any difference to the game.First of all, double-check that you've downloaded LOOT from an official source (i.e., GitHub or Nexus Mods). If you downloaded it from anywhere else, the provider may have introduced some form of malware to the installer or package.
If you have downloaded it from an official source, some antivirus software will mistakenly report new releases of LOOT as malware. False positives for new releases are fairly commonplace among antivirus software; just report the flagged executable as a false positive to your antivirus software and/or whitelist it to continue using it.
If you're still suspicious of LOOT, it's an open-source program, so you can review its source code on GitHub and build it yourself. There is also a link to a VirusTotal report for new releases next to each download at LOOT's Nexus Mods page.
This error tends to happen when the name of the mod in Mod Organizer containing the plugin mentioned in the error message is too long, i.e., long enough that the full path of the plugin is over the Windows path length limit of 260. Try shortening the mod's name.
It's worth double-checking the load order LOOT gives you, in case it's gotten something wrong. Also, if you're not starting a new game, changing your load order may cause in-game issues. To avoid disaster, you can backup your load order as follows:
.ess save file, and its accompanying .skse file (if you have SKSE installed). These are found in the %USERPROFILE%\Documents\My Games\Skyrim\Saves folder.plugins.txt and loadorder.txt, which are found in the %LOCALAPPDATA%\Skyrim folder.That way, if something does go wrong, you have backups to roll back to. If you don't overwrite or delete save files, you don't need to back them up, so long as you can remember which save was made before you made the changes that caused problems.
LOOT support may be added to SkyProc patchers in time. Until then, you can do the following:
-NOBOSS argument.