• #1 by acollin on 28 May 2020
  • Hi all,

    Hopefully this isn't a daft question. 

    Let's say I place a £100 bet outside of the current available prices so it is initially unmatched.

    Then on a refresh of my program, £20 of the initial £100 bet gets matched.

    Do variables such as bm_backa and bm_laya report the £20 at that  point? Or not because it's a partial match of the initial amount?

  • #2 by Oxa (WellDoneSoft) on 29 May 2020
  • Hi!

    We welcome all kinds of questions here, and yours is most certainly not daft.

    The variable bm_backa will return 20, and bu_backa will return 80.

    Hope this helps!
  • #3 by acollin on 29 May 2020
  • Hi Oxa,

    Many thanks for the reply.

    So just to confirm, let's say we start with the same £100 unmatched bet...

    The next refresh £20 gets matched, next refresh an additional £30 and another refresh another £40, so £90 of the £100 had now being matched.

    Would the variable bm_backa for each of these refreshes report £20, £30 and £40? So in other words it is reporting the difference in the matched amount between these refreshes?

    Or would it report £20, £50 and £90 for these refreshes?

    Hopefully I'm making sense.

    Many thanks.
  • #4 by Oxa (WellDoneSoft) on 01 Jun 2020
  • Quote
    Or would it report £20, £50 and £90 for these refreshes?

    This one, as the bet will have the same transaction ID for all the matched chunks.
  • #5 by acollin on 01 Jun 2020
  • Perfect, thank you very much.
  • #6 by acollin on 07 Jun 2020
  • Hi Oxa,

    Sorry for bringing this one back up again.

    Can you please explain what happens with the variables like bm_backa and bm_backp when a recent bet is matched before an earlier placed bet, and then the earlier placed bet is matched after?

    For example in my logs I noticed a back bet at 3.85 was placed first and remained unmatched. Later a back bet at 3.80 was placed and then matched. Later again the earlier bet at 3.85 was then matched but the variable bm_backp was still reporting 3.80 when I was expecting it to be now 3.85.

    I'm sure this is expected behaviour with 3.80 being the last placed bet, but I was looking for a variable to report the last matched bet price?

    Many thanks again.
  • #7 by Oxa (WellDoneSoft) on 08 Jun 2020
  • Quote
    I'm sure this is expected behaviour with 3.80 being the last placed bet, but I was looking for a variable to report the last matched bet price?

    Bets are sorted by their placed date.
    Unfortunately, there is no way to look specifically for the last matched bet. You will have to find another workaround for your strategy. Perhaps I could suggest one if you briefly describe it.
  • #8 by acollin on 08 Jun 2020
  • Hi Oxa,

    Many thanks again for your help.

    I am 'simply' wanting to produce a list of matched bets and prices specifically including the matched time.

    You can sort of get this from the betfair website under betting profit and loss, but if you've placed a lot of bets in the market it involves clicking on each bet and then the next page shows the matched time of each partial amount from that specific bet.

    I can't see a way to export all this data from betfair so I can order by matched time.

    So for example:

    13:05 - £10 back bet matched @ 3.6
    13:10 - £10 lay bet matched @ 3.5
    13:15 - £6 back bet matched @ 3.7
    13:16 - £4 back bet matched @ 3.7
    13:20 - £10 lay bet matched @ 3.7

    Many thanks. 
  • #9 by Oxa (WellDoneSoft) on 08 Jun 2020
  • That's tough, I can't think of any ways to do this in MF Pro, I'm sorry!
  • #10 by acollin on 08 Jun 2020
  • Hi Oxa,

    That's a shame but not to worry.

    I can get the amount easy enough by monitoring the back_matched / lay_matched amount every refresh and then fire a trigger when the value changes recording the difference.

    I'm just thinking out loud here but maybe I can do the same thing with the average price variables, record it every refresh then when it changes use the difference to work out the latest matched bet price.

    Not sure if that's possible, but I'll have a look.

    Thanks again.