Non Squeeze 3bets vs specific position

[martinstiago]

Hello,

Having assumed that the '3bet' stat counts every situation a player 3bet regardless of how many players vpip'ed before his action, I have been looking for a way to discount those 3bet's that were squeezes. I haven't found this anywhere and have tried to customize it on pokertracker but I'm having a bit of trouble because my goal is to have the more specific '3bet vs position' stat on my HUD (exempted of squeezed situations). In order to get to that I'd need to discount the squeezed situations vs that specific position which as an expression doesn't exist on PT (only the global cnt_p_squeeze). Any idea of any workaround to get to the "pure" '3bet' stat that I'm idealizing?

Thanks in advance

[Flag_Hippo]

cnt_p_squeeze is a column and there are expressions for squeezing. In your custom columns you can use:

Player did not squeeze preflop

Code: Select all

NOT cash_hand_player_statistics.flg_p_squeeze

Player did not have the opportunity to squeeze preflop

Code: Select all

NOT cash_hand_player_statistics.flg_p_squeeze_opp

See this guide for the basics on custom statistics creation and this guide for a deeper walkthrough. While the latter was written for PokerTracker 3 and the user interface is different the techniques still apply to PokerTracker 4.

[martinstiago]

After spending a good deal of time trying to get it right I decided it was not worth it because the difference in the end is not a major one (even though squeezing ranges do differ from 'direct 3bet' ones in PLO). I just couldn't find an easy way of isolating the hands where there was a 3bet from specific to specific position (let's say BB vs UTG) that was not a squeeze.

I did manage to do it for the BB vs BTN scenario where I established in the column section a cnt_p_notsqueezeBB as if[ position_type = 9 AND NOT cash_hand_player_statistics.flg_p_squeeze , 1 , 0 ] as a workaround. I would now have to create a column for every single position (if my thought process is even right).

Anyway just wanted make the suggestion for future iterations of the software to include this statistic and thank you once again for the attention.