• #1 by Oxa (WellDoneSoft) on 24 Feb 2017

  • In today’s update:

    1. We introduced a new setting for trading-out operations (green up and distribute loss). The setting (“Against last matched bet”) allows you to offset each new green-up or loss distribution against the last bet you placed on the selection, in comparison to the previous state of things, when the program always considered all of the bets you placed on that selection.
    This allows you to continuously open and close your positions disregarding the past profits or losses you had previously accumulated on that selection. If this setting is OFF, the program will green up (or distribute loss) based on the average weighted price of your existing bets. If this setting is ON, the program will green up (or distribute loss) based on the price of the last matched bet you made. See the examples in the screenshot against_last_matched_bet.png attached. The new settings has been added to triggers and Auto-Greenup.

    2. The interface of the Ladder is slightly different now. We have replaced the “Green Up” and “Distribute Loss” buttons with just one trade-out button that shows the “what if P/L” you will get if you trade that selection out immediately. The “Attempt to green up” button has been renamed to “Green up to zero loss” to indicate that the bet it will place intends to cut your loss on this selection to zero by placing a bet that will close your position with a zero profit/loss.

    3. New trigger action “write to file”. You can now write directly to a text file using triggers. There is a number of options available for this action, including the capability to clear its contents). Read the updated manual for more details.

    4. There is an option for a recurring import of selections for auto-trading from a file. So now you can periodically update the selections you want to bet on through changing the contents of the imported text file. (See recurring_import.jpg).

    5. We have added the option to “Hide real bets” in Test Mode, which seems to be essential for many MF Pro users. Check the new option in the “Test Mode” tab.

    6. We are now taking your discount rate into account when calculating P/L net of commission and settling test bets. You can see your discount rate by checking the new discount_rate variable.

    7. There are new trigger variables (ending with _backmtime and _laymtime) for the time at which a particular bet was matched (see the updated help file for notation). This means you can now check how much time has passed since your latest bet was matched, not placed.

    8. The option “Clear My Markets” is now a part of the search template that can be loaded using the “Scheduled Market Search.” In practice, this means that you can now set the program to clear your previous markets before searching for new ones. Beware though that this will also clear any test bets you had in those markets.

    9. The balance figure is back to the main menu.

     Bugs Fixed:

    - Function r_ticks has been adjusted for Asian Handicap markets, as in those markets the tick is always equal to 0.01.

    - The ladder was not being refreshed at an adequate rate when “Retrieve all price offers” was turned on in the Settings.

    - After a certain time since the start of your OS Market Locator would throw an error messages or stop loading sports.
  • #2 by LarpHager on 25 Feb 2017
  • Excellent Oxana. 

  • #3 by MarkV on 25 Feb 2017
  • Hi Oxa

    running nice and smooth, and the new green up options are very useful.

    much obliged   
  • #4 by Oxa (WellDoneSoft) on 26 Feb 2017
  • Thank you for your feedback!
  • #5 by Oxa (WellDoneSoft) on 27 Feb 2017
  • A user reported a glitch with the "attempt to green-up" trigger action: when you chose "Based on profit%", it would green up to a zero P/L.

    We have now fixed this glitch and updated the program on the server. Please re-download and reinstall.
  • #6 by Tim (WellDoneSoft) on 28 Feb 2017
  • Does anybody, especially Norton Antivirus users, faces a (false of course) virus alarm for the latest version?
  • #7 by londolozi on 05 Mar 2017
  • Yes, Trend Micro warns of this virus