I wasn't aware but this is actually a known issue when applying a site filter to NoteTracker note definitions. If you would like to be automatically notified if this is resolved in a future update you can open a Support Ticket quoting reference #5899.

thanks a lot! Now I have 2 more stats that I want to see in that way but they are like x/x, I tried to replace those values in that expression for example format('{1}/{2}', format_number(x,0,false,false), format_number(x,0,false,false)) But it didn't worked, how can I do it? You need to replace 'x'...

I don't know what would be causing that. Please export your HUD Profile and attach that to a Support Ticket where we can follow up with you.

AND tourney_hand_player_statistics.flg_p_3bet Anything using tourney_hand_player_statistics is specific to the player you are writing the statistic for and this says the player 3bet themselves which isn't what you want. Since you've also specified the SB is 2betting using the aggressors string you ...

To achieve that duplicate the VPIP statistic, change the 'Format Type' in the copy to 'Expression' and enter this:

Code: Select all

format('{1}/{2}', format_number(cnt_vpip,0,false,false), format_number(cnt_hands - cnt_walks,0,false,false))

You can filter for specific sites or NOT via 'Game Details -> Sites'.

Qwaserd wrote:H'mm is this because of BB going all-in some of the time and that means that the SB just has no opportunity to raise in those cases

That is correct.

Are you using any HUD filters at all via 'HUD -> Edit HUD Options' that can filter your HUD stats based on player count, stack size and/or date?

Guide: HUD Options & Profiles (Filters)

You can do that with built-in filters: (Position of Active Player Position of Selected Exactly 8) AND (Position of First Raiser Position of Selected Exactly 0) AND (Called Steal) AND ((First Flop Action Check) AND (Second Flop Action Call)) AND (First Turn Action Check) AND (NOT (Second Turn Action ...

That is a known issue with some GGPoker hands. If you would like to be automatically notified when that has been resolved then please open a Support Ticket quoting reference #5726.