Sarched forum but couldnt find
Is there a way to trigger a rule x seconds
after another rule has triggered?
Timed Trigger
Also keen on an answer to this one 
Anyone??
edit: Idea - if it was to place a bet that I wanted to green up at a certain time after the bet places, could I use the 'fill or kill bet time condition'? And, If the bet fills immediately, does that still mean it's an 'active' fill or kill' bet?
Thanks
Anyone??edit: Idea - if it was to place a bet that I wanted to green up at a certain time after the bet places, could I use the 'fill or kill bet time condition'? And, If the bet fills immediately, does that still mean it's an 'active' fill or kill' bet?
Thanks
I just worked this one out myself. Well, actually from an example Dallas posted
Set a signal on the first rule then use a Signal Changed Condition in your second, referencing the first signal changed timing
https://www.betangel.com/user-guide/signal_changed.html#
Set a signal on the first rule then use a Signal Changed Condition in your second, referencing the first signal changed timing
https://www.betangel.com/user-guide/signal_changed.html#
-
ShaunWhite
- Posts: 10470
- Joined: Sat Sep 03, 2016 3:42 am
If you increment a signal at 1 second intervals it basically becomes a timer.
Do it in such a way that that incrementing only happens once a bet has been placed.
Add a condition to your closing bet to only fire if the timer is > x seconds
So, something like......
Initialise a timer signal to a value of 0 (do this once).
When you place your bet, do so only if the timer signal = 0, and then increment the timer signal (it now becomes 1).
Then have a rule that just increments then timer signal at 1 second intervals if it's not zero. (you'll notice that setting the signal to 1 when the bet was placed above, starts the clock running).
Add a condition to your closing bet to only fire if timer signal is above x seconds ....and to reset the timer signal to 0 if you plan to repeat the whole process.
There's probably several other ways, but that's one....don't use it verbatim it's just an idea you'll need to incorperate into whatever other condition and rules you have. It's a while since I used Guardian but I seem to remember having a bot that used 4 or 5 timers controlled like that so it works in principal.
Do it in such a way that that incrementing only happens once a bet has been placed.
Add a condition to your closing bet to only fire if the timer is > x seconds
So, something like......
Initialise a timer signal to a value of 0 (do this once).
When you place your bet, do so only if the timer signal = 0, and then increment the timer signal (it now becomes 1).
Then have a rule that just increments then timer signal at 1 second intervals if it's not zero. (you'll notice that setting the signal to 1 when the bet was placed above, starts the clock running).
Add a condition to your closing bet to only fire if timer signal is above x seconds ....and to reset the timer signal to 0 if you plan to repeat the whole process.
There's probably several other ways, but that's one....don't use it verbatim it's just an idea you'll need to incorperate into whatever other condition and rules you have. It's a while since I used Guardian but I seem to remember having a bot that used 4 or 5 timers controlled like that so it works in principal.
Thanks for replies.
Yes signals has resolved it.
So first rule triggers , then x seconds later triggers again
it has an increment signal value which is therefore =2
The delayed 2nd rule that can trigger now has condition that
rule 1 signal value=2
EDIT
I initially spent hours working on this
therefore
Its one small step for automation
and one giant leap for mankind
Yes signals has resolved it.
So first rule triggers , then x seconds later triggers again
it has an increment signal value which is therefore =2
The delayed 2nd rule that can trigger now has condition that
rule 1 signal value=2
EDIT
I initially spent hours working on this
therefore
Its one small step for automation
and one giant leap for mankind