Signal when Goals are Scored Guardian Automation Bot

Post Reply
shakespeare
Posts: 113
Joined: Sat May 21, 2016 1:43 pm

Actually, there is one other potential problem with your bot. You are waiting for the market to have been unsuspended for 180 seconds. That seems too long to me. What could happen is that a goal gets scored, the market gets suspended for a minute, then it comes back and within a minute the odds have shot up 15 ticks. Then they stabilise and by the time you come to do your test, they have been fairly stable for 65 seconds, so your bot does not fire.

If I were doing this I'd probably use a value less than 180 seconds, maybe in the 60-90 range. You probably want to experiment with some such numbers in practice mode on a Saturday afternoon, to see how long it takes for the market to settle down after a goal. You mustn't wait for too little or too much time. Like Goldilocks' porridge, it has to be just right.

EDIT: Doh! Just realised that you seem to have the times the wrong way round. You need to test to see if the odds have moved by greater than 15 ticks in 180 seconds, provided the market has been unsuspended for at least 65 seconds. That makes so much more sense.
sausage
Posts: 5
Joined: Fri Nov 18, 2016 10:37 pm

Thanks again Shakespeare, I'll try it on the couple of games tonight
shakespeare
Posts: 113
Joined: Sat May 21, 2016 1:43 pm

As a general point, for Dallas and others who write these bots, I think the "unsuspended time > 65 seconds" is not the best condition to use anyway. My preference is to use a relative odds condition like "back price > lay price - 3 ticks". When the market comes back from suspension the odds are all over the place until the market has formed properly, and a symptom of this is a wide spread. So rather than waiting for a fixed number of seconds, I prefer to wait until the spread is only 1 or 2 ticks wide. A short spread means the market has finished forming. That seem preferable to me than waiting for a fixed time period, which might be sometimes too short or sometime too long.
tegli4a
Posts: 4
Joined: Sat Nov 19, 2016 8:09 am

Hi there, I am testing this signal with under/over 4.5... It seem like the 15 ticks difference is too much for this market, specially for the first goal so I lower it to 10 ticks. Then in the next game it triggers twice but there is only 1 goal so far in the game. I now that the liquidity and time when the goals are scored are important but anywhere if some one has observation of the market and could point me how to set up the signal will be really helpful to me.
10x in advance.
timbillington
Posts: 45
Joined: Tue Dec 15, 2015 3:46 pm

Hi all again,

With some help this looks to be doing almost exactly what I want.

However, it did something strange on one match today and I can't work out why.

If anyone can help that would be great.

It should place bets at 15, 25, 35 minutes (if no goal has been scored).
It should place them for £12.50, £25, £12.50 at those times.
It should green up after a goal has been scored.
It should red up at half time if 0-0

So, it seems to run fine for most matches. However, it placed two of the 25 minute bets today and I can't see why.

Many thanks,

Tim

The log file looks like this.

14/01/2017 15:01:28: Guardian has detected that the market is in-play
14/01/2017 15:01:28: Guardian has detected that the market is suspended
14/01/2017 15:01:28: Guardian has detected that the market is now unsuspended
14/01/2017 15:05:14: Guardian has detected that the market is suspended
14/01/2017 15:05:50: Guardian has detected that the market is now unsuspended
14/01/2017 15:10:31: Guardian has detected that the market is suspended
14/01/2017 15:10:48: Guardian has detected that the market is now unsuspended
14/01/2017 15:16:33: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 3.25. Entirely unmatched when it initially reached the market. Ref: 83459493298
14/01/2017 15:26:33: [G_Auto] : £ 25.00 Back bet placed on Over 2.5 Goals at 4. Entirely unmatched when it initially reached the market. Ref: 83461777997
14/01/2017 15:27:21: [G_Auto] : £ 25.00 Back bet placed on Over 2.5 Goals at 4.1. Entirely unmatched when it initially reached the market. Ref: 83461940557
14/01/2017 15:33:49: Guardian has detected that the market is suspended
14/01/2017 15:34:10: Guardian has detected that the market is now unsuspended
14/01/2017 15:53:33: [G_Auto] : Greened up Over 2.5 Goals by Laying 31.17 at 7.8
14/01/2017 16:36:41: Guardian has detected that the market is suspended
14/01/2017 16:36:46: Guardian has detected that the market is now unsuspended
14/01/2017 16:52:03: Guardian has detected that the market is suspended
You do not have the required permissions to view the files attached to this post.
timbillington
Posts: 45
Joined: Tue Dec 15, 2015 3:46 pm

Dallas,

I've only just read the thread back and hadn't been alerted to your previously uploaded update.

Thank you for that. I'll take a look.

Tim
timbillington
Posts: 45
Joined: Tue Dec 15, 2015 3:46 pm

Dallas,

Thank you for taking the time to post an update, it's much appreciated.

I can't work out though why those changes are a good fit. Sorry.

Taking away the unmatched bet condition means that it will fire the place bets part twice won't it?

Also, doesn't the fill or kill mean that I could get less than my full amount matched?

