Attack Range of Unit

[Jay the Editor]

Is it possible, in trigger (no Jass/vJass scripts), that I get the value of the attack range of a unit?

Or any possible way to check the attack range of a unit?

 

[TwoVenomous]

Not possible.

But you can check the distances between attacking and attacked unit.

• Untitled Trigger 001
  • Events
    • Unit - A unit Is attacked
  • Conditions
  • Actions
    • Set tempPoint = (Position of (Triggering unit))
    • Set tempPoint2 = (Position of (Attacking unit))
    • Set Distance = (Distance between tempPoint and tempPoint2)
    • Custom script: call RemoveLocation(udg_tempPoint)
    • Custom script: call RemoveLocation(udg_tempPoint2)

 

[HesitationSnow]

If it's just one unit, you do this:

• Set Get_Attack_Range = ((Current acquisition range of Target_Unit) - 400.00)

In this example, the Target_Unit's Acquisition Range is 1000 and it's Attack Range is 600 (Which is why you subtract 400 here).

If it's lots of units, you must set acquisition range to be proportional to attack range so that you can subtract 400 to all or something like that.
If you don't want to make proportional, you can use unit point-values as a multiplier to calculate attack range (eg. Range = (Acquisition - 400 )(0.01 * unit point value)), or something along those lines.

 

[Jay the Editor]

Hmm.. I see. Then, is there any way to check range? Just like in Element TD; where you type "-range xxx", you can see the light there indicating the range of it from the unit that you select if I'm not mistaken.

 

[HesitationSnow]

Hmm.. I see. Then, is there any way to check range? Just like in Element TD; where you type "-range xxx", you can see the light there indicating the range of it from the unit that you select if I'm not mistaken.

Yup. Just do what I said. Use Acquisition Range.
Edit: I am suddenly confused.
Do you want to check for tower attack ranges? Or.... do you want a -range xxx indication trigger?

 

[Almia]

The one you are talking about in that TD is that the maker actually looked up inside the object editor,listed up units and their ranges and cached it like this:

• Set unit[1] = example
• Set range[1] = 600

or

• Set unit = example
• Set range = 600
• Custom script: call SaveReal(hash,unit,StringHash("range"),range)

 

[HesitationSnow]

Yeah, you can cache all of your units like that.
What I did when I coded for a TD before was set all tower Acquisition Range = Attack Range.
Here is a copy paste of Attack Range indicator spell on TD towers I made a while ago:

• Range Checker
  • Events
    • Unit - A unit Starts the effect of an ability
  • Conditions
    • (Ability being cast) Equal to Range Checker
  • Actions
    • Set Attack_Range = (Default acquisition range of (Casting unit))
    • Set NumberOfRangeIndicators = 20
    • For each (Integer A) from 1 to NumberOfRangeIndicators, do (Actions)
      • Loop - Actions
        • Set TempReal = (TempReal + (360.00 / (Real(NumberOfRangeIndicators))))
        • Set TempPoint = ((Position of (Casting unit)) offset by (Attack_Range + 50.00) towards TempReal degrees)
        • -------- I added extra 50 range because the dummies visuals were showing range to be slightly less than what it really was. --------
        • Unit - Create 1 DummyIndicator for (Triggering player) at TempPoint facing Default building facing degrees
        • Unit - Add a 4.00 second Generic expiration timer to (Last created unit)
        • Custom script: call RemoveLocation (udg_TempPoint)

For -range xxx trigger, the trigger is almost the same, but incorporate something like this to it:

• Set Attack_Range = (Real((Substring((Entered chat string), 8, (Length of (Entered chat string))))))

(why 8? because -range xxx : - = 1, r = 2, a = 3, n = 4, g = 5, e = 6, space = 7, integer value = 8 to end of chat string)

 

[Jay the Editor]

I see. Thanks a lot, both of you
Actually, at first I want to make a spell that check the attack range but then since there are researches in my map that increases the attack range of the towers so I decided to use command instead to check the attack range.

 

[Maker]

• Set TempPoint = ((Position of (Casting unit)) offset by (Attack_Range + 50.00) towards TempReal degrees)
• Custom script: call RemoveLocation (udg_TempPoint)

I can't help but inform that this leaks the position of casting unit. It is a common mistake.

 

[HesitationSnow]

I can't help but inform that this leaks the position of casting unit. It is a common mistake.

Thanks for pointing that out.
I do have tons of those leaks in many of my triggers to fix then.

Glad you found a solution Jay.
I hope that your command trigger for range check is working.