Recent rules (including this edit) have been done using V1.48.1
https://www.betangel.com/securedownload ... _beta1.exe
Signal when Goals are Scored Guardian Automation Bot
Hi Dallas. I'd like to place a back bet in the CS market after a goal, or more than one goal, has been scored. I have read through this thread and very much appreciate your efforts with the goals signals solutions here but I am concerned about the risk of using the historical relevant odds condition. The odds movements (and time duration of those movements) will differ each time a goal is scored and in different matches there will be different movements of odds (and different time durations). Add in the unpredictability of the timing of the suspended period in each case plus the red card risk and reliability would seem to be an issue?
Is there any future development of automation in the offing that might resolve this?
I will probably apply the back rule(s) manually as and when a goal is scored. What is the easiest way to do this? Add the rule(s) to the chosen matches in Guardian each time a goal is scored (seems a little cumbersome)? Or can they be added pre match and triggered when needed (manually)?
Many thanks
Is there any future development of automation in the offing that might resolve this?
I will probably apply the back rule(s) manually as and when a goal is scored. What is the easiest way to do this? Add the rule(s) to the chosen matches in Guardian each time a goal is scored (seems a little cumbersome)? Or can they be added pre match and triggered when needed (manually)?
Many thanks
The problem is Betfair dont make the live scores available via their API, once they do life will become much easier as a series of conditions could be added to the automation (practically overnight) the same as there is for tennis markets that would allow bets/trades to be triggered from them.
Until then the use of signals is the best work around. As you have not pointed out its not perfect and cant be used in every match as a blanket approach without some tweaking but with a bit of testing you can find a set of variables that will work 99% of the time in the match odds and over/under markets depending on the game your trading.
For example in a game with equally matched teams the draw odds will always drifts 10 or more ticks following a goal - however if one team is a strong fav and the underdog scores the draw odds will usually shorten slightly but certainly wont drift, therefore a different variable is required for these type of games.
The CS market is a little more difficult and tbh not one that i have traded much so im not overly familiar with how far the odds would move after a goal so to use signals on them would require a bit of testing to get right
Until then the use of signals is the best work around. As you have not pointed out its not perfect and cant be used in every match as a blanket approach without some tweaking but with a bit of testing you can find a set of variables that will work 99% of the time in the match odds and over/under markets depending on the game your trading.
For example in a game with equally matched teams the draw odds will always drifts 10 or more ticks following a goal - however if one team is a strong fav and the underdog scores the draw odds will usually shorten slightly but certainly wont drift, therefore a different variable is required for these type of games.
The CS market is a little more difficult and tbh not one that i have traded much so im not overly familiar with how far the odds would move after a goal so to use signals on them would require a bit of testing to get right
You can create a automation rule with your backs ready to place at best odds for your chosen liability on the score lines you want then just apply that rule to the market in guardian after a goal is scored (or whenever you want) and it will submit all bets for you
Yes, this would be as per my answer given on the 'Lay CS' thread where you would set a range up that the odds must be in and only the next unders would fall into that range
-
- Posts: 45
- Joined: Tue Dec 15, 2015 3:46 pm
Hi,
The attached automation file is generally working well.
I want to back at 15, 25, 35 mins and green up on a goal, or red up at HT.
It went in my favour today, but I don't understand why the FOURTH back bet below was placed.
Can any of you explain please?
Thanks,
Tim
13/08/2017 15:59:11: Guardian has detected that the market is in-play
13/08/2017 15:59:11: Guardian has detected that the market is suspended
13/08/2017 15:59:12: Guardian has detected that the market is now unsuspended
13/08/2017 16:14:17: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 2.68. Entirely unmatched when it initially reached the market. Ref: 99709970786
13/08/2017 16:24:17: [G_Auto] : £ 25.00 Back bet placed on Over 2.5 Goals at 3.5. Entirely unmatched when it initially reached the market. Ref: 99711701597
13/08/2017 16:34:17: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 4.5. Entirely unmatched when it initially reached the market. Ref: 99713456950
13/08/2017 16:36:04: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 4.6. Entirely unmatched when it initially reached the market. Ref: 99713799362
13/08/2017 16:42:17: Guardian has detected that the market is suspended
13/08/2017 16:42:22: Guardian has detected that the market is now unsuspended
13/08/2017 16:44:09: [G_Auto] : Automation Signal for market: goal = 1
13/08/2017 16:45:28: [G_Auto] : Greened up Over 2.5 Goals by Laying 100.32 at 2.34
13/08/2017 17:03:44: Guardian has detected that the market is suspended
13/08/2017 17:04:54: Guardian has detected that the market is now unsuspended
13/08/2017 17:48:27: Guardian has detected that the market is suspended
The attached automation file is generally working well.
I want to back at 15, 25, 35 mins and green up on a goal, or red up at HT.
It went in my favour today, but I don't understand why the FOURTH back bet below was placed.
Can any of you explain please?
Thanks,
Tim
13/08/2017 15:59:11: Guardian has detected that the market is in-play
13/08/2017 15:59:11: Guardian has detected that the market is suspended
13/08/2017 15:59:12: Guardian has detected that the market is now unsuspended
13/08/2017 16:14:17: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 2.68. Entirely unmatched when it initially reached the market. Ref: 99709970786
13/08/2017 16:24:17: [G_Auto] : £ 25.00 Back bet placed on Over 2.5 Goals at 3.5. Entirely unmatched when it initially reached the market. Ref: 99711701597
13/08/2017 16:34:17: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 4.5. Entirely unmatched when it initially reached the market. Ref: 99713456950
13/08/2017 16:36:04: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 4.6. Entirely unmatched when it initially reached the market. Ref: 99713799362
13/08/2017 16:42:17: Guardian has detected that the market is suspended
13/08/2017 16:42:22: Guardian has detected that the market is now unsuspended
13/08/2017 16:44:09: [G_Auto] : Automation Signal for market: goal = 1
13/08/2017 16:45:28: [G_Auto] : Greened up Over 2.5 Goals by Laying 100.32 at 2.34
13/08/2017 17:03:44: Guardian has detected that the market is suspended
13/08/2017 17:04:54: Guardian has detected that the market is now unsuspended
13/08/2017 17:48:27: Guardian has detected that the market is suspended
You do not have the required permissions to view the files attached to this post.
-
- Posts: 45
- Joined: Tue Dec 15, 2015 3:46 pm
Dallas,
Thanks again for the reply.
Yes, should be no reason for that third back to be placed twice with these conditions (since either there were unmatched bets, or the total matched was > £49.99).
Setting them to trigger only once is indeed safer, just wanted to be sure to get them all into the market.
Perhaps better to miss one going in than to have too many firing in.
Based on the file then would you say that this is a bug somewhere in the automation?
Tim
Thanks again for the reply.
Yes, should be no reason for that third back to be placed twice with these conditions (since either there were unmatched bets, or the total matched was > £49.99).
Setting them to trigger only once is indeed safer, just wanted to be sure to get them all into the market.
Perhaps better to miss one going in than to have too many firing in.
Based on the file then would you say that this is a bug somewhere in the automation?
Tim