[Trigger] removing this array point custom script

[oxxo]

to clean leaks

the point was set by using this trigger

• Set DU_frostbeampointholder[(Player number of (Owner of (Triggering unit)))] = (Target point of ability being cast)

so what is the custom script that removes it?

please only post if you are sure it is correct, since i have no way to testing if the script i copy paste from you is correct and i really want to have a leakfree map.

thx

 

[Dr Super Good]

set index = (Player number of (Owner of (Triggering unit)))

call RemoveLocation(udg_DU_frostbeampointholder[udg_index])

index is a global integer.

 

[13ack.Stab]

Now I'm curious as to whether I'm removing certain leaks correctly.

If I had a leak like this:

• Set SpawnCreeps_Points[0] = (Center of RSpawn 1 <gen>)
• Set SpawnCreeps_Points[1] = (Center of RSpawn 2 <gen>)

Would this effectively remove the leak?

• Custom script: call RemoveLocation(udg_SpawnCreeps_Points[0])
• Custom script: call RemoveLocation(udg_SpawnCreeps_Points[1])

 

[GhostWolf]

Yes, and this was asked at least 300 times...

 

[oxxo]

sry =P

thanks alot

hm sry but in order to keep the trigger mui i can not use the method you guys provide. i cant store the player number as "index". i need to get the player number from inside the remove function.

would this work ?

• call RemoveLocation (udg_POINT[GetPlayerId(GetOwningPlayer(GetTriggerUnit()))+1])

 

[Element of Water]

You can store the player number as "index". It will cause no problems since you won't need to use a wait after it. But yes, your example will work.

 

[Dr Super Good]

You simply use it like a local variable, you temporarly asign it a value and then use it. After a wait action you can then reasign it a value incase it has changed and so continue using it.

 

[GhostWolf]

No, those are GUI functions.
Put them in some trigger, convert it to custom script and see what it looks like in Jass.

 

[Element of Water]

He already has done...