floydg
Posts: 2052
Joined: 6/27/2004 From: Middletown, NJ Status: offline
|
quote:
ORIGINAL: Kull Even though the change-list accompanying the patch is quite large, I can almost guarantee that changes were made which don't appear on the list. This is no slam at the dev team - I've worked on a large mod, and it's simply impossible to write down EVERY change that is made. Given that you guys are the masters of AE data reporting, could you possibly create a "one-off" data change report? Basically it would compare the pre-patch release with the patch, and list only those data elements which are different. From a "key field" perspective, look at Ships, LCUs, Air Groups, and Bases, and note any individual element that may have changed - be it unit size, HQ, location, number of active vs. damaged elements, fuel levels, etc. And to be truly accurate, we're really taking about one report per scenario. Would this be hard to do? If it's a nightmare, then forget I asked - no worries. But if not, I for one could REALLY use this. Over the past few months I've utilized WitP Tracker report extracts to slowly develop an "AE-Allies Setup" spreadsheet that comments on 4588 individual lines, and I dread having to go back and look at each one individually to verify what may or may not have changed as a result of the patch. FWIW, the spreadsheet will be made available as a community resource once it's complete (only 160 lines to go), so this would benefit others, too. To say nothing of the many PBEM'ers who have their own, private set-up sheets, who would also greatly appreciate such a report. Have you looked into using the CSV files and using something like OpenOffice's "Compare Documents" to compare pre-Beta-patch version to a Beta-patch version (using two separate WitPTracker AE folders)? It may not capture all of the data (just what's dumped in the files), but it could give you a good first pass.
|