[Trigger] kill\explode\remove

[darkrider]

ive been searching in internet for a good explanation about this.. and i only got more confused than what i used to be

so... i need some nice person to explain... which is the best way to remove a unit from the MEMORY... kill unit leaks... i know... but ive seen somewhere that remove also leaks... how about hide unit,Explode unit? or just explode?...

Thx in advance ^^

 

[Need_O2]

Make unit not decay and not revivable
hide and kill it
it will be in memory for some time
but it will get repleaced after some seconds

and HINDYhat sais Remove Unit is not safe about leaks

 

[darkrider]

how about units that i want to be revivable if chosen ... but i want to remove them if they are not?

and...whats the use for explode units then?

srry for my nw questions

 

[raft_pl]

As its stated in its name, it explodes unit. When Blizz was creating W3, nobody knew that leaks exist ; o

You'd check if unit is revivable and if its not = remove it/do what O2 said. Im not sure if there is a condition checking if unit is revivable, though.

 

[PurplePoot]

raft, people have known that leaks exist for ages, they're a basic programming concept. It's just that most languages have garbage collectors to deal with that sort of garbage, or only work in primitive types which don't need to worry about it.

Anyways, RemoveUnit doesn't directly leak, but it isn't safe due to the fact that it doesn't fire death events (though Kill+Remove will).

KillUnit is fine, but the unit takes a while to decay.

SetUnitExploded effectively skips decay upon KillUnit, and changes the death animation to a blood splash.

 

[darkrider]

so.. instead of changing the decay and revivable thing... i should just kill+remove it?

am i correct?

 

[Just_Spectating]

it would have to be like, checking when the unit has <10 hp or something.

 

[darkrider]

so... if i hide then kill then remove... would be ok