12 replies to this topic

[OneEyedPhoenix]

I have discovered how to do a change-log after having run cleanup.bat.

When I tried before I got this: sys_error<"azenmod/backup/0/mapping.0: No such file or directory">

In my install the problematic mods were AzenMOD and NSC Portraits, which had not retained their backup files.
By copying a mappings.0 file (and the necessary folder) from another mod into the needed "modname"/backup/"needed number" folder and renaming the mappings file as "mappings.(needed number)", the Weidu no longer gets a sys_error on checking the relevant file.
I had to create a whole lot of these folders and files manually, but it eventually worked.
Finally I had to manually create "results/log1.txt", after which I was able to get a changelog.

The conclusion is that the cleanup.bat does not screw all that much with the possibilities of running a changelog.
But for some reason I had two problematic mods in my setup, AzenMOD and NSC Portraits, which did not retain their backups.

Obviously I will get no relevant information from these mods, but I will from the rest.

Edited by OneEyedPhoenix, 28 September 2009 - 07:09 AM.

[Lollorian]

Ok, two teensy weensy questions about this:

1. Won't a mappings.0 from another mod affect the changelog?? Are they same for all mods??
2. Why does the Bleanup.bat remove only those specific mod backups and leave the rest??

Cheers,
Lol

[OneEyedPhoenix]

Ok, two teensy weensy questions about this:

1. Won't a mappings.0 from another mod affect the changelog?? Are they same for all mods??
2. Why does the Bleanup.bat remove only those specific mod backups and leave the rest??

Cheers,
Lol

Mappings.0 from another mod will list all the files that mod has affected. This is obviously false information when moved to a new mod, so the shorter the list of files the better. And it goes without saying that you can not trust the information, if any, given by the changelog about these mods.

As to your second question I have no Idea. Maybe one of the modders can answer this. As far as I know it might be a problem with the mods themselves.

Edited by OneEyedPhoenix, 14 September 2009 - 04:35 AM.

[OneEyedPhoenix]

Who made the cleanup.bat anyway? Or, more importantly, who supports it?
If it's cleanup.bat that's causing the problems with "change log" then it doesn't look like it would be too difficult to fix (as only a few mods were problematic).
If not, and the mods are the problem (as I might suspect), then maybe something can be with the mods themselves...

[dabus]

Since the files comes with the Installpack, ask Leonardo Watson. Although he might have had some help from others.

If you look at the batch, it's

FOR /R %%t IN (*.tp2) DO (

, so it only does work on tp2-files in the BG2-main-dir.
So you should have had trouble with TOD/SETUP-TOD.TP2, TOA/SETUP-TOA.TP2 and so on, which are put in sub-folders.

Would be nice to hear if you can confirm that.

Edited by dabus, 21 September 2009 - 10:24 AM.

[OneEyedPhoenix]

If you look at the batch, it's

FOR /R %%t IN (*.tp2) DO (

, so it only does work on tp2-files in the BG2-main-dir.
So you should have had trouble with TOD/SETUP-TOD.TP2, TOA/SETUP-TOA.TP2 and so on, which are put in sub-folders.

Would be nice to hear if you can confirm that.

Not quite sure what you mean... I have not had any reason to use modfolder/setup-modfolder.tp2.
As far as I can see the change-log function only looks for mappings.0 (and above) in the backup folder of each mod. (Unless there is a whole level of code I don't know about). I have tp2's in some mod folders and not in others. This appears to be random.

Edited by OneEyedPhoenix, 21 September 2009 - 10:34 AM.

[dabus]

Nope. They are not.

The script searched for the backup-folders in the tp2-files, and a few of them are not in the BG2-dir but in sub-dirs.
So if the tp2 is not there, the attrib-command cannot be used to set the read-only-flag to save these files from being deleted later.

X.TP2 >>> backup saved
X\X.TP2 > backup is lost

Have a look at the weidu.log and you can see that there are a few lines starting with tp2-files in sub-dirs. If you remind a few, my theory is right.

I will test it before I'll start a new test. The batch just needs another for-loop while looping through the folders to search for "doc"-files (which are not only winword-documents by the way), that are set to read-onky, too.

Edited by dabus, 21 September 2009 - 10:44 AM.

[OneEyedPhoenix]

Nope. They are not.

The script searched for the backup-folders in the tp2-files, and a few of them are not in the BG2-dir but in sub-dirs.
So if the tp2 is not there, the attrib-command cannot be used to set the read-only-flag to save these files from being deleted later.

X.TP2 >>> backup saved
X\X.TP2 > backup is lost

Have a look at the weidu.log and you can see that there are a few lines starting with tp2-files in sub-dirs. If you remind a few, my theory is right.

I will test it before I'll start a new test. The batch just needs another for-loop while looping through the folders to search for "doc"-files (which are not only winword-documents by the way), that are set to read-onky, too.

I think I get what you're saying, but it doesn't look like that's the problem. Both Setup-AzenMOD.tp2 and Setup-NSCPortraits.TP2 are present in the main "BGII - SOA" folder, like the weidu-log states, and both have either "BACKUP ~AzenMOD/backup~" or "BACKUP ~NSC Portraits/backup~",respectively, listed at the top of the tp2.

[Wisp]

X.TP2 >>> backup saved
X\X.TP2 > backup is lost

The /R makes it look in all subfolders as well. (Doesn't it?)

[dabus]

Oh my god. You are so right. Must have missed it since I used these FOR switches for reading files or from a file only. So there must be another explanation for the problem.

[OneEyedPhoenix]

Could it be the mods themselves that delete the backups? (or don't make proper ones in the first place)

[Lollorian]

Hey, I was just thinking, from what I know, WeiDU creates a changelog based on the modname\backup\... and its subfolders right?? So, why not just create an option in the Cleanup.bat to:

1. Enable changelogging (RECOMMENDED FOR DEBUGGING!!!) (leave backup\)
2. Disable changelogging (delete backup\)

And I saw that .tra files were saved as well ... Now why would you need them?? I seriously doubt anyone would be translating mods in the middle of their game

And another thing it saves are .tp? files (.tph, .tpa, ...) Any reason to keep em?? The .tp2 is needed for a changelog, so I'd recon keep it in the "Enable changelogging" part

Cheers,
Lol

[OneEyedPhoenix]

I tried to install just Azenmod on a vanilla BG2 install, and run the cleanup afterward. The results are clear:

Azenmod correctly made a backup, which cleanup.bat later removed!

Edit: The same goes for NSC portraits.

Edited by OneEyedPhoenix, 28 September 2009 - 07:08 AM.