DOB with Moving Exit Guardian Automation Bot

[ANGELS15]

Thanks for the tip. Just curious you saw my observation re keeping the intial back bet. How did you get this to work without a 'keep' bets before the off?

Arrgh duh! of course if the back bet is initially matched it's not a problem!

[Dallas]

wow Dallas, thanks again, what else can i say.

i will definitely be using some parts of this specifically the moving exit as i was trying to achieve something like this but mine is just static.

this is so cool.

please take a look at viewtopic.php?f=53&t=21427 if you have any spare time, would much appreciate it.

I did notice the post yesterday but not had the time to look into the file yet, i'll try and do it before the end of the week, if i haven't posted back to it then give me a prod by bumping the thread

[Dallas]

Thanks for the tip. Just curious you saw my observation re keeping the intial back bet. How did you get this to work without a 'keep' bets before the off?

Arrgh duh! of course if the back bet is initially matched it's not a problem!

[salmanim140i]

Hi dallas.

Once again a great bit of automation.

Got me thinking though could your idea here be used in the opposite sense as to exit of in loss as well.

One of the things I noticed with on play racing the odds my fly out and hit the loss target say to red up but will also tend to come back in and then go out etc, etc....

If a the same here could be used as to manage losses I think we have a game changer here??

Was thinking along the lines of using a stored value of the loss amount say being a -50% of the profit amount and then maybe using a signal increment count to count out how long the red stays in the negative beyond that target, but how would you start the count again if it came back say plus -50%???

If that makes sense, or am I just over complicating it?

Thanks

[Dallas]

Hi dallas.

Once again a great bit of automation.

Got me thinking though could your idea here be used in the opposite sense as to exit of in loss as well.

One of the things I noticed with on play racing the odds my fly out and hit the loss target say to red up but will also tend to come back in and then go out etc, etc....

If a the same here could be used as to manage losses I think we have a game changer here??

Was thinking along the lines of using a stored value of the loss amount say being a -50% of the profit amount and then maybe using a signal increment count to count out how long the red stays in the negative beyond that target, but how would you start the count again if it came back say plus -50%???

If that makes sense, or am I just over complicating it?

Thanks

Already done
viewtopic.php?f=56&t=11954

[salmanim140i]

Thanks again for that Dallas.

Just wondering though can the Dob bot you made be used with a Profit and loss indicator instead of using odds?

Had a go but seemed to have got fairly confused... there does not seem to be a stored value option to look at the current greening position just the profit and loss of the runners or you can use the set stake but that then just gets really complicated???

thanks

[salmanim140i]

Hi Dallas,

I have been running the Dob File you uploaded and for some reason it is not wanting to Green up if the "New Exit" stored value is triggered?

any thought why this could be?

[Dallas]

Hi Dallas,

I have been running the Dob File you uploaded and for some reason it is not wanting to Green up if the "New Exit" stored value is triggered?

any thought why this could be?

I'd need to see the log from that market to be able to answer

[salmanim140i]

Hi Dallas,

Sorry mate I had worked out what I done wrong, but thanks for coming back to me.

But was wondering if you had any thoughts on using this sort of rule file with the Profit and loss as oppose to using the odds.

say in the use of a dutching bot as oppose to a DOB???

thanks

[salmanim140i]

Hi Dallas

Any Ideas on the above post...?

Appreciate your a busy man, but would be good to know if this can be done?

Thanks again

[Autolearner]

Hi Dallas

Firstly - and most importantly - big thanks to the many generous souls on this forum who are so helpful with their time, insights and files like this. And in particular to you for your manifest generosity of spirit to newcomers.

Secondly - have been experimenting with this Bot over the past few days and today's 13:40 race at Beverly it proved itself with Storific, where I got £5.90 back on what would otherwise have been a £2 DOB - so many thanks!

