Pages:
Actions
  • #1 by Alden on 02 Mar 2011
  • Hi.

    I have a trigger which has some user variables. Those variables saves the hand player name in every round using the internal variable h_1_sel_name.

    Example:

    hand_1_r_2_name saves the favourite hand name in round 2, for example Hand2.
    hand_1_r_3_name saves the favourite hand name in round 3, for example Hand3.

    After that I compare if the favourite hand in round 3 has changed with respect to round 2. If this is the case, I have to launch a back bet for the new favourite. The trigger expression used to make it is:

    One per game exactly in round 3 met the condition
    trigger expression hand_1_r_2_name is not equal to hand_1_r_3_name

    I have checked the variables using the Variables View window and I see how these get the correct value in every round.

    Furthermore, I created a new variable called "difference_value" which set value is hand_1_r_2_name = hand_1_r_3_name. Viewing it in the watch window I see that the value is "Hand3 = Hand2", so effectively the variables have different values.

    But the problem is the trigger is not detecting correctly the favourite hand name has changed between rounds using the variables.

    The log file of the trigger shows it:



    -------------------------------------
    02/03/2011 13:50:18:   Round 3. Channel POKER_TURBO refreshed. Game ID: 35313488
    -------------------------------------

    Checking:  Trigger Expression hand_1_r_2_name is not equal to hand_1_r_3_name
    Condition is false.  ( Selection 'Hand 3': Trigger Expression is Hand2.)



    As you see the condition is true, 'Hand3' is different of 'Hand2', but the trigger is returning false.

    Could anybody tell me what is happening and why the trigger is returning a false when itself confirm the value variables are different? I am not understanding anything well about how triggers work?

    Regards.
  • #2 by rubold on 02 Mar 2011
  • IS your strategy to place a back bet on the favourite in R3, if it was not the fav in R2?

    If so your method is too complicated.

    Back
    favourite
    exactly in R3

    Conditions:
    Selections Price in Round 2 is not the minimum overall
  • #3 by Alden on 02 Mar 2011
  • IS your strategy to place a back bet on the favourite in R3, if it was not the fav in R2?

    If so your method is too complicated.

    Back
    favourite
    exactly in R3

    Conditions:
    Selections Price in Round 2 is not the minimum overall

    No, what I try is bet in round 3 if the favourite has changed with respect to round 2. Imagine in round2 the favourite is Hand2, then I place a back bet. If in round 3 the favourite is not Hand2, I want to make a back bet again to the new favourite, but if the favourite continues being Hand2 I don't want to make a new bet.

    It means, I only want to make a bet if the favourite hand has changed from one round to other posterior.

    So I want to know in every round the relation between the hand name and the position (or prices).

    But as you see the trigger seems to be not working correctly.

    Regards.
  • #4 by Tim (WellDoneSoft) on 02 Mar 2011
  • Selection's Matched Back is equal to 0
    prevents you to place bet twice.
  • #5 by Alden on 02 Mar 2011
  • Anyway why the trigger I am using is returning that? Can I send you here an example of my trigger?
  • #6 by rubold on 02 Mar 2011
  • So you back the favourite in R2 ?
    If the same hand is still the favourite in R3, you do nothing.
    If the favourite in R3 is different, you back the new favourite.

    You are not interested in R4.

    Trigger attached
  • #7 by Alden on 03 Mar 2011
  • So you back the favourite in R2 ?
    If the same hand is still the favourite in R3, you do nothing.
    If the favourite in R3 is different, you back the new favourite.

    You are not interested in R4.

    Trigger attached

    Not exactly. Also I'm interested to bet in round 4 if the favourite is different with respect to round3 and round2. But not only with favourite, but even second favourite, etc. I want to try a lot of possibilities, so it's important I understand to use intermediate variables correctly.

    I send you here an example of my trigger. It's very simple, it sets a variable in round 2 called h_1_r_2_name with the favourite name and in round 3 set other variable called h_1_r_3_name with the favourite name in that round. After it, a trigger checks if h_1_r_3_name value is different of h_1_r_2_name value and then bet.

    To test this trigger you can use in the Time Machine the game with date 17/02/2011 in which the second game  of that day has a different favourite in round 3 with respect to round 2.

    If you open the View Variables window during that game, you can see how the variables take the correct values in round 2 and 3, but the trigger doesn't work. It's supposed the triggers are executed in order, so the assignation to h_1_r_3_name in round 3 is executed before the trigger that checks h_1_r_3_name is different of h_1_r_2_name.

    Maybe there are ways to make it easier, but in what I'm really interested to know is why this trigger doesn't work when it should be.

    Regards.
  • #8 by rubold on 03 Mar 2011
  • You are making it too complicated.
    It is easy to add R4 to the trigger I posted
    Just have: Selections Matched Back is equal to 0 in the conditions.

    Even simpler:
    Back favourite
    Once per round
    No sooner then R2

    Condition: Selections Matched Back is equal to 0

    This will back the fav from R2 to R4, but will only back each hand once.

    The second favourite can be backed with the same trigger, just substitute second favourite for favourite.

    I'm certain you won't need to employ user variables for what you want.
    Although they are very useful in the correct circumstances.

    I would suggest you send your trigger to [email protected] to find out why it doesn't work as expected.
Pages:
Actions