New User-defined variable

[thunder]

Hello

I work all-in variables, is this working code, i meen this : raises = 1 or calls >= 1

// if someone raises or call early position, we go all-in
 when User_HandGroup_FullRing_Cat_1 and raises = 1 or calls >= 1 and firstRaiserposition >= 7 and not (User_SBlind or User_BBlind)RaiseMax Force

[Egor]

you must bracket 'or' conditions

when User_HandGroup_FullRing_Cat_1 and (raises = 1 or calls >= 1) and firstRaiserposition >= 7 and not (User_SBlind or User_BBlind)RaiseMax Force

[thunder]

Ok, thanks Egor

[thunder]

you must bracket 'or' conditions

when User_HandGroup_FullRing_Cat_1 and (raises = 1 or calls >= 1) and firstRaiserposition >= 7 and not (User_SBlind or User_BBlind)RaiseMax Force

Can you say how i can add smallblind raisers too? is this right metod?
-> and (firstRaiserposition >= 7 or firstRaiserposition = SBlind) and not (User_SBlind or User_BBlind) RaiseMax Force
[/quote]

[sngbot]

The small blind is position 1 so:-

when User_HandGroup_FullRing_Cat_1  and ( raises = 1  or calls >= 1 )  and ( FirstRaiserPosition >= 7  or FirstRaiserPosition = 1 )  and not ( User_SBlind  or User_BBlind )  RaiseMax Force

You're aware this will only work first orbit...?

[thunder]

is this okay, if my positions are this or need i change something?

When User_BLA_None and StilltoAct = 9   User_EP1
When User_BLA_None and StilltoAct = 8   User_EP2
When User_BLA_None and StilltoAct = 7   User_EP3
When User_BLA_None and StilltoAct = 6    User_MP1
When User_BLA_None and StilltoAct = 5    User_MP2
When User_BLA_None and StilltoAct = 4   User_MP3
When User_BLA_None and StilltoAct = 3    User_Cutoff
When User_BLA_None and StilltoAct = 2    User_Button
When User_BLA_None and in SmallBlind    User_SBlind <-- meen this
When User_BLA_None and in BigBlind    User_BBlind

need i change like this: When User_BLA_None and in StilltoAct = 1  User_SBlind

[sngbot]

No, you don't need to change that. "In SmallBlind" works fine on its own as it is. Mixing it with "StillToAct" is a recipe for a headache.

[Egor]

I see a lot of new coders needlessly over-complicating things. In my opinion user-defined variables should be used sparingly. We have enough regular variables to almost do the job for just about any situation. The user-defined variables are for freezing a situation on the current betting round that you want to easily refer to later, which will be difficult to define later with the regular variables.

Now, I can understand that defining your original table position seems like a desirable thing to a lot of people and that is fine. But personally I cannot see it being useful beyond just knowing that you were originally in early, middle, or late position.

I guess what I am trying to warn against is making a needlessly long detailed complicated profile. We have seen those before, they have come and gone, and usually they don't do well. More detail does not = better player. The best profiles are made by good poker players who use what they need and ignore the rest.

[milliondollar]

if i define one in the flop code - will it be ignored for prefolp action ? Which is exactly what i want to achieve..

?

[sngbot]

Technically speaking, it won't be "ignored" because the bot will simply never read flop code for preflop play. But you're correct in thinking that it won't be acted upon.

[milliondollar]

yea thats what i thought - hoped .. thanks ""

[webber04]

i also use them to add info to the log file that i can easily look at later to make adjustments

[Egor]

if i define one in the flop code - will it be ignored for prefolp action ? Which is exactly what i want to achieve..

this is a moot point since flop codelines cannot be executed on any other betting round

once a user-variable is set as true, it is true for the remainder of the hand

[tr34187]

how about this when i am stealing from the button and get 3bet by the BigBlind. want to call the 3bet 80% of the time and 4bet 20% of the time.

when (StillToAct = 2 and position = last) and (Raises = 0 and Calls = 0) and (userbun2 or usergap1 or userlate1 or usersuited1 or userbtnjunk or userdraw) userstealbtn

  when (StillToAct = 2 and position = last) and (Raises = 0 and Calls = 0) and (userbun2 or usergap1 or userlate1 or usersuited1 or userbtnjunk or userdraw) RaisePot Force

  when (userstealbtn) and (raises = 1) and (firstraiserposition = 0) and random >= 80 call force
  when (userstealbtn) and (raises = 1) and (firstraiserposition = 0) and random >= 100 raise 40% force

[Egor]

looks good 

you have come a long way baby 

FYI you don't need the random >= 100 part

[tr34187]

your a good  teacher egor 

[SethUnter]

random < 80 raise as the first line of two seems more obvious than >= 80 call, but maybe it's a language thing

[tr34187]

when (userstealbtn) and (raises = 1) and (firstraiserposition = 0) and random < 80 call force
  when (userstealbtn) and (raises = 1) and (firstraiserposition = 0) raise 40% force

will this call 80% of the time and raise 20% seth?

[fleurie]

Yes!

One more point - you're original post says "you are 3bet by the big blind" but your code will also match to when you are 3bet by the small blind and the big blind folds.

[postenjak]

I am not really sure about this, but if its multiple action needed from the bot on the same street and UDV is first True, but later False, the UDV will remain as True, because it will not get resetted to False.

Here is an example,

Lets say I want to have UDV BetSizeLessThan5, I set it as "When BetSize < 5 UserBetSizeLessThan5"
An hand comes down, I am in MP and there is one raise to 3x in front of us, which means BetSizeLessThan5 is True.
bot calls and another player behind us re-raises to 15x which means BetSizeLessThan5 is False.
But because UDVs dont get resetted in the same round if there is multiple action, the value of BetSizeLessThan5 remains True because of our first action.

Do we need to keep an eye for such cases and adjust our code to avoid them or is Shanky bot capable of re-evaluating UDVs that are True in previous action, but should be False on later ?