Thirdly - as part of this experimentation I notice there can occasionally appear to be some issues greening up when the odds are flying about towards the end of the race. Indeed there was one race yesterday (can't remember which - and no log) where the odds flew in and out a couple of times, and the green-up ended up with a loss of greater than the original (admittedly only £2) stake.

So my question is, is it possible that compared to a "traditional" DOB placing a lay bet at half the back price (but double the stake) which guarantees a doubling of payout (as long as the price at least halves) your new Bot will most of the time at least double the payout (again as long as the price halves) and at times do significantly better than that (for instance Storific above went on to win) but at the risk of occasionally losing more than the stake if you happen to be unlucky as the odds fly around in the multiple green-up process? As long as the latter case (if it can happen?) is a relatively rare occurrence it still seems to be a "no-brainer" to use your new (magical!) bot.

Thanks again for all your support and enthusiasm!

[Dallas]

Hi Dallas

Firstly - and most importantly - big thanks to the many generous souls on this forum who are so helpful with their time, insights and files like this. And in particular to you for your manifest generosity of spirit to newcomers.

Secondly - have been experimenting with this Bot over the past few days and today's 13:40 race at Beverly it proved itself with Storific, where I got £5.90 back on what would otherwise have been a £2 DOB - so many thanks!

Thirdly - as part of this experimentation I notice there can occasionally appear to be some issues greening up when the odds are flying about towards the end of the race. Indeed there was one race yesterday (can't remember which - and no log) where the odds flew in and out a couple of times, and the green-up ended up with a loss of greater than the original (admittedly only £2) stake.

So my question is, is it possible that compared to a "traditional" DOB placing a lay bet at half the back price (but double the stake) which guarantees a doubling of payout (as long as the price at least halves) your new Bot will most of the time at least double the payout (again as long as the price halves) and at times do significantly better than that (for instance Storific above went on to win) but at the risk of occasionally losing more than the stake if you happen to be unlucky as the odds fly around in the multiple green-up process? As long as the latter case (if it can happen?) is a relatively rare occurrence it still seems to be a "no-brainer" to use your new (magical!) bot.

Thanks again for all your support and enthusiasm!

Glad to hear you are finding the examples useful, regarding your question you could add a 'Close trade profit condition' is greater than £0.00 (or whatever the amount you want.

That will stop it triggering in a potential loss, ie, the price flies out green up rules triggers around £1.20 profits its not matched and price continues out that greening bet will stay there and may come back in a get matched.

[Autolearner]

Hi Dallas

Many thanks for your quick, and useful, response.

I am indeed finding all the examples and suggestions very helpful.

So as I understand your suggested addition, this will stop the green-up triggering at a loss so the worst case scenario would be just losing your stake (as in a traditional DOB) rather than some greater amount. And you have the additional benefit if the price does come in subsequently you may be matched on the green-up?

Many thanks again!

[Dallas]

Hi Dallas

Many thanks for your quick, and useful, response.

I am indeed finding all the examples and suggestions very helpful.

So as I understand your suggested addition, this will stop the green-up triggering at a loss so the worst case scenario would be just losing your stake (as in a traditional DOB) rather than some greater amount. And you have the additional benefit if the price does come in subsequently you may be matched on the green-up?

Many thanks again!

Yes, it will basically work the same as it is now but will never trigger on the way out if the profit goes below the amount you set it at

[ANGELS15]

While we're on the subject of this bot, I love it think it's great. I've been experimenting with it using it instead of my usual traditional DOBs. I've noticed a few things:

a) sometimes it will place the store value on the horse's price but doesn't place the back bet.

b) sometimes places the back bet but no store value

c) occasionally after successfully placing the bet and store value get a message in the log 'the whole transaction has been rejected' therefore no exit trades are executed.

I don't know if it's something to do with my pc which is only really a tablet not being 'man enough for the job' or possibly because I rely on wifi, again with the same problem.

For now fortunately I've been around when the races have been going off so been able to manually intervene.

When it does work it works brilliantly.

I don't know if the two could be related but yesterday I responded in another forum post. at the time the OP had asked an intitial question and someone had replied, I then submitted an observation. What was strange is that my post was delayed in appearing as it appeared after other later posts therefore out of sequence.

Also when I log into Bet Angel and go to the 'today's racing' forum instead of entering where the last post is I now enter a couple of pages behind having to scroll through to the end.

As I say I wonder if others have had similar issues with the above automation or perhaps in my case the problem is somehow with my tablet.