Today the 17:15 Sandown race had the longest delay I ever seenDallas wrote:If your automation starts just before the race goes in-running using the 'Restrict Refresh' and setting to something like
20 secs before event start time
900 secs after event start time
Then on the main Guardian page set the 'Refrseh Interval' to 200ms
With that set up even on a busy day no more than 3-4 races should be getting refreshed at any one time and using 200ms thats still going to be at least one refresh every second for each market.
Laying the lowest selection.
95% of the time 900 secs will be more than enough but you can set the seconds for longer if you want extra security, obviously the longer the time used means more markets could be getting refreshed at the same times so they are being checked less often and rules could miss being triggered at the best time.
You can never truly account for everything, ie, in the NH races if there is a bad fall the remaining races at that meeting can be delayed upto 30 mins and this can play havoc with automation at times
Another way is to open a second instance of BA and put alternative markets into each, i do this on busy days so i can try and keep at least a 10 min gap between each off time.
You can never truly account for everything, ie, in the NH races if there is a bad fall the remaining races at that meeting can be delayed upto 30 mins and this can play havoc with automation at times
Another way is to open a second instance of BA and put alternative markets into each, i do this on busy days so i can try and keep at least a 10 min gap between each off time.
How to run a second instance of BA in the same device PC? I run a second instance of BA on 2 devices sometimes.Dallas wrote:95% of the time 900 secs will be more than enough but you can set the seconds for longer if you want extra security, obviously the longer the time used means more markets could be getting refreshed at the same times so they are being checked less often and rules could miss being triggered at the best time.
You can never truly account for everything, ie, in the NH races if there is a bad fall the remaining races at that meeting can be delayed upto 30 mins and this can play havoc with automation at times
Another way is to open a second instance of BA and put alternative markets into each, i do this on busy days so i can try and keep at least a 10 min gap between each off time.
I would like the automation bot to run in events with 8 or over selections, I need to add the same condition in rules one and two:
Volume condition
Is it the market or the selection to chose?
Greater than 7
Today some of the races the 3.0 lay bet don't get fully matched and when the bot cancels unmatched bets it cancel it too. how can I make sure that lay bet get fully matched.Dallas wrote:Volume is for money matched on a selection or market, 'Number of selections' is for how many runners are required
Can 'Cancel All Unmatched Bets In Market' leave the bet that is not fully matched and cancel the rest?Dallas wrote:If no one is willing to match it at the odds you want and have offered you would have to offer higher odds.
Condition
Matched Bet Amount Condition
total amount matched of your Lay Bet
equal to
the following fixed amount
£0
Can 'Cancel All Unmatched Bets In Market' in rule 3 leave the bet that is not fully matched and cancel the rest? I set up a condition below please review it and tell me if its correct or needs changing.Dallas wrote:If no one is willing to match it at the odds you want and have offered you would have to offer higher odds.
Condition
Matched Bet Amount Condition
total amount matched of your Lay Bet
equal to
the following fixed amount
£0
Thanks in advance.
Sometimes the lay bet don't get fully matched and when the trigger cancel all bets it cancels the one that didn't get fully matched too, I would like to cancel all bets without canceling the non fully matched bet, I was wondering if there is a condition to do that in the cancel all bets in the market rule.Dallas wrote:Im not 100% sure what your trying to do here but with that condition It would be better to use the rule type 'Cancel unmatched bets on Selection' and look at each selection individually.
This has happened every day.
Hi DallasDallas wrote:It would require 3 rules types to do this, the first rule type should be a normal lay bet applied to selection 'By Poisition (Sorted in order of favourtism) 1'
Armed 00:00:10 to 00:00:06
using the condtion
'Fixed odds Condition'
'Last traded price'
Is 'Less' than 3.0
Second rule type
Lay All selections at fixed odds of 3.0
Armed 00:00:05 to whenever you want
using the condtion
'Number of place bets condtion'
On 'Market'
is equal to '0'
Third rule type
Cancel all unmatched bets
Armed 00:00:04 to the same time as used for the rule above
using the condtion
'Number of Matched Bets Condtion'
On 'Market'
Is 'Equal' to 1
That should do it
I would need some help with the automation you helped me with shown above please.
I would like to add a forth rule to place a back bet in-play time only on the same selection that the lay bet was triggered in the first or second rule.
How will I let the automation know which selection to place the back bet?
Thanks in advance..
I have followed your steps on the back bet rule and its not working it never placed a back bet.Dallas wrote:On your back bet rule Add a the condition
'Number of Matched Bets Cond'
on 'Selection'
is 'Equal' to 1
I have attached the automation, please have a look and check it.
Its rule number 4.
Thanks in advance.
You do not have the required permissions to view the files attached to this post.
Its not even backing all selections, I followed the conditions to input in that rule and nothing is happening.Dallas wrote:Your 4th rule is Backing all selections not just the one with a matched bet
Have you checked the conditions of that rule, maybe I didn't do it correctly, please check.
