Pages:
Actions
  • #1 by racepro on 02 Aug 2014
  • Hi,
    I would like a condition to prevent a trigger laying the opposing player which has a matched back bet.
    example:
    Nadal   back 5.00   1.30
    Murray lay    5.00   1.70
    The above bet (Murray) should not be placed.
    Thanks
    R
  • #2 by mcbee on 02 Aug 2014
  • hi
    and selections back matched is equal to 0


    mcbee
  • #3 by racepro on 02 Aug 2014
  • hi mcbee,
    The only problem with that is I may want to place a lay bet on the same selection as the matched back bet.
    I am trying to avoid laying player B when I have backed Player A which is about the same thing.
    Hope that makes sense
    R
  • #4 by mcbee on 02 Aug 2014
  • hi
    if the index number for A and B are always the same per match then use
    and selections trigger expression s_1_back_matched is equal to 0  (for A if a is index 1)

    mcbee

  • #5 by racepro on 02 Aug 2014
  • hi mcbee,
    I have two triggers and both are designed to bet the favourite.
    Trigger1  places a back bet on Nadal  5.00 @ 1.40
    Sometime later favourite order changes
    Trigger 2 places a lay bet on Murray  5.00 @ 1.70
    The above bet should not be placed as it only increases the liability on Murray.
    I need conditions for both triggers.
    I wasn't sure what the s_1 meant.
    can you kindly write out for each of them
    Many thanks
    R
  • #6 by mcbee on 02 Aug 2014
  • hi
    that only adds to the confusion
    can you start a fresh and say how you end up backing then laying, is it if the favourite is less than x price back or more than x price lay.
    do you only want to bet on the first favourite back then lay and not on any other selection that is favourite after the first bet.

    mcbee
  • #7 by racepro on 02 Aug 2014
  • hi mcbee,
    yes upon further study it does sound a bit confusing.
    I would even make it sound more confusing by trying to explain it.
    Perhaps you could give me the formula for the last matched lay bet
    and I can figure it out. Also what is  s_1_back_matched  does that relate to index 1?
    Thanks again
    R
  • #8 by mcbee on 03 Aug 2014
  • hi
    yes s_1 , is selections index 1
    if you only have 1 back bet on the favourite and want to lay it if the conditions are correct later, but you do not want to lay bet the other selection, then in your lay betting trigger all you need is
    and selections back matched is greater than 0
    but if you do want to lay and back any, then you will need to add condition blocks to your lay trigger, with conditions to place bets if the selection has a matched back bet or whatever your other conditions are for the lay bet.


    mcbee
  • #9 by racepro on 03 Aug 2014
  • Hi mcbee,

    Okay I am a bit fresher this morning, so let me have a go at explaining my set of triggers.
    I'll describe the formulas in words rather than code is places.
    Bear in mind I have two sets of triggers one for each index.
    I'll just list index 1 here.
    Firstly bets are only placed on the favourite.
    the trigger1 will place a back and lay bet x ticks either side of the current back price.
    When one is matched the other one is cancelled.
    so the basic conditions are
    and selection's index is equal to 1
    and rank is equal to 1
    The next time a bet is placed is if the Index 2 trigger selection becomes favourite.
    Then trigger2 will place a back and lay bet x ticks either side of the back price.
    when one is matched the other one is cancelled
    Herein lies the problem.... if the former fav has a matched back bet then the new fav has a matched lay bet that would double the exposure on the one player.
    I would only want trigger2 in this example to place a back bet only, as trigger 1 placed a back bet.  If Trigger 1 had its lay bet matched then I would only want Trigger 2 to place a lay bet.
    Bearing in mind as I said earlier this example only relates to Index 1 placing the first bets meaning the fav was index 1 related. If this formula could be worked out the one for trigger 2 would be a simple amendment.
    If you refer to my examples given in previous posts it may make sense
    Hope this is clearer than mud :)
    Thanks
    R

  • #10 by racepro on 06 Aug 2014
  • Any luck mcbee? or is it mission impossible?
    R
  • #11 by 1oser on 07 Aug 2014
  • please test attached .. even if not 100% .. it should set you on the right track I hope.
  • #12 by LarpHager on 07 Aug 2014
  • hi,

    Here's another one for luck!!!

    Tried it on horseracing and cricket........conditions work, albeit you need to vary the prices/amounts


    Good luck
    • LarpHager
  • #13 by racepro on 07 Aug 2014
  • Thanks 1oser, I am going to look at this in the morning and see how I can incorporate into my existing triggers or maybe they are already stand alone and ready to go.
    Will come back to you tomorrow
    Cheers
    R
  • #14 by racepro on 07 Aug 2014
  • Hi LarpHager, It must be my lucky day two replies in one day :)
    I'll look at it tomorrow and come back to you with my findings.
    Cheers/Thanks
    R
  • #15 by racepro on 09 Aug 2014
  • Hi Guys,
    I'm working on my existing triggers which are similar to the ones you supplied however I have learned a few tricks from yours especially some coding
    I'll know in a few days and will let you know my progress.
    thanks a million
    R
     
Pages:
Actions