Linked Automation Re-arming

[jamesedwards]

Many thanks James - Qatar F1 Sprint Qualifying has just finished so I'll take a look now.

The files you looked at have been updated a few times to include place/fill/kill and other adjustments.

------------------------------

What are the best settings in your opinion to get the triggers to cycle in the quickest time?

In the rules file I've set '0.1s before re-arming' and the global setting will have 'Refresh every 20 ms'

It works by saving the relevant Betfair ID as several different SVs at event level with one SV for each type of market. Then, as it triggers a bet in each individual place market, it resets that specific SV back to 0, ready to be primed once again on the next trigger.

[Dabbla]

You should probably add a (stop this servant) rule to the end of the servant file. Otherwise it will remain running in the background and the cancels will still be active.

[jamesedwards]

You should probably add a (stop this servant) rule to the end of the servant file. Otherwise it will remain running in the background and the cancels will still be active.

Yep. I always forget this until one day I get an unexpected trigger!

[Tuco]

It works by saving the relevant Betfair ID as several different SVs at event level with one SV for each type of market. Then, as it triggers a bet in each individual place market, it resets that specific SV back to 0, ready to be primed once again on the next trigger.

Just been in practice mode trying that out James and I'm pleased to say that it works and does allow a selection to be backed twice or different selections to be backed and it triggers the same ID selection in the place market.

I'll delve down into how you've made this happen, learn what you've done and copy and paste the relevant rules across into the SV's I've created...then of course test again before going live!

At first glance, it looks like you need a separate stored value in Market (A) for each of the linked markets (B), (C), (D), rather than using a single stored value for all of the linked markets.

Once, again many thanks for your efforts

[jamesedwards]

It works by saving the relevant Betfair ID as several different SVs at event level with one SV for each type of market. Then, as it triggers a bet in each individual place market, it resets that specific SV back to 0, ready to be primed once again on the next trigger.

Just been in practice mode trying that out James and I'm pleased to say that it works and does allow a selection to be backed twice or different selections to be backed and it triggers the same ID selection in the place market.

I'll delve down into how you've made this happen, learn what you've done and copy and paste the relevant rules across into the SV's I've created...then of course test again before going live!

At first glance, it looks like you need a separate stored value in Market (A) for each of the linked markets (B), (C), (D), rather than using a single stored value for all of the linked markets.

Once, again many thanks for your efforts

No worries. I enjoy a good BA puzzle.

The reason you need a separate stored value for each type of place market is because you need to reset the SV ready to prime for a repeat trigger. If you were to use a single SV for all place markets then because you don't know which order the markets will cycle through Guardian you would end up either resetting the SV too soon and missing place markets, or too late and end up duplicating triggers. With separate SVs you can simply reset them one at a time at each place market as they cycle through and the order no longer matters.

[Tuco]

I'm still getting some mixed results from this Servant / Automation.

I'm getting a situation where the servant will fire correctly however many times I want and on any selection I want, but the linked markets will fire however many times I want, but only once on the initial selection.

I copied across the rules to apply them to the markets that were of interest to me and they didn't work as hoped for...so I keep trying to find solutions to the puzzle.

Your version did work for me on horse racing, but I think for only 1 linked automation place market and not for additional (multiple) markets.

Is it essential to have an entry for 'Market Type' in 'Market Type Conditions' and if so why? What purpose does that serve?

---------------------------

Whilst working on this conundrum I had another servant wish that I'm already working on:

In a market with 10 selections where 4 of the 10 selections have been nominated, I'm trying to create a servant/automation that will lay one of the servant context nominated selections and back the other 3 nominated selections whilst doing nothing with the remaining 6 un-nominated selections.

The laying bit is OK, it's the backing of the other 3 nominated selections that I'm having the trouble with.

[jamesedwards]

I'm still getting some mixed results from this Servant / Automation.

I'm getting a situation where the servant will fire correctly however many times I want and on any selection I want, but the linked markets will fire however many times I want, but only once on the initial selection.

Your version did work but I think for only 1 linked automation market and not for multiple markets.

I copied across the rules to apply them to the markets that were of interest to me and they didn't work as hoped for...so I keep trying to find solutions to the puzzle.

Is it essential to have an entry for 'Market Type' in 'Market Type Conditions' and if so why? What purpose does that serve?

---------------------------

Whilst working on this conundrum I had another servant wish that I'm already working on:

In a market with 10 selections where 4 of the 10 selections have been nominated, I'm trying to create a servant/automation that will lay one of the servant context nominated selections and back the other 3 nominated selections whilst doing nothing with the remaining 6 un-nominated selections.

The laying bit is OK, it's the backing of the other 3 nominated selections that I'm having the trouble with.

Exactly what markets are you using?

[Tuco]

Let's say, for example you were using it in an F1 race where you have separate winner, podium (top 3) finish, top 6 finish, points (top 10 finish), fastest lap markets - in all of these markets the selection id is exactly the same for each of the drivers.

...or it could be in a reality TV market where you have winner, winner w/o, top 3, top female, top male markets etc.

What I'm also doing is clearing guardian of all of the markets except the ones pertinent to the automation to avoid any mistakes.

[jamesedwards]

Let's say, for example you were using it in an F1 race where you have separate winner, podium (top 3) finish, top 6 finish, points (top 10 finish), fastest lap markets - in all of these markets the selection id is exactly the same for each of the drivers.

...or it could be in a reality TV market where you have winner, winner w/o, top 3, top female, top male markets etc.

What I'm also doing is clearing guardian of all of the markets except the ones pertinent to the automation to avoid any mistakes.

The rule I built is for horse racing place markets only. If you want to make it work for other sports then you need to amend these conditions in all the trigger rulelines.

z347.jpg

[Tuco]

Hi James - yes I know it was for horse racing place markets with the TBP2, TBP3, TBP4, TBP5 etc. - I'll take a look and make sure I copied and amended the files and stored values correctly for all the markets I'm hoping to use them on and the trigger market conditions linked to the servant's stored values - pretty sure I did, but I'll take another look as it's often after midnight when I'm working on them (though that's the best time for me to concentrate).

Thanks again for all of your input, help and assistance.