enhancement: script editor commands.pak edit log

[ghramsey]

Is there any way to create an edit log that gets dumped to text upon saving edits?

It doesn't need to be overly complex though it might be harder to impement than I'm thinking.

After all the changes I made and documenting them I have found multiple instances where upon file compare to a vanilla commands.pak my written down changes don't match what I saved.
Either I made a further change I did not record or plain forgot I'd changed it and didn't write it down.

An edit log saved by the editor would help with such changes being recorded as a running log.

[MattFiler]

This is a nice idea, and kinda tied to #301 - basically just more explicitness about modifications.

It'd also potentially be useful down the line for making lighter weight mod installers, as you could probably have something that re-runs the modification steps rather than distributing all the asset files.

[ghramsey]

OH. I'm sorry for the duplication. I forgot I'd actually made such a request before.

OliverGoetz made a handy program for comparing two commands.paks of same mission. It's very handy for making sure I've written down change. I've asked him for something similar though a way to output the changes to either PDF or maybe XML so they're more visible.

https://github.com/Oliver2Goetz/AIPAKFileDifferentiation He's using CathodeLib to gather the information.
Any way to add a native export function to CathodeLib ?

[MattFiler]

I think there's a differentiation here - the log from OpenCAGE would be step-by-step changes made via the GUI. The log from Oliver's tool would be raw diffs without any context history.

[ghramsey]

Yeah. That's true.

It's all I've had to date to check for changes.