The latest file that I posted yesterday is working almost perfectly. But again today, in one match only (out of 5 where the others worked as expected) it fired in the same back bet (#3) twice.

15/01/2017 15:37:40: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 4.8. Entirely unmatched when it initially reached the market. Ref: 83544720240
15/01/2017 15:38:52: [G_Auto] : £ 12.50 Back bet placed on Over 2.5 Goals at 4.9. Entirely unmatched when it initially reached the market. Ref: 83544862735


It "shouldn't" have done that as the total matched bets were £50 OR there was still something unmatched. (These are both conditions).

I don't see ****LIGHT BULB MOMENT****

condition says < £50

£50 is not less than £50 is it?!?!?!

I reckon this is all set now then.

(although it's still not clear why this didn't happen every time when firing in the bets).

Thank you.

Now to put it into action.


Tim
User avatar
Dallas
Posts: 22674
Joined: Sun Aug 09, 2015 10:57 pm
Location: Working From Home

Sorry Tim i've got a bit confussed over your last 3 messages and if these relates to a new issue or the messages where sent prior to see seeing my response several weeks back.

If your still having any issues if you just post whats happening below with the relevent file i can take a look for you
timbillington
Posts: 45
Joined: Tue Dec 15, 2015 3:46 pm

Dallas,

Thank you again, and sorry for the confusion.

I have this working as desired now. Thanks for the help.

Tim
Bavski
Posts: 4
Joined: Sun Jul 31, 2016 11:08 pm

I've been having some luck simply laying weaker away teams but I'm hoping this automation could add an extra bit of profit.

What I'm hoping to do, is to lay the away team at kick off then if they go on to score the first goal lay them again using this system when they are just one nil up and their odds come in to maybe 3 or so. The plan being the stronger home team come in and atleast draw.

Would 'Signal value condition' is 'equal' to 1 work for this or would I need something else?

Thanks again for the hard work :-)
User avatar
Dallas
Posts: 22674
Joined: Sun Aug 09, 2015 10:57 pm
Location: Working From Home

Bavski wrote:I've been having some luck simply laying weaker away teams but I'm hoping this automation could add an extra bit of profit.

What I'm hoping to do, is to lay the away team at kick off then if they go on to score the first goal lay them again using this system when they are just one nil up and their odds come in to maybe 3 or so. The plan being the stronger home team come in and atleast draw.

Would 'Signal value condition' is 'equal' to 1 work for this or would I need something else?

Thanks again for the hard work :-)
Yes that would work but if your wanting just one goal then you could also trigger the lay bet using the 'Historic relative odds condition'
Selections 'last traded price' 60 secs ago
was 'greater' than
Selections 'last traded price' now
plus 10 ticks (or similar)

Which baically triggers after a drop in the price, you can also add a 'fixed odds cond' to ensure the odds are also below 3.0 or whatever you want
krunalbarot
Posts: 9
Joined: Fri Feb 24, 2017 10:20 am

hi i modified this one to back the u2.5 when a goal is scored and offset with 10 ticks..
but it didnt trigger the back bet ...

i have attached the file and logs as below
26/02/2017 13:30:07: Guardian has detected that the market is in-play
26/02/2017 13:30:07: Guardian has detected that the market is suspended
26/02/2017 13:30:07: Guardian has detected that the market is now unsuspended
26/02/2017 13:33:41: Guardian has detected that the market is suspended
26/02/2017 13:33:43: Guardian has detected that the market is now unsuspended
26/02/2017 13:34:16: Guardian has detected that the market is suspended
26/02/2017 13:34:24: Guardian has detected that the market is now unsuspended
26/02/2017 13:43:11: Guardian has detected that the market is suspended
26/02/2017 13:43:48: Guardian has detected that the market is now unsuspended
26/02/2017 13:44:50: [G_Auto] : Automation Signal for market: goal = 1
26/02/2017 13:48:56: Guardian has detected that the market is suspended
26/02/2017 13:49:28: Guardian has detected that the market is now unsuspended
26/02/2017 13:52:47: Guardian has detected that the market is suspended
26/02/2017 13:52:50: Guardian has detected that the market is now unsuspended
You do not have the required permissions to view the files attached to this post.
User avatar
Dallas
Posts: 22674
Joined: Sun Aug 09, 2015 10:57 pm
Location: Working From Home

krunalbarot wrote:
Sun Feb 26, 2017 1:56 pm
hi i modified this one to back the u2.5 when a goal is scored and offset with 10 ticks..
but it didnt trigger the back bet ...

i have attached the file and logs as below
There is no back bet (or lay bet) in your automation file - just the signal rule to set a signal when a goal is scored and which it has done as per your log.

You need to actually add a back or lay rule to the file to place a bet and use the 'signal set condition' as a condition of this back or lay bet so it knows when to fire
krunalbarot
Posts: 9
Joined: Fri Feb 24, 2017 10:20 am

oh i checked.. it is there.. pls see the screenshot attached :?:
You do not have the required permissions to view the files attached to this post.
User avatar
Dallas
Posts: 22674
Joined: Sun Aug 09, 2015 10:57 pm
Location: Working From Home

Not sure why it was'nt in the file you uploaded, unless you had two copies and sent the wrong one, anyway looking at that screenshot you only have the back bet armed for the first 55secs of the match so this needs increasing.
I assume the condition on your back rule is just that the signal is set? If so increasing the time as above is all that should be needed
Post Reply

Return to “Bet Angel Automation - Football”