Pages:
Actions
  • #1 by racepro on 16 Mar 2013
  • Hi,

    I would like to bet the fav "in play"/"idle" and trigger another bet with a differing bet amount whenever there is a new fav.
    eg:   blackjack (fav) 2.70  bet  5
            Geronimo (newfav)  2.40  bet 10% higher bet 5.5
    I'd like the trigger to detect whenever there is a new fav in the event and place an amount of x% more than the previous bet amount.
     Any help to design the trigger much appreciated.
    thanks
    R
  • #2 by mcbee on 16 Mar 2013
  • hi
    your betting trigger would have to be set to
    no more than 1.00 sec    (1.00 more or less your choice)
    set to favorite
    in the amount box type
    default_backa+(market_mbnum*.10)
    and selections back matched is equal to 0  (important miss this and you will have muliple bets per sec)
    and selections back unmatched is equal to 0   (important miss this and you will have muliple bets per sec)

    alter the .10 to the percent that you want to increase .10=10%

    mcbee
  • #3 by racepro on 16 Mar 2013
  • mcbee,

    Thanks for the formula. Two queries I have.
    1) the formula you gave me goes up in increments of 10. What
         I was looking for is the new bet to be say 10% higher than the last bet. 
         eg: 5.00, 5.50, 6.05, 6.66 etc.
    2) if a horse is fav more than once during "in play"/"idle" then it should be bet each        time. In other words the trigger should not recognise horse name.
    Thanks again
    R
         
  • #4 by mcbee on 16 Mar 2013
  • hi
    it is  .10 NOT 10
    the trigger will keep betting on any selection that becomes favourite and has no matched or unmatched amounts.
    BUT to set the trigger to bet each time the selection becomes the favourite, it would just keep placing bets every sec, not a good idea.
    you could set the trigger to only place a bet if the back price is less than the back matched price


    mcbee
  • #5 by racepro on 16 Mar 2013
  • Hi mcbee,

    I copied and pasted your formula "default_backa+(market_mbnum*.10)"
    However that increases the bets by increments of 10  using a 5.00 bet stake
    they appear as follows  5.10, 5.20, 5.30, 5.40 etc.
    What I am trying to achieve is to increase the bet by 10% from
    the last bet. So if last bet was 5.00 then next bet is 5.00*1.1 =5.50 and next bet would be 5.50*1.1= 6.05.
    The idea is to bet only when a change of favourite.
    eg:  Horse A @ 2.80 Fav bet = 5.00 ...... then B becomes fav at  2.30
    So   Horse B @ 2.30 Fav bet = 5.50 (5.00*1.1=5.50)........ then A becomes fav again 
    So   Horse A @ 2.10 Fav bet = 6.05 (5.50*1.1=6.05)  etc etc
    The fav order may only change a couple of times in a race so there would only be a handful of bets at most in one race, but they could involve the same horses swapping fav order.
    Hope this is clearer
    Many thanks if a solution could be found.
    R
     
  • #6 by mcbee on 16 Mar 2013
  • hi
    default_backa+(bm_backa*.10)


    mcbee
  • #7 by racepro on 16 Mar 2013
  • hi mcbee,

    seems like it has to be done in excel as changing fav order
    as I explained below, is not possible.
    R
  • #8 by mcbee on 16 Mar 2013
  • hi
    it all depends on how many bets you want to place per fav selection
    if you set a trigger to once every 1 sec, then every time the fav odds drop, it would place a bet .


    mcbee
  • #9 by racepro on 16 Mar 2013
  • hi mcbee,

    I only want to bet on fav order changes as mentioned above.
    If horse A is fav then that would be my first bet
    if horse B takes over as fav then I want to bet that horse. If horse A
    becomes fav again I want to again bet that horse.
    In the above example I would have bet horse A twice and horse B once so a total of only three bets on the race.
    I am curious to know what conditions would be required to bet only when fav  changes.
    Maybe it can't be done using the build trigger and excel may be required.
    I hope I am explaining it clearly
    thanks
    R
  • #10 by mcbee on 16 Mar 2013
  • hi
    i think i understand now
    only place a second bet if the fav changes, not the odds.
    maybe this could be used
    bm_backid
     long integer
     The ID of the last non-SP matched back bet that you placed on the selection
     
    it sounds like it records the last sel id
    so a condition with
    and selections trigger expression sel_id is not equal to bm_backid

    i have to many bots running at the moment to test the example, but i will look further into it when i can

    mcbee
  • #11 by MarkV on 16 Mar 2013
  • Hi
    Hope you don't mind me adding to this topic.
    Try the attached trigger in test mode. It is the basic mechanics of backing the next change of favourite. If you are happy with it then add mcbee's amount formula.
  • #12 by racepro on 16 Mar 2013
  • Thanks mcbee for your patience. I know you are extremely busy.
    If I could bet each time there is a fav change which means a horse
    could be bet more than once during idle/in play modes. A simple example
    if the first two favs took turns being fav say 3 times each then we have three bets
    on each horse. eg;   horse A, Horse B, Horse A, Horse B, Horse A, Horse B.
    A selection id as you say would be required to identify that a horse has become fav and is different from last fav bet but could be same as 2nd last fav bet.
    If that makes sense.
    When time permits
    Many Thanks
    R
  • #13 by racepro on 16 Mar 2013
  • Hi MarkV,
    Thanks for your input, yes it helps me for sure.
    My next question is how can I keep repeating the process
    as shown in my last posting as the fav changes throughout
    the idle/in play which could be ten or more minutes and could
    alternate between two or three horses and each horse could
    be fav more than once as explained in last posting.
    Thanks again for helping this new kid on the block. I'm
    trying to learn a little everyday.
    R
  • #14 by MarkV on 16 Mar 2013
  • Hi
    Try the last attached trigger at post 10 in test mode. I have not fully tested it, but it should do as you ask. Let me know though if it does not.
  • #15 by mcbee on 16 Mar 2013
  • hi
    it is placing multiple bets for some reason.
    but it is on the right track
    also i had to add another trigger to set the variable to 0
    because it was only betting in 1 race and missing all others after if the fav was the same index


    mcbee
Pages:
Actions