Closed AaronGullickson closed 5 years ago
I found this one too and asked Neoancient about it. MML is saving the armor data in one order, and there was some kind of conversion in the BLK loader for warships that changes the order. So essentially, you'll see this on any of the Canon ships that were modified with this release to bring them in line with construction rules.
The blk files for JS/WS/SS previously had the armor values in a different order than the location indices. Rather than maintain extra code for changing the order on writing and reading I switched it to the natural order and the files were adjusted when they were updated. Apparently some were missed, which happens with an update of this magnitude. I can write a script that will implement a batch fix.
Not trying to make work for @HammerGS, but I am wondering if this is a small enough list that it could be fixed as quickly by hand. I did notice that at least one ship (Aegis 2582, IIRC) had a swap with ALS and AFT rather than ARS and AFT so an automated solution could be tricky.
I've got time this weekend to do the list. So I'm good either way.
Environment
v0.45.1, OSX, Java 8. The issue is with the underlying data and is the same on MHQ, MM, and MML.
Description
Several of the warships seem to have their AFT armor value swapped with one of the aft rear sides, most commonly ARS. I tracked the issue all the way back to the BLK file for the Black Lion II Cruiser so it is likely the same problem for other units. I have not checked against canon for alll units, but since ALS and ARS are generally supposed to match, its fairly easy to identify the problem cases. Here is what I have ID'ed: