|
Let's break down OP...
when peopple have an AK they generally raise
It's a premium hand, we should raise our best hands and there aren't many better than this. AA KK obviously, QQ is probably better than AKo and the equal of AKs, JJ is on a par with AKo but I'd rather have AKs. Everything else is worse.
So if we're facing limps, or opening, then it's a clear raise, always. If we're facing a raise, it's usually a 3bet but occasionaly we should call. And if we're facing a 3bet, it's either a call or a 4bet depending on the villain. Very rarely we can fold it facing a 3bet, but only against someone we know is only 3betting AKs KK+, the ultimate nit. Facing a 4bet, it's very much villain dependent and can be a fold, call or 5bet.
This would depend on stack size and pot size, or perhaps there's a donkey who is calling shoves light. Going all in pre flop with AK is not often going to be -ev.
but i think that tournament survival should be more important than hoping your AK is going to make the best hand?
There is a critical flaw in your thinking here. You are more concerned about survival than building a stack. This mentality will result in you playing too cautiously, and you will rarely go deep in tournaments. You might make the cash with a higher frequency, but your overall winrate is almost certainly going to be lower.
When we play a tournament, our goal should be to make the final table, not to simply make the cash.
i normally limp with it and if i feel its strongest ill go all in on the turn or the rive depending on the board
Never limp AK, not unless you know the bb is an idiot who will go all in when people try to limp his blind.
Generally, don't limp anything. Either raise, fold, or call a raise. But don't limp.
And don't "feel" if your hand is good. Put your opponents on a range, consider board texture and how your hand holds up against villain's range. AK is great on K22 in a 3bet pot, but it's not so good on KJT in a 4bet pot.
You have much to learn.
Go here... https://www.flopturnriver.com/pokerf...st-198113.html
|