(In the context of a Horse Racing In-Running bot)
How can I achieve this?
Cheers
(SOLVED) Prevent bot from placing bets on photo market
you could of course set that same rule up, but only have it armed from 20-30 seconds out...
I think the market gets suspended before a photo finish so if you have a signal increment with a unsuspended time condition then you can place your bets contingent on signal < 2, or something like that.eightbo wrote: ↑Fri Jun 14, 2019 5:16 pmWell I thought to set a stored value RaceEnded = 1 when Time since unsuspended > 1s and have my bets fire if RaceEnded = 0 but it's always going to instantly fire because the mkt suspends when it goes In-Play, unless it will work on a rule which arms 5s after In Play has started?
I've done it before, there's a way to do it based on number of times it's been suspended. Try it out.
Yes just had a look, I set a signal to increment at unsuspended time condition = 1 while in-play, so when it's = 2 then it's likely a photo finish.sa7med wrote: ↑Fri Jun 14, 2019 5:20 pmI think the market gets suspended before a photo finish so if you have a signal increment with a unsuspended time condition then you can place your bets contingent on signal < 2, or something like that.eightbo wrote: ↑Fri Jun 14, 2019 5:16 pmWell I thought to set a stored value RaceEnded = 1 when Time since unsuspended > 1s and have my bets fire if RaceEnded = 0 but it's always going to instantly fire because the mkt suspends when it goes In-Play, unless it will work on a rule which arms 5s after In Play has started?
I've done it before, there's a way to do it based on number of times it's been suspended. Try it out.
Yeah stewards/photo both should be avoided for this bot.
I was checking unsuspended time was greater than a number and completely forgot about equal to, which was the solution.
Now I need to figure out why my bets are triggering but not showing up in the log, any ideas? (Trying to test it in prac mode)
I was checking unsuspended time was greater than a number and completely forgot about equal to, which was the solution.
Now I need to figure out why my bets are triggering but not showing up in the log, any ideas? (Trying to test it in prac mode)
i think my thinking was that that by going way out to 20 seconds before arming, then you could be sure that you'd skipped that little crossover point at the start. the 1 second comparison would only be valid after the race was IP for at least 20 seconds... just a throw away thought
Do you have 'export reports on market closure' ticked on the Advanced Settings Tab?eightbo wrote: ↑Fri Jun 14, 2019 5:30 pmYeah stewards/photo both should be avoided for this bot.
I was checking unsuspended time was greater than a number and completely forgot about equal to, which was the solution.
Now I need to figure out why my bets are triggering but not showing up in the log, any ideas? (Trying to test it in prac mode)'
I do. No sign of any back bets in the log.
It's worth noting that when my back bet triggers it sets a stored value which I've set to show up in the log and I can see that just no evidence of the back bet. Any ideas?
Yeah I had the same line of thought thanks for input tho. Must mean unsuspended time variable is still incrementing behind the scenes until it's called for which makes sense.jimibt wrote: ↑Fri Jun 14, 2019 5:32 pmi think my thinking was that that by going way out to 20 seconds before arming, then you could be sure that you'd skipped that little crossover point at the start. the 1 second comparison would only be valid after the race was IP for at least 20 seconds... just a throw away thought