2024-03-19 15:00 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003481Spring engineLuapublic2017-09-24 19:14
ReporterJools 
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version92.0 
Target VersionFixed in Version 
Summary0003481: UnitID not flushed on cloak + jam
DescriptionA delicate bug which applies to cloak + radar jamming. When a unit that is within radar jamming area also cloaks, enemies still keep attack lock on this unit, although it should be completely invisible.

This applies to attack orders that are given before target cloaks, and applies to attacking units such as snipers and bombers.

The correct behaviour should be to removed the target unit's ID from the attack order, when the mentioned target unit cloaks. Note that this also requires the presence of radar jamming, for solely cloaking should not prevent a unit to be fired upon.

It would also be preferable (although maybe not possible) that the unit would receive a new unitID when sighted again by either radar or visially. Maybe separate unitID into one engine-internal and one dynamic and local to enemy information set (from radar and visual).



Steps To ReproduceRequires two teams: team 1 should build radar jammer and energy enough to cloak commander. Team two needs a sniper.

Place commander under radar jamming coverage. Order sniper to attack commander. Cloak commander. Watch sniper keep attack order and getting the updated position of commander.
Additional InformationApplies at least to XTA and BA.
Tagsintel, problem, simulation
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes
There are no notes attached to this issue.
+Notes

-Issue History
Date Modified Username Field Change
2013-02-19 16:30 Jools New Issue
2013-02-19 16:32 Jools Tag Attached: problem
2013-02-19 16:32 Jools Tag Attached: intel
2013-02-19 16:32 Jools Tag Attached: simulation
2013-02-19 16:33 Jools Tag Attached: something is unnatural here.
2013-02-19 17:45 Kloot Assigned To => Kloot
2013-02-19 17:45 Kloot Status new => assigned
2013-02-19 18:57 Kloot Changeset attached => spring release ee13fb16
2013-02-19 18:57 Kloot Status assigned => resolved
2013-02-19 18:57 Kloot Resolution open => fixed
2017-09-24 19:14 Kloot Tag Detached: something is unnatural here.
+Issue History