1) It can just add it to the rule and it will auto select 'by position 1' as a default to begin with as that's who the rule is applied toubfxu wrote: ↑Thu Feb 18, 2021 10:16 pmComing back to this very useful Automation File. Been playing around with various Conditions - it is looking quite promising when applied to AUS Racing.Dallas wrote: ↑Sat Jul 30, 2016 7:48 pmHere you go, those instructions where given several months ago before the introduction of signals which is now a much better and cleaner way of achieving this so i have modified it slightly and used the signals to set a signal on the market and another on the actual 1st runner below 1.25 - the runners without this signal set which are also trading between 5.0 and 30.0 will then be layed.
I have only tested on 1 race but worked fine, let me know if you have any problems or there is something you dont understand.
Couple of things I wanted to check on.
1) What I want to do is to exclude any runners whose Actual SP is above or below a particular price.
Is the Actual SP available immediately when an event goes in-play? If so, then is it possible to include it as a Condition, eg:
Fixed Odds Condition - The Selections Actual SP <greater than/less than> x
and should I choose
"Current (ANY Selection)" OR "Nominated - Any Selection"
2) Just to cross-check that the above is working correctly (ie if its possible) - Does Betfair provide any results Service for UK/Irish Racing that shows the actual Betfair SP in Decimal Odds or Prices ?
and that will stop it triggering on any selection that was below your SP min
If you want to ensure it doesn't trigger on a short priced horse to begin or one with an SP just above where its going to trigger with you can use signals to exclude them
for example if you wanted it to avoid runner with a SP below 2.0
You'd add a Set/Modify Signal rule (applied to the fav) at 00:00:10 before post till 00:00:00 after post
and on the signal tab set a signal on the selection (giving it any name you want)
The add your fixed odds condition the Actual SP is greater than 2.0
Finally on the back bet rule add a signal set condition
to test the signal named (whatever you called it)
is NOT set with a value
ie, if it is then the fav had a SP below 2.0 and therefore the rule can't trigger on it
2) You can get all historical SP data from here
https://promo.betfair.com/betfairsp/prices
Or use this tool to download it from the same place in bulk
viewtopic.php?f=54&t=14395