Home
(0 votes) 
February 18, 2013
Offline
My 2x PF raise was an oversight here – I hadn't noticed UTG limp in as there was no SB, I would normally raise to 3x here with 1 limper. After the SB shove I don't really want to shove iso here as I feel I'm losing value – I end up 3x the shove and flat from the BB. Would be interested to know if you guys would have played up to this point any differently but my big question is how you play the flop. From watching TPE vids I think the preferred option is to shove the flop as it's so wet and hope the BB didn't hit a set – I'm guessing my flop bet was too small but as played could you ever find a fold in this spot? Thanks. Al.
Full Tilt – 200/400 NL – Holdem – 8 players
Hand converted by PokerTracker 3
CO: 13,579.00
BTN: 10,330.00
BB: 1,365.00
UTG: 17,313.00
UTG+1: 12,361.00
Hero (MP): 22,260.00
MP+1: 8,010.00
LP: 18,954.00
CO posts ante 50.00, BTN posts ante 50.00, BB posts ante 50.00, UTG posts ante 50.00, UTG+1 posts ante 50.00, Hero posts ante 50.00, MP+1 posts ante 50.00, LP posts ante 50.00, BB posts BB 400.00
Pre Flop: (800.00) Hero has K
K
UTG calls 400.00, fold, [color=red]Hero raises to 800.00[/color], fold, fold, fold, fold, [color=red]BB raises to 1,315.00 and is all-in[/color], UTG calls 915.00, [color=red]Hero raises to 4,000.00[/color], UTG calls 2,685.00
Flop: (9715.00, 3 players) 6 5
8
UTG checks, [color=red]Hero bets 3,750.00[/color], [color=red]UTG raises to 13,263.00 and is all-in[/color]
November 18, 2014
Offline
Except for the initial 3x instead of 2x I would have played it exactly the same way, and in the flop I'm calling his shove. I feel his range is pretty much A8, maybe even 8x if he's really fishy and 55+ but if he has aces or has flopped a set then so be it, I'm not folding in that spot no matter what.
February 18, 2013
Offline
Thanks for the reply chaos – I think I often delay fist pumping & snap calling in these situations as I'm not reshoving in villains spot here without a set or slowplayed AA as in that position I don't think the board is wet enough to give credit for much else, but then I forget at times of tilt I would spew here and there are plenty of villains who will spew with 77, 99+.
I honestly don't see very many A8s, 89s getting to the flop here but again I may be giving too much credit to some villains.
I think because in this situation I may be convinced to bet/fold the flop I should just shove as it takes any indecision when re-raised out of my hands, or hopefully in the future convince myself to bet with the intention to call a reshove.
TPE Pro
August 25, 2012
Offline
I think you played it fine, with the exception of the misclick obviously. On the flop you can't ever, ever, ever fold. You're getting around 3 to 1, and UTG has a ton of weirdly played 99-QQ, 77, A8, 98s and probably some other stuff too. Players who are limp/call/calling in UTG's spot here are usually bad enough to have unpredictably wide ranges here.
February 18, 2013
Offline
Never say never Matt – ashamedly I did fold in this spot, I made the mistake of weighting him towards a set instead of focusing on his range, and I guess panic folded as the clock counted down – turns out he had 77 and rivered his straight so it was a bad, but lucky fold in this case =0(
October 21, 2013
Offline
Al29 said:
Never say never Matt – ashamedly I did fold in this spot, I made the mistake of weighting him towards a set instead of focusing on his range, and I guess panic folded as the clock counted down – turns out he had 77 and rivered his straight so it was a bad, but lucky fold in this case =0(
TPE Pro
August 25, 2012
Offline
Riar said:
Al29 said:
Never say never Matt – ashamedly I did fold in this spot, I made the mistake of weighting him towards a set instead of focusing on his range, and I guess panic folded as the clock counted down – turns out he had 77 and rivered his straight so it was a bad, but lucky fold in this case =0(
Given the randomness of the software system they use, if you had called in this spot (as you should have =D) the cards on the turn and river would be different than the cards that actually came in this case…so you cant say it was a lucky fold, because nobody knows what would have came on turn and river 😉
As far as I know, this is actually not true. I used to think it was too, but apparently this hasn't been the case for a long time. The RNG they use now is actually truly random, so it's entirely possible that he could have called and seen the exact same runout. Although I'm not sure why I'm pointing this out, because thinking about what cards actually came out is irrelevant anyway. 🙂
October 21, 2013
Offline
Did i say it was categorically impossible that the same runout could have come ? Nope.
It certainly CAN happen, even tough given the randomness of the distribution it’s highly unlikely. (A PS manager explained it to me that way, i also think they posted a video somewhere explaining how their site shuffles the cards) .
Anyway I simply pointed it out because OP said that in the end “it was a lucky fold”, but focusing on the cards that came afterwards in order to biasing/justify yourself is something that you shouldnt be doing. (like saying/thinking oh i should have folded 92 pf cause the flop came 222)
(now that i think of it if you know epiphany77, since you are both brits, ask him about the randomness thing…he ll confirm you what i wrote)
Anyways i certainly dont wanna start a useless conversation about such a topic, so if my post wasnt welcome you can simply erase it, no big deal 😉
Most Users Ever Online: 2780
Currently Online:
19 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
bennymacca: 2616
Foucault: 2067
folding_aces_pre_yo: 1133
praetor: 1033
theginger45: 924
P-aire 146: 832
Turbulence: 768
The Riceman: 731
duggs: 591
florianm1: 588
Newest Members:
Tillery999
sdmathis89
ne0x00
adrianvaida2525
Anteeater
Laggro
Forum Stats:
Groups: 4
Forums: 24
Topics: 12705
Posts: 75003
Member Stats:
Guest Posters: 1063
Members: 12008
Moderators: 2
Admins: 5
Administrators: RonFezBuddy, Killingbird, Tournament Poker Edge Staff, ttwist, Carlos
Moderators: sitelock, sitelock_1
