2025-07-21 04:39 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003697Spring engineLuapublic2013-04-16 17:48
ReporterFLOZi 
Assigned ToKloot 
PrioritylowSeverityfeatureReproducibilityN/A
StatusresolvedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0003697: Feature Request: Check if unit is under a friendly jammer from lua
DescriptionEither via a new function or an extension of one of the LOS checking ones, currently the only way to do it is either;

a. Find maximum jamming range in game and check all GetUnitsInCylinder around the unit in question

b. Iterate over all existing friendly jammer units and GetUnitSeparation

Feel free to tell me I'm an idiot if there is a more direct way already.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0010443

Kloot (developer)

Last edited: 2013-04-13 23:20

View 2 revisions

the engine would actually have to do it in much the same way because there is (at present) only one jammer map shared across all allyteams, so your chances aren't good ;)

~0010445

FLOZi (reporter)

:(

Even a 'GetUnitUnderJammer' regardless of friendly or otherwise would be useful, if it could return the jammerID (but I suspect it can't?)

~0010461

FLOZi (reporter)

Sorry if bumping is poor etiquette;

It should be possible to detect if a set of map coordinates is under a(ny team's) jammer, correct? Even that would give us much easier access to information than we have now.

~0010462

Kloot (developer)

Yep, that would be a simple change to GetPositionLosState. Will add it in a day or so.
+Notes

-Issue History
Date Modified Username Field Change
2013-04-13 20:51 FLOZi New Issue
2013-04-13 23:19 Kloot Note Added: 0010443
2013-04-13 23:20 Kloot Note Edited: 0010443 View Revisions
2013-04-14 00:31 FLOZi Note Added: 0010445
2013-04-15 19:16 FLOZi Note Added: 0010461
2013-04-15 20:35 Kloot Note Added: 0010462
2013-04-16 17:48 Kloot Changeset attached => spring develop 862ae4cc
2013-04-16 17:48 Kloot Assigned To => Kloot
2013-04-16 17:48 Kloot Status new => resolved
2013-04-16 17:48 Kloot Resolution open => fixed
+Issue History