Range + Acquisition

2 problems i've been having:

1) It seams that certain units have a maximum range, and even though i set it to 5000 or something, it still only goes up to a certain amount when I test the map. The maximum veries for different units. Why is this? How do you change it?

2) I set my unit's acquisition range a really low number, and still they seam to automaticly accumilate targets. At 0 the acquisition range always seams to be really high. How do I make it so that a certain unit wont automaticly accumilate a target?

Generally in Warcraft III using the value 0 means unlimted. Or max I supose you could say. Use .01 to get the smallest possible value.

I'm having some trouble with this too. At one point I got an aquisition range of 65 to work, but now it doesn't... I'm pretty confused.

I *think* it got bugged somehow... I remember you could limit theunit's ability of auto-acquireing targets by reducing it's acquisition range with triggers, but when I tried to use it recently for something it didn't work.

The first problem is with object editor's acquisition range. The range you set there will not only limit the unit's ability to auto acquire targets, but the whole attack range as well. You must increase that acquisition range together with the attack range.

I fixed a typo in my triggers, and I think I get everything now:
The aquisition range in the unit editor has to be the same or higher than the attack range. If you want the lowest aquisition range possible, change it to 65 with triggers (it's the lowest value I could find that works, 64 didn't work). Hope that helps =)

If the acquisition range is lets say, 500 and your range is, 1000. Your range will be 500.
If your acquisition range is 1000 and your range is 700. Your range will be 700
If your acquisition range is 400 and your range is 400. Your Range will be 400

Yeah. I think the others covered this already, but the acquisition range is also the limit to your range. Your range may only be lower, or equal to the acquisition range for it to work.

Are you sure that, once a unit has acquired a target, it can't fire upon that target once it gets past its acquisition range?

For example, if a troll has a 700 range and a 300 acquisition, if a weasel comes within 300, the troll will throw an axe at it. However, if the weasel moves out of 300, won't the troll continue throwing at it until it goes outside of 700, at which point the troll will pursue the weasel?

I'm 80% sure =D. In my TD the acquisition range was 700 and range 1500 but clearly it stopped when the other towers did (other towers had 700 range)

so if you check the units range (in-game) it is, (taking your example) 300.

Right. Since there seems to be some confusion about this:

Situations:
1: Target inside attack range, but OUTSIDE aquisition range: Unit will ignore target unless you order it to attack, in which case it will run until the target is INSIDE aquisition range, THEN attack.

2: Target inside attack range and inside aquisition range: Unit will automatically attack target.

3: Target inside aquisition range, but OUTSIDE attack range: Unit will automatically run until target is INSIDE attack range, THEN attack.

4: Target OUTSIDE aquisition range, and OUTSIDE attack range: Unit will ignore target until ordered to attack, in which case it will run until the unit is inside both aquisition and attack range, THEN attack.

I think the biggest problem with acquisition range, that which causes most misunderstandings and confusion, is that the acquisition range you set in the object editor and the acquisition range you modify with triggers do not appear to be the same thing.

Acquisition range you set in the object editor will function like Hyarion explained. Acquisition range changed with triggers will operate like Panto anticipated. These are the conclusions I got from extensive testing a while back, however, my more recent attempts to modify acquisition range with triggers didn't work so well... it either got bugged with a recent patch, or I was giving it wrong values (in earlier test, I was usualy setting the acquisition range to a value about half of the units normal attack range, this time I was trying to set it to something near 0), anyway the unit ignored what I did and behaved as usual.

seeing as most units have a collision radius of 32, then they have a 64 diameter circle around them. This might be why a unit with an aquisition range of 64 or less cannot attack - which means that the aquisition range in the editor is the radius, as the units need 32 for the unit attacking, 1 for the gap, and 32 to get to the attack unit, making a minimum of 65. Maybe the game detects this and ignores the trigger if it is less that 65 anitarf - check if 65 works to stop a unit attacking

Hmm, I would try that, but I have already deleted the old system and triggered a new one where I no longer use dummy unit attackers, but dummy unit projectiles, so the whole thing isn't relavant for me anymore.

Actually, if you upgrade range with an upgrade, it can still go past the aquisition range, right? So if you have a trigger that in the beggining of the game researches an upgrade that increases the range of X_unit up by 999.99 (aquisition range is .01), it would have a range of 1000 and not be restricted by aquisition range.

Correct me if I'm wrong, but I'm almost certain I'm correct.

Actually, if you upgrade range with an upgrade, it can still go past the aquisition range, right? So if you have a trigger that in the beggining of the game researches an upgrade that increases the range of X_unit up by 999.99 (aquisition range is .01), it would have a range of 1000 and not be restricted by aquisition range.

Correct me if I'm wrong, but I'm almost certain I'm correct.