PokerTracker

Hello I would like to create the following stats, if they don't already exist:

- 3Bet vs Steal

- Fold vs 4bet after 3Betting vs steal
- Call vs 4bet after 3Betting vs steal
- Raise vs 4bet after 3Betting vs steal

Can anyone help me ? thanks

Raise vs Steal Att is a default stat already available.

The others you would need to build.

For Fold vs 4bet after 3Bettings vs Steal:

cnt_p_3b_vs_steal_4bet_def_action_fold: sum(if[holdem_hand_player_statistics.flg_blind_def_opp AND holdem_hand_player_statistics.flg_p_3bet and holdem_hand_player_statistics.enum_p_4bet_action = 'F', 1, 0])

To make the call and raise ones change 4_bet_action to 'C' and 'R'.

For the opportunities column use:

cnt_p_3b_vs_steal_4bet_def: sum(if[holdem_hand_player_statistics.flg_blind_def_opp AND holdem_hand_player_statistics.flg_p_3bet and holdem_hand_player_statistics.flg_p_4bet_def_opp, 1, 0])

For more on creating custom statistics please see the Tutorial: Using Custom Statistics and Reports.

what would be the value expression for the actual statistic? I am entering in:

(cnt_p_3b_vs_steal_4bet_def_action_fold/ cnt_p_3b_vs_steal_4bet_def)*100

and it's telling me that the Value expression is NOT valid!


weird, seems like it's always the name of the top one divided by the name of the opportunity times 100. I already entered in both columns successfully.

That would be the value expression - make certain you have typed the column names exactly in the statistics section - it's easy to end up slightly off at which point it won't validate.

I figured it out... the reason the value expression wasn't working for me was because I didn't have a space before and after the "/" sign and didn't have spaces before and after the multiplication sign.

This third stat, raise 4-bet after 3-betting vs steal.... that is the same thing as 5-bet after 3-betting vs a steal. I remember reading somewhere that PT3 databases do not currently have the capacity to calculate pre-flop 5-bet statistics... what is the deal with this 5-bet type stat?

In this particular case since you're narrowing things down to just vs a steal I think we can manage it using the actions string - because we know we've 3-bet vs the steal and that was our first action, so if lookup_actions_p.action LIKE 'RR%' then we've made two raises - a 3-bet and a 5-bet. We can also know that if lookup_actions_p.action LIKE 'R_%' that we faced a 4-bet. However, if we're in the small blind, the big blind could be 4-betting cold here and you would get those situations counted in.