Pages:
Actions
  • #1 by racepro on 11 Feb 2014
  • Hi,
    How can I 'spread loss' in favour of favourite instead of 'selection' ?
    I have a trigger that lays the non fav in a 2 player match.
    Is there an action or condition I can add to do that ?
    example A: when a green up takes place
    Player A Lay  2.40  5.00
    Player A GUB 2.50  5.00 

    Example B:  when a Greenup doesn't take place and places lay bet on other player:
    Player A Lay  2.40 5.00
    Player B Lay  2.30 5.00
    Player B GUB 2.40 5.00
    In both cases I would like to spread any losses from the Fav to the non fav.
    Thanks for your help
    Cheers
    R
  • #2 by MarkV on 11 Feb 2014
  • Hi
    In mcbee's unequal stop loss trigger (attached) if you back the fav and it goes against you:
    set the stop loss percent constant for the percent constant to 100
    it will eliminate the loss on the new fav

    If you lay the fav and it goes against you:
    set the stop loss percent to 0.01
    it will  eliminate the loss on the fav you layed on.

    The attached spread loss trigger will eliminate a loss on the fav spreading the loss to other selections. You can add other conditions relevant to your betting.

    Please use test mode when trying the triggers.
  • #3 by racepro on 11 Feb 2014
  • Hi Mark,
    Thanks for the triggers.
    I am getting a (red) error message in the 'eliminate loss' logs
    'There is no potential loss on Selection xyz'
    It does not appear to pose any problem and wondering why
    it is shown as an error rather than just a statement in green.
    Secondly, I am curious to know what criteria causes the trigger to fire as it is
    not tick or % driven. Is the 'spread loss' hard coded?
    Any ideas ?
    Thanks
    R
  • #4 by MarkV on 11 Feb 2014
  • Hi
    Spread Loss action will check all matching selections until a loss is detected on the matching selections, and will then eliminate the loss on them.
     
    The condition in the trigger restricts the spread loss to the fav (selections rank is equal to 1). So each refresh it checks the fav to see if it has a potential loss. If not, it reports in the log there is no potential loss on <fav name>. It will continue to do this each refresh until a potential loss is detected, at which time (depending on other conditions) it will eliminate the potential loss on that selection by "spreading" the eliminated potential loss across all other selections, increasing the potential liability on all other selections. Hope that makes sense.

    Second question is also answered above. Spread Loss is hard coded, but you can use conditions to decide when to invoke it.

    Typically Spread Loss is used once per market in an attempt to zero any potential loss on the potential winner. Therefore it is not without risk, because after the loss has been eliminated, another selection with the increased liability may win.
  • #5 by racepro on 11 Feb 2014
  • Hi Mark,
    Thanks once again for your succinct description of the workings of 'spread loss'
    It certainly makes sense.
    However one query I have is your last couple of lines:
    "another selection with the increased liability may win."
    If my conditions include "rank equals 1" then wouldn't the eventual winner have a liability of zero at worst ? as it would have become favourite and the spread loss trigger would hopefully have fired.?
    Cheers
    R
  • #6 by MarkV on 11 Feb 2014
  • Hi
    I said the potential winner.
    Rank equals 1 would have a liability of zero at the time the spread loss bet is matched. This selection will quite likely win, however, it is possible the favourite may change after you spread the loss on the original favourite, and the new favourite will go on to win. In this situation you will incur the higher liability on the winner because the original favourite on which the potential loss was eliminated is not the actual winner.
  • #7 by racepro on 11 Feb 2014
  • OK got it
    Thanks
    R
Pages:
Actions