Bet river after missed cbet turn and 2 others custom stats

[NastyRabbit]

Hi, i wonder if there's a way to make this custom stat : How often villain bet the river when he did cbet the flop and both players checked the turn.

If possible i'd also like to filter the two custom stats i attached only for 3bet pot.

Ty

[kraada]

That is definitely possible. See this guide for the basics on custom statistics creation and this guide for a deeper walkthrough. The latter was written for PT3 but the techniques all apply to PT4, the interface is just slightly different.

To add that a situation only occurred in a pot that is exactly 3bet add this into the column definition: char_length(cash_hand_summary.str_aggressors_p) = 3

[Waterd103]

Would this colum be valid for that stat?

sum(if[tourney_hand_player_statistics.flg_r_bet AND tourney_hand_player_statistics.flg_f_cbet_opp AND tourney_hand_player_statistics.flg_f_bet AND tourney_hand_player_statistics.flg_t_cbet_opp AND lookup_actions_t.action='X', 1, 0])

[kraada]

That should work.

[NastyRabbit]

Hi, first thx for the 3b pot filter.

I made a column pretty close to Waterd103's one but without all the flop conditions. I thought cbet opportunity on the turn involve that aplyer did a cbet on the flop ?

sum( if[ cash_hand_player_statistics.flg_t_cbet_opp AND lookup_actions_t.action='X' AND cash_hand_player_statistics.flg_r_bet, 1 , 0 ] )

[kraada]

Yes, flop action is implied - that should work.

[dave2085]

i tried to build this stat aswell, i am an absolut newbie in this.
here is the stat, can someone check if the logic is correct?
this is my first postflop stat i build.

i used the expression of NastyRabbit. Then i took the same expression for checking the river... it seems it works, but i am completely not sure.

if its correct we can upload it in the warehouse

[Flag_Hippo]

That's good although a couple of points to be aware of:

1. For the opportunities column you can use cash_hand_player_statistics.flg_r_open_opp instead of adding together the times the player bets and checks so your stat expression can just be (a / b) * 100 instead of (a / (a + b)) * 100.

2. You use 'cbehind' in your column name which implies that you might want this specifically for the preflop aggressor being in position postflop? Your stat as it stands now will be counting all instances whether the PFR is IP or OOP so if you want this for IP or OOP you can specify that in the HUD Profile Editor or the stat itself.