GAME INFORMATION
These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: 14.7908
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 10 / Windows 8 / Windows 7 / Mac / Linux
ISSUE EXPERIENCED
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
This issue is cause by the segmented range priority system(don’t mind my poor naming) which was originally designed for shorter-range charged attacks.
<unit id="816" name="SaloonOutlawRifleman">
~
<tactics>chargeSaloonRifle.tactics</tactics>
~
<protoaction>
<name>LongRangedAttack</name>
<damage>20.000000</damage>
<damagetype>Ranged</damagetype>
<maxrange>18.000000</maxrange>
<minrange>12.000000</minrange>
<rof>2.000000</rof>
<damagebonus type="AbstractHeavyInfantry">2.000000</damagebonus>
<damagebonus type="AbstractLightCavalry">2.500000</damagebonus>
<damagebonus type="AbstractRangedShockInfantry">2.500000</damagebonus>
<damagebonus type="AbstractCavalry">0.600000</damagebonus>
<damagebonus type="AbstractLightInfantry">0.500000</damagebonus>
</protoaction>
<protoaction>
<name>RangedAttack</name>
<damage>20.000000</damage>
<damagetype>Ranged</damagetype>
<maxrange>12.000000</maxrange>
<minrange>2.000000</minrange>
<rof>2.000000</rof>
<damagebonus type="AbstractHeavyInfantry">2.000000</damagebonus>
<damagebonus type="AbstractLightCavalry">2.500000</damagebonus>
<damagebonus type="AbstractRangedShockInfantry">2.500000</damagebonus>
<damagebonus type="AbstractCavalry">0.600000</damagebonus>
<damagebonus type="AbstractLightInfantry">0.500000</damagebonus>
</protoaction>
<protoaction>
<name>BuckshotChargeAttack</name>
<damage>3.000000</damage>
<damagetype>Ranged</damagetype>
<maxrange>18.000000</maxrange> <!--originally 12-->
<minrange>0.000000</minrange>
<rof>3.000000</rof>
<damagecap>18.000000</damagecap>
<damagearea>2.00000</damagearea>
<damageflags>GAIAEnemy</damageflags>
</protoaction>
</unit>
<tactic>Volley
~
<action priority="100">LongRangedAttack</action> <!--range 12 to 18-->
<action priority="90">BuckshotChargeAttack</action> <!--range 0 to 18-->
<action priority="80">RangedAttack</action> <!--range 2 to 12-->
<action priority="75">BuildingAttack</action>
<action priority="30">HandAttackCrate</action>
<action priority="25">HandAttack</action>
~
</tactic>
Since the unit will always use the action with the highest priority to attack its legal target, the added range for BuckshotChargeAttack that is covered by LongRangedAttack is useless.
FREQUENCY OF ISSUE
How often does the issue occur? CHOSE ONE; DELETE THE REST!
- 100% of the time / matches I play (ALWAYS)
EXPECTED RESULT
What was SUPPOSED to happen if the bug you encountered were not present?
Here is my solution: Disactive LongRangedAttack, change the range of RangedAttack to 2-18.
By the way, his Baja California counterpart(deSaloonOwlhoot) did not get this update.