Automation: Storing the "row index" of matched bet

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
crr4253
Posts: 10
Joined: Sun Jul 02, 2023 1:23 pm

Hi All

I wanted some help with storing the selection on a market to use this selection "row index (Betfair order)" on another rule.

Rule 1 (current state): If any selection on the market hits a criteria, a bet is placed.

New rule criteria: Once Rule 1 is triggered and the bet is matched, I would like to retrieve "row index (betfair order)" of this selection into a stored value/criteria to trigger another rule based off the "row index"

I thought this article may have helped, but i was not able to get the intended result : viewtopic.php?f=46&t=22831&p=250255&hil ... ue#p250255

I appreciate any help you can provide.
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

If you are just after placing additional bets on the same selection the first rule triggers on you don't need to use stored values

Leave your first rule as it is (without setting any SV's)

Then on your second rule apply it to 'ANY' selection, and add a;
'Number of Place bet Triggers' condition
On Selection
is Greater than 0

That will ensure the second rule only triggers on the same selection as the first
crr4253
Posts: 10
Joined: Sun Jul 02, 2023 1:23 pm

Hi Dallas,

Thanks for the reply.

For the 2nd rule, I would like to place a bet on another selection if the 1st section matched the price changed to X value. So I thought if i could store "row index" matched i could have a condition for NOT this "row index" but any other.

I hope that clarifies where I am trying to get to
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

crr4253 wrote:
Fri Jul 07, 2023 5:54 pm
Hi Dallas,

Thanks for the reply.

For the 2nd rule, I would like to place a bet on another selection if the 1st section matched the price changed to X value. So I thought if i could store "row index" matched i could have a condition for NOT this "row index" but any other.

I hope that clarifies where I am trying to get to
Yes, it does

So in that case you could still do exactly the same as I put above, except in the condition use
equal to 0

The second rule will then trigger on ANY selection that has not already had a bet placed on it
crr4253
Posts: 10
Joined: Sun Jul 02, 2023 1:23 pm

That is great, thanks for the help :D
crr4253
Posts: 10
Joined: Sun Jul 02, 2023 1:23 pm

Sorry Dallas 1 more thing...

How would i compare the current BACK price of the section? This is a criterion i am missing to compare against

Thanks in advance again
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

crr4253 wrote:
Fri Jul 07, 2023 6:23 pm
Sorry Dallas 1 more thing...

How would i compare the current BACK price of the section? This is a criterion i am missing to compare against

Thanks in advance again
What are you comparing the back price to?
ie, is it just greater or less than
Or is it against the price of another selection
crr4253
Posts: 10
Joined: Sun Jul 02, 2023 1:23 pm

If the BACKED/Matched price of the selection was say 2 but "last traded price" of the selection has is now drifted to 6 run the rule
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

crr4253 wrote:
Fri Jul 07, 2023 6:36 pm
If the BACKED/Matched price of the selection was say 2 but "last traded price" of the selection has is now drifted to 6 run the rule
For that you'll need to add another rule

If you use a 'Set/Modify Signal' rule with the following condition
'Number of place bets trigger condition' - on selection is greater than 0
'Fixed odds condition' - LTP is greater than (whatever price)

and on the signal tab set a signal on the market (with any name you want)

Then on your second rule also add a Signal Set condition
to test if the signal named (whatever you called it) on the market is set with a value


What you might need to consider is if the 1st runner goes above 'X' but other conditions on your second rule aren't satisfied, then the 1st runner drops below 'X' again, - would you still want the second rule to trigger when its conditions are met (as the signal from the first runner will still be set)
Or would you want to clear the signal if it dropped below and have the signal set again if it goes above 'X' ?
crr4253
Posts: 10
Joined: Sun Jul 02, 2023 1:23 pm

Thanks for the further detail.

On your instruction, "Fixed odds condition' - LTP is greater than (whatever price)" Need to specify the selection, which would I choose?

On this point:
What you might need to consider is if the 1st runner goes above 'X' but other conditions on your second rule aren't satisfied, then the 1st runner drops below 'X' aagain- would you still want the second rule to trigger when its conditions are met (as the signal from the first runner will still be set)
Or would you want to clear the signal if it dropped below and have the signal set again if it goes above 'X' ?

Maybe easier with example:

1. Selection is backed based on criteria (from any selection), IF this selection drifted to X move to rule 2 (if not do nothing)
2. back The current favorite (by fav position sort order)

For this reason I need to be able specify the exact selection backed initially to allow a rule to be triggered to look for LTP to know if it has drifted.
You do not have the required permissions to view the files attached to this post.
User avatar
Dallas
Posts: 23597
Joined: Sun Aug 09, 2015 10:57 pm

crr4253 wrote:
Fri Jul 07, 2023 11:37 pm

On your instruction, "Fixed odds condition' - LTP is greater than (whatever price)" Need to specify the selection, which would I choose?
The rule would be applied to 'ANY' selection
The number of place bet triggers condition will ensure it checks and triggers on the first selection bet on

crr4253 wrote:
Fri Jul 07, 2023 11:37 pm

On this point:
What you might need to consider is if the 1st runner goes above 'X' but other conditions on your second rule aren't satisfied, then the 1st runner drops below 'X' aagain- would you still want the second rule to trigger when its conditions are met (as the signal from the first runner will still be set)
Or would you want to clear the signal if it dropped below and have the signal set again if it goes above 'X' ?

Maybe easier with example:

1. Selection is backed based on criteria (from any selection), IF this selection drifted to X move to rule 2 (if not do nothing)
2. back The current favorite (by fav position sort order)
It was just something to consider if you had additional conditions on your second bet rule which might keep it from triggering as soon as the first drifted out,
If the only condition is the first runner has drifted out then you don't need to worry about this scenario
Post Reply

Return to “Bet Angel - Automation”