Pages:
Actions
  • #16 by LarpHager on 02 Feb 2014
  • Ty
    • LarpHager
  • #17 by racepro on 02 Feb 2014
  • Thanks Mark
    R
  • #18 by racepro on 02 Feb 2014
  • Mark,

    I'm going to try using both above tick gap conditions in an effort to prevent
    trigger from ignoring the r_ticks one. I've had bets firing when there are more than 2 ticks separating back and lay odds.
    To confirm:
    Lay bet condition:
    and Selection's Back Price is equal or greater than r_ticks(lay_price, -2)
    Comments appreciated/thanks
    R
  • #19 by MarkV on 02 Feb 2014
  • Hi
    Add a condition before the g_ticks and r_ticks conditions:
    and selections lay price is between 1.02 and 50.00 (say)
    to ensure there is a lay price available for the tick gap conditions.
  • #20 by racepro on 03 Feb 2014
  • Mark,

    I already have price conditions in place.
    If no lay price available it usually reflects as an error in the logs
    'error in trigger expression or bet amount'
    probably due to a divide by zero error.
    thanks
    R
Pages:
Actions