I am looking to set up the following. Have tried several times but still can't get it. I just need someone to give me a breakdown on how to automate this. I am looking for the "bot" to take note of horses within a certain price range just before the off.. i.e lets say between 2.00 and 3 .5. I DO NOT want to the bot to place a bet at this time, only to select these horses. Then I want the bot to place a LAY bet ONLY when these horses drift to a higher odds range. Then possibly place another lay bet should the selections drift further. I am doing this manually at the moment but close to the end of the race the odds move so quickly I am just missing so many bets and not getting taken as they have moved out of the range I wish to place. I am sure this can be automated but I just cannot work out how
I am no techie and therefore really need to know how to do this in such a way as a child could understand. I know this may take some time for somebody to explain but I really want to try this on very small stakes so as I can see if there is any mileage in it
Can anybody out there help in any way. It would be really appreciated. Thanks for your time in reading this
I cannot seem to get this right. Please help
Ok,
I've attached a rule below that will do this for you. I can't say if it's going to cover off every avenue that you may wish to explore, but it does address all of the points above using soft coded values (thus you can change them without modifying the logic).
Here's a breakdown of what happens:
1. Stored Values (SV) are setup to determine the upper and lower bounds of the target odds range (2.00->3.50 in your example). Also, a second set of values are setup to flag the drift odds min and max (your drift odds lay range). This is setup 5 seconds before the off.
2. Just AT the off, all runners are examined to see if their odds fall within the target odds range threshold identified in the rule #1 above. If so, a flag is set against the runner for use later in the race (isLayCandidate).
3. The FIRST lay rule kicks in when a runner identified in rule #2 above has LAY odds that are within the range identified as being the drift odds lay range (range values from rule #1 also)
4. the SECOND lay rule kicks in AFTER the first rule has been actioned. This has an arbitary condition that it be placed when the lay price is 33% ABOVE the price of the bet placed in #2 (change % to suit). [hint - this same rule could be duplicated and pointed the other way and red out if the price was xx% BELOW the price of the selection's lay in the market]
It's not really complex but if you've never coded any rules before, it may be a little dauntung to comprehend. For this reason, all the moving parts are in the form of parameters which you can edit in rule #1 (called SV - Odds parameters).
I'm sure you'll have questions, so i'll say no more for now.
enjoy...
[edit - 10:55] -have uploaded the file again as there was a small copy 'n paste duplication/logic error!!
I've attached a rule below that will do this for you. I can't say if it's going to cover off every avenue that you may wish to explore, but it does address all of the points above using soft coded values (thus you can change them without modifying the logic).
Here's a breakdown of what happens:
1. Stored Values (SV) are setup to determine the upper and lower bounds of the target odds range (2.00->3.50 in your example). Also, a second set of values are setup to flag the drift odds min and max (your drift odds lay range). This is setup 5 seconds before the off.
2. Just AT the off, all runners are examined to see if their odds fall within the target odds range threshold identified in the rule #1 above. If so, a flag is set against the runner for use later in the race (isLayCandidate).
3. The FIRST lay rule kicks in when a runner identified in rule #2 above has LAY odds that are within the range identified as being the drift odds lay range (range values from rule #1 also)
4. the SECOND lay rule kicks in AFTER the first rule has been actioned. This has an arbitary condition that it be placed when the lay price is 33% ABOVE the price of the bet placed in #2 (change % to suit). [hint - this same rule could be duplicated and pointed the other way and red out if the price was xx% BELOW the price of the selection's lay in the market]
It's not really complex but if you've never coded any rules before, it may be a little dauntung to comprehend. For this reason, all the moving parts are in the form of parameters which you can edit in rule #1 (called SV - Odds parameters).
I'm sure you'll have questions, so i'll say no more for now.
enjoy...
[edit - 10:55] -have uploaded the file again as there was a small copy 'n paste duplication/logic error!!
You do not have the required permissions to view the files attached to this post.
Thanks for the reply. Unfortunately I cannot get the download to open 
Always had trouble with these baf files. tried to open some historical data on Betfair and they use the same. Could not open one of them either. Thanks for your help anyway buddy
Always had trouble with these baf files. tried to open some historical data on Betfair and they use the same. Could not open one of them either. Thanks for your help anyway buddyYou open them by importing them into Bet Angel (from guardian). If it's not working then you need to upgrade your BetAngel
yup, that's exactly it i think. you need to ensure you're on the latest version of BA (v1.52.0). Then, as sa7med says, simply import from guardian as normal.
let me know if you succeed or otherwise...
Thanks Guys for your help. Sorry for the delay in getting back to those that were kind enough to reply. I have just spent a little time in Hospital. Nothing serious...more of an inconvenience. Over this week I will trying to take your advice and implement your help. Will let you know how I get on later in the week. Thanks again fellas
Jim,
I would like to say thankyou for your neat bit of automation. Ive always been attracted to in play automation for some reason. I've been using it for a couple of days. I've sey your second rule to look for the favourite between 2-4.5. I find you need to adjust the drift odds to a higher figure say min: 10 max: 18. When in Play, as the prices fluctuate it matches to early and that's when it goes wrong. I have tried setting the lay prices to best market price and a fixed odds condition i.e above 5 and 2nd lay above 12. For some reason it then doesn't behave itself. Frustrating really because 70% of the time it runs well. It's the fine tuning a can't get a grip on. It's very difficult explaining in text
These things take time.......cheers Jim
I would like to say thankyou for your neat bit of automation. Ive always been attracted to in play automation for some reason. I've been using it for a couple of days. I've sey your second rule to look for the favourite between 2-4.5. I find you need to adjust the drift odds to a higher figure say min: 10 max: 18. When in Play, as the prices fluctuate it matches to early and that's when it goes wrong. I have tried setting the lay prices to best market price and a fixed odds condition i.e above 5 and 2nd lay above 12. For some reason it then doesn't behave itself. Frustrating really because 70% of the time it runs well. It's the fine tuning a can't get a grip on. It's very difficult explaining in text
These things take time.......cheers Jim