[General] AoE Range starts at unit or at unit's...

[Ramsey]

In object editor, when changing the AOE of an ability

Lets say the units collision size is 50 and the AOE of warstomp is 300

Does the ability's final AOE stay at 300 from the point of the unit or does it become 350 because its 300 + 50 of the collision size?



Because I have a spell that does 300 aoe and a trigger that creates something at 300 aoe but it doesnt look equal, the trigger looks like its doing it at something less than 300range

Thanks

 

[Nichilus]

I think collision size doesn't add to spell range, never tested it though.
However this would explain why it may seem smaller to you, as the caster himself takes some space, so it leaves less space for enemies to get caught in the spell.

 

[IcemanBo]

I think not. But you can simply test these things. Create a unit with offset 330 of your unit then you cast your ability.

 

[Ezekiel12]

Hardcoded abilities take collision size of targets into account. You can see this very easily by giving a unit a huge collision size and then hover near it with the targeting circle of e.g. blizzard.
Triggers on the other side do just use a units center.

 

[Ramsey]

thanks guys and thanks ezekiel

It makes sense though because if a giant unit's collision size is 500 and his warstomp is normally 300, it makes sense to be 300 on top of the collision size because otherwise he wouldnt even be able to damage units

 

[Ezekiel12]

It makes sense though because if a giant unit's collision size is 500 and his warstomp is normally 300, it makes sense to be 300 on top of the collision size because otherwise he wouldnt even be able to damage units

No, youre understanding this wrong. The targets collision size counts, the collision size of the caster doesnt matter.

(For attack range both collision sizes are taken into account though)

 

[Adiktuz]

The caster's collision doesn't matter, the AOE is picked from it's center/origin... from there collision is checked using the AoE and each target's collision size...

example:

Unit B = 500 collision radius, center/origin is 1000 units away from Unit A, Unit A casts a 600 radius war stomp. Unit B will still be hit since his bounds is just 500 units away from A (1000 - 500)

now on your case of a 300 AoE war stomp casted by a unit that has 500 collision, then you really won't hit any unit unless that unit has collision off so he can go "inside" your unit

 

[Ezekiel12]

now on your case of a 300 AoE war stomp casted by a unit that has 500 collision, then you really won't hit any unit unless that unit has collision off so he can go "inside" your unit

Collision size is only loosely tied to the actual pathing (square) which stays the same size for higher collision values. So you can happily walk "inside" a unit with 500 collision size.

 

[WaterKnight]

You can use
constant native IsUnitInRangeXY takes unit whichUnit, real x, real y, real distance returns boolean
to determine if a unit is within a circle while considering its collision size.