[General] Remove Unit

[Chaosy]

I want to kill a unit without the body decaying on the ground.

1. Using the remove unit leaks
2. expiration timer shows decay
3. I cannot use object editing because I want to kill a genetic unit like the footman/rifleman.

I was thinking that hiding the unit on death, maybe that would also hide the decay effect?

 

[DarcReaver]

Cant you simply use "make unit explode on death" ? Exploding units don't create corpses/decay aswell...

 

[EdgeOfChaos]

But then they explode.
I've never heard of remove unit leaking

 

[DaneTheBeast]

Maybe set the gameplay constant to 0?

 

[Dr Super Good]

1. Using the remove unit leaks

Actually it is removing any unit leaks. Or in other words units always leak. This was tested long ago so it is possible it has been fixed in 1.28. Basically if a unit gets removed by decaying, exploding or by RemoveUnit call it always leaves something in memory.

This leak can be considered trivial. It takes well over 10,000 units before it even starts to be considered problematic, and if your map uses so many units chances are the problem is with your map design and not units leaking. If one needs to create a lot of dummy units for triggered abilities then consider recycling the dummies rather than making them new each time. Simply caching a few of each type of dummy unit is more than enough for 99.9% of play cases the dummy is needed.

I was thinking that hiding the unit on death, maybe that would also hide the decay effect?

It might pause decay by removing it from appropriate sub systems, thus making an actual unit object leak and not some leftover memory from a unit object.

 

[Athur12A2]

Wouldn't reducing art-death time and setting combat-death type to cant raise, cannot decay work?

 

[Dr Super Good]

Wouldn't reducing art-death time and setting combat-death type to cant raise, cannot decay work?

Not any better than RemoveUnit. Also he wants to avoid modifying so many fields of standard units.

 

[Chaosy]

Maybe set the gameplay constant to 0?

No. This would affect other units as well.

Actually it is removing any unit leaks. Or in other words units always leak. This was tested long ago so it is possible it has been fixed in 1.28. Basically if a unit gets removed by decaying, exploding or by RemoveUnit call it always leaves something in memory.

This leak can be considered trivial. It takes well over 10,000 units before it even starts to be considered problematic, and if your map uses so many units chances are the problem is with your map design and not units leaking. If one needs to create a lot of dummy units for triggered abilities then consider recycling the dummies rather than making them new each time. Simply caching a few of each type of dummy unit is more than enough for 99.9% of play cases the dummy is needed.

It might pause decay by removing it from appropriate sub systems, thus making an actual unit object leak and not some leftover memory from a unit object.

But then they explode.
I've never heard of remove unit leaking

Well in GUI we always use the expiration timer instead of the remove unit, thought it was because it leaked.

 

[Dr Super Good]

Well in GUI we always use the expiration timer instead of the remove unit, thought it was because it leaked.

Expiration timer is used so that a unit exists for a short period before removal. Otherwise one needs to maintain a reference to the unit and then remove it later.

 

[Chaosy]

Oh, ok. So I can safely use remove unit then, nice.

 

[streetpunk]

I would go for "hide unit", specially if you want to recycle them later...

 

[Callahan]

Change death type in object editor?