Building exploitative ranges vs. LLSNL/micros pop
Posted by 240SS
Posted by 240SS posted in Low Stakes
Building exploitative ranges vs. LLSNL/micros pop
THIS MIGHT BE A HUGE RAMBLE IDK...
Most of you guys build/construct "balanced/unexploitable" ranges using pio, snowie, or w/e softwares on a daily basis (which i don't have). If any of you guys w/these softwares could pull up a exploitative range or something for me as an example that would be helpful so i could see how i should play my range in a certain spot vs. an exploitable villain.
###
-Conversely how would you try to construct an exploitative range vs. a villain who isn't playing "optimal"?
-Also how would you build these exploitative ranges vs a villain who is capable of adjusting or employing some sort of counter strat? ...there are some spots where i'm vs. a villain who is starting to play back @ me and i can't figure out how i should construct my range w/o losing too much EV.
-Do you just click a few buttons in the program and say: This is how villain is deviating from a "optimal strat"... and it spits out the exploitative range for you?
^^^Basically my question(s).
###
I get that...
-Basically @ the limits i'm playing @... i'm just looking to play a maximally exploitative style/strat as much as possible (which is obvious) based on my reads/population tendencies.
-Such as we aren't worried about having enough bluffs or value here when betting "most of the time" etc... just trying to maximize our EV in a certain spot with our specific hand vs. villain's range and make as few mistakes as possible while not letting villain's gain a EV in a lot of spots.
Ex:
Assume 100BB effective HU vs. LLSNL/Micros pop (full-ring)
UTGvs.Bu
Flop = QdTd6s
Ex II:
Assume 100BB effective MW (3-4 other villains) vs. LLSNL/Micros pop (full-ring)... a lot of pots go MW live so how should our ranges postflop change accordingly?
UTGvs.MPvs.Bu
Flop = QdTd6s
Loading 12 Comments...
Be the first to add a comment
You must upgrade your account to leave a comment.
This thread has been locked. No further comments can be added.