Pages:
Actions
  • #16 by mcbee on 18 Feb 2016
  • hi
    just confirming that the r_x_sel_name does not work and can cause mfp to crash.
    i have emailed support.

    mcbee
  • #17 by mips on 19 Feb 2016
  • Hello,
    still nothing regarding variable ''seconds since score change''? Is there any hope that something like that will be finally added? I wait over 1 year for this.
  • #18 by pcal72 on 19 Feb 2016
  • Hi mips

    It is so important to you?

    Why you do not create a variable that imediatly after a goal keep the now_time and then, later you use it to calculate your second after a goal??

    pcal72
  • #19 by mips on 20 Feb 2016
  • Hi pcal72,
    Yes this is very important for me. I tried your suggestion already in cooperation with one forum member, but that wasn't successful. I was promised that this will be added about a year ago, but still nothing. Meantime I lost over 1500 Eur without this variable, and that is quite significant amount for me.
  • #20 by mcbee on 20 Feb 2016
  • hi mips
    are you betting in one market or multiple, ie-match odds or over/under markets.
    and what do you want to do with the goal time.


    mcbee
  • #21 by mips on 20 Feb 2016
  • hi mcbee,
    I trade on large amount of markets, and mostly on correct score markets. Strategy depends on current score,and because score is wrong from time to time, I need to wait some time after goal is scored, to be sure that score is correct. We already tried to make some kind of counter(which reset after every goal) for this purpose, but it is quite complicated and didn't work as expected.
    We already have ''last suspend'' and ''last inplay'' variables but they are not good enough(some suspensions are not detected), so simple variable which count time since last score change would be far easiest and simplest solution for me. Also some other users could have benefit with this.
  • #22 by mcbee on 20 Feb 2016
  • hi
    as a quick work around.
    new trigger
    set to once every 1.00
    variable gt (or whatever name you want)
    value   now_time
    variable sc (or whatever name you want)
    value market_score1+market_score2
    conditions
    new block
    conditions
    OR selections trigger expression market_score1+market_score2 is greater than sc
    OR trigger (name of this trigger) number or runs is equal to 0
    new block
    and selections trigger expression market_score1+market_score2 is equal or greater than 0

    in your betting trigger add the condition
    and selections trigger expression now_time is equal or greater than gt+(mf_minute*1)  (set the 1 to however long you want to wait)

    so the new trigger will record the score and time, every time the score changes.
    the betting trigger will not fire until now_time is greater than the recorded time plus your waiting time.

    mcbee
  • #23 by Oxa (WellDoneSoft) on 24 Feb 2016
  • I am looking into the r_ prefix problem and will provide a solution ASAP...
  • #24 by mips on 24 Feb 2016
  • Quote from: mcbee on 20 Feb 2016, 14:45
    hi
    as a quick work around.
    new trigger
    set to once every 1.00
    variable gt (or whatever name you want)
    value   now_time
    variable sc (or whatever name you want)
    value market_score1+market_score2
    conditions
    new block
    conditions
    OR selections trigger expression market_score1+market_score2 is greater than sc
    OR trigger (name of this trigger) number or runs is equal to 0
    new block
    and selections trigger expression market_score1+market_score2 is equal or greater than 0

    in your betting trigger add the condition
    and selections trigger expression now_time is equal or greater than gt+(mf_minute*1)  (set the 1 to however long you want to wait)

    so the new trigger will record the score and time, every time the score changes.
    the betting trigger will not fire until now_time is greater than the recorded time plus your waiting time.

    mcbee
    hi mcbee,
    we already tried similar solution earlier, but trigger wasn't work properly. Are you sure this will work?
    My triggers are already pretty complicated, and this way just make things tougher.

    We already have variables ''last_suspend'',''last_inplay''. I am not familiar with programming, but  is it very complicated to be added something like ''last_scorechange''?
  • #25 by Oxa (WellDoneSoft) on 28 Feb 2016
  • I have fixed the r_x_sel_name problem now.
    Please re-download and update your MF Pro in order to notice the change.
  • #26 by MarkV on 29 Feb 2016
  • Quote from: Oxa (WellDoneSoft) on 28 Feb 2016, 17:16
    I have fixed the r_x_sel_name problem now.
    Please re-download and update your MF Pro in order to notice the change.
    Thank you Oxa.
  • #27 by mikejcshaw on 10 Mar 2016
  • Thanks Oxa. There also appears to be a small problem reporting race status. I am monitoring a win and a place market - the status is only reported on screen for the place market and the win market shows dormant. If I stop monitoring the place market the win market then correctly displays status. Thanks
  • #28 by sanyboy3400 on 23 Mar 2016
  • Hi
    a quick question regarding live trading in football matches. Some of the bookies offers complete live statistics, like Shot on target, cards, corners etc. Are you planning to implement those variabiles in MF in the future? This would be a really major thing.
    Thank you
  • #29 by tupp on 27 Mar 2016
  • ...selection's name is in file file dont work - takes name that's not in the file!!
  • #30 by tupp on 27 Mar 2016
  • Quote from: tupp on 27 Mar 2016, 13:38
    ...selection's name is in file file dont work - takes name that's not in the file!!

    This is in soccer, it always take selection 1+ one more if the "tipster" file say selection 2-3.
Pages:
Actions