How villian views us popup

[nurssbetty]

Is there a HUD group popup available of the way villian views us? So the stats would be of ourselves, but only over the hands that villian has played with us.

[WhiteRider]

No – that kind of information is pretty complicated to extract from the database, and would add significant delays.
That kind of information could also be misleading, as you will not know what stats your opponent has on you (if any) or whether they are paying attention to them.

[nurssbetty]

I'm not sure if I was clear regarding the stats. I meant our stats in a popup of all hands the villian was dealt in with us, not necessarily played with us. Therefore, it should include all hands of us that the villian could see.

Too bad if it is too much trouble, because I know my stats can get very misleading on certain players. If I was aware of the "misleading" info on me that could exist from small sample re particular villian, from his perspective, it would provide a nice opportunity to exploit.

[kraada]

This is the sort of thing WhiteRider was responding to which cannot be done currently in the HUD.

But also one point to consider about misleading data - imagine you've played about 1,000 hands with an opponent. At the beginning, he had just started playing poker and knew relatively little. Somewhere in the middle, he purchased our software and began tracking data - there's no way for you to know if he started tracking at hand 400, hand 600, or if he even doesn't use the HUD at all, just uses our software for postgame analysis. As such, this data could be highly misleading.

[pasita]

FWIW, I don't like the "this data could be misleading" argument on this (frequently requested) feature. If we have 1000 hands on a villain, but 900 of those he was playing drunken in a FL .05/.10 table and now we're going NL1000 and he's sobered up, his stats can appear a bit misleading also. I'd leave that for the customer to judge (no harm pointing it out though).

[kraada]

I understand your point, but there is also a substantial technical hurdle to overcome - queries of this nature would be very complex, could not be cached with the manner the cache is built currently, and would thus take a very long time as the database grew large. This technical reason is (more than any philosophical reason) the biggest factor in the current lack of this functionality. What use would it be to have this feature if the only people who could use it effectively have databases of less than 10,000 hands and play only 1 or 2 tables?