Feature Request #1: HUD Stats 'Att to Steal','Fold to Steal'

[TrustySam]

Preface

Hi, so I downloaded the PT4 Beta a couple of days after it went public, and I'm enjoying it immensely! A lot of wonderful new additions such as the interactive graph, and the ability to revise tournament results by right-clicking that have really helped save me a lot of time, and made checking my performance a lot easier, so thanks so much for the great product!

So I am greatly enjoying PT4. However there were a couple of items that got tweaked from PT3 - I can see benefits to the changes, but perhaps there's also some drawbacks?

I think all of the things I'm going to be bringing up are tools/stats that are still present in PT4, but that now require us all to take additional steps to use. Like they're things that before might have just taken us one click of the bottom, whereas know it requires is to think more like programmers so that we can customize the software to get the same functionality?

I went and scrolled through this PT4 Subsection and noticed that there were others who wanted to know about these same features I'm about to mention, so perhaps there's a lot of people who might be feeling the same way?

So with that being said, here's the first feature that's changed from PT3 to PT4:

Feature Request #1: HUD Stats 'Fold BB to steal', 'Attempt to Steal from C/O'

I guess the decision was made to streamline these stats, with there being the option for individuals to further customize it. Except that there's like 200 stats that are very detailed - of all the stats to choose to streamline, could we possibly have these more common ones put back (attempt to steal from c/o, attempt to steal from d, attempt to steal from sb, fold bb to steal, fold sb to steal)? I think it would save PT support a lot of time too!

And here's some of the threads I saw where people were asking about these stats (for reference):

https://www.pokertracker.com/forums/vie ... 59&t=38390
https://www.pokertracker.com/forums/vie ... 59&t=38459
https://www.pokertracker.com/forums/vie ... 59&t=38579
https://www.pokertracker.com/forums/vie ... 59&t=39274

[kraada]

Each additional stat that we add puts further strain on every user's system. Each stat we add is cached, meaning we calculate the stat at import time for all players and store that value as a running total for everyone.

In PT3 we did not have a CO specific position area - now in PT4 you can set a stat to be for just the CO in the HUD (similarly, BB and SB are also now split).

If you want to see one of these stats in the HUD all you need to do is change the value of one drop down box. After adding the stat, click on it and change the Position value Item Properties area to whatever position you want to see.

If you want to see these stats broken down by position all you need to do is go to either the Overview or Summary report and look at stats By Position. You can add more stats much more easily in PT4 - right click and Configure Report to add more stats.

We understand this is a change, but we think that it is actually a step forward, and slowing down everyone's system for data that is now redundant does not seem to be the best next step.

[TrustySam]

Each additional stat that we add puts further strain on every user's system. Each stat we add is cached, meaning we calculate the stat at import time for all players and store that value as a running total for everyone.

In PT3 we did not have a CO specific position area - now in PT4 you can set a stat to be for just the CO in the HUD (similarly, BB and SB are also now split).

If you want to see one of these stats in the HUD all you need to do is change the value of one drop down box. After adding the stat, click on it and change the Position value Item Properties area to whatever position you want to see.

If you want to see these stats broken down by position all you need to do is go to either the Overview or Summary report and look at stats By Position. You can add more stats much more easily in PT4 - right click and Configure Report to add more stats.

We understand this is a change, but we think that it is actually a step forward, and slowing down everyone's system for data that is now redundant does not seem to be the best next step.

Hi -

First off, thank you very much to the PT team for making the HUD stat lock feature optional - the reason I was so insistent on wanting to ensure that my position was heard was because I did feel like it was representative of a majority of people, and that the solution I offered would best serve the most number of people, and I didn't feel like the majority view was being heard. Clearly at the time you all disagreed, but I do believe that we all shared the goal of wanting PT to be the best in can be for the most number of people, so hopefully we can put any past unpleasantries behind us and move forward.

So to follow through with this second request I made at the time which was of lesser priority. I did in fact go on to customize my stats as per these instructions. However, I'm not sure the stats are actually tabulating correctly with the generalized 'steal%' stat when it's customized by position. Because here is what the program outputs for this opponent for example (this example is no different from most others):

HUD view (2nd line are the steal% stats customized by position - co,d,sb):
[ img ]

Pop-up view:
[ img ]


It doesn't really matter to me if you keep the steal% stats general and want us to customize them by position, or whether they come customized, but something appears to be off with the accuracy there ... can somebody look into this? Thx.

[WhiteRider]

Can you explain what problem you're seeing with the steal by position stats?
Your second screenshot shows VPIP rather than steals, so I'm not sure what problem you're showing us?

[TrustySam]

Can you explain what problem you're seeing with the steal by position stats?
Your second screenshot shows VPIP rather than steals, so I'm not sure what problem you're showing us?

:) You mean to say that the steal% is calculated differently from VPIP for position - ie the steal% is the vpip for that position for only the times when it's been folded to the person. Hence the different results? :)

Ok thx - I forgot about that ... problem solved :)

[WhiteRider]

VPIP is entirely different from Att to Steal. You can VPIP from the cutoff, button or small blind in any hand, whether you have chance to open or not. Even if you have chance to open you could limp (call) which wouldn't count as a steal but is VPIP.

[TrustySam]

VPIP is entirely different from Att to Steal. You can VPIP from the cutoff, button or small blind in any hand, whether you have chance to open or not. Even if you have chance to open you could limp (call) which wouldn't count as a steal but is VPIP.

Sigh ................ so what you mean to say is that yes, the att. to steal stat is in fact different from VPIP by position, not only because it's limited to situations where everybody has folded to the player in position to steal, but also because it needs for a person to have entered the pot with a raise, not just a call for it to count towards the att. to steal %.

Okay, interesting to note the differences. Cool!

[WhiteRider]

Exactly - a steal is specifically a raise from the cutoff, button or small blind when everyone else has folded to that point.

[TrustySam]

Okay, cool! That helps a lot - tyty!!! :) :) :)