ANY DOUBTS RE CUSTOMER SERVICE READ THIS!

[londolozi]

Perhaps some investigating.
Try a set user variable Value = back_matched
Affected by Trigger  xxxxxxx

Sounds like it will show zero. If it does you have you evidence.

[mcbee]

hi
if the bets are showing on the screen, then there is another checking condition.
trigger expression  bm_1_backa+bm_2_backa+bm_3_backa+bm_4_backa+bm_5_backa    is equal or less than 3
this checks each back amount upto 5 bets, if you need more then just add the extra backa's
it might work better than the back_matched because it is checking any back bets placed on the selection

mcbee

[SMF]

Hi SMF,

You would need a user variable for EVERY selection in the race that has a matched bet (that might myseriously disappear later).

Can that be done?  I have tried this before but whilst you can tick the box to say set individually for each race, I have never managed to set a variable for each selection.

For example you could create variable eg 'my_bet_matched' and set it to 1 if there is ever a bet matched on Selection A.   This could be used to prevent futher bets on that selection. 

But could you also use that same variable to detect a bet on Selection B as well - I think not but I am not sure ?

Perhaps it can be done with a remember trigger but I have never had much success getting these to do what I want either.  Also if the platform closes at any time would it remember the user variable was set to 1 on restarting ?

Alfaman

I had to think this over a bit.

Perhaps create a trigger per selection where you set a user variable to the selection name once the conditions have been reached, and check on this in your back trigger.

A lot of additional triggers, one per possible selection, but could be worth to try.

Created an example, don't know if it works though. 

Find attached

[alfaman]

Thanks SMF,

I'll have a look.

Cheers

Alfaman

[betfair winner]

Hi Mcbee, Alfaman, SMF, and Rubold.
Can I thank you all so much for the help and support in trying to solve this issue. 

I have now adopted a user variable that has highlighted that (as many of you suggested) the bets are simply disappearing and no longer visible to the triggers, hence the meltdown. I traced this to and IP conflict and reconfigured my router which seemed to be the source of the problem.

I am keeping my fingers crossed that today we have normal trigger service resumed!
But once again I cannot thank you all enough for your advice and suggestions to get me on the right track.

It is sad fact that even now I have had no input regarding this from Support despite numerous request and ticket numbers, so everyone will make their own minds up regarding this aspect.

[apples999]

ok

so after all the to-ing and fro-ing...
you had some problem that was fixed!
     

Where do I download the latest version of MFPro?

Or was the problem just bullshit?

(Some minor bug another customer could have handled as easily as WelldoneSoft
 and didn't require a software rewrite.)


WelldoneSoft are busy
The have much do and so little time to do it in.

so if your problem doesn't involve a  software rewrite
Ask another customer.
 Firstly it develops a community spirit.
Secondly you might make a friend and develop better trigggers.
Thirdly And most importantly it free's up WelldoneSoft for the important stuff.

   for instance
      which is the most import?

  A. An inplay trigger which calculates the length of time to the end of a race!
  B. The bugs in Test Mode fixed
        MAXV(last_traded,back_price)>=bu_backp = bet matched @ bu_backp
 C. Rev 7.


So there's heaps for WelldoneSoft to do.


So like I said.
 If your problem doesn't involve a software rewrite.
 Ask another customer.




Happy Punting
Apples999

[betfair winner]

Hi Apples

No not a minor bug but a problem that has continued for several months which had also affected you.

Support have already fixed two bugs which i highlighted, so this is another.
The multiple bet problems where existing bets are not seen by the triggers; as you have already made it clear, is a bug in the software. Having used the triggers for 2 years now in a variety of formats the same old chestnuts continue.

However this problem was exasperated by a wireless router configuration issue. Your fix suggestion using the remember trigger is the answer I am sure. But happily the problem for now (although still existing) is under control.

I actually started this thread to applaud and commend the work of support, however as time has gone on this appears to be no longer the case.

My complaint regarding Support is that despite my unparalleled levels of patience, I was ignored. Surely it makes good business sense to communicate. Even a negative comment is preferable than to willfully ignore peoples emails.

A simple response saying "we have looked into the problem and am unable to duplicate the issue so we suggest this is a configuration issue" would suffice. Failing that a response "we are too busy to answer" would also be acceptable.
Nothing annoys people more (apart from losing a lot of money) than to be IGNORED!

[JS]

Hi,

Could somebody from support please reply to ticket AQW-846035?

Thanks.

[WellDoneSoft]

Peter,

Please let me know when possible.

We'll let you know when it be ready. Thank you for your offer.

[JS]

Hi,

Could somebody from support please reply to the latest question on ticket AQW-846035?

Thanks.

[JS]

Thanks Tim, could you please also answer the second part of my question (same ticket)?

[drphil]

E-mailed a problem to support yesterday and it was sorted by Tim in 7 minutes!!!!!

As I have always found, excellent customer service, guys, especially in view of all that's going on with v7

Phil