Using squads.csv to create minimum ranges... But?
Posted: Thu May 23, 2013 10:13 am
Squads.csv has 5 statistics for APEffective, 5 for APAccuracy and 5 for HEeffective... The titles for APAccuracy imply that the 5 values represent different distances to the target, ie. the 1st value is the APaccuracy for 1 square away, the 2nd for 2 squares, the 3rd 4 squares, the 4th 6 squares, the 5th 7+ squares...
Using this, I've tried to setup a minimum AP range for warships and coastal guns... initially setting the values of each of the first three numbers to zero. However, doing it that way, the BA engine ignores that there are any fourth and fifth values, and reports "out of range" or some such error, no matter the distance to target...
So then I've tried a low and meaningless, dummy "1" value, as the 1st number, which tricks BA into actually checking that it can open fire at the greater ranges...
However, I've noticed that these units sometimes seem to be capable of targeting units less than 6 squares away, even though the 2nd, 3rd & 4th values (ie. ranges 2-5 squares) for APEffective, APaccuracy and HEeffective are still set to zero...
Any ideas why this is happening? Does BA's game engine use the squads.csv data for different ranges? Or might it be creating it's own values, based on some of the data? Confused.

Using this, I've tried to setup a minimum AP range for warships and coastal guns... initially setting the values of each of the first three numbers to zero. However, doing it that way, the BA engine ignores that there are any fourth and fifth values, and reports "out of range" or some such error, no matter the distance to target...
So then I've tried a low and meaningless, dummy "1" value, as the 1st number, which tricks BA into actually checking that it can open fire at the greater ranges...
However, I've noticed that these units sometimes seem to be capable of targeting units less than 6 squares away, even though the 2nd, 3rd & 4th values (ie. ranges 2-5 squares) for APEffective, APaccuracy and HEeffective are still set to zero...
Any ideas why this is happening? Does BA's game engine use the squads.csv data for different ranges? Or might it be creating it's own values, based on some of the data? Confused.