Plans for version 7.0

I hope it will have a function to prevent multiple bets -if I anly want one bet at a time!

/Mattias

"Log information about triggers" - why is this such a killer?

I had always stupidly assumed that this function was best turned on for diagnostic purposes, and then turned off for optimal performance.  However, this is not the case.

If trigger logging is NOT ticked, then with as few as 10 triggers, MFP will rapidly grind to a halt.

Take a 3 mile horse race lasting about 6 minutes, with 12 triggers active (a typical arrangement for me). With trigger logging turned OFF, the CPU usage begins to steadily climb from a start of say 10%.  By about 1-2 miles into the race the CPU usage has got to say 80% and is slowing down.  Very often before the end of the race CPU has maxed out and MFP has all but stopped.

This problem is simply solved by ensuring trigger logging is turned ON.

In the new version I suggest that either the option to turn off trigger logging is removed, or better still, when it is turned off performance is improved rather than  MFP coming to a standstill.

Please send your triggers to our support. It's possible a dead loop is in your triggers. Thank you.

space bar to add market

when adding markets manually you have to click on each individual one.

After expanding the market tree (today's horse racing) .. when you click on the first market it gets added and also becomes highlighted ... pressing up down arrows enables you to move withing that expanded selection ... when you find the next market you want to add you have to go to the mouse and click .. when as simple space bar press would be faster.

adding to the above .. a right click add all would be nice also.

Right click on a market tree, then get a drop down option to add all and adds all the markets below that tree.

right click on English soccer .. add all english soccer
right click on Eng Soc --> Npower Leage one and adds all league one markets or
right click on eng soc --> Np L1 --> Fixtures 28 March adds all Npower league one 28 March Markets.

This will be very useful, in other markets too .. for example tomorrow if I want to bet only on Wolverhampton markets I have to add them one by one .. win and place!! With the above I can just go Horse Racing --> GB then right click add all on Wolverhampton

hi
in the new update could you have it so that we can monitor different markets set to different times.
ie- we set greyhound markets to monitor 3 mins before the start
horse markets set to 20 mins before the off
and so on
this would lower the amount of calls to the api, when using horse and greyhounds etc at the same time.

thank you

mcbee

Oxa, any news on developments?

Oxa

Yep, it would be good to have an update on V&.

I suspect it might be too late, but a piece of functionality which would be absolutely brilliant (and perhaps not that difficult to do), would be to provide the capability for triggers to address the best 6 prices on the Back and Lay sides, i.e. back_price4, back_price5, back_price6, and similarly on the Lay side.  Similarly for back_amount4, 5 & 6, etc.

This wouldn't necessarily have to be graphically displayed, but it would allow for far more sophisticated WOM type calculations.

Any chance?

How about  this, at the same time,   placing some triggers / blocks in real mode and others in demo mode  and keeping separate records.

This would be great because we would not have to stop our real betting while testing new systems and  Betfair would receive their commission.

The list of features for the new version looks excellent - I would use all of them. I would just like to add the following points.

1) As a user who has only just started converting from MF Pro 5 to MF Pro 6 (mainly due to the huge increase in CPU resource requirements when using MF Pro 6), please can you make sure you make sure that the performance of the new version at least matches that of MF Pro 6

2) The problem of multiple bets (as stated by an earlier poster) could be solved if MFPro itself remembered whether there were any bets on the selection, and this could be used as a condition for making another bet. This would instantly solve this problem, admittedly for a small increase in memory footprint

Is there any update on when v7 will be available ?

I was hoping that it would be available with the football season starting. As the markets my bot works on are not available for automatic loading, I would like to know if I can wait for v7 or investigate some time in setting up some auto load workaround.

Thanks ! 

I wounder why not implemnet more markets to automatic load in this version (6) (insted features that do not give you higer turn around are implemnetd all the time).
If the software can add markets today, then expanding to more markets would be easy - suppose mfp-programmer are only interested in horse-race!

I agree Mat, it seems all focus is on horses.

To be selfish, just an option to autoload all of todays available soccer markets would be fine, I can delete the ones I'm not interested in via a trigger, as I'm only doing 1.5 and 6.5 markets.
Do need the "eventName" which the betfair api gives to be available in mfpro though, to distinguish league matches from friendlies etc, but this should be a minimal coding effort.

Currently doing this manually, but its a pain for the weekends with about 250 markets to choose from on a friday evening

Ideally would need some jittered start of scanning the markets or have mfpro first do a cycle through the triggers when starting to monitor the markets before sending requests to betfair so non relevant markets can be deleted (or perhaps this is already done ? ).

The same for tennis, though this is a bit less effort because tennis is there as an option in the add/delete specific markets, so that's just one click in the morning, and then I have a trigger deleting all those junk markets. Also only few tennis markets start at the same time.

The above is in my humble opinion minimal effort compared to the plans presented for v7 as the whole infrastructure is already there but would make us football botters very very happy.

Thanks for listening (I hope  )

Doesn't seem like the developers are listening here...

Yes, they are.
To be honest we decided to add no more features and finish everything we already started. It has taken ages! We have to release something :|