2025-07-22 20:51 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004806Spring engineGeneralpublic2015-06-14 00:55
ReporterGoogle_Frog 
Assigned TojK 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version98.0.1+git 
Target VersionFixed in Version 
Summary0004806: Guard reveals undetected attackers location
DescriptionThere is a simple trick which can be used to reveal the location of any attacking unit.
1. Find a unit which you think is going to be attacked by an unseen enemy.
2. Tell one of your units to guard that unit.
3. Wait for the guarded unit to be damaged.
4. Look at the command queue of the guarder (just hold shift).

The command queue visualization will include an attack command at the location (with some radar wobble) of the unit which damaged the guarded unit. This does not require radar, the command is drawn regardless of enemy visibility. This can be used to detect any long ranged artillery.

I think this bug was introduced in the last few years because, as I recall, the attack command was not draw. I have two possible solutions.


Solution 1: Don't draw the attack command. This solution involves not drawing commands with enemy unitID targets if the unitID is unseen (outside radar (or jammed) and outside LOS). This still reveals units in radar but I think that is ok.

Solution 2: Don't use attack commands for guard. This solution replaces attack commands with move goals and unit targets.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0014585

jK (developer)

Fix 00174811725905776e276256f2dffffde1e6dccc committed to develop branch: fix 0004806: don't reveal errorpos of invisible stationary units, repo: spring changeset id: 5109
+Notes

-Issue History
Date Modified Username Field Change
2015-06-13 05:20 Google_Frog New Issue
2015-06-14 00:55 jK Changeset attached => spring develop 00174811
2015-06-14 00:55 jK Note Added: 0014585
2015-06-14 00:55 jK Assigned To => jK
2015-06-14 00:55 jK Status new => resolved
2015-06-14 00:55 jK Resolution open => fixed
+Issue History