Author Topic: Feature request: --change-log output for DEBUG files on C_E_R failures  (Read 658 times)

Offline CamDawg

  • Infidel
  • Planewalker
  • *****
  • Posts: 834
  • Dreaming of a red Xmas
    • The Gibberlings Three
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?
The Gibberlings Three - Home of IE Mods

The BG2 Fixpack - All the fixes of Baldurdash, plus a few hundred more. Now available, with more fixes being added in every release.

Offline Wisp

  • Moderator
  • Planewalker
  • *****
  • Posts: 1082
Re: Feature request: --change-log output for DEBUG files on C_E_R failures
« Reply #1 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).


With Quick-Reply you can write a post when viewing a topic without loading a new page. You can still use bulletin board code and smileys as you would in a normal post.

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:
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)?: