Pages:
Actions
  • #16 by MarkV on 16 Mar 2013
  • Hi
    It should not place a bet on the same selection UNLESS the previous index was different.

    I'll test it now using selections name instead of index
  • #17 by MarkV on 16 Mar 2013
  • Hi
    I've taken a different approach using a remember trigger in a repeating block. I tested it on a few markets and it seems to be OK.

    Please try it in test mode.
  • #18 by racepro on 16 Mar 2013
  • MarkV & mcbee,
    I have tested the change.mft and it is part way there in that it bets
    on more than one fav. as it was designed to do of course.
    However it does not repeat a bet on the same horse.
    Horse names are not important for my purposes only fav changes
    it can be two horses swapping fav order several times and each horse would
    be bet at alternate fav changes  as explained in my last post/s
    Thanks for this ongoing support.
    R
    ps..... I just noticed another version of change.mft I will try it now
  • #19 by mcbee on 16 Mar 2013
  • hi mark
    WOW. well done
    the trigger worked perfect

    mcbee
  • #20 by racepro on 16 Mar 2013
  • Hi guys,

    Yes I tested it on a couple of races and has worked.
    The only other part I need is to bet 10% higher than the previous bet.
    eg:
    bet 1  5.00
    bet 2  5.50
    bet 3  6.05
    etc
    Thanks again.... better get some sleep stayed up all night watching the rugby.
    I'm in Asia.
  • #21 by MarkV on 16 Mar 2013
  • Quote from: mcbee on 16 Mar 2013, 18:54
    hi mark
    WOW. well done
    the trigger worked perfect

    mcbee
    Thanks mcbee. It's a modification based on Oxa's back the 2nd to go below 2
  • #22 by racepro on 16 Mar 2013
  • Hi mcbee & MarkV,
    Further to my previous posting I have one final condition and that is
    bet number two. I would like to make it a higher percentage bet then the next bets
    eg: 
    base bet      5.00
    second bet  7.00   (that is 40% higher than base bet)
    third bet      7.70  10% higher than previous one
    fourth bet    8.47  10% higher than previous one
    fifth bet     11.86   10% higher than previous one
    and so on...........
    Is this possible?
    Thanks
    R
  • #23 by mcbee on 16 Mar 2013
  • hi
    in the amount box type or copy and paste
    IF(r_1_bm_number=0,default_backa,IF(r_1_bm_number=1,default_backa+(bm_backa*.40),default_backa+(bm_backa*.10)))


    mcbee
  • #24 by racepro on 17 Mar 2013
  • hi mcbee,
    thanks again for the formula and we're getting closer but not quite there yet.
    I ran the trigger on a few races and here is a race where there were 3 horses changing fav order several times. A good test for the trigger.
    Below are the results. Alongside are what the bets should have been.

    Horse A  bet 5.00    5.00
              B  bet 5.00    7.00  previous bet *1.4 (2nd bet always 40% higher)
              C  bet 5.00    7.70  previous bet *1.1
              B  bet 7.00    8.47  previous bet *1.1
              C  bet 7.00    9.32  previous bet *1.1
              B  bet  5.70  10.25 previous bet *1.1
              C  bet 5.70   11.27 previous bet *1.1
              B  bet  5.57   12.40 previous bet *1.1
              C  bet  5.57   13.64 previous bet *1.1
    I think currently the horse id is linked whereas horse name doesn't matter
    as long as fav changes. The above is a good example
    Thanks for your continuous patience..
    R


     
  • #25 by racepro on 17 Mar 2013
  • Hi,
    I've tested the trigger on about 15 races and mostly the bets are on the new fav.
    However on a couple of races there were consecutive bets on the same horse.
    eg:
    Horse A
    Horse A
    Horse B
    Horse A

    and

    Horse A
    Horse B
    Horse C
    Horse C

    In the first example two consecutive Horse A were bet
    in the second example two consecutive Horse C were bet.
    Somehow I need to build a safety factor in to ensure that doesn't happen.
    any ideas?
    thanks
    R
  • #26 by mcbee on 17 Mar 2013
  • hi
    i noticed that if in play the fav changes pos back and fore withing a split sec and this causes extra bets
    maybe a time limit with the prices might help
    something like using the pdiff_.016=0 , but it would need experimenting with the time, .016=1second, pdif=price difference


    mcbee
  • #27 by racepro on 17 Mar 2013
  • Thanks mcbee I will look at that.
    Did you see my earlier post ? There is a problem with the bet sizing
    Thanks
    R
  • #28 by MarkV on 17 Mar 2013
  • Hi
    The close block action waits for an updated list of bets. The favourite may have changed and changed back during this delay. Try increasing the frequency the bets list is updated in the Betting settings.
  • #29 by racepro on 17 Mar 2013
  • Hi MarkV & mcbee,

    I've reposted this again fearing it may get shuffled to the back.

    thanks again for the formula and we're getting closer but not quite there yet.
    I ran the trigger on a few races and here is a race where there were 3 horses changing fav order several times. A good test for the trigger.
    Below are the results. Alongside are what the bets should have been.

    Horse A  bet 5.00    5.00
              B  bet 5.00    7.00  previous bet *1.4 (2nd bet always 40% higher)
              C  bet 5.00    7.70  previous bet *1.1
              B  bet 7.00    8.47  previous bet *1.1
              C  bet 7.00    9.32  previous bet *1.1
              B  bet  5.70  10.25 previous bet *1.1
              C  bet 5.70   11.27 previous bet *1.1
              B  bet  5.57   12.40 previous bet *1.1
              C  bet  5.57   13.64 previous bet *1.1
    I think currently the horse id is linked whereas horse name doesn't matter
    as long as fav changes. The above is a good example
    Thanks for your continuous patience..
    R
  • #30 by mcbee on 17 Mar 2013
  • hi
    so you want to increase per bet not for individual selection increase
    IF(market_mbnum=0,default_backa,IF(market_mbnum=1,default_backa+(bm_backa*.40),default_backa+(bm_backa*.10)))

    this is for per bet

    mcbee
Pages:
Actions