Jump to content

source I/O


Sentura

Recommended Posts

As it would require this entity to get the Kill Input from somewhere first before it could send its OnKilled Output, why don't you just take a func_brush and trigger your desired event with the same entity(-ies) that also Kill the brush?

Link to comment
Share on other sites

i considered that, but i wanted to incapsulate it better so that the trigger didnt know what the actual objects did, other than killing them. i worked around it, sending an OnFireUser output instead, and appropriately triggering the desired effect before using a Kill on !self.

this still fulfills the notion that the trigger does not know what each object does. this way, each object could easily be copy/pasted and retain same properties, only changing the name. i am just saying this for reference if anyone else would ever come in this situation.

Link to comment
Share on other sites

×
×
  • Create New...