First of all, the profile is designed to be a general-purpose and adaptable profile that can handle different types of games and situations. It is not optimized for any specific game or format, but rather tries to balance between risk and reward, and exploit the weaknesses of the opponents. It uses a combination of factors, such as stack size, position, hand strength, pot odds, opponent tendencies, and game phase, to make the best decision possible.
The game phase code is based on the M-ratio, which is a measure of how many orbits you can survive with your current stack, assuming that you do not play any hands. The M-ratio is calculated by dividing your stack size by the sum of the blinds and antes. The profile uses the following ranges to determine the game phase:
• Early game: M > 300
• Middle game: 300 > M > 20
• Late game: 20 > M > 10
• Bubble game: 10 > M > 6
• Lame game: 6 > M > 1
• All-in game: M < 1
Dynamo - main thread
Re: Dynamo - main thread
The game phase code also uses a multiplier to adjust the M-ratio based on the number of players at the table. The multiplier is calculated by dividing the number of players by 10. For example, if there are 9 players at the table, the multiplier is 0.9. This means that the M-ratio is multiplied by 0.9 to determine the game phase. This is done to account for the fact that the blinds and antes increase faster when there are fewer players.
The game phase code is not game specific or dynamic based on starting chip amount, because the profile does not know the type or format of the game in advance. It only knows the current stack size, blind size, and number of players. Therefore, it uses the M-ratio and the multiplier as a universal and simple way to estimate the game phase.
The game phase code is not game specific or dynamic based on starting chip amount, because the profile does not know the type or format of the game in advance. It only knows the current stack size, blind size, and number of players. Therefore, it uses the M-ratio and the multiplier as a universal and simple way to estimate the game phase.
Re: Dynamo - main thread
However, you can modify the game phase code to suit your needs and preferences. You can change the ranges of the M-ratio, the multiplier, or both, to make the profile more or less aggressive in different game phases. You can also add more game phases, such as early middle game, late middle game, etc., to fine-tune the profile's behavior. You can also make the game phase code game specific or dynamic based on starting chip amount, by adding some conditions or variables to the code. For example, you can use the GameType variable to check the type of the game, such as STT, MTT, or cash, and use different ranges or multipliers for each game type. You can also use the StartingChips variable to check the starting chip amount, and use different ranges or multipliers based on that.
Re: Dynamo - main thread
Zadak, I actually have a little knowledge about this profile and profiles in general. Froggy and I bounced and shared a lot of idea's and code on the Private developers forum when we were both building our own profiles.
Re: Dynamo - main thread
Here is why I don't like General Purpose profiles.
Let's take a situation where calculated M-zone is red / orange border or Stack size ~ 6 times the Big-blind and 5 players at the table.
Cash, perhaps M-zone shouldn't be calculated, or the code used here, but it is. 5 player $.05 BB with roughly 45 BB's or $2.25 on a max $5.00 buy in table. Please correct the match if I'm wrong.
Single table sit-n-go with 5 left approaching the bubble, probably a very common position to be in.
MTT early game as table's are opening up starting with 1500 chips, but a big loss puts you around 250 not critical but not a good position.
MTT bubble with 11 or 10 players and nine make the final table. Bot can't tell this from above situation unless it uses Game phase based on Big Blind size and the specific game's avg total players and starting chips. Dynamo has some code to detect this, my code was even more specific but then that's "proprietary"
Final table with 5 left, final table should be recognized, and it may be in a "dllfunc" for "proprietary" theft avoidance, but I don't think so. I've been mapping the values for the dllfunc's, sorry Froggy, and think I have most of them understood.
So, in all those situations is playing the same hand range preflop, aggressiveness throughout the hand and post flop strategy really optimal or desirable?
Plus, the short stack code is kicking in, is that appropriate for any of these situations?
Your thought's please Zadac.
Let's take a situation where calculated M-zone is red / orange border or Stack size ~ 6 times the Big-blind and 5 players at the table.
Cash, perhaps M-zone shouldn't be calculated, or the code used here, but it is. 5 player $.05 BB with roughly 45 BB's or $2.25 on a max $5.00 buy in table. Please correct the match if I'm wrong.
Single table sit-n-go with 5 left approaching the bubble, probably a very common position to be in.
MTT early game as table's are opening up starting with 1500 chips, but a big loss puts you around 250 not critical but not a good position.
MTT bubble with 11 or 10 players and nine make the final table. Bot can't tell this from above situation unless it uses Game phase based on Big Blind size and the specific game's avg total players and starting chips. Dynamo has some code to detect this, my code was even more specific but then that's "proprietary"
Final table with 5 left, final table should be recognized, and it may be in a "dllfunc" for "proprietary" theft avoidance, but I don't think so. I've been mapping the values for the dllfunc's, sorry Froggy, and think I have most of them understood.
So, in all those situations is playing the same hand range preflop, aggressiveness throughout the hand and post flop strategy really optimal or desirable?
Plus, the short stack code is kicking in, is that appropriate for any of these situations?
Your thought's please Zadac.
Re: Dynamo - main thread
However, you can also modify the short stack code to suit your needs and preferences. You can change the table of hand ranges, or use a different source of hand ranges, such as [HoldemResources Calculator] or [ICMIZER], which are tools that can calculate the optimal hand ranges for short stack situations, based on various factors and settings. You can also disable the short stack code altogether, by setting the UseShortStackCode variable to false, and use the normal profile code instead.