mcgoo wrote: ↑Wed Sep 19, 2018 9:53 pm
Thanks for that Dallas. So that would only work if the fav appeared in row 2? How do you track all the runners and bet only on the fav..or have I missed something? The other problem I can see with what I had in mind is if you want to have different conditions for different race lengths (to act at specified times during the race) you need a separate rule for each race length and a separate rule for each row, which would mean I have 250+ rules
...not easy this stuff
You just need to duplicate the rule and apply each one to a Betfair row index, then on the stored value tab change the stored value entered amount to correlate with the Betfair row
rule 1 Applied to Betfair row 1 uses SV amount entered 1
rule 2 Applied to Betfair row 2 uses SV amount entered 2
and so on
If you ran the automation file on its own and looked at the log what you'd see is when the runner in row 1 is fav the SV will show as 1
if the runner in row 4 became fav then the SV will show as 4 (and 1 would be cleared)...... this will go on throughout the race.
**Actually thinking about it it would show which runners became fav and for how long and how many times it changed etc so a bit of data collecting)
Anyway, if you then duplicate the rules in the bet file (and change the SV in conditions to match the rows) it's basically doing the same thing but the condition is testing the SV from above match the row this fav is in this market
For example
if the fav is in row 4 in the win market the bet will trigger only if the currently stored value from the place market is 4 (ie, the fav is in row 4 of the place mkt)
if the fav is in row 7 in the win market the bet will trigger only if the currently stored value from the place market is 7 (ie, the fav is in row 7 of the place mkt)
Or vice verse depending which way around you apply the files.