I still cant believe This unit has no reference

[Bond009]

I cant believe when using the event (Unit - A unit comes within 400.00 of (some unit))
This unit has no reference.. You can reference the triggering unit getting in that distance but not the unit you get close too..

I think out of everything this is the one thing that annoys me the most with stupid limitations blizzard didn't add something for.

 

[Adiktuz]

I think it's because by default (without using things like Add Event) you can only set "some unit" to a specific unit so you should already know which unit was it...

 

[Bond009]

yea true but then in the actions based on that event you cant do anything with it easily.

 

[Binsu]

Yes, I am also thinking of this but doing this through Condition is possible: http://www.hiveworkshop.com/forums/graveyard-713/unit-within-range-169015/


It's no easy task creating a whole editor for me so there might be times that Blizzard committed some mistakes or rushed some parts.

 

[Adiktuz]

@bond - not really, since you will always have access to that specific unit's generated global variable after you chose it for the event (via the default method)... the only time you'd have problems is if you used the action "Trigger - Add Event" in order to use the Unit within range event...

 

[Bond009]

the only time you'd have problems is if you used the action "Trigger - Add Event" in order to use the Unit within range event...

there lies my problem lol

 

[Adiktuz]

you should probably just make a periodic trigger that checks if units are within range of another unit...

 

[Zwiebelchen]

you should probably just make a periodic trigger that checks if units are within range of another unit...

Which is basicly the same this event does anyway.

 

[Adiktuz]

Minus his main problem that apparently there's no handler for the Unit...

 

[Bond009]

Minus his main problem that apparently there's no handler for the Unit...

exactly.. like all these years and no one at blizzard once thought wow maybe a handler for this unit they get in range of would be nice. I mean common sense

And the work around im using for this is trash.. basically what im doing now is making a temp unit group to check if a unit matching the condition of that unit is in range when this event goes off.. so annoying

 

[vypur85]

> work around im using for this is trash..
Well, this is the best way to solve the problem.

> ...so annoying
I know... The feeling is mutual.

 

[Adiktuz]

well, I think they never thought that somebody would need actually set unit in range using the Add Event action... there are lots of things on the editor that doesn't make sense...

Plus, it was even stated on the editor itself that it is not directly supported by Blizzard, so it's not really surprising

 

[Zwiebelchen]

> work around im using for this is trash..
Well, this is the best way to solve the problem.

No it's not. The best way is to do a periodic "all units in range" check and not using the event.
There is no speed advantage in using that event over "all units in range", as the event basicly is a periodic "all units in range" check over an interval of 0.1 seconds anyway.

 

[vypur85]

> No it's not..
> ...not using the event.
Only if one insist to using the same event.

> ...periodic "all units in range" check over an interval of 0.1 seconds anyway.
This is new to me. Nice info.

 

[Bond009]

No it's not. The best way is to do a periodic "all units in range" check and not using the event.
There is no speed advantage in using that event over "all units in range", as the event basicly is a periodic "all units in range" check over an interval of 0.1 seconds anyway.

is that really true..? all the events in wc3 use time polling for their event checks and not interrupts? lmao so f'ing sad if that is the case..
I was under the impression it was more efficient because it was using interrupts.

 

[BPower]

There is a resource UnitInRangeEvent.
It stores the source unit or it's index on the trigger handle id on a Table.
source = table.unit[GetHandleId(GetTriggeringTrigger())]
source = GetUnitById(table[GetHandleId(GetTriggeringTrigger())])

There is no speed advantage in using that event over "all units in range"

I don't think that is true, I'll run some tests later.

 

[Zwiebelchen]

I don't think that is true, I'll run some tests later.

It might be a little bit faster, as JASS natives execute on a lower code layer and enuming units has to check for the filter aswell.

However, the difference will be very small.

 

[WaterKnight]

is that really true..? all the events in wc3 use time polling for their event checks and not interrupts? lmao so f'ing sad if that is the case..
I was under the impression it was more efficient because it was using interrupts.

Most events react instantly but this one is polled. I do not think it's as effective to do via periodics yourself, simply because the native implementations are faster than jass. You also need to manage a group per unit target because you want to trigger on entering of the range, not permanently while it is in.

Blizzard could improve a lot of obvious stuff if they actually cared about it. I doubt they have taken a second look on the implementations after the game was released. They never have shown any support for mapmaking and when you ask the tech support, they have no idea about the assets and ingame mechanics.

 

[Bond009]

some good info ill see if i can use that UnitInRangeEvent to make it better

 

[Cokemonkey11]

Step 1: Don't use GUI

Step 2: Don't not use things that aren't GUI