Help attack range

[Mellstorm]

“I’m trying to set the attack range, but for some reason it doesn’t work. I’m confused that in the object editor it’s set through an integer, but in the trigger through a real number. And the line codes are different. What am I doing wrong?”

 

[Chaosium]

These new functions are quite inconsistent and some of them straight up don't work. You can try changing the Index as well (some start at 0, others 1)

Also remember that attack range cannot be higher than acquisition range, so maybe try changing this one first

 

[Pyrogasm]

One wholeass type category is fucked for GUI and in the trigger editor supplies the wrong list of codes (based on expected type) for the thing you want to modify. So you might be seeing that category; don't remember which it is off the top of my head. If you write some JASS code you can manually make lines to modify any field code you want, as well as fix the ones GUI can't use properly because of the editor mistakes. As Chaosium said many of the intended ones just don't work, so the likelihood of other random ones you define working is pretty low too but if it's the only option for you....

 

[Uncle]

You can adjust attack range using that function, it's just buggy. Also, you need to make sure you change Acquisition Range to always be >= to it.

[Snippet] Set unit range partial fix & Set unit AoE Small fix

Hello there, the native BlzSetUnitWeaponRealField (and BJ too) is bugged for setting the range (UNIT_WEAPON_RF_ATTACK_RANGE). ☼ Doesn't work for the weapon index 2 ☼ For weapon index 1, will add the new range minus the difference between the base value of weapon 1 and 2 Also some getter/setter...

www.hiveworkshop.com

 

[Mellstorm]

One wholeass type category is fucked for GUI and in the trigger editor supplies the wrong list of codes (based on expected type) for the thing you want to modify. So you might be seeing that category; don't remember which it is off the top of my head. If you write some JASS code you can manually make lines to modify any field code you want, as well as fix the ones GUI can't use properly because of the editor mistakes. As Chaosium said many of the intended ones just don't work, so the likelihood of other random ones you define working is pretty low too but if it's the only option for you....

the one who wrote about the fucking gui, let him give the code in jass.

 

[ThompZon]

What Uncle linked is probably the best solution.

If you're fine with having acquisition range equal to attack range, you can have acquisition range and attack range equal to highest possible range the unit can have, and then set acquisition range as the unit is spawned to what it's supposed to have "right now" and then use the acquisition range to modify to whatever it supposed to have. Lowest possible value is 64 IIRC.

And FYI: Acquisition range is the range to acquire a target and if longer than attack range, unit will move into range to attack said target.
(This is how I solved the "attack range issue" before knowing about the trick that Uncle linked).

 

[Pyrogasm]

the one who wrote about the fucking gui, let him give the code in jass.

So giving an incomplete answer is better? What exactly is your point here? There is no way to fix the GUI fields without using JASS, so if they want to do this they will have to. And you literally only have to use two custom script lines to read or set the field not make a wholeass JASS trigger.

 

[Remixer]

Also worth to note that the actual attack range of a unit cannot be higher than it's acquisition range, so you need to also increase acquisition range and only then any range increase would take place.