Version 6.2 - Match Score

Dear all!

What do you think of version 6.2?

http://www.marketfeederpro.com/blog/mfpro-version-6-2/

The main feature there is the ability to get the score for some matches and use it in triggers. We're working on a trigger example to make it more obvious.

Discussion is welcome, as well as problem reports (although make sure you've read the new relevant help file chapters before you post).

Come on, people, I need your feedback! Any will do, even if its "I can't see any scores at all and my MF Pro is actually not refreshing markets".

I need to understand whether the latest update is stable and makes sense in order to start working on the next update.
Thanks!

I installed 6.2 last night but found my usual trigger was not firing correctly.

In the variable logs theres a strange square at the end of each final value or it's a [], doesn't show when I paste it here.

There is a condition that it only fires if the value I have in my spreadsheet is equal or greater than back_price1. but it was firing and the lay bet was going to back_price2, then the cancel trigger immediately cancels it. So it was in a constant loop. I've gone back to v6.1 for now. Do you need me to explain this in more detail?

Apart from that, I look forward the using the match scores in the future

Oxa,

It looks good to me although I've not had a chance to work with the scores "in anger".

The "delete events when settled" is very useful and it worked for me yesterday.  Now we can leave it running day after day auto loading markets in test mode, leaving them to be settled without building up a few hundred finished events in My Markets.

I am looking forward to trying to apply the score in tennis markets but I could not find one to test it on last night.  The snooker score did not show up though - not that this effects me.

Personally I did not have Maddox's problems but I have not looked at the variables log, just the triggers.

Alfaman

In the variable logs theres a strange square at the end of each final value or it's a [], doesn't show when I paste it here.

Can you email your trigger file to the support please, so that they could take a look and help you/fix the bug?

I'll email it soon but just looked at the log file running now and the square is still there but its running fine. I'll reinstall the new version again aswell.

Ah ha!  I've noticed that a trigger I have run for the last 94 days did not fire yesterday or today.  Once I put down to fluke - twice means that something in it is not liking 6.2.

I'll check the log files.

Alfaman

Ah ha ah ha !

the ofending line is in the "price" window or the amount but this has not changed since the trigger for 6.1 which worked:

Log file says:

Error in the trigger expression of price or amount: MINV(r_ticks(lay_price,2),15), default_laya+0.01

Is MINV not acceptable any more ?

Fixed it by changing "r_ticks(back_price, 0)" to just "back_price"
Silly of me using that line I know but it returns 0 in the new version and the current back price in v6.1

So Alfaman it may be the r_ticks thats the problem.

Maddox, thanks, No - I tried this to be sure:

"Error in the trigger expression of price or amount: MINV(10,20)"

Perhaps it is any formula in the Price window.

I've gone back to 6.1 and told the support line.

Alfaman, Maddox, OK, I got it.
Am going to look into it urgently and make a patch.

Look, I know I've said this before, but I find the service standards of WellDone, and Oxa in particular, as simply brilliant.

I can't think of anyone I have dealt with in the last 5 years or so who seems to enjoy fixing client problems as much as Oxa. Once the facts are known, the problem is fixed!

So top marks to "The Ox" for service standards, and to the WellDone team for producing such a quality product.

Its great having the correct score, and now I would like to use this in the Next Goal market. Would it be possible to add this market to the auto-load list ?

Thanks.

Bob, to say that I'm pleased is saying nothing at all! You are very kind.

Thank you all for being tolerant to occasional problems with the software.

I've just made a new update to version 6.2. Hopefully it has rectified the reported issues.

----------------------------------------------
SMF, as I said in one of other topics, I think it's time to start working on a comprehensive market search that would make it possible to add any type of market (including "Next Goal") based on predefined criteria. So that's going to be one of our next objectives.

Bob,

I agree, I am chuffed to have some of my suggestions built into the software, I would not expect any other software developer to be so responsive, there was nothing critical about my comments I was merely trying to identify why our triggers had stopped working following an update.

I think we must have identified a bug which is surely a good thing to have done so quickly after a release.  I have gone back to 6.1 simply because I don't want to rewrite all my trigggers around a problem that will no doubt, as you point out,  be quickly fixed.

Alfaman