Pages:
Actions
  • #1 by Oxa (WellDoneSoft) on 18 Jun 2015
  • In this update we've mainly focused on new trigger variables, but there are some other important additions.

    IMPROVEMENTS

    1. New trigger variables for getting info on all bets you have placed across all markets and selections (as opposed to bets related to a specific market or selection):

    allbets_num - The number of all your bets (matched, unmatched and SP);
    allbets_bm_num - The number of all your back matched bets;
    allbets_bu_num - The number of all your back unmatched bets;
    allbets_bsp_num - The number of all your back SP bets;
    allbets_lm_num - The number of all your lay matched bets;
    allbets_lu_num - The number of all your lay unmatched bets;
    allbets_lsp_num - The number of all your lay SP bets;
    allbets_bm_amount - The amount of all your back matched bets;
    allbets_bu_amount - The amount of all your back unmatched bets;
    allbets_bsp_liab - The amount of all your back SP bets;
    allbets_lm_amount - The amount of all your lay matched bets;
    allbets_lu_amount - The amount of all your lay unmatched bets;
    allbets_lsp_liab - The amount of all your lay SP bets.

    2. New trigger variable for the number of settled markets in your list.

     settled_market_num

    3. New trigger variables for the number of markets and selections affected by the import file (when importing selections for auto-trading):

    imported_mkt_num - the number of markets where imported selections were found;
    imported_sels_num - the number of selections found in the import file.

    4. More betting codes for markets and corresponding prefixes:

    football22_ - DRAW NO BET
    football23_ - First Goal Odds
    football24_ - Odd or Even
    football25_ - Double Chance

    See updated manual's chapters "Triggered Betting - Reference - Variables - General" and "Triggered Betting - Reference - Variables - Selection Variables - Variables referring to imported selections".

    5. Logging in without browser. It is now possible to choose the way you log in to MarketFeeder Pro. Those with disfunctional Internet Explorer will be glad to hear the news that they can switch to the "built-in form" tab to log in like they used to in the previous version.

    However this mode does not support any additional log-in parameters, tokens or whatever BetFair may ask of you apart from your username and password.

    6. Trigger variables are now recognized in trigger conditions containing "is in list", "is not in list", "is in file" and "is not in file".

    7. You can check the current month in the Global Current Time condition. Example:

    Global Current Time is between Mar and Aug.


    BUGFIX

    1. In some AUS and RSA horse races silk colours would be inverted, i.e. blue would be displayed as red and vice versa.

    2. The conditions for the market's number of matched / unmatched bets in Market Locator were being checked incorrectly.

    The new version is now officially released.
  • #2 by alfaman on 19 Jun 2015
  • Hi,  thanks for all the improvements

    In the next issue, it would really help me if you could consider adding an option, in the Settings, Monitoring tab, whereby if you auto load markets you can "Clear my market list" first, like in the Market locator.

    Otherwise when you go away and leave it auto loading each day your market list just continues to grow, and grow with past days.

    Thanks

  • #3 by Oxa (WellDoneSoft) on 19 Jun 2015
  • alfaman, I've added that to the wish list.
  • #4 by cybernet69 on 19 Jun 2015
  • Any news on when/if the tennis API score update will be introduced ?
  • #5 by tupp on 21 Jun 2015
  • Hi,  thanks for all the improvements

    In the next issue, it would really help me if you could consider adding an option, in the Settings, Monitoring tab, whereby if you auto load markets you can "Clear my market list" first, like in the Market locator.

    Otherwise when you go away and leave it auto loading each day your market list just continues to grow, and grow with past days.

    Thanks



    looking forward to it!
  • #6 by pcal72 on 22 Jun 2015
  • Hi Oxa

    Congrats for that new update and improvments on it.

    I m a litle confused about point 6 can you clarify that a litle?

    All my tests on this new version seems ok, great work Welldone team!

    pcal72
  • #7 by Oxa (WellDoneSoft) on 23 Jun 2015
  • Any news on when/if the tennis API score update will be introduced ?

    That's scheduled for the next major update.

    I m a litle confused about point 6 can you clarify that a litle?

    Sure pcal72.

    Before this update you could not add a condition like this:

    Selection's Index is in list runner_number-2, runner_number-3, runner_number-4

    The runner_number variable would not be parsed in that list. Nor any other variables / trigger expressions. Now it is possible to include trigger variables in such expression where "is in list", "is not in list", "is in file", "is not in file" participate as condition operators.

  • #8 by pcal72 on 23 Jun 2015
  • Hi Oxa


    ohhhhh SUPER!  8)

    thanks
    pcal72
  • #9 by mips on 29 Jun 2015
  • Hi Oxa,
    Any possibility that new variable "Minutes(or seconds) since score change" for football can be added in next software update?
    Regards.
  • #10 by Oxa (WellDoneSoft) on 30 Jun 2015
  • mips, I've added this to our wish list.
  • #11 by mips on 30 Jun 2015
  • Nice to hear that, thank you.
  • #12 by betfair winner on 01 Jul 2015
  • Hi Oxa
    The upgrade sounds awesome thanks BUT i upgraded last night and found that the program was hanging for several minutes between refreshes and the old one was much faster.
    Plenty of triggers slow down my processor in the old version, but it did not hang.

     i have switched back this morning to the older version and everything is running smoothly again.......Weird !!!
  • #13 by Oxa (WellDoneSoft) on 01 Jul 2015
  • BF Winner, could be a coincidence or could be something in your triggers. If you send me your trigger file on support, I could take a look.
  • #14 by armarni on 01 Jul 2015
  • Hi Oxa

    many thanks for including the month in the current time variable, I can now automate which triggers run during the summer and which are better in the winter.

    Much appreciated.
  • #15 by Oxa (WellDoneSoft) on 01 Jul 2015
  • armarni, you are welcome.

    Apologies for getting ahead of myself, the correct spelling of that condition would be:

    Global Current Time is between Mar and Aug.

    Months should be addressed by their 3-letter code (the manual has this notation explained).
Pages:
Actions