loot/loot.github.io
0
0
Fork 0
mirror of https://github.com/loot/loot.github.io.git synced 2026-07-27 14:13:30 -07:00
Code Issues Packages Projects Releases Wiki Activity

Additional upload suggestion

Browse Source
This commit is contained in:
egocarib
2014-09-10 07:18:41 -07:00
parent abf1999974
commit 549cb3d7a9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
How To Report Issues Helpfully.md → How-To-Report-Issues-Helpfully.md
+1 -1
View File
@@ -2,7 +2,7 @@ If LOOT is crashing, or there is some other problem that's not due to missing or
1. In LOOT's settings, set the debug verbosity to its medium setting. (If you're running the 0.7 alpha, it's an Enable Debug Logging checkbox instead.)
2. Run LOOT again to replicate the issue.
3. Upload the debug log that is generated at `%LOCALAPPDATA%\LOOT\LOOTDebugLog.txt` to some location you can share it from. If the log is less than 512 KB, you can upload it to [Pastebin](http://pastebin.com/) without requiring an account. Otherwise, a service such as Dropbox, Google Drive, OneDrive, etc. can be used. Please don't use filesharing websites with countdown timers or captchas.
3. Upload the debug log that is generated at `%LOCALAPPDATA%\LOOT\LOOTDebugLog.txt` to some location you can share it from. If the log is less than 512 KB, you can upload it to [Pastebin](http://pastebin.com/) without requiring an account. Larger logs can be pasted as a [Gist](https://gist.github.com/) without requiring an account. Otherwise, a service such as Dropbox, Google Drive, OneDrive, etc. can be used. Please don't use filesharing websites with countdown timers or captchas.
4. If you're running the 0.7 alpha, also upload the `%LOCALAPPDATA\LOOT\CEFDebugLog.txt`.
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.