Ive just come across this piece of automation and I note that some have had difficulty in getting this to fire. I seem to be having the same trouble myself. In the log I see there is a message:
"08/09/2020 19:44:16: [G_Auto] : Unable to : Store: 'liability' for the event. First value invalid. "
Im not yet clued up enough to determine this. Could this be the reason?
Lay the Draw with Correct Score Insurance Guardian Automation Bot
Was the rule applied before that match started?tonyburn wrote: ↑Tue Sep 08, 2020 11:14 pmIve just come across this piece of automation and I note that some have had difficulty in getting this to fire. I seem to be having the same trouble myself. In the log I see there is a message:
"08/09/2020 19:44:16: [G_Auto] : Unable to : Store: 'liability' for the event. First value invalid. "
Im not yet clued up enough to determine this. Could this be the reason?
Also if you have a lot of markets in Guardian make sure you have your refresh rate set fast enough
viewtopic.php?f=37&t=11491
If both of those are OK and it's still not working post preferably with the complete log from the market and i'll take a closer look
Thanks for replying Dallas. Yes, refresh was set to 20ms. I had 20 markets loaded in guardian (MO & CS). Time wise they were spread over a few hours so I had restrict refresh on. Im going to have another go at the weekend. Ill post the log if it occurs. Appreciate your time in helping.
No problem, if it does the log should give a better idea or what happenedtonyburn wrote: ↑Wed Sep 09, 2020 10:33 pmThanks for replying Dallas. Yes, refresh was set to 20ms. I had 20 markets loaded in guardian (MO & CS). Time wise they were spread over a few hours so I had restrict refresh on. Im going to have another go at the weekend. Ill post the log if it occurs. Appreciate your time in helping.
Hi Dallas, ran it again on tonight's Watford v Boro game which fit the criteria. Same settings as before. Im also using the original rules files without any amendments. Here are the logs:
MATCH ODDS
--------------
11/09/2020 19:44:16: [G_Auto] : Unable to : Store: 'liability' for the event. First value invalid.
11/09/2020 19:45:36: Guardian has detected that the market is in-play
11/09/2020 19:45:36: Guardian has detected that the market is suspended
11/09/2020 19:45:36: Guardian has detected that the market is now unsuspended
11/09/2020 19:55:54: Guardian has detected that the market is suspended
11/09/2020 19:55:58: Guardian has detected that the market is now unsuspended
11/09/2020 20:28:33: Guardian has detected that the market is suspended
11/09/2020 20:28:38: Guardian has detected that the market is now unsuspended
11/09/2020 21:37:44: Guardian has detected that the market is suspended
CORRECT SCORE
-----------------
11/09/2020 21:36:08: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:18: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:28: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:39: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:49: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:59: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:09: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:19: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:29: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:39: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:44: Guardian has detected that the market is suspended
MATCH ODDS
--------------
11/09/2020 19:44:16: [G_Auto] : Unable to : Store: 'liability' for the event. First value invalid.
11/09/2020 19:45:36: Guardian has detected that the market is in-play
11/09/2020 19:45:36: Guardian has detected that the market is suspended
11/09/2020 19:45:36: Guardian has detected that the market is now unsuspended
11/09/2020 19:55:54: Guardian has detected that the market is suspended
11/09/2020 19:55:58: Guardian has detected that the market is now unsuspended
11/09/2020 20:28:33: Guardian has detected that the market is suspended
11/09/2020 20:28:38: Guardian has detected that the market is now unsuspended
11/09/2020 21:37:44: Guardian has detected that the market is suspended
CORRECT SCORE
-----------------
11/09/2020 21:36:08: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:18: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:28: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:39: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:49: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:59: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:09: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:19: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:29: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:39: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:44: Guardian has detected that the market is suspended
The very first rule to trigger is in the match odds market 2 min before KO, and this stores a value on the event named 'drawodds'tonyburn wrote: ↑Fri Sep 11, 2020 10:41 pmHi Dallas, ran it again on tonight's Watford v Boro game which fit the criteria. Same settings as before. Im also using the original rules files without any amendments. Here are the logs:
MATCH ODDS
--------------
11/09/2020 19:44:16: [G_Auto] : Unable to : Store: 'liability' for the event. First value invalid.
11/09/2020 19:45:36: Guardian has detected that the market is in-play
11/09/2020 19:45:36: Guardian has detected that the market is suspended
11/09/2020 19:45:36: Guardian has detected that the market is now unsuspended
11/09/2020 19:55:54: Guardian has detected that the market is suspended
11/09/2020 19:55:58: Guardian has detected that the market is now unsuspended
11/09/2020 20:28:33: Guardian has detected that the market is suspended
11/09/2020 20:28:38: Guardian has detected that the market is now unsuspended
11/09/2020 21:37:44: Guardian has detected that the market is suspended
CORRECT SCORE
-----------------
11/09/2020 21:36:08: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:18: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:28: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:39: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:49: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:36:59: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:09: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:19: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:29: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:39: [G_Auto] : Store Value (Shared) for event: goalless = 1000
11/09/2020 21:37:44: Guardian has detected that the market is suspended
As this isn't in the log it means it hasn't fired, rules after that are dependant on this rule triggering, the only conditions on this rule are
Fav is greater than 2.1
draw odds are less than 4.0
If you are certain the match odds market met that criteria was the rule file also applied to the market and being refreshed between 2min and 1:30mins before KO (the time this first rule is armed for)?
- dragonsfire1981
- Posts: 17
- Joined: Sat Jul 13, 2019 1:27 am
Interesting looking strategy- thanks for the upload!
I'm going to reduce stakes to about 25p, 50p or £1 whilst I test it.
Apart from the stake size in Laydraw in MO file, there's nothing else I need to change? I saw a betamount parameter in the CS file, though wasn't sure what that was linked to - or is this for the automatic calculation that takes an appropriate stake according to the stake set in Laydraw?
Also can you explain a little more about moving 80% of the profits on H+A teams- so you're greening up but in the general tab it shows you're placing a laybet on the away team only?
I'm going to reduce stakes to about 25p, 50p or £1 whilst I test it.
Apart from the stake size in Laydraw in MO file, there's nothing else I need to change? I saw a betamount parameter in the CS file, though wasn't sure what that was linked to - or is this for the automatic calculation that takes an appropriate stake according to the stake set in Laydraw?
Also can you explain a little more about moving 80% of the profits on H+A teams- so you're greening up but in the general tab it shows you're placing a laybet on the away team only?
- dragonsfire1981
- Posts: 17
- Joined: Sat Jul 13, 2019 1:27 am
If I set the main LTD stake to £1, I should set the number to 0.25 in the stored liability if I'm also going to allow it to lose 50% of stake if it finishes at 0-0 right?
Currently testing it. I've also reduced the criteria in draw criteria to 3.2 as well. Doesn't seem to be firing, will post a log a little later.
Currently testing it. I've also reduced the criteria in draw criteria to 3.2 as well. Doesn't seem to be firing, will post a log a little later.
Dallas wrote: ↑Thu May 07, 2020 12:03 pmAnything within the files can be changed, to amend the stake so that you could lose half if it ends 0-0 go onto the MO filecyocyy wrote: ↑Thu May 07, 2020 11:14 amThis is a very good strategy but the chances that you will find a game that has 0-0 odds x5 the draw odds , are small to 0 , or maybe i`m crazy but on every game that i checked it was like this fav is 2.3 2.2 2.4 and other team 3.3 3.4 3.5 Draw odds 3.5 3.6 so that means the 0-0 should be 17.5 18 and in most of the cases odds on 0-0 are like 9 10 11 maximum 12. i was wondering if its possible to make some changes to lose half of the stake if the game ends on 0-0 and only to make profit if the game will not finish 0-0. to change X3 the draw odds this will produce a loss for sure but i don`t think it will produce any profit if you green up after a gol.
and on the 'store liability after laying the draw' rule edit the stored value named 'liability' to 50% of the stake being used on that rule
By default its set to £25 as is the stored value, so you'd change the stored value to 12.50
Sorry missed this one from a few days agodragonsfire1981 wrote: ↑Fri Sep 18, 2020 1:46 pmInteresting looking strategy- thanks for the upload!
I'm going to reduce stakes to about 25p, 50p or £1 whilst I test it.
Apart from the stake size in Laydraw in MO file, there's nothing else I need to change? I saw a betamount parameter in the CS file, though wasn't sure what that was linked to - or is this for the automatic calculation that takes an appropriate stake according to the stake set in Laydraw?
Also can you explain a little more about moving 80% of the profits on H+A teams- so you're greening up but in the general tab it shows you're placing a laybet on the away team only?
You only need change the stakes on the LTD rule, the other is calculated for you from that.
Can you post a screenshot of the part you are referring to for that last part?
The strategy is one that a few users have requested, its not something I've used myself.dragonsfire1981 wrote: ↑Wed Sep 23, 2020 8:45 pmIf I set the main LTD stake to £1, I should set the number to 0.25 in the stored liability if I'm also going to allow it to lose 50% of stake if it finishes at 0-0 right?
Currently testing it. I've also reduced the criteria in draw criteria to 3.2 as well. Doesn't seem to be firing, will post a log a little later.
Dallas wrote: ↑Thu May 07, 2020 12:03 pmAnything within the files can be changed, to amend the stake so that you could lose half if it ends 0-0 go onto the MO filecyocyy wrote: ↑Thu May 07, 2020 11:14 amThis is a very good strategy but the chances that you will find a game that has 0-0 odds x5 the draw odds , are small to 0 , or maybe i`m crazy but on every game that i checked it was like this fav is 2.3 2.2 2.4 and other team 3.3 3.4 3.5 Draw odds 3.5 3.6 so that means the 0-0 should be 17.5 18 and in most of the cases odds on 0-0 are like 9 10 11 maximum 12. i was wondering if its possible to make some changes to lose half of the stake if the game ends on 0-0 and only to make profit if the game will not finish 0-0. to change X3 the draw odds this will produce a loss for sure but i don`t think it will produce any profit if you green up after a gol.
and on the 'store liability after laying the draw' rule edit the stored value named 'liability' to 50% of the stake being used on that rule
By default its set to £25 as is the stored value, so you'd change the stored value to 12.50
All the calculations, the amounts of liability and odds criteria used were as per the instructions so I can't confirm if making those changes would leave you exposed somewhere.
Probably better to test in PM with larger stakes just in case the lower labilities mess up the calculations
- dragonsfire1981
- Posts: 17
- Joined: Sat Jul 13, 2019 1:27 am
https://imgur.com/a/76PtfRx
It's in the MO file in the bottom rule- I was trying to figure out the mechanisms of how it all works. I think I sort of understand how its triggered- the spreadprofits signal from "Store profit after greening" is then applied. It then looks like another laybet is applied to the draw using the green profit- so 80% of the profits is placed on this laybet after greening I take it?
It's in the MO file in the bottom rule- I was trying to figure out the mechanisms of how it all works. I think I sort of understand how its triggered- the spreadprofits signal from "Store profit after greening" is then applied. It then looks like another laybet is applied to the draw using the green profit- so 80% of the profits is placed on this laybet after greening I take it?
Dallas wrote: ↑Wed Sep 23, 2020 8:54 pmSorry missed this one from a few days agodragonsfire1981 wrote: ↑Fri Sep 18, 2020 1:46 pmInteresting looking strategy- thanks for the upload!
I'm going to reduce stakes to about 25p, 50p or £1 whilst I test it.
Apart from the stake size in Laydraw in MO file, there's nothing else I need to change? I saw a betamount parameter in the CS file, though wasn't sure what that was linked to - or is this for the automatic calculation that takes an appropriate stake according to the stake set in Laydraw?
Also can you explain a little more about moving 80% of the profits on H+A teams- so you're greening up but in the general tab it shows you're placing a laybet on the away team only?
You only need change the stakes on the LTD rule, the other is calculated for you from that.
Can you post a screenshot of the part you are referring to for that last part?
- dragonsfire1981
- Posts: 17
- Joined: Sat Jul 13, 2019 1:27 am
It has been firing today actually, not sure why it didn't work yesterday though I did it on a whim at the end of the night. My edited version has been firing too though it's been placing very small stakes for the 0-0 CS.
The "Store liability after laying the draw" rule on the MO file appears to be a multiple of something, though in your previous reply to someone else it sounds more like an absolute figure for the stored liability used to calculate the stake for the CS 0-0?
What I'm trying to do is reduce everything proportionately, so that the Draw odds vs 0-0 criteria are reduced to 3x (this seems to have worked though i set it to 3.2) and you only cover 50 to 75% of the stake/liability if the match ends 0-0.
When I reduced the "Store liability after laying the draw" to 0.25- and main stake for lay the draw to £1 I was expecting it to use a 25p stake for the 0-0 CS however it came up with a 5p stake instead, this is what the log shows. I'm trying to get my head around how this all fits together. Because this last value is by default 25, if I reduce it to 12.5 will that produce a 50% 0-0 CS stake instead?
MO file log
24/09/2020 10:58:00: [G_Auto] : Store Value (Shared) for event: MOmarketgood = 1
24/09/2020 10:58:00: [G_Auto] : Store Value (Shared) for event: drawodds = 3.5 * 3.2 = 11.2
24/09/2020 10:59:01: [G_Auto] : Store Value (Shared) for event: odds = 3.5 - 1 = 2.5
24/09/2020 10:59:01: [G_Auto] : £ 1.00 Lay bet placed on The Draw at 3.55. Fully matched at 3.5. Ref: 10001
24/09/2020 10:59:16: [G_Auto] : Store Value (Shared) for event: liability = 2.5 * 0.25 = 0.625
24/09/2020 11:00:12: Guardian has detected that the market is in-play
24/09/2020 11:00:12: Guardian has detected that the market is suspended
24/09/2020 11:00:13: Guardian has detected that the market is now unsuspended
CS file log
24/09/2020 10:58:31: [G_Auto] : Store Value (Shared) for event: CSmarketgood = 2
24/09/2020 10:59:31: [G_Auto] : Store Value (Shared) for event: backprice = 14 - 1 = 13
24/09/2020 10:59:31: [G_Auto] : Store Value (Shared) for event: betamount = 0.625 / 13 = 0.048
24/09/2020 10:59:46: [G_Auto] : £ 0.05 Back bet placed on 0 - 0 at 14. Fully matched at 14. Ref: 10003
The "Store liability after laying the draw" rule on the MO file appears to be a multiple of something, though in your previous reply to someone else it sounds more like an absolute figure for the stored liability used to calculate the stake for the CS 0-0?
What I'm trying to do is reduce everything proportionately, so that the Draw odds vs 0-0 criteria are reduced to 3x (this seems to have worked though i set it to 3.2) and you only cover 50 to 75% of the stake/liability if the match ends 0-0.
When I reduced the "Store liability after laying the draw" to 0.25- and main stake for lay the draw to £1 I was expecting it to use a 25p stake for the 0-0 CS however it came up with a 5p stake instead, this is what the log shows. I'm trying to get my head around how this all fits together. Because this last value is by default 25, if I reduce it to 12.5 will that produce a 50% 0-0 CS stake instead?
MO file log
24/09/2020 10:58:00: [G_Auto] : Store Value (Shared) for event: MOmarketgood = 1
24/09/2020 10:58:00: [G_Auto] : Store Value (Shared) for event: drawodds = 3.5 * 3.2 = 11.2
24/09/2020 10:59:01: [G_Auto] : Store Value (Shared) for event: odds = 3.5 - 1 = 2.5
24/09/2020 10:59:01: [G_Auto] : £ 1.00 Lay bet placed on The Draw at 3.55. Fully matched at 3.5. Ref: 10001
24/09/2020 10:59:16: [G_Auto] : Store Value (Shared) for event: liability = 2.5 * 0.25 = 0.625
24/09/2020 11:00:12: Guardian has detected that the market is in-play
24/09/2020 11:00:12: Guardian has detected that the market is suspended
24/09/2020 11:00:13: Guardian has detected that the market is now unsuspended
CS file log
24/09/2020 10:58:31: [G_Auto] : Store Value (Shared) for event: CSmarketgood = 2
24/09/2020 10:59:31: [G_Auto] : Store Value (Shared) for event: backprice = 14 - 1 = 13
24/09/2020 10:59:31: [G_Auto] : Store Value (Shared) for event: betamount = 0.625 / 13 = 0.048
24/09/2020 10:59:46: [G_Auto] : £ 0.05 Back bet placed on 0 - 0 at 14. Fully matched at 14. Ref: 10003
Dallas wrote: ↑Wed Sep 23, 2020 8:58 pmThe strategy is one that a few users have requested, its not something I've used myself.dragonsfire1981 wrote: ↑Wed Sep 23, 2020 8:45 pmIf I set the main LTD stake to £1, I should set the number to 0.25 in the stored liability if I'm also going to allow it to lose 50% of stake if it finishes at 0-0 right?
Currently testing it. I've also reduced the criteria in draw criteria to 3.2 as well. Doesn't seem to be firing, will post a log a little later.
Dallas wrote: ↑Thu May 07, 2020 12:03 pm
Anything within the files can be changed, to amend the stake so that you could lose half if it ends 0-0 go onto the MO file
and on the 'store liability after laying the draw' rule edit the stored value named 'liability' to 50% of the stake being used on that rule
By default its set to £25 as is the stored value, so you'd change the stored value to 12.50
All the calculations, the amounts of liability and odds criteria used were as per the instructions so I can't confirm if making those changes would leave you exposed somewhere.
Probably better to test in PM with larger stakes just in case the lower labilities mess up the calculations
-
- Posts: 3219
- Joined: Thu Oct 24, 2019 8:25 am
- Location: Newport
Hi,
I have, potentially, found an edge which could be built into this bot using stored values and you don't need to worry about which team scores first.
1. Games to select is where the Correct Score -> 0-0 Back Price is >= 12.
2. Dont worry about the price of either team to win, its taken care of elsewhere, see below.
Markets
- Match Odds
- Correct Score
- Home Team +1
- Away Team +1
Rules
1. Correct Score -> 0-0 -> Back Price is >= Match Odds -> Draw -> Back Price + 100%
2. Home Team + 1 -> Draw Odds -> Back Price is >= Match Odds -> Draw -> Back Price + 100%
3. Away Team + 1 -> Draw Odds -> Back Price is >= Match Odds -> Draw -> Back Price + 100%
However, there is a limited timeframe of opportunity which normally occurs on average for around 2/3 minutes from the 45+ minute mark onwards if the above rules are ALL valid.
The only problem I can forsee is if you initially put the lay bet on and the event gets suspended and never gets unsuspended again before another goal go in. Therefore, i would pick big profile events to help negate this, although that means fcuk all with BF running things.
I suggest you paper trade it first.
Have fun,
I have, potentially, found an edge which could be built into this bot using stored values and you don't need to worry about which team scores first.
1. Games to select is where the Correct Score -> 0-0 Back Price is >= 12.
2. Dont worry about the price of either team to win, its taken care of elsewhere, see below.
Markets
- Match Odds
- Correct Score
- Home Team +1
- Away Team +1
Rules
1. Correct Score -> 0-0 -> Back Price is >= Match Odds -> Draw -> Back Price + 100%
2. Home Team + 1 -> Draw Odds -> Back Price is >= Match Odds -> Draw -> Back Price + 100%
3. Away Team + 1 -> Draw Odds -> Back Price is >= Match Odds -> Draw -> Back Price + 100%
However, there is a limited timeframe of opportunity which normally occurs on average for around 2/3 minutes from the 45+ minute mark onwards if the above rules are ALL valid.
The only problem I can forsee is if you initially put the lay bet on and the event gets suspended and never gets unsuspended again before another goal go in. Therefore, i would pick big profile events to help negate this, although that means fcuk all with BF running things.
I suggest you paper trade it first.
Have fun,
In what way do you want to mitigate it? in almost all cases you could just green up or trade out part of the stake on the LTD market without needing to use the CS