Prevent multiple back bets firing when using more than 1 back rule within 1 automation rule.

[howarth4422]

I have made a scalping bot and copied the back bet rule a few times and changed the historic odds timings slightly. Sometimes the criteria is true for 2 or all 3 of the back bets and they all fire. How do I stop more than 1 from firing? Obviously they’re firing at exactly the same time so can’t find a way of using ‘matched bets amount condition’ or similar
Thanks

[eightbo]

They don't fire at exactly the same time but rather from a top-down perspective e.g. Row 1 then 2 then 3 then 4 etc. so you may want to think about ordering your rules appropriately. This all happens very fast of course so it seems like they fire together.

1) Set a stored value on all rows of 'Fired' = 1 which activates when a back bet is placed.
2) Also put conditions for all back bet rules that 'Fired' = 0 must be TRUE. This way only 1 should back bet rule should fire because when it gets to the next row 'Fired' = 0 returns FALSE.

You would need to reset the value of 'Fired' back to 0 after your first scalp cycle to allow yourself to repeat the process.
I would advise ticking the option to show stored value changes in the log to help you figure out what's going on.

[jimibt]

If the back bets are all for the same runner but are on different rules, you can add the *Number of Place Bet triggers* option (=0). This will effectively only allow the 1st rule with that runner to fire. Even if they *appear* to be all firing at the same time they are in effect sequentially analysed.

If the rules apply to different runners and only one back bet is allowed, then use a similar idea to what Eightbo suggested by throwing a Market signal into the mix which prevents other bets being added once it's present.

[howarth4422]

They don't fire at exactly the same time but rather from a top-down perspective e.g. Row 1 then 2 then 3 then 4 etc. so you may want to think about ordering your rules appropriately. This all happens very fast of course so it seems like they fire together.

1) Set a stored value on all rows of 'Fired' = 1 which activates when a back bet is placed.
2) Also put conditions for all back bet rules that 'Fired' = 0 must be TRUE. This way only 1 should back bet rule should fire because when it gets to the next row 'Fired' = 0 returns FALSE.

You would need to reset the value of 'Fired' back to 0 after your first scalp cycle to allow yourself to repeat the process.
I would advise ticking the option to show stored value changes in the log to help you figure out what's going on.

Thanks for the reply. I’m struggling with setting up the stored value though. If possible could you tell me which options to select or post a screenshot if you have time.
Thanks

[howarth4422]

If the back bets are all for the same runner but are on different rules, you can add the *Number of Place Bet triggers* option (=0). This will effectively only allow the 1st rule with that runner to fire. Even if they *appear* to be all firing at the same time they are in effect sequentially analysed.

If the rules apply to different runners and only one back bet is allowed, then use a similar idea to what Eightbo suggested by throwing a Market signal into the mix which prevents other bets
being added once it's present.

Thanks for the reply. Would this mean each one would only fire once in total though? I want them to fire numerous times but only one per scalping opportunity if that makes sense.

[jimibt]

If the back bets are all for the same runner but are on different rules, you can add the *Number of Place Bet triggers* option (=0). This will effectively only allow the 1st rule with that runner to fire. Even if they *appear* to be all firing at the same time they are in effect sequentially analysed.

If the rules apply to different runners and only one back bet is allowed, then use a similar idea to what Eightbo suggested by throwing a Market signal into the mix which prevents other bets
being added once it's present.

Thanks for the reply. Would this mean each one would only fire once in total though? I want them to fire numerous times but only one per scalping opportunity if that makes sense.

caveat -yes, those would only fire once in total. However, you can also issue a *Checkpoint Matched Bets* rule to clear any of the bet related triggers, such as *Number of Place Bet Triggers*... I've never used this rule type before, but believe that this is its intention.

[gstar1975]

What condition do I use if I want to keep the place bets to 1 per runner when I also want to have the opposing lay bets to be offset in batches of more than 1. As if I also have Number of place bet triggers conditions set to 1 then only 1 of the opposing closing lay bets gets placed.

[decomez6]

. Sometimes the criteria is true for 2 or all 3 of the back bets and they all fire. How do I stop more than 1 from firing?

Nest them in a group of conditions , then mark only one must be true , meaning…
- use dedicated signals for each .
- make 1 back rule for all with a condition that checks all the three signals , nested in a group conditions which only fires if any one of those signals change value . So one or more must be true.

If you want more flexibility with varying combinations , then use the decreament/ increament functions part of the signal . This will help you count the number of times the signals have been called and you can use this number as part of a nested group of conditions. E.g
,” only back when signal x has a count of y amount and the others have a count of z amounts .

[decomez6]

What condition do I use if I want to keep the place bets to 1 per runner when I also want to have the opposing lay bets to be offset in batches of more than 1. As if I also have Number of place bet triggers conditions set to 1 then only 1 of the opposing closing lay bets gets placed.

Set up dedicated back signal with a decreament / increament .
Set up lay rules that monitor the signal count values and fires accordingly ..