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: September 04, 2017, 02:12:04 PM »

Having the usual COPY actions print a change-log for all exceptions in the patch code should be doable, yes. (Less generally it should also be possible, but more work).
Posted by: CamDawg
« on: August 30, 2017, 03:29:30 PM »

I was thinking about this from a bug report about a failed copy from Tweaks. It spawned the usual failure message:

ERROR: illegal 1-byte read from offset 24 of 0-byte file IPLOT01K.ITM

And I was thinking how nice it would be if--on errors such as these, and in particular for regexp copies--WeiDU appended the output of --change-log to the debug file. While these failures are generally bad code from the modder (or mine are, at least) there is the rare case like this where I have to find out what other mod in the wild is doing bad things.

Is this a feasible request?