MarketFeeder Pro Changelog

What's new in MarketFeeder Pro 8.1.0.1

• New BetFair API (JSON):
• MarketFeeder Pro 8 communicates with the BetFair server through the new API, coded in lightweight JSON. The new API makes it possible for MarketFeeder Pro to improve the speed and efficiency of your trading, read more about it below.
• Markets can be settled as soon as they are finished:
• It has become possible to know the outcome of an event right after its finish. So the winners of most BetFair markets can be determined once the market is finished. This is a major improvement in terms of testing staking plans, since the profit/loss of the previous market will be available much earlier than it used to be before. Besides, the winners are now determined for all types of markets unlike before when this feature depended on the availability of those markets in the rss.betfair.com service.
• Data request limits are lifted:
• Well, at least for now. We can forget about the 20 requests per second – for that reason we have abolished the Connection Monitor. There is a different kind of limitation in the new API, but you need not worry about it, since a) it does not entail any charges and b) the program will take care of it for you.
• Please bear in mind that the maximum refresh rate for each market is 0.2 sec, and that there is still a limit of 1000 betting transactions per hour.
• Bets can be refreshed together with market data:
• Market prices and bets placed in that market can now be refreshed in sync, in one request to BetFair. Apart from saving traffic, it also allows you to refresh them as frequently as once per 0.2 sec. It used to be impossible for more than 5 markets at a time, because of the request limit, so the default option was to update all existing bets every 3 sec. This could be an impediment to scalping and other strategies requiring fast reaction.
• Account statements for main and AUS wallets are now combined:
• We heard the voices of so many customers asking us to make it possible track the profit/loss from both wallets simultaneously, without the need to switch between them in the settings. In the new version the bets from both main and Australian wallets are combined in one statement, so that you can carry on with your staking plans without thinking which wallet a market belongs to.
• Easy addressing of football and tennis markets in triggers:
• In the new API there is a new market property called betting code. It reflects the type of selections and betting logic common for all events of a particular kind of sports. For example, I’m talking about Match Odds in Football and Tennis or Under/Over markets in Football. One used to take great pains to identify such markets before, because the only way of doing it was through looking for certain patterns in the market’s name. This of course was hardly reliable considering the multi-lingual interface and the fact that several markets could share this pattern between them.
• Now that market codes can be retrieved, we have introduced a new set of prefixes, akin to winplace_, that will refer to particular types of football and tennis markets within the same match.
• More decoration to the Events Tree and My Markets:
• In the new version all kinds of market statuses (i.e. Idle, Suspended, In-Play, Finished) have their specific colour, to make them stand out from each other.
• The new API requirements and architecture is incompatible with some of the features MF Pro had before. We had to remove them from the program, and it is currently unknown whether we will ever be able to bring them back.
• Here is the list of things that have been removed from MarketFeeder Pro 8:
• Launch from Command Line:
• Since the logging in to BetFair takes place directly on their web site, the software does not have access to your credentials. So it is no longer possible to pass them to BetFair without your actual presence. We regret this very much and acknowledge the importance of this feature.
• Request password when restoring from tray:
• Again, since the software can’t know your password, this type of security precaution is not feasible. We’re open to suggestions as to what can be asked of instead.
• In the application title show Username:
• You already know that we have no idea of your username, right? So we’ve replaced this with showing the name of the currently open trigger file.
• Display prices exactly as they are on the BetFair website:
• Since this option has been added, we’ve never heard of anyone wishing to display prices differently from the website. Because the virtual or cross-matching prices are now available in the API, we decided to make this option permanently ON.