Trigger processing [08052013LND]

I have a trigger that bets on up to 3 greyhounds in an event.
One trigger backs, another trigger lays.

The lays trigger does not fire until ALL back bets have been matched. So if 1 back bet remains unmatched, the subsequent lay trigger won't submit the lay bets. Thus time lapse sees prices changes, sometimes against my position.

Can anyone suggest a way to have the lay trigger fire a complementary lay bet as soon as the greyhound has a backa amount?

hi
condition
and selections back_matched is greater than 0

or condition
and markets number of matched back bets is greater than 0

without triggers i do not know how your first trigger selects the bet,so it is difficult to give a correct answer.
but if your first trigger backs up to 3 selections.
then your lay trigger should be set to
once per selection
condition
and selections back matched is greater than 0

mcbee

Original Trigger attached.

The other issue I have is this.
When a partial back bet is matched.
Example: $20 back bet submitted.
$10 is matched $10 is unmatched
Lay bet is submitted and $10 is matched
Both triggers have 'once per selection'
Now the unmatched $10 back bet is matched.
As the lay trigger has 'once per selection' it won't fire again and I am left with $10 back bet exposed.
What is the work around for this situation?

If I change the lay amount to bm_backa-bm_laya and set 'no more often then 2secs"
Will that work?

Thank you my friend.

hi
had to rush this to get it out before the greyhound racing starts.
have altered your trigger so that the lay will keep betting until the lay matched equals the back matched per selection.

mcbee

please download below

Hi,
don't forget to use the setting 'Update bets individually for each market' and 'Simultaneously with refreshing the market' ON to avoid multiply laying by second trigger. I would also use the repetitive interval 2 times greater than the market refresh rate for sure. First, try the test mode ...

mkas

Trigger processing [08052013LND]

Hello Guest