Contents

Identifying The Issue

Reporting The Issue

Supplying Debug Logs For Application Issues

Identifying The Issue

The first step is to identify what type of issue you're having, so that you can report it in the most appropriate place. Issues can be one of two basic types:

1. A metadata issue. It's probably this type if LOOT displays incorrect information, such as incorrect messages and Bash Tag suggestions. It's also probably a metadata issue if LOOT sorts your mods incorrectly, as it's most likely because it's lacking some sorting metadata, or the sorting metadata it has is incorrect.
2. An application issue. It's probably this type if LOOT behaves incorrectly or unexpectedly, such as crashing or doing the wrong thing when you click on a button. Some sorting mistakes can also be due to application issues, but it's best to treat them as metadata issues unless you know otherwise.

Metadata issues are also game-specific, so make a note of which game you're having the issue with.

Mod Organiser users who are experiencing a LOOT application issue should first try to replicate it while running LOOT independently of Mod Organiser. Running LOOT through Mod Organiser is unsupported.

Reporting The Issue

Once you know which type of issue yours is, it's time to report it. It's best to report issues on LOOT's issue trackers, where they can't get lost, overlooked or disorganised, but doing so requires a free GitHub account. The links below can be used to report your issue in the appropriate tracker.

• Morrowind metadata
• Oblivion and Nehrim metadata
• Skyrim metadata
• Skyrim Special Edition metadata
• Skyrim VR metadata
• Enderal and Enderal Special Edition metadata
• Fallout 3 metadata
• Fallout: New Vegas metadata
• Fallout 4 metadata
• Fallout 4 VR metadata
• LOOT application

If you don't have a GitHub account and don't want to sign up for one, you can instead report the issue in LOOT's official forum thread.

Supplying Debug Logs For Application Issues

If you're experiencing an application issue, you should supply debug logs to help solve the issue. You can do this by following the instructions below.

1. In LOOT's settings, toggle the Enable Debug Logging checkbox on.
2. Run LOOT again to replicate the issue.
3. Select "Open LOOT Data Folder" in the File menu.
4. Upload the generated LOOTDebugLog.txt log file contained within.

If you're reporting the issue in the LOOT application issue tracker, you can attach the log files to your report by dragging and dropping them into the report's text box, as explained here.

Otherwise, a pastebin can be used for logs smaller than 512 KB, or a service such as Dropbox, Google Drive, OneDrive, etc. can be used. Please don't use filesharing websites with countdown timers or captchas.

Note that LOOT wipes the log each time it starts, so if you encounter an issue, don't run LOOT again without first uploading or making a copy of the log.

If you can't reach the settings dialog

If LOOT is crashing on startup, or you can't get to its settings dialog for some other reason, its settings file can be manually edited to enable debug logging.

1. Open settings.toml in a text editor, eg. Notepad.
   • On Windows, settings.toml can be found at %LOCALAPPDATA%\LOOT\settings.toml.
   • On Linux, settings.toml can be found at $HOME/.var/app/io.github.loot.loot/data/LOOT/settings.toml if you have LOOT installed as a Flatpak application, or at $XDG_DATA_HOME/LOOT/settings.toml otherwise.
   • If you use the loot-data-path command-line argument, open the settings.toml within your custom LOOT data directory.
2. Replace the text enableDebugLogging = false with enableDebugLogging = true.
3. Save the file.

Then run LOOT and upload your debug log as detailed above.