1.51c - the "+accuracy" and "*Attack Strength" modifiers in sect.dat are being applied twice

[floralpond]

Description:

In section I1 of Sect.dat, it has "+accuracy" and "*Attack Strength". These are being applied twice. So for example, Vau is +accuracy of 2, but if you look at their units, the accuracy value is added twice (+4 instead of +2), and the strength multiplier is multiplied twice (x1.56 instead of x1.25).

Same issue with Symbiot and Brother battle sects. Symbiot should be +1 accuracy and 1.10 strength, but they actually get +2 accuracy and 1.21 strength.

For example, shroud weaver is 4/100 ranged space in unit.dat, but in game it is 8/156 (should be 6/125). Blow ship is 8/100 in unit.dat, but in game is 10/121 (Should be 11/110)

Expected behavior: Modifiers should reflect sect.dat settings.

Actual behavior:

"+accuracy" and "*Attack Strength" modifiers in sect.dat are being applied twice

Game version:

1.51c

Steps to reproduce:

Open the game Do HDIVIEW Check Vau and symbiot units

Additional information:

none

[Matt-Caspermeyer]

Do you know if it is only for display purposes or is it also during combat?

[floralpond]

Ran some tests to see if it's a display issue only, or does it also affect combat?

In my testing with no sect modifications:

• a 1 accuracy attack can hit a 11 agility unit, but not a 12 agility unit.
• a 2 accuracy attack can hit a 12 agility unit, but not a 13 agility unit.
• a 3 accuracy attack can hit a 13 agility unit, but not a 14 agility unit.

in my testing with the symbiot sect modification:

• a 1 base accuracy attack with +1 accuracy for symbiot sect based on sect.dat (displays as 3 accuracy attack) can hit a 12 agility unit but not a 13 agility unit. -- therefore, the symbiot sect is displaying like +2 accuracy, but behaves like +1 accuracy. -- my assumption is that strength is similar to accuracy in that it's a display only issue.

[Matt-Caspermeyer]

I have an update on this issue.

I have created a fix and it is currently undergoing our testing, review, approval, and merge process. Once this is complete we hope to have this fix in a future update (V1.51).