User-Defined Variables

WHEN FirstCallerPosition = 9 Set user_UTG_Was_Limping

• As you see, there’s the Set command and after it there is a user-defined variable instead of an action after a condition, but no keyword force.
• Whenever OpenPPL / OpenHoldem sees such a construct it evaluates the when-condition. If the condition is true, OpenHoldem sets the user-variable to true and continues with the evaluation, until it finds a true condition with an action.
• All user-defined variables start with false (0). Once you set them they become true (or 1, which is technically the same).
• User-defined variables keep their value for the current hand and can’t be reset back by the user. But when the hand is over they get reset automatically.
• Naming: every user-defined variable starts with the prefix “user”, followed by a sequence of characters [a-zA-Z], digits [0-9] and underscores [_].
• Querying the value of a variable is simple: you can use it just like any other symbol as part of an expression:

  ##f$preflop##
      WHEN Hand$AA RaiseMax FORCE 
      WHEN Hand$KK Set userDoesNotKnowWhatToDo 
      WHEN Hand$QQ Set userStartsToCry 
      WHEN userDoesNotKnowWhatToDo Call FORCE 
      WHEN userStartsToCry SitOut FORCE 
      WHEN Others Fold FORCE
  

Expert Tricks (Memory Symbols)

WHEN (...) Set me_st_MySecretVariable_3_141592653

WHEN (... me_re_MySecretVariable ...) ...

• OpenHoldem’s user-defined variables are case sensitive. me_st_x_1 is something different than me_st_X_1.
• No underscores allowed in the name of the variable. Underscores are used to separate name and value. (If you wonder, why underscores are allowed in simple user-variables: because the translator removes them).
• No automatic reset. If you need such a reset, you could do it e.g. before your first action preflop:

  ##f$preflop##
  WHEN (BotsActionsOnThisRound = 0)
      WHEN Others Set me_st_MySecretVariable_0
      ...
  

• Table occlusion reset the memory variables.