Ares

Versus.XXX.ForceFire=no prevents picking up own targets

Bug #970499 reported by Rogan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Fix Committed
Medium
AlexB
Ares 0.e

Bug Description

Setting Versus.XXX.ForceFire=no to a warhead where XXX is any armor type prevents the unit holding the weapon containing the warhead from picking up its own targets even with Versus.XXX.PassiveAcquire=yes included.

Try setting force fire to no for all armor types that are primarily used for infantry types such as none, flak, and plate and you'll encounter the problem.

Tested with fatman 12.78.1222.

See original description
Rogan (pdrogan)
description: updated
DCoder DCoder (dcoder1337)
Changed in ares:
assignee: nobody → DCoder DCoder (dcoder1337)
status: New → In Progress
Revision history for this message
Graion Dilach (graiondilach) wrote :

Confirmed.

DCoder DCoder (dcoder1337)
Changed in ares:
assignee: DCoder DCoder (dcoder1337) → nobody
Revision history for this message
mevitar (mevitar) wrote :

17.170.22, Versus.XXX.ForceFire=no doesn't prevent Versus.XXX.PassiveAcquire=yes or Versus.XXX.Retaliate=yes from working anymore.

It also doesn't show the "not allowed" cursor for the player, but because of it, the player can give attack orders against the object with said armor type normally, as if it had Versus.XXX.ForceFire=yes (i'd expect the player isn't supposed to be able to give attack orders against such targets).

AlexB (alexander-b)
Changed in ares:
assignee: nobody → AlexB (alexander-b)
status: In Progress → Fix Committed
importance: Undecided → Medium
milestone: none → 0.e
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.