tigger_kill and / or trigger_remove

[GoogleCodeExporter]

Different from target_kill as target_kill requires a bot / player to touch it.

Allow for a targeted entity to be removed from the map when triggered.

Original issue reported on code.google.com by tigger...@gmail.com on 17 Apr 2011 at 3:19

[GoogleCodeExporter]

This may be best as an improvement to target_disable or target_kill. Maybe a 
spawnflag of 'remove' '1' to either of this existing ents would be better that 
adding another.

Original comment by tigger...@gmail.com on 17 Apr 2011 at 3:33

[GoogleCodeExporter]

The current implementation of target_disable links or unlinks an entity to or 
from the world, which basically means that if you target an entity, it is 
removed from the world when it's disabled. 

Try pointing a target_disable at a func_static and it will be removed. I 
haven't extensively tested the result of target_disable being aimed at various 
entities other than triggers, so funky things may happen, but it should work I 
think.

For a next release, I'll make or describe target_disable as a more generic 
entity that can be used in the way as described above.

Original comment by era...@gmail.com on 18 Apr 2011 at 7:32

[GoogleCodeExporter]

Original comment by era...@gmail.com on 18 Apr 2011 at 7:36

• Added labels: Component-Code

[GoogleCodeExporter]

target_disable is now called target_unlink. It's sole purpose is to remove 
entities from the world or put them back in. This makes the entity generic and 
its behavior is clearly defined.

Original comment by era...@gmail.com on 1 Jul 2011 at 1:49

• Changed state: Fixed