Signal when Goals are Scored Guardian Automation Bot

[Dallas]

Mate,

I aim to lay Any Other Home Win. Either entering or exiting after, say, 2 goals by the home team.

Give this a try in practice mode, ive never done this on the CS market so not 100% sure of the expected movement of the 2-0 odds so this may need tinkering with.

Basically to start with if the odds of 2-0 go to 800.0 or greater a signal is set to abort the rule (this would mean the score is either 0-1 or 1-1)

At the same time if a goal is scored and the 2-0 score line falls 10 or more ticks (row 6) then a signal is set, once this has happened twice ie, should be 2-0 providing the first signal 'Abort' has not been set then it will lay AOHW (row 17)

The first part should be fine its just how many ticks the 2-0 socre line will drop depending on the odds at K.O and the time during the match

Any problems let me know

[Rastis]

Hey Dallas,
I gave it a whirl! I applied it randomly trying to jag a home team in the mood for a goal fest, but, struggled to get a team that could hit a barn at 5 paces.
However, for those that weren't shanking em, the triggers appeared to work well!!
I will continue to trial it and report back to you.
Thank you very much for the help!
Stay tuned...

[timbillington]

Hi,

Thanks again to Dallas for the great work on the signals.

The attached looks to be working fine, basically wait until 15 mins of a match where the goal expectancy is high, then back at 15,25 and 35 mins. Exit for green on any goal. Exit at half time for a loss (if no goal scored).

I am having trouble with the "safety nets" though. So, ensuring that the back bet is made, but only once (actually I think that the current set of conditions are OK) but for the greening up, I had it arm multiple times, and I must have done this wrong since it just kept backing/laying and eroding the position.

What is the correct way to have greening done so that it does it multiple times to ensure it's properly exited? Many thanks for the help.

If anyone looks at this and sees other areas to improve/errors please let me know.

Happy Christmas all.

Tim

[Dallas]

I have made some minor changes to your file and if i've understood your requirments correctly should work correctly.

If not just message back and ill amend / let you know how to amend it

[boomzee-uk]

DALLAS
Hi Dallas, i've been looking at your system and it is definitely the most comprehensive i have seen, although i am a newbie and trying to write my own bot, is there anyway i can pm you to get some more info as i am puzzled yet intrigued by your system,
kind regards,
dave

[Dallas]

DALLAS
Hi Dallas, i've been looking at your system and it is definitely the most comprehensive i have seen, although i am a newbie and trying to write my own bot, is there anyway i can pm you to get some more info as i am puzzled yet intrigued by your system,
kind regards,
dave

If its a general question and/or relates to one of the example bots its often better to post directly to the thread its to do with so i know which one your refering to and the answer could be of use to other in the future, but if its something that you dont want to post to the forum then yes you can PM me although it will be after xmas before ill be able to reply now.

[sausage]

Apologies for the basic newbie question, but I'd be grateful if someone could explain why the attached rule does not match any bets. Basically, the rule is looking to back under 2.5 goals when there is 1 goal between 2 and 25 minutes (and then offset). I suspect its something to do with the 'row 1' in the General & Conditions bit of the Goals for Unders rule. If you have the ladder view set on Reverse does this affect whether you should choose Row 1 or Row 2, or does the Reverse setting not apply to Guardian but manual betting only. Thanks

[shakespeare]

Apologies for the basic newbie question, but I'd be grateful if someone could explain why the attached rule does not match any bets.

You're testing to see if row 1 (which is always the row for "Under 2.5 goals" regardless of your ladder settings) is trading at 15 ticks below its price 65 seconds ago. But odds are only going to move that fast if a goal is scored - and if a goal is scored then the "Under 2.5 goals" price will go up, not down.

[sausage]

Thanks Shakespeare, so I just need to change the 'Historic Relative Odds Condition' to plus 15 ticks not minus 15 ticks? Do I keep the Selection A last traded price now as 'less than'. (I only want to trigger the bet if a goal is scored). Thanks again, appreciate it.

[shakespeare]

If you change the "minus" to "plus" and the "less than" to "greater than", the bot should fire if the odds rise by more than 15 ticks in 65 seconds. That will (almost) always be when a goal is scored. So you'll be backing the "Under 2.5 goals" selection after a goal is scored.

This means that your strategy is to back that selection when the price has just shot up, and look to trade out for a profit a few minutes later as the odds start falling again; or hope that no further goals are scored till the end of the game, so you win your back bet. If that's what you want to do then the changes above should enable you to do it.

[shakespeare]

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]

Thanks again Shakespeare, I'll try it on the couple of games tonight

[shakespeare]

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]

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]

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