Two different EMPluse SWs affect each other while targeting
Bug #1428208 reported by
AetherDawn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ares |
Fix Released
|
High
|
AlexB |
Bug Description
Two different Type=EMPluse SWs.
SuperWeaponA
AutoFire=yes
AITargeting=xxx (eg. Self or Base)
EMPulse.Cannons=A
SuperWeaponB
AutoFire=no
EMPulse.Cannons=B
If you fire SuperWeaponB a bit sooner or later than the moment that SuperWeaponA fires:
sometimes SuperWeaponB may fire at SuperWeaponA's AITargeting instead of your selection,
and sometimes SuperWeaponA may fire at your selection for SuperWeaponB instead of its own AITargeting.
summary: |
- something weird about EMPluse SW + Two different EMPluse SWs affect each other while targeting |
Changed in ares: | |
milestone: | none → 0.a |
assignee: | nobody → AlexB (alexander-b) |
importance: | Low → High |
status: | Triaged → Fix Committed |
Changed in ares: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This also happens for the Nuke, as there are two fields on HouseClass that store the coordinates for both SW types. Firing one type more than once in rapid succession resets the target before the earlier launches are complete. This could be fixed by putting the target coordinates on the building itself.