[Requin]

Well this is awkward. I'm tempted to c/c once and then give up UI.

Edit: Well you're about a cointoss against a loosish PF range

Text results appended to pokerstove.txt

60,390 games 0.091 secs 663,626 games/sec

Board: Qh Tc 8c
Dead:

equity win tie pots won pots tied
Hand 0: 50.498% 49.67% 00.83% 29996 500.00 { JcJs }
Hand 1: 49.502% 48.67% 00.83% 29394 500.00 { QQ+, TT-66, AQs-AJs, KQs, JTs, T9s, AQo }


Alot worse off against a tight PF range

29,700 games 0.002 secs 14,850,000 games/sec

Board: Qh Tc 8c
Dead:

equity win tie pots won pots tied
Hand 0: 24.717% 24.40% 00.32% 7246 95.00 { JcJs }
Hand 1: 75.283% 74.96% 00.32% 22264 95.00 { QQ+, TT, AQs, AQo }


Against the tight range you do so badly I might just c/f

Against the loose one, you have a bunch of EQ against it. Can you bet call? Let's see a loose PF/loose shoving range (I didn't include KQs, maybe I should have):

Text results appended to pokerstove.txt

39,600 games 0.001 secs 39,600,000 games/sec

Board: Qh Tc 8c
Dead:

equity win tie pots won pots tied
Hand 0: 33.987% 32.88% 01.11% 13019 440.00 { JcJs }
Hand 1: 66.013% 64.90% 01.11% 25701 440.00 { QQ+, TT, 88, AQs-AJs, JTs, T9s, AQo }

Against this we can't call so I don't like bet/call, maybe bet/fold if we think he has the loose PF/loose shoving range but we had so much EQ against his loose PF (and I think he might stab a bunch of hands) so i you put him on loose PF and think he stabs with crappy hands like a small pp we can probably c/c profitably.

Against loose PF/tighter shoving range we oviously can't bet/call, so again c/c seems best if we think he stabs.


Cliff notes:
If you think he's loose in calling PF and will stab if you check a halfway decent % of the time with crap hands, then c/c is probably best. If he's loose PF but won't stab alot bet/fold has some merit I think, although I was too lazy to work out FE and such. If he's tight PF because of your nitty image just c/f. Never bet/call.

I did his quickly and don't really want to get into it that much, but please point out any glaring mistakes. There might be a bunch I don't usually spend the time I should working with Pstove