Hi, I wish to automate backing a horse when it drifts in-play and reaches a certain price. If I ask for the bet as soon as the race goes in-play I am subject to the price matching if there is a faller.
So I have automated:
Place a back bet
-conditions last traded price is greater than SP plus 20 ticks
and last traded price is less than SP plus 40 ticks
Will this avoid backing a horse if it falls? I'm assuming the price will have shot past these parameters.
Or is there a better way?
How to avoid backing a faller in-running
- MemphisFlash
- Posts: 2369
- Joined: Fri May 16, 2014 10:12 pm
how can you predict a horse will or will not fall. Impossible.
Just accept at some point you will have losers.
Just accept at some point you will have losers.
- jamesedwards
- Posts: 5574
- Joined: Wed Nov 21, 2018 6:16 pm
The last traded price of a faller will likely curve very quickly from current odds to 1000. It won't go straight from current odds to 1000.
So you would need to check prices in two separate steps. eg;
1) current price is above your set threshold
2) a second or so later, check that the price is lower than 1000.
Then place your bet.
So you would need to check prices in two separate steps. eg;
1) current price is above your set threshold
2) a second or so later, check that the price is lower than 1000.
Then place your bet.
- ShaunWhite
- Posts: 10725
- Joined: Sat Sep 03, 2016 3:42 am
If the price has massively drifted then your 2nd condition (ltp<sp +40) should stop it being placed.MIYAGI52 wrote: ↑Tue Apr 14, 2026 12:33 pmHi, I wish to automate backing a horse when it drifts in-play and reaches a certain price. If I ask for the bet as soon as the race goes in-play I am subject to the price matching if there is a faller.
So I have automated:
Place a back bet
-conditions last traded price is greater than SP plus 20 ticks
and last traded price is less than SP plus 40 ticks
Will this avoid backing a horse if it falls? I'm assuming the price will have shot past these parameters.
Or is there a better way?
- ShaunWhite
- Posts: 10725
- Joined: Sat Sep 03, 2016 3:42 am
2) and that the price > threshold still.jamesedwards wrote: ↑Tue Apr 14, 2026 1:35 pmThe last traded price of a faller will likely curve very quickly from current odds to 1000. It won't go straight from current odds to 1000.
So you would need to check prices in two separate steps. eg;
1) current price is above your set threshold
2) a second or so later, check that the price is lower than 1000.
Then place your bet.
Thank you. I've set a signal when the first threshold is met but wondered how I can check another threshold 2 seconds later.
ie signal set when price in-running is 20 ticks above SP how do I delay the next check that the price is 40ticks below SP or not trading at 1000?
ie signal set when price in-running is 20 ticks above SP how do I delay the next check that the price is 40ticks below SP or not trading at 1000?
It may occasionally go in your favour when a horse makes a horrific blunder and either nearly comes down or the jockey appears to be going out the side door only to recover. Some people have been matched at big odds and the horse has managed to recover and win.
- jamesedwards
- Posts: 5574
- Joined: Wed Nov 21, 2018 6:16 pm
There's lots of ways to do this.
Personally I prefer to add the creation of a stored value x =1 to the first trigger, then add conditions to the second trigger that the stored value x = 1 and has NOT changed in the last 2 seconds.
You do not have the required permissions to view the files attached to this post.
