Pages:
Actions
  • #1 by Dii84 on 12 May 2020
  • Can you please make a greyhound trigger?
    I want to lay a trap number of my choice. Lets say always trap number 5 but with option to change it if I want to. 
    Odds no higher than 9.
    Staking is 0,5% of the bank.

    The first part of the recovery process is after a loss, recover 100% of the loss in one bet. The recovery stake should also include the original stake amount so I still achieve a profit.

    If the second bet is lost then software should work out the total loss suffered over the 2-loss sequence I had and divide this by 4. Then stake this amount with the aim of winning 4 bets in a row. When I have done so, return to the original stake.

    If I suffer another loss whilst going for 4 wins in a row, re-calculate my entire loss and the new stake by dividing by 4 again.

    But I also want to be able to choose max stake amount. Like never bet more than 15 euros.

    Regards
    Dace







  • #2 by Dii84 on 15 May 2020
  • If it's not too late is it possible to add the time when to place bets? It's no sooner than 0,5 minutes before start. Thanks!
  • #3 by Oxa (WellDoneSoft) on 26 May 2020
  • Hello!

    Please see your triggers attached. Use the constants inside the file to adjust the trigger settings.

    With the maximum odds set at 9 and the initial bet size at 0.5% of the bank, there is little chance that you will have enough bank to cover the next bet after the second loss. So I'd recommend reducing the initial stake to at least 0.1% of the bank. Anyway, experiment with init_bet, max_odds/max_recovery_odds and max_bet_size.

    Make sure to test the triggers in Test Mode first.
  • #4 by Dii84 on 26 May 2020
  • Thank you!
  • #5 by Dii84 on 27 May 2020
  • I am testing the trigger but for some reason it is not placing any bets
  • #6 by Oxa (WellDoneSoft) on 27 May 2020
  • Hello!

    Please check your Program Log for any error messages. Here is the video tutorial on how to do it:

    https://youtu.be/LcCEiXc6Ovk

    If this does not reveal the problem, please check the log of the trigger that is placing bets.

    Again, here is another video tutorial on how to view trigger logs:

    https://youtu.be/1iEeXNCwAFQ

    Start watching from 02:43.
  • #7 by Dii84 on 27 May 2020
  • There are no error messages on Program log and in trigger log for all races is the same text Inappropriate market status (Finished)
  • #8 by Dii84 on 28 May 2020
  • Today I got this error
  • #9 by Dii84 on 28 May 2020
  • And in trigger log under laying section all selections are like this
  • #10 by Oxa (WellDoneSoft) on 28 May 2020
  • Hello!

    Please do the following:

    1. Go to "Logger Options" and tick "Log trigger expressions".
    2. Add £500 to your Test Account (I assume you are testing the triggers in Test Mode).
    3. Run the triggers again.

    Then re-send me the trigger log please.
  • #11 by bobh on 28 May 2020
  • The first condition in the lay trigger looked unusual to me, as it simply reads "selection's is equal to trap". I changed it to read "selection's name contains trap", and the trigger fired away ok.

    Anyway, give it a go and see if it works for you.

    Doggies are finished in Oz now, so you'll have to wait until tomorrow!

    Bobh
  • #12 by Dii84 on 28 May 2020
  • The first condition in the lay trigger looked unusual to me, as it simply reads "selection's is equal to trap". I changed it to read "selection's name contains trap", and the trigger fired away ok.

    Anyway, give it a go and see if it works for you.

    Doggies are finished in Oz now, so you'll have to wait until tomorrow!

    Bobh


    Thanks. Will try tomorrow.
  • #13 by Oxa (WellDoneSoft) on 28 May 2020
  • Quote
    The first condition in the lay trigger looked unusual to me, as it simply reads "selection's is equal to trap". I changed it to read "selection's name contains trap", and the trigger fired away ok.

    That's because you are still using the older version of MF Pro.

    The newest version supports Greyhound Trap number, so unfortunately this advice won't help.
  • #14 by bobh on 29 May 2020
  • Could that be the problem? Older version?

    Just tryin' to help.

    bobh

  • #15 by Oxa (WellDoneSoft) on 29 May 2020
  • Bobh, thanks for offering your help!

    The client is using the latest version. Yes, if she had been using the older version, like you are, she wouldn't have been able to run these triggers.
Pages:
Actions