kara260588
Legend
Bronze Level
It also seems to me that they show me nonsense.Never heard of it before.
It is a call, to raise half of your stack and then fold without seeing a flop is a mistake.
The real mistake in the hand is raising 2.5 BB. Should have either shove or folded. Fold mostly but will shove sometimes with correct table dynamics.
It also seems to me that they show me nonsense.
What do you mean?
fwiw, folding in this spot would be nonsense. (I think that's what they're getting at)
fwiw, 'fold pre'
that is, in this position with 34o you had to immediately push everything?
And will that be entirely reasonable?
Hey. Tell me, what mistake did I make in this hand? After that I immediately received aggression against me, fish, idiot.
https://www.youtube.com/watch?v=_H18R_KEeIM
maybe the translator shows me a little wrong. Did I understand correctly that I should have folded such a hand after I was raised? Calling would be fine if there were no raises before the game got to me. because even a call would have been wrong after those raises before . Or am I still wrong?First hand is what others have been saying, you shouldn't have raised to 2,5BB in the first place, and once you did that, you are already compromised and the correct play would be to call.
Second hand was not good enough to call the raise. Facing a raise like that, opponent range can have you beat easily in many cases, AT+, TT+, you are a underdog in most of these ranges, and thus it's a negative EV play. You got quite lucky with the flop, so that's probably why people were lashing out at you (which I do not agree, because you choose how you want to spend your chips), but in the long run, that kind of calls will lose you more money than they'll earn you, so you should avoid them.
here I did not understand anything at all. But I think there is again a problem in the translation made by Google translator.well reason is a sense of the human being that can be discerned by the right type of character
I just decided to post this photo. I rarely see this.View attachment 280495