Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Wisp
« on: January 23, 2016, 05:40:52 PM »

The question is a rather broad. I can't think of anything useful which is not similarly broad.
Posted by: agb1
« on: January 07, 2016, 07:12:21 AM »

The spirit of this request is to increase the amount of information logged automatically when an error occurs.

I understand that the resource that was being processed is not always itself responsible for the error (ex a problem processing a creature file because some other mod changed one of its original items).

On the other hand, for the times when it IS a change to that resource directly that is problematic, it would be helpful to have the change-log with the original report.

If auto-change-log on the specific resource being processed at the time of error is a red herring 75% of the time, is there other information that we could automatically collect that would help to narrow down where the problem is?
Posted by: The Imp
« on: January 06, 2016, 03:55:23 PM »

I agree 100% with Wisp on this.
Which is why the FAQ for the Mega Moding has the instructions, originally "stolen" from here, and then adopted from other better users from SHSforums and so forth.
Posted by: Wisp
« on: January 06, 2016, 03:26:47 PM »

No. Too often an error is caused by file B or circumstance C even though it is encountered during file A. Change-logs in these situations would only be so much noise, but people would think it was relevant because the information would appear in connection with the error message. Knowing which file to change-log is at least 75 % of using --change-log.
Posted by: agb1
« on: January 03, 2016, 10:20:07 PM »

Asking users to run change-logs is a very common debugging request, but some users (especially those who are unfamiliar with command prompts) are often confused about how to provide change-logs when asked.

Therefore, since these logs greatly improve our ability to track down problems -- when WeiDU prints an error for a particular file, please have it automatically print a change-log for that file.