[Trigger] Facing Degree Help

[Killzerker]

Hi, Im currently working a spell where a unit casts on another unit which summons up a dummy unit to do a shockwave. The problem is I cant get the facing degree right, I want the dummy unit to cast the shockwave where ever the caster is facing. Can anyone help me?

 

[CoolSoFar]

Don't really get it, is this what you want??

E-
A unit cast a skill
C-
Skill casted equal to Dummy Shockwave
A-
Set [Casting Unit] = siA
Set [Targeted Unit of Ability being Cast] = siB
Create 1 Dummy at position of siA using facing of siA
Issue [last created unit] to Shockwave position of siB
Remove [last created unit]

or this one??

E-
A unit cast a skill
C-
Skill casted equal to Dummy Shockwave
A-
Set [Casting Unit] = siA
Set [Targeted Unit of Ability being Cast] = siB
Create 1 Dummy at position of siB using facing of siA
Issue [last created unit] to Shockwave position of siB offset by 200 from facing of siA
Remove [last created unit]


which mean casted to range of 200 from your hero facing

 

[Killzerker]

It was the first one, thank you so much!

 

[PurplePoot]

By the way, you may want to clean up those narsty leaks, Cool.

 

[Deep Sea Kraken]

I could be wrong here, but if you use triggering unit and stuff like that and no variables you WONT get leaks?

And cool your ability will make the targeted unit shockwave the casting unit.
Do this instead
E-Unit begins the effect of an ability (begins casting can be maninupalted if you know how)
C-Ability Being cast equal to Shockwave [dummy]
A-
Unit - Create 1 Dummy Caster for (owner of casting unit) at postion of (casting unit
Unit - Add Shockwave [dmg] to (last created unit)
Unit - Order (last created unit) to do (Tauren Chieftan - Shockwave [could be dread lord - carrion swarm though]) to (postition of targeted unit)
Unit - Add a 1 second generic expiration timer to (last created unit)

 

[CoolSoFar]

Say it multiple times to you Purple, I just beginner in WE and don't know anything about programming.. I just always test any trigger that I want to so I have some intelligent about it but terribly sorry I still can't fix leaks...

I recommended myself to begin fixing, learn GUI than learn JASS but I can't... My body too lazy for it

 

[PurplePoot]

Here we go, leak fixing isn't all that hard.

Instead of just using a trigger such as

• Don't Fix Leaks
  • Events
    • Unit - A Unit Dies
  • Conditions
  • Actions
    • Unit - Create 1 Footman for (Owner of (Triggering Unit)) at (Position of (Triggering Unit)) Facing 0.00 degrees

do the following (where loc is a global Point variable)

• Fix Leaks
  • Events
    • Unit - A Unit Dies
  • Conditions
  • Actions
    • Set loc = (Position of (Triggering Unit))
    • Unit - Create 1 Footman for (Owner of (Triggering Unit)) at loc Facing 0.00 degrees
    • Custom script: call RemoveLocation( udg_loc )

 

[CoolSoFar]

Here we go, leak fixing isn't all that hard.

Instead of just using a trigger such as

• Don't Fix Leaks
• Events
• Unit - A Unit Dies
• Conditions
• Actions
• Unit - Create 1 Footman for (Owner of (Triggering Unit)) at (Position of (Triggering Unit)) Facing 0.00 degrees

do the following (where loc is a global Point variable)

• Fix Leaks
• Events
• Unit - A Unit Dies
• Conditions
• Actions
• Set loc = (Position of (Triggering Unit))
• Unit - Create 1 Footman for (Owner of (Triggering Unit)) at loc Facing 0.00 degrees
• Custom script: call RemoveLocation( udg_loc )

Purple I do the thing you write down if that's the mean of fixing leaks but I didn't write the >>
Custom script: call RemoveLocation( udg_loc )

What does it use to be??

 

[PurplePoot]

If you don't add that, it doesn't remove the location, and thus it still leaks

(if that's what you're asking)

 

[CoolSoFar]

so all I must do from now is make an Custom Script trigger and write call RemoveLocation( udg_loc )??

If I only forgot these at all my trigger than I can fix all leaks from now on

 

[PurplePoot]

well, udg_loc if the point-type variable is called loc.

If you named your Point variable Cheese, it would be

call RemoveLocation( udg_Cheese )

Get the idea?

 

[Equal]

Here we go, leak fixing isn't all that hard.

Instead of just using a trigger such as

• Don't Fix Leaks
• Events
• Unit - A Unit Dies
• Conditions
• Actions
• Unit - Create 1 Footman for (Owner of (Triggering Unit)) at (Position of (Triggering Unit)) Facing 0.00 degrees

do the following (where loc is a global Point variable)

• Fix Leaks
• Events
• Unit - A Unit Dies
• Conditions
• Actions
• Set loc = (Position of (Triggering Unit))
• Unit - Create 1 Footman for (Owner of (Triggering Unit)) at loc Facing 0.00 degrees
• Custom script: call RemoveLocation( udg_loc )

PurplePoot can you explain me this? i dont get it why a shorter function that
doesnt use variables nor a costomscript cause more leaks than a 3 line function that needs a
variable and a script?

 

[PurplePoot]

When a Point (location) is created in Warcraft III, it allocates memory space for it. (among with many other types)

Whenever you need to access that Point, it searches for it, then returns what you need.

However, it will remember that point forever unless you manually delete it, thus sucking up CPU speed.

Eventually, these Points build up and cause lag.

RemoveLocation essentially tells wc3 to free up that point's memory from the memory space, so it can be used for other things, and not uselessly suck up CPU speed.

 

[Equal]

this would mean for every time a unit dies the memory will be filled a bit til i cant do nothin anymore? .... k good to know so this is how to fix that leak .... thx

 

[PurplePoot]

No, it doesn't, as a unit that dies will eventually be removed by the game (I think it's 40 seconds, except for heroes of course)

But creating dummy units over and over can cause that kind of lag buildup. Same with Points (as stated), Unit Groups, Player Groups (except All Players), etc

 

[Equal]

so to fix this, no matter of unit , player groups etc just remove or destroy it
to prevent leak...
btw if i add life time to a unit does the unit will be removed or still "stay in
memory"...

 

[PurplePoot]

If a unit dies, it is cleaned up after around 40 seconds.