Quite a technical one for me

[Emtaxx]

On the road atm will take a look when I get back
Do you think it’ll then work as intended once this has been fixed ?

[Emtaxx]

Hi
your "back bet" rules are not applied to "every", they are applied to 1,2 and 3rd fav.

I've just looked, looked like its set to EVERY to me. the last rule is the back bet. Not sure where its aplied to 1,2,3 fav?

[jamesedwards]

If your selections flit in and out of condition criteria then your problem could be because it will trigger every selection that achieves the set conditions on that specific refresh cycle. If it triggers against 1 or more selections then it will wait until the next applicable refresh before it will trigger again and you have set this between 1 and 5 secs.

So if selectionA sits within criteria but selectionB doesn't then it will trigger on selectionA and won't trigger on selectionB (even if selB moves into qualifying criteria) until the next applicable refresh cycle.

[jamesedwards]

Or it could be a problem with your signalling. When building a rulefile it's helpful to check the 'market log' boxes as this can help you review what is happening step by step when it's not behaving as you expect.

[Emtaxx]

Hmm yes flitting in and out maybe why but I'm not sure it would e 100% be the issues maybe, I'm not sure at this point to be totally honest and not sure what else to do to make it do what I want other than give it to u guys to see if you can fix it lol.

[jamesedwards]

Hmm yes flitting in and out maybe why but I'm not sure it would e 100% be the issues maybe, I'm not sure at this point to be totally honest and not sure what else to do to make it do what I want other than give it to u guys to see if you can fix it lol.

Why do you need the gap in between retriggers?

If the time gap is needed for individual selections then change the main trigger to every refresh and find another way to prevent retrigger by selection using SVs and conditions. There are several ways to achieve this.

[Emtaxx]

Hmm yes flitting in and out maybe why but I'm not sure it would e 100% be the issues maybe, I'm not sure at this point to be totally honest and not sure what else to do to make it do what I want other than give it to u guys to see if you can fix it lol.

Why do you need the gap in between triggers?

I put the gap between triggers so that it has a cool down period, and doesn't fire 100's of times. A seconds. Do you think I should put it to rearm every refresh then?

[jamesedwards]

Hmm yes flitting in and out maybe why but I'm not sure it would e 100% be the issues maybe, I'm not sure at this point to be totally honest and not sure what else to do to make it do what I want other than give it to u guys to see if you can fix it lol.

Why do you need the gap in between triggers?

I put the gap between triggers so that it has a cool down period, and doesn't fire 100's of times. A seconds. Do you think I should put it to rearm every refresh then?

If the time gap is needed for individual selections then change the main trigger to every refresh and find another way to delay retrigger at selection level using SVs and conditions. There are several ways to achieve this.

I would probably do it by setting an incrementing signal at selection level on the trigger rule, and applying a condition 'signal changed condition' between x and 9999 second ago. (You will need to set the signal to 0 initially at in-play for every selection to make sure the first trigger triggers.)

[Emtaxx]

Why do you need the gap in between triggers?

I put the gap between triggers so that it has a cool down period, and doesn't fire 100's of times. A seconds. Do you think I should put it to rearm every refresh then?

If the time gap is needed for individual selections then change the main trigger to every refresh and find another way to prevent retrigger by selection using SVs and conditions. There are several ways to achieve this.

I'm gana rebuild it with SV's I cant see that I've done anything wrong with the Signals tbh, I cant actually see anything wrong at this point in time to why it just isn't firing on all horses when what tigger has been armed. MAYBE i need to apply Back on all selections could work?

[jamesedwards]

MAYBE i need to apply Back on all selections could work?

Never used it, but I assume that will back all selections which isn't what you want.

Most likely you need to apply my solution above that prevents retrigger at selection level rather than globally.

[Emtaxx]

Just to confirm I've made myself understood with my idea so there's no confusion

when this bot has triggered I want it to fire on all runners at the exact same time, except the one which caused it to trigger.

That's the mission here.

[jamesedwards]

Just to confirm I've made myself understood with my idea so there's no confusion

when this bot has triggered I want it to fire on all runners at the exact same time, except the one which caused it to trigger.

That's the mission here.

It all depends exactly what you are up to as to how easiest to achieve this. Here's a couple of options:

When you identify the selection you don't want to trigger, then set a signal or SV to = x at selection level for that selection.
Then trigger against all selections using 'every' but with the condition that the above signal or SV does not = x.

OR

You could create a consistently-updating custom ranking that keeps the relevant selection at the top, and then trigger on every selection that is not number 1 in the custom ranking.

z155.jpg

[Emtaxx]

Just to confirm I've made myself understood with my idea so there's no confusion

when this bot has triggered I want it to fire on all runners at the exact same time, except the one which caused it to trigger.

That's the mission here.

It all depends exactly what you are up to as to how easiest to achieve this. Here's a couple of options:

When you identify the selection you don't want to trigger, then set a signal or SV to = x at selection level for that selection.
Then trigger against all selections using 'every' but with the condition that the above signal or SV does not = x.

OR

You could create a consistently-updating custom ranking that keeps the relevant selection at the top, and then trigger on every selection that is not number 1 in the custom ranking.
z155.jpg

Hmm the consistently updating raking system seems a bit above my pay grade for now. I'll give the SV option you have suggested a go.

I have also just created a very simple bot that says fire on all under 10.0 odds and it does exactly that, so yeah, not sure whats up with mine above. but will go over it and try rebuild it with SV. I admit my brain is a little fried. So I appreciate the helping hands.