Author Topic: Selection ID condition help please  (Read 1721 times)

Tags:
  • All members
  • Posts: 829
Selection ID condition help please
« on: 26 Aug 2014, 09:27 »
Hi,
I've noticed with the help of Time Machine that when the favourite order changes in a tennis match (in-play) the Back and Lay Book %'s  are all over the place for 4-5 seconds before they settle down. The reasons are a different subject for another day.

As a result of these changes, in this case, a lay bet, cannot be placed as the percentages are outside the limits of the condition. Once settled, what was once Rank 2 now becomes Rank 1. This leads to my trigger placing a lay bet on the wrong selection.

To overcome this I need a condition that is unique to the last back selection.

example:
Selection ID is same as Selection ID of last matched back bet.

Can you assist?
Many thanks
R

ps.... This probably won't help getting the bet on as the bird would have flown but it will prevent betting on the wrong player.     
My grandma taught me not to run downstairs and never back odds on.

  • Élite
  • Posts: 3698
  • Gender: Male
*
Re: Selection ID condition help please
« Reply #1 on: 26 Aug 2014, 15:29 »
hi
add an action to your back betting trigger
set use variable
name    lb
value     sel_id
individually for each market

in your lay betting trigger add the condition
and selections trigger expression lb is equal to sel_id

so when a back bet is placed, lb records the selections id number, then your lay trigger will only place a lay bet on the selection id that had a back bet placed last


mcbee
Please read the following  disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: Selection ID condition help please
« Reply #2 on: 27 Aug 2014, 04:19 »
Hi mcbee, Thank You, it works a treat.
Cheers
R
My grandma taught me not to run downstairs and never back odds on.

 

Please note, BetFair is seems to be currently OFFLINE