For example if I play 2k hands with a player.
After that, I somehow decide to purge my database in HM2.
I am guessing the HUD stats I collected are all gone now?
If that´s the case, how do I save infinite amounts of hands? Like do I need to do something so that I can track a player over a longer period?
Please someone help me with this.
For example on Party I can save the data for a certain amount of time (f.ex. 100 days) . HM2 will import the data. The HUD will show the data.
But what is after let´s say 200 days. Is the data from the first 100 days just gone and will not be included in the HUD data?
I am so confused.
March 26, 2019 | 10:42 p.m.
and yet there is no option in HM2 to make the HUD only visible when you hover over it like in PT4?
Are you kidding me?! Why the fuck did they not fix this. You can barely see your table with a HM2 Hud. Wtf is going on with their shit?
March 26, 2019 | 7:35 p.m.
if we exclude utg/mp limper
March 26, 2019 | 6:50 p.m.
following one up:
this should add up to 100% right?
March 26, 2019 | 6:43 p.m.
I see. So the difference is in the limping. Thank you
March 26, 2019 | 6:29 p.m.
is there a difference between these two stats:
SB Fold vs Resteal and SB Fold to 3B OOP
March 26, 2019 | 5:30 p.m.
trying to design a preflop hud and was always generally wondering if it makes a difference if I use the 3B/vs3B stats or the Steal stats
March 26, 2019 | 4:17 p.m.
The upper one is Snowie´s opening range UTG. The one on the bottom is Snowie´s defense range vs a MP 3B (either calling or 4b).
Snowie defends around 27,31% of its range against a pot sized raise. This means MP could 3B any two cards to profit.
Can somebody explain why that is? I thought Snowie is close to GTO preflop?
I tried to come up with some explanations myself, but couldn´t really come to a conclusion with which I could say: "that must be it".
March 26, 2019 | 2:52 p.m.
Really like this answer from belrio.
Totally agree that with what he said. They will have a wide range on the turn and probably will play a "bet the good stuff" or polarized strategy on the turn.
So if they check you can apply very agressive strategies (that´s what solvers are doing) as they probably at best have bluff catchers.
If you let solvers do their thing they just go overbet overbet on turn river if he never checks his nutted hands.
Sure you can´t do this everytime since villain´s gonna notice but you can apply the basic principle of playing agressivly with the hands you choose to do so.
So yeah, in reality it makes your life easier since you don´t have to defend so much. Also they probably sometimes check the flop and if you can figure out what they check there you can take advantage of that too.
Most of the time people check second pair/ third pair typish hands.
March 24, 2019 | 5:03 a.m.
Really in trouble coming up with an answer.
I won´t justify the number but I don´t know how to come up with an answer right now.
I guess everything in the area of the loss trough a pure strategy is totally fine and significantly more probably not.
March 24, 2019 | 2:58 a.m.
AQo no matter the combo is a pure call in the simualation I did.
BTN: Dark meaning 50% freq.
BB: Dark meaning 10% freq.
Ranges might not be what is used but probably will do the job for what we are trying to figure out.
99, 88 100% call seems weird but villain was very nitty with his 3b freqs anyway. It´s a mistake I did when creating the sim but it shouldn´t matter too much I guess.
Given the action on the flop and the 6c as a specific turn club and BB following up with a small bet (I used 33%), the BTN´s optimal strategy looks like this:
As we can see AQ gets called 100%.
The EV difference between raising and calling is not negligible:
I nodelocked BTN strategy a bit on the turn: Raising his strong Q on the turn:
I haven´t looked deeper into how the BB can exactly play vs this but what I spotted is that BB betting freq. on river goes up on the river if you just call turn (thinner value bets and more bluffs).
What´s the most interesting one is that BB now starts to 3b you a ton once you raise:
Left is optimal // right is nodelocked
Hm it´s tough to see details:
Optimal 7.51%r // 43%c // 49.5%f
Nodelocked: 29.0%r // 19.0%c // 51.9%f