2020-02-24 16:03 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002683Spring engineGeneralpublic2018-02-11 14:22
Assigned ToKloot 
Product Version0.82.7+git 
Target VersionFixed in Version104.0 +git 
Summary0002683: new unit tag: Unhardcoded cloak detection behaviour
DescriptionI would like control over how effective a unit is at detecting cloaked units. Currently it is hardcoded to modelRadius. In general algorithm for decloaking is shown below for the current system:

If (distanceBetween(me, enemy) < enemy.modelRadius + me.minCloakDistance)

enemy.modelRadius should be replaced with a new unitdef tag called something like 'cloakDetectionRadius'. This value would default to modelRadius for backwards compatibility.

The tag should be able to take negative values because a unit could be really bad at detection or even completely unable to detect cloaked units.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files




Kloot (developer)

cloak behavior (energy drain, forced detection, etc) is now fully customisable via the AllowUnit{Cloak,Decloak} callins.

-Issue History
Date Modified Username Field Change
2011-10-05 11:02 Google_Frog New Issue
2018-02-11 14:22 Kloot Assigned To => Kloot
2018-02-11 14:22 Kloot Status new => resolved
2018-02-11 14:22 Kloot Resolution open => fixed
2018-02-11 14:22 Kloot Fixed in Version => 104.0 +git
2018-02-11 14:22 Kloot Note Added: 0018801
+Issue History