Here you go. I couldn't find a non-sport example to use so I built this for the Premier League. But the principle is the same for any competition where there is the same selection ID across multiple markets. You just need to go in and adjust the SVs in the back bet line in the servant, and the conditions and SV in all the place market lines.
'Tucotastic Servant v2' is to trigger as a servant on the market of choice, eg WINNER.
'Tucotastic - apply to all place markets v2' is set to duplicate triggers on the TOP_2_FINISH, TOP_4_FINISH, and TOP_6_FINISH markets.
I've added a line that reports the 'market type' in the log so you can see how this is done.
Linked Automation Re-arming
-
jamesedwards
- Posts: 5098
- Joined: Wed Nov 21, 2018 6:16 pm
You do not have the required permissions to view the files attached to this post.
I have been having a play with this idea,here’s my effort.
Markets used > strictly, (win) and (Top Female).
The servant will only store the ID. (James file from above slightly changed.)
The file will bet 3 times per back bet. Then Reset.
What you need to do >
Add a new Event SV to the servant for new markets.
To add a new market to Guardian file, create (copy) a new (start / count) rule, and add the relevant conditions. **See file for examples.
Clear the Event SV in new (start / count) rule.
Add the stop other servants rule to (start / count) rule. ** Not sure how well this will work, you might need another approach.
Add the Back bet rules that you need with the same condition. Currently set to back at 1000 and 990.
Make sure the refresh rate is same for all rules from the Back bets rule, down.
This file is very untested and will need a good stress test.
Markets used > strictly, (win) and (Top Female).
The servant will only store the ID. (James file from above slightly changed.)
The file will bet 3 times per back bet. Then Reset.
What you need to do >
Add a new Event SV to the servant for new markets.
To add a new market to Guardian file, create (copy) a new (start / count) rule, and add the relevant conditions. **See file for examples.
Clear the Event SV in new (start / count) rule.
Add the stop other servants rule to (start / count) rule. ** Not sure how well this will work, you might need another approach.
Add the Back bet rules that you need with the same condition. Currently set to back at 1000 and 990.
Make sure the refresh rate is same for all rules from the Back bets rule, down.
This file is very untested and will need a good stress test.
You do not have the required permissions to view the files attached to this post.
Thanks so much James and Dabbla for your efforts.
Had a late night play with James' version and had some success so far.
Having the 'Stop Servant' rule makes the servant stop before cycling through the additional triggers - without the Stop Servant, the Servant will trigger each rule multiple times .
I'm wondering if I have to many rules requests which can't all be cycled through in the time I have the settings for.
On my quick laptop, I deleted all markets in Guardian and set it to Refresh every 20ms which I also set for the Refresh interval on Guardian.
James' files certainly allowed the 'place' markets to accept more than one trigger from a different servant click which is progress, but they wouldn't do all of the rules I'd asked of them.
[multiple markets each with multiple (back) rules (with different parameters) & conditions all to trigger multiple times]
I was wondering whether each Servant back rule needs a unique SV for each of the 'place' markets to use - I'll give that a try as well.
I'll do some more testing later tonight and report
Had a late night play with James' version and had some success so far.
Having the 'Stop Servant' rule makes the servant stop before cycling through the additional triggers - without the Stop Servant, the Servant will trigger each rule multiple times .
I'm wondering if I have to many rules requests which can't all be cycled through in the time I have the settings for.
On my quick laptop, I deleted all markets in Guardian and set it to Refresh every 20ms which I also set for the Refresh interval on Guardian.
James' files certainly allowed the 'place' markets to accept more than one trigger from a different servant click which is progress, but they wouldn't do all of the rules I'd asked of them.
[multiple markets each with multiple (back) rules (with different parameters) & conditions all to trigger multiple times]
I was wondering whether each Servant back rule needs a unique SV for each of the 'place' markets to use - I'll give that a try as well.
I'll do some more testing later tonight and report
-
jamesedwards
- Posts: 5098
- Joined: Wed Nov 21, 2018 6:16 pm
It works fine for me.Tuco wrote: ↑Sun Dec 21, 2025 1:47 pmThanks so much James and Dabbla for your efforts.
Had a late night play with James' version and had some success so far.
Having the 'Stop Servant' rule makes the servant stop before cycling through the additional triggers - without the Stop Servant, the Servant will trigger each rule multiple times .
I'm wondering if I have to many rules requests which can't all be cycled through in the time I have the settings for.
On my quick laptop, I deleted all markets in Guardian and set it to Refresh every 20ms which I also set for the Refresh interval on Guardian.
James' files certainly allowed the 'place' markets to accept more than one trigger from a different servant click which is progress, but they wouldn't do all of the rules I'd asked of them.
[multiple markets each with multiple (back) rules (with different parameters) & conditions all to trigger multiple times]
I was wondering whether each Servant back rule needs a unique SV for each of the 'place' markets to use - I'll give that a try as well.
I'll do some more testing later tonight and report
I set it to trigger the place markets a maximum of 5 times to prevent you accidentally changing something that made it run away with itself. If you want more than 5 max triggers then amend the max number of triggers upwards.
Guardian will of course need to refresh each place market for each to trigger. Therefore good market refresh management is essential.
The 'stop servant' line is just best practice to prevent accidental delayed triggers in the event of conditions not met at point of trigger then meeting in the future. It shouldn't stop any of the place markets from triggering.
...yes thank you for that James - your v2 is an improvement on v1 and does allow additional Servant clicks to be triggered in the place markets
We're getting there and progress is definitely being made and I'm learning more by the minute. My problem is I know what I want the Servant & Automation to do, but I don't know the best way of achieving it and I don't as yet know the difference between some of the options and (terminology), ie is 'Wait 0.02 seconds before rearming' the same as 'Rearm every refresh' when the refresh rate is set to 20ms? If there is cycling congestion, what would be the fastest/best settings for this?
With the way I trade, speed is everything for me. I'll be using these servant/automation very differently when markets are in-play or not in-play, and as such will need to adjust the rules accordingly due to the in-play delay.
Without the 'Stop Servant' I'm able to get the Servant to cycle through the rules and trigger multiple times with a single click. Less important when backing a selection but when laying a selection this is something I'll often be doing (of course with a different set of servant/automation files).
Yes that works fine if you click the Servant 5 times, but as yet I don't think the 'place' markets file can trigger multiple back bets in multiple place markets all with a single Servant click. I'll be trying and testing again later along with the files from Dabbla.jamesedwards wrote: ↑Sun Dec 21, 2025 2:11 pmI set it to trigger the place markets a maximum of 5 times to prevent you accidentally changing something that made it run away with itself. If you want more than 5 max triggers then amend the max number of triggers upwards.
We're getting there and progress is definitely being made and I'm learning more by the minute. My problem is I know what I want the Servant & Automation to do, but I don't know the best way of achieving it and I don't as yet know the difference between some of the options and (terminology), ie is 'Wait 0.02 seconds before rearming' the same as 'Rearm every refresh' when the refresh rate is set to 20ms? If there is cycling congestion, what would be the fastest/best settings for this?
With the way I trade, speed is everything for me. I'll be using these servant/automation very differently when markets are in-play or not in-play, and as such will need to adjust the rules accordingly due to the in-play delay.
Without the 'Stop Servant' I'm able to get the Servant to cycle through the rules and trigger multiple times with a single click. Less important when backing a selection but when laying a selection this is something I'll often be doing (of course with a different set of servant/automation files).