-
-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add target mod list path to the log file. #2685
Comments
Both of these pieces of information are already part of the log. At least I recall using the log information to inspect something similar. 🤔 |
I have looked at countless logs and I have never seen the target modlist path in any of them. Name yes, path no. I just thought it would be a simple add that can help troubleshoot. |
I just looked at a log containing that information yesterday.🤔 But the target modlist is the .wabbajack file of the list and the full path for that was in said installed log. |
Here is a typical installation log. If you can show me where the path to the .wabbajack file is in that log, I will happily withdraw the request. I'm not trying to be a pain in the ass, I just really don't see it in the log. |
Same and it seems I got it confused with some other logging cause the target is missing in this log at least. |
What I was hoping for was to include it along with these other paths. It's not often needed, but when someone doesn't get the .wabbajack file through the gallery, they often place the file in random places. One of those places is the install folder. and of course, that will get deleted and cause the install to fail. 00:02:49.730 [INFO] (Wabbajack.Installer.StandardInstaller) Install Folder: E:\LitR703 |
Is your feature request related to a problem? Please describe.
When trying to help troubleshoot installation errors some users place their .wabbajack file into the installation folder. trying to get this information from the users can be difficult.
Describe the solution you'd like
Add the target modlist path to the log in the same place the installation path and resource download path are listed. This will make it easier to identify this specific mistake,
The text was updated successfully, but these errors were encountered: