trigger_relay and trigger_push Created 10 years ago2014-08-13 08:02:15 UTC by Chill it BanG

Hi, everyone!
I have a little problem with trigger_relay and trigger_push.
On Counter-strike map.

The situation:
I have made trigger_push, with targetname, speed and of course Yaw... it works. Lets call it "pusher".
But, I have a button, that triggers "pusher". Also button works, when I press it, "pusher" toggles - on/off.

But, I need it to be toogled off in round start (as I said, mapping for CS), so I added func_door outside of map (as always, if I need something to trigger in round start) that targets trigger_relay, let`s call it "relay", it`s target is "pusher", trigger state is off, but the problem is - despite of "off", it turns it on (if the button didn`t trigger "pusher" on previous round)!

Have any ideas?
I am too lazy to set up trigger_changetargets, but if noone knows I will have to do that :<
Also tried multisource, it had, the same effect...

EDIT: "pusher" has "Start Off" flag, since func_door isn`t triggered in very first round.

Is the multisource the buttons master?

When I tried with multisource it was "pushers" Master.
Button triggered multisource, but again, "relay" with trigger state off reacted like toggle. If multisource was off, it turned it on.

I even do not know what was the problem, made some kind of fix with trigger_changetarget, now if "pusher" is off, "relay", that should turn it off, gets fake target.

Anyway, I am still curious why trigger_relay with trigger state off worked like it had toogle state
Is there entities that are not supported with it? Should create some small test map...

try making the multisource the button's master.
So the button won't work unless the multisource is active.
Still have the button target the pusher.

Trigger relays always gave me trouble.

Yeah, but I need to disable pusher, not option to enable it (button)

The idea is that push is in front of button... like an force shield that does not let anyone reach the button, when it is activated. And it seems like with trigger_changetarget it is one of the easiest ways for me to control when it can / can`t be turned off.

Thanks for your replies, they helped a bit