Hi there
Can anybody help, I have managed to Clear stored values but how can I then reset stored values???
Cleared Stored Value then reset a Stored Value???????
If you still need the Stored values why are you clearing them with that signal rule?
To have them again you'd need to trigger the first rule, to do this you'd need to arm it more than once and add a signal set condition/s to test there are no signals set (you may have to add a few if you have multiple signal names)
To have them again you'd need to trigger the first rule, to do this you'd need to arm it more than once and add a signal set condition/s to test there are no signals set (you may have to add a few if you have multiple signal names)
sorry, mate, cant get my head around that one! this is what I am trying to do viewtopic.php?f=52&t=19554
I can send you the .baf file if you like
I can send you the .baf file if you like
Thanks, that makes it a little more clearer.billbo001 wrote: ↑Mon Sep 16, 2019 4:56 pmsorry, mate, cant get my head around that one! this is what I am trying to do viewtopic.php?f=52&t=19554
I can send you the .baf file if you like
In the .baf of the OP in the link it would lay the 2nd fav when its 150% above its SP,
Is it meant to place a series of lays as it drift? ie, at 80%, 110% and 130%
and then to pick up on this thread repeat that process if it comes back down to its SP but then begins drifting again?
sorry for the delay boss,
yes, so basically it will store the 2nd fav at BSP, then record 80%, 110%, 130% and 150% drift then lay a £2 liability, then stop (1 bet)
As it sometimes jumps to this 150%, getting to the finish of the race. I want it to reset the process if, the horse starts to go the other way i.e shorten in price, the stored values reset.
it might help, again the fine tuning of a price dashing to 150% drift then shortens and goes on to win the bloody race, everyone has been there before!!!
hope this is reasonably clear to you Dallas.........
yes, so basically it will store the 2nd fav at BSP, then record 80%, 110%, 130% and 150% drift then lay a £2 liability, then stop (1 bet)
As it sometimes jumps to this 150%, getting to the finish of the race. I want it to reset the process if, the horse starts to go the other way i.e shorten in price, the stored values reset.
it might help, again the fine tuning of a price dashing to 150% drift then shortens and goes on to win the bloody race, everyone has been there before!!!
hope this is reasonably clear to you Dallas.........
So the best way would be to set a signal on the market with your lay bet rulebillbo001 wrote: ↑Mon Sep 16, 2019 8:13 pmsorry for the delay boss,
yes, so basically it will store the 2nd fav at BSP, then record 80%, 110%, 130% and 150% drift then lay a £2 liability, then stop (1 bet)
As it sometimes jumps to this 150%, getting to the finish of the race. I want it to reset the process if, the horse starts to go the other way i.e shorten in price, the stored values reset.
it might help, again the fine tuning of a price dashing to 150% drift then shortens and goes on to win the bloody race, everyone has been there before!!!
hope this is reasonably clear to you Dallas.........
Then add a 'Checkpoint matched bets' rule which resets the stored values and clears the signal on market above
also add a 'Signal set condition' to test the signal on market is set (ie, it will only reset everything after the lay bet rule has trigger)
The number of times you then set this reset rule to trigger will be the number of times you can keep laying as it drifts back out again
Checkpoint rule
Signal condition needs to test for the signal named 'watchgain' to be set on the market and not the selection
On the signal tab of that rule it needs to clear that 'watchgain' market signal
Also required is a Stored value condition to test the last traded price is less than the stored value named 'SPdrift'
Or you might want to add another SV to your Store SP rule to store the actual SP of 2nd fav
If you do that on your checkpoint rule you can test the last traded price is less than actual SP (rather than using SPDrift)
Signal condition needs to test for the signal named 'watchgain' to be set on the market and not the selection
On the signal tab of that rule it needs to clear that 'watchgain' market signal
Also required is a Stored value condition to test the last traded price is less than the stored value named 'SPdrift'
Or you might want to add another SV to your Store SP rule to store the actual SP of 2nd fav
If you do that on your checkpoint rule you can test the last traded price is less than actual SP (rather than using SPDrift)