Timer block won't turn ON/OFF sensor and other blocks.

[Sir_Ninonino]

I want to make a secret door mechanism with sensors. Part of this mechanism involves "Sensor 1 (S1)" triggering a timer block that turns "Sensor 1" OFF and turns "Sensor 2 (S2)" ON to then, after the set delay, turn "S1" back ON and "S2" back OFF. When I trigger "S1" the timer block gets activated but will not carry out any truning ON or OFF of "S1" or "S2", only sometimes it will simply turn "S2" OFF if I had left it ON myself. The timer block is working though, as I tested if it could trigger actions or turn ON/OFF other blocks and did (except the turn ON/OFF, some other blocks didn't get affected just like the sensors). Is this a bug or am I missing how something works? Please help.

[Nightwing]

Did you set the actions to absolute, or did you set them to toggle?
If you look at the setup menu, you'll notice that three of the options should look something like this:
Toggle Block On/Off
Turn Block On
Turn Block Off
If you used that first one, that's your issue. If you used the last two, though, I'm not sure what's going on.

[Sir_Ninonino]

Originally posted by Nightwing:

Did you set the actions to absolute, or did you set them to toggle?
If you look at the setup menu, you'll notice that three of the options should look something like this:
Toggle Block On/Off
Turn Block On
Turn Block Off
If you used that first one, that's your issue. If you used the last two, though, I'm not sure what's going on.

I used the last two. In the timer block I have set in the "first toolbar" to:
S1: Toggle OFF - S2: Toggle ON
And the second to:
S1: Toggle ON - S2: Toggle OFF
Delay is 5 sec.

I'm playing in a creative world I use for testing. No block limits. Barely built in it though. Experimental ON. Only mod is EasyInventory. Game version 1.189.044. (Writing this in case anything might be of importance)

[Sir_Ninonino]

Ok, I think I got and it was just me being dumb. I'm using one timer block. I though one could time serveral events because of the serveral toolbars (and, unless I'm going crazy or amnesic, I once did use only one timer to make a piston go backwards and then forwards again just one cicle with the delay) but apparently it doesn't. The toolbars are there simply to have more events for just one block. Correct me if they changed it. But I guess I'll just have to use several timer blocks.

Sorry for my mistake and thanks for your time.

[Nightwing]

That must be your issue, then. Timer blocks are more like delay gates in functionality. Basically, you'll set up an action to occur after X amount of time. For actions that involve multiple steps, though, you MUST have multiple timer blocks. Basically, set it up in such a way that step one of your process triggers step two, step two triggers step three, on and on like that. Whenever I do something that requires multiple steps, I always like to put the timer to trigger the next step in the last slot.

You should also keep in mind, that actions activate on the falling edge of the timers. What I mean by that is, that if you have a process that requires step 2 to be taken 30 seconds after step 1, then the 30 second delay MUST be on the second timer block. The first one can be instant after activation if you want, but any actions you want to take only occur AFTER the timer on the trigger block expires, not as soon as the block gets activated.