Pages:
Actions
  • #1 by londolozi on 05 May 2013
  • I have a trigger that bets in Aust NRL games. Yesterday it failed to fire a bet on a team that won at $7.00 Canberra Raiders

    Here is the trigger log.
    17:36:56 Condition is: FALSE.  
    17:36:56 Selection: Canberra Raiders, initial expr.: NRL 2013, intermediate: NRL2013, final: NRL2013.

    17:36:56 Checking condition  and Market's Name contains NRL 2013.

    17:36:56 Condition is: TRUE. valid for 1 selections: Canberra Raiders.

    17:36:56 Checking condition  and Market's Minutes Before the Off is less than 3.

    17:36:56 Condition is: TRUE. valid for 1 selections: Canberra Raiders.

    17:36:56 Checking condition  and Selection's Rank is equal to 2.

    17:36:56 Condition is: TRUE. valid for 2 selections: Melbourne Storm, Canberra Raiders.
    .......................
    17:36:39 Checking market "Rugby League / NRL 2013 / Round 8 - 04 May / Storm v Raiders / Match Odds".

    The final check is market's name contains NRL 2013
    As you can see 17:36:39 it does.
    But at 17:36:56 it returns FALSE

    Can anyone explain this expensive error?
    This trigger has been working all season and has about 2-3 bets a round.
  • #2 by londolozi on 05 May 2013
  • I have done additional testing today with these variations
    NRL2013
    "NRL2013"
    NRL 2013
    "NRL 2013"

    all return false???
    Checking market "Rugby League / NRL 2013 / Round 8 - 05 May / Knights v Sharks / Match Odds".

    When I stated this trigger has worked before it was without this market name check block of course. I need this trigger now as it covers multiple codes.
  • #3 by londolozi on 05 May 2013
  • Further testing shows if i use just one word NRL
    Condition returns True
    Then I ask name contains 2013
    Condition returns True

    Why should I need to separate NRL 2013 when you can see that exists in the Markets name?
    MFPro 7 strikes again?
  • #4 by mcbee on 05 May 2013
  • hi
    i have run tests on this and if you have "NRL 2013" or "nrl 2013" , the condition returns TRUE.


    mcbee
  • #5 by londolozi on 05 May 2013
  • Well that is confusing now McBee  ???


    Mine definitely returns FALSE with NRL 2013 but TRUE when I have two trigger conditions.
     Ver 7.0.0.46


     
  • #6 by mcbee on 05 May 2013
  • hi londolozi
    can you try the again .
    "NRL 2013"
    and let me know if you get a true or false this time.

    thank you

    mcbee
  • #7 by londolozi on 06 May 2013
  • Still returns FALSE Mcbee
  • #8 by mcbee on 06 May 2013
  • hi
    could you include the trigger that has this condition, you can remove any other conditions if you want, but it would be better to have all conditions in the trigger.
    then i can test the trigger and find out why it is returning false.


    thank you

    mcbee
  • #9 by londolozi on 07 May 2013
  • Solved
    I thought we did away with inverted commas in v7?

    NRL 2013 - fails
    NRL - succeeds
    NRL 2013 - fails
    2013 - succeeds
    "NRL 2013" - succeeds

    So is the rule, if using more than one word you must use inverted commas?
  • #10 by mcbee on 07 May 2013
  • hi
    the correct way is to use "" at all times , without these the bot is looking for full words without spaces.
    so if you typed             one for the road
    without the "" the bot looks for  onefortheroad   because it cannot see the space and will return false.
    but if you typed          "one for the road"
    the bot has to look for the exact wording with spaces.


    mcbee
Pages:
Actions