Jump to content

MDB+SAP Questions


Recommended Posts

  • Replies 74
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Post your MDB+SAP questions and comments on this thread.

For your convience:

[ATTACH]3245[/ATTACH]

Ellis, how are you thinking about using SAP as an indicator when to make, or not make, MDB bets? Looking at your short example, what would you say about this after the 20 plays? To me, SAP is not indicating to stay away for MDB, so I would continue to look for signals in this shoe. Why? Because each count is essentially equal to its mean after 20 plays, so at least at this point there does not appear to be much bias. My biggest concern is whether SAP will signal the decisions in time. SAP always looks brilliant in hindsight, but our previous attempts on using it an early warning/signal have been very disappointing. I'm anxious to to understand your new thinking on this.

Link to comment
Share on other sites

Ellis, how are you thinking about using SAP as an indicator when to make, or not make, MDB bets? Looking at your short example, what would you say about this after the 20 plays? To me, SAP is not indicating to stay away for MDB, so I would continue to look for signals in this shoe. Why? Because each count is essentially equal to its mean after 20 plays, so at least at this point there does not appear to be much bias. My biggest concern is whether SAP will signal the decisions in time. SAP always looks brilliant in hindsight, but our previous attempts on using it an early warning/signal have been very disappointing. I'm anxious to to understand your new thinking on this.

Ellis, anxiously awaiting your thoughts on this.

Link to comment
Share on other sites

Would like to ask when using SAP count as an indicator for MDB play, which way is more effective: to use the MC event or to use the LC event?

I was thinking to use MC event. For example:

1. if SAP count for 1s is highest, i will play 3zz goes to 4zz but not 3zz stays 3zz

2. if SAP count for 2s is highest, i will play 2s stays 2s and 3s stays 3s, but neither 2s goes to 3s nor 3s goes to 4s

3. if SAP count for 3s is highest, i play both 2s goes to 3s and 3s stays 3s, but neither 2s stays 2s nor 3s goes to 4s

Link to comment
Share on other sites

Still no updates on how SAP will aid in MDB play?

Sorry guys but I'm still not getting any post notifications so I only see your questions if I luck on to them.

OK, when we are playing MDB+ we are going by relatively recent information.

For instance, we get two 2s without a 3 between, we bet the next 2 goes to 3.

That's usually a pretty good bet especially when we get 3 chances to get it right.

But not if 3s are already high.

SAP may be saying that in spite of your two 2s, 3s are hi and 4+s are lo.

Therefore don't bet the next 2 goes to 3. Instead, bet the next 3 goes to 4.

Then, SAP itself doesn't distinguish between 4s and 4+s, but WE certainly can

because it is right there under our nose.

4s might already be high and it is 5+s that are lo. In which case we'd rather wait and bet the next 4 goes to 5.

See, MDB+ gives you probable information

But SAP gives you exact information.

In other words you don't want to make an MDB+ bet that SAP does't agree with.

I think this is even more true when you are playing for very high stakes.

You want to be winning at the first bet level - at worst - the 2nd bet level.

You don't want to get to the dreaded 3rd bet level.

And SAP can help with that. Not every bet mind you.

But every now and then SAP won't agree with your MDB+ bet.

SAP may be saying "Hold off, it's not time for that bet yet".

Now, let's take a wholly different situation - in fact two situations.

1.) Let's say you are betting $1000 units and those are the highest at the table.

and your last 2 shoes were +8,+8. YOU are now the casino's target.

2.) Everybody at the table is winning, regardless of the stakes they are playing.

In either case, you can expect a ringer shoe - a change up.

SAP is going to tell you that right away because of SAP Count high dispersion.

Maybe 1's and 4+s are too low, while 2s and 3s are too high.

That's going to get you in big trouble quickly with MDB+

But meanwhile SAP is telling you to drop MDB+ and play OTB4L

And if that situation changes, so will the SAP advice.

Look, I've been playing a long time and I therefore do not trust casinos - not at all.

Whether Bac or BJ.

When you are winning, especially if the whole table is winning with you, it is the Pit Boss's job to DO something.

THAT is what he gets paid for.

But, if you are expecting a change up, and you are prepared for it, you can often take advantage of it.

SAP defines the perfect MDB+ shoe. All your counts will be running close together and may even tie now and then.

That puts MDB+ in a perfect position no matter where you start your progs.

In fact in such a situation, the sooner you start your progs the better.

But now we are getting less than ideal MDB+ situations.

So fine, we react by delaying our progs - smart move.

Except, the more we delay our progs the fewer bets we get.

Every time you delay a prog you cut the bets in half on that bet trigger.

Sometimes that's good and sometimes it isn't.

It depends on the quality of the shoe from an MDB+ persective.

The closer the 4 counts the better the shoe is for MDB+.

We don't want to be delaying progressions in a close count shoe.

We may miss the only bet opportunities the shoe produces.

On the other hand, it behooves us to delay our progs in a far flung SAP count shoe.

In fact, we can say that the worse a shoe is for MDB+, the better it is for NOR.

I've seen Perfect NOR shoes in Vegas recently - even at touch tables - especially touch tables.

We don't want to be found playing MDB+ in a perfect NOR shoe.

Well, our SAP counts tell us the difference.

Granted, we don't get NOR shoes often in Vegas.

BUT when we do, SAP not only warns us -

It tells us the best NOR system to play AND the Mode to play it in.

IF we are listening.

AND the better MDB+ is doing in a touch game, the more likely you are to get a NOR shoe thrown at you.

Sure, we might be having a bad MDB+ day - shit happens!

It might be bad because the SAP counts are TOO close - leaving us with few or even no MDB+ bets.

In that case, we bet sooner - not later. We can bet the highest count goes down and the lowest count goes up.

And it might be bad because the SAP counts are too far flung and in that case right, we delay our progs.

But the worse a table is for MDB+, the better it is for NOR.

That's just simple Math.

THOSE are the ways I see SAP guiding us with MDB+.

When we have our head on straight.

Nothing fancy here, we are just using our head.

Edited by Ellis
Link to comment
Share on other sites

To play MDB+ at it's peak, you would need to play when the casino is at it's busiest with many tables working. Walking around the tables looking for opportunities. Using SAP would confine you to that table?

Sorry guys but I'm still not getting any post notifications so I only see your questions if I luck on to them.

OK, when we are playing MDB+ we are going by relatively recent information.

For instance, we get two 2s without a 3 between, we bet the next 2 goes to 3.

That's usually a pretty good bet especially when we get 3 chances to get it right.

But not if 3s are already high.

SAP may be saying that in spite of your two 2s, 3s are hi and 4+s are lo.

Therefore don't bet the next 2 goes to 3. Instead, bet the next 3 goes to 4.

Then, SAP itself doesn't distinguish between 4s and 4+s, but WE certainly can

because it is right there under our nose.

4s might already be high and it is 5+s that are lo. In which case we'd rather wait and bet the next 4 goes to 5.

See, MDB+ gives you probable information

But SAP gives you exact information.

In other words you don't want to make an MDB+ bet that SAP does't agree with.

I think this is even more true when you are playing for very high stakes.

You want to be winning at the first bet level - at worst - the 2nd bet level.

You don't want to get to the dreaded 3rd bet level.

And SAP can help with that. Not every bet mind you.

But every now and then SAP won't agree with your MDB+ bet.

SAP may be saying "Hold off, it's not time for that bet yet".

Now, let's take a wholly different situation - in fact two situations.

1.) Let's say you are betting $1000 units and those are the highest at the table.

and your last 2 shoes were +8,+8. YOU are now the casino's target.

2.) Everybody at the table is winning, regardless of the stakes they are playing.

In either case, you can expect a ringer shoe - a change up.

SAP is going to tell you that right away because of SAP Count high dispersion.

Maybe 1's and 4+s are too low, while 2s and 3s are too high.

That's going to get you in big trouble quickly with MDB+

But meanwhile SAP is telling you to drop MDB+ and play OTB4L

And if that situation changes, so will the SAP advice.

Look, I've been playing a long time and I therefore do not trust casinos - not at all.

Whether Bac or BJ.

When you are winning, especially if the whole table is winning with you, it is the Pit Boss's job to DO something.

THAT is what he gets paid for.

But, if you are expecting a change up, and you are prepared for it, you can often take advantage of it.

SAP defines the perfect MDB+ shoe. All your counts will be running close together and may even tie now and then.

That puts MDB+ in a perfect position no matter where you start your progs.

In fact in such a situation, the sooner you start your progs the better.

But now we are getting less than ideal MDB+ situations.

So fine, we react by delaying our progs - smart move.

Except, the more we delay our progs the fewer bets we get.

Every time you delay a prog you cut the bets in half on that bet trigger.

Sometimes that's good and sometimes it isn't.

It depends on the quality of the shoe from an MDB+ persective.

The closer the 4 counts the better the shoe is for MDB+.

We don't want to be delaying progressions in a close count shoe.

We may miss the only bet opportunities the shoe produces.

On the other hand, it behooves us to delay our progs in a far flung SAP count shoe.

In fact, we can say that the worse a shoe is for MDB+, the better it is for NOR.

I've seen Perfect NOR shoes in Vegas recently - even at touch tables - especially touch tables.

We don't want to be found playing MDB+ in a perfect NOR shoe.

Well, our SAP counts tell us the difference.

Granted, we don't get NOR shoes often in Vegas.

BUT when we do, SAP not only warns us -

It tells us the best NOR system to play AND the Mode to play it in.

IF we are listening.

AND the better MDB+ is doing in a touch game, the more likely you are to get a NOR shoe thrown at you.

Sure, we might be having a bad MDB+ day - shit happens!

It might be bad because the SAP counts are TOO close - leaving us with few or even no MDB+ bets.

In that case, we bet sooner - not later. We can bet the highest count goes down and the lowest count goes up.

And it might be bad because the SAP counts are too far flung and in that case right, we delay our progs.

But the worse a table is for MDB+, the better it is for NOR.

That's just simple Math.

THOSE are the ways I see SAP guiding us with MDB+.

When we have our head on straight.

Nothing fancy here, we are just using our head.

Link to comment
Share on other sites

To play MDB+ at it's peak, you would need to play when the casino is at it's busiest with many tables working. Walking around the tables looking for opportunities. Using SAP would confine you to that table?

I get your point but nothing is stopping you from looking around for MDB+ opportunities. The question is, are they, in fact, the best opportunities?

And there is nothing to stop you from doing a SAP count just using the tote boards.

All the 1's, 2s, 3s and 4+s are right there for anyone to count in just a few seconds.

Link to comment
Share on other sites

Hi Ellis-

I have a trip planned to Vegas in about two weeks and this is the first time I will be there since learning MDB+. I live in South Florida, my home casino uses regular cards and is dealing mostly NOR friendly shoes.

I plan on using my first day (or at least part of it) in Vegas to do a little recon. I would like to use the SAP count to determine if the casinos I plan to play at (and more specifically the tables) are MDB+ friendly. So for MDB+ I would like to see the SAP counts to be pretty much even with little disparity correct?

Your input and feedback will be greatly appreciated. I asked the question here rather than privately because I'm sure your answer will help others as well. Thanks...

Link to comment
Share on other sites

Hi Ellis-

I have a trip planned to Vegas in about two weeks and this is the first time I will be there since learning MDB+. I live in South Florida, my home casino uses regular cards and is dealing mostly NOR friendly shoes.

I plan on using my first day (or at least part of it) in Vegas to do a little recon. I would like to use the SAP count to determine if the casinos I plan to play at (and more specifically the tables) are MDB+ friendly. So for MDB+ I would like to see the SAP counts to be pretty much even with little disparity correct?

Your input and feedback will be greatly appreciated. I asked the question here rather than privately because I'm sure your answer will help others as well. Thanks...

I'm not sure we have figured out how to really use SAP with MDB+. Yes, it makes sense that you want the counts to be pretty much even, which signals the lack of a strong bias. But what defines "pretty much even"? To get an MDB signal, you need some disparity first, so the counts will likely not be even. So it may be a matter of how strong the bias is.

I have charted SAP on a bunch of my played MDB shoes, and so far I am still not seeing a clear correlation. Some of my very best MDB shoes do finish with close to the same SAP numbers, but there is plenty of what appears to be bias during the shoe. Remember, bias is exactly what MDB needs to set up wining bets. So while SAP continues to be an interesting way to analyze a shoes's HISTORY, I still have not found a way for the SAP counts to be much of a signal whether to take a MDB+ bet or not. In the shoes I looked at so far, about half my winning bets seem to be "confirmed" by SAP and about half of the winning bets might not have been made if following SAP. Any analysis that takes a 50/50 decision and returns a 50/50 outcome is probably not a valuable analysis.

Have not given up yet, and will continue to analyze both good and bad shoes. Logically it seems there should be something there, but we might just have to accept that we can't improve upon a 90% win rate. LOL.

Link to comment
Share on other sites

I would like to use the SAP count to determine if the casinos I plan to play at (and more specifically the tables) are MDB+ friendly. So for MDB+ I would like to see the SAP counts to be pretty much even with little disparity correct?

I'm not sure we have figured out how to really use SAP with MDB+. Yes, it makes sense that you want the counts to be pretty much even, which signals the lack of a strong bias. But what defines "pretty much even"? To get an MDB signal, you need some disparity first, so the counts will likely not be even. So it may be a matter of how strong the bias is.

I have charted SAP on a bunch of my played MDB shoes, and so far I am still not seeing a clear correlation. Some of my very best MDB shoes do finish with close to the same SAP numbers, but there is plenty of what appears to be bias during the shoe. Remember, bias is exactly what MDB needs to set up wining bets. So while SAP continues to be an interesting way to analyze a shoes's HISTORY, I still have not found a way for the SAP counts to be much of a signal whether to take a MDB+ bet or not. In the shoes I looked at so far, about half my winning bets seem to be "confirmed" by SAP and about half of the winning bets might not have been made if following SAP. Any analysis that takes a 50/50 decision and returns a 50/50 outcome is probably not a valuable analysis.

Have not given up yet, and will continue to analyze both good and bad shoes. Logically it seems there should be something there, but we might just have to accept that we can't improve upon a 90% win rate. LOL.

Link to comment
Share on other sites

  • 2 weeks later...

Ellis

The recent integration of SAP with MDB + makes MDB+ a much more effective tool in my opinion.

Case in point at my local casino in Maryland I could get nowhere with MDB+ but since integrating SAP and waiting for the signals to come within 2/1 I haven't lost a bet. Now you don't get many bets but the few you do get are winners. Let me note also that the low bet shoes would have difficult to win at otherwise. Reminds me of Ellis saying that we have to be aggressive in the good shoes and protective in the bad shoes.

When Random is qualified there may be anywhere from zero to four MDB+ events already happening. In my case I find it ok to just wait for at least two triggers while the shoe is in random mode.

Also the Vegas shoe at the Flamingo that you tried MDB+ would have never qualified for MDB+ had you been using SAP.

SAP just points you in the right direction for NOR or MDB+. It's very effective in telling you whether the shoe is Random or Biased when you use weighted averages and the 2/1 and even spread as the trigger. So much so that I was even contemplating a random/ bias count.

PurpleInk

Link to comment
Share on other sites

Ellis

The recent integration of SAP with MDB + makes MDB+ a much more effective tool in my opinion.

Case in point at my local casino in Maryland I could get nowhere with MDB+ but since integrating SAP and waiting for the signals to come within 2/1 I haven't lost a bet. Now you don't get many bets but the few you do get are winners. Let me note also that the low bet shoes would have difficult to win at otherwise. Reminds me of Ellis saying that we have to be aggressive in the good shoes and protective in the bad shoes.

When Random is qualified there may be anywhere from zero to four MDB+ events already happening. In my case I find it ok to just wait for at least two triggers while the shoe is in random mode.

Also the Vegas shoe at the Flamingo that you tried MDB+ would have never qualified for MDB+ had you been using SAP.

SAP just points you in the right direction for NOR or MDB+. It's very effective in telling you whether the shoe is Random or Biased when you use weighted averages and the 2/1 and even spread as the trigger. So much so that I was even contemplating a random/ bias count.

PurpleInk

Good points Purpleink: You know, I didn't create MDB+ with regular cards in mind - just the Vegas touch games.

But way2fast has done a good job stretching the delays to include regular cards.

We are sacrificing a few bets in random cards to cover regular cards. But I think with practice, SAP can tell us the difference

so we can play the most effective way for the table/shoe at hand. You seem to be "getting " it.

We always need to have flexibility in Baccarat - a way to adjust to the shoe at hand.

NOR does that very well. It has both system selection and mode selection as well as prog selection.

We never want to tie our hands with purely mechanical unflexable rules.

Right a random vs bias count could help. My 2 to 1 suggestion needs further development, thought and testing.

It is merely an idea at this point.

I've said before that SAP can't compete with NOR at biased tables

But I'm not so sure about MDB+ vs RSAP in random shoes.

MDB+ may never get a bet in a highly random shoe.

But, RSAP arrives at its bets by looking at the whole shoe thus far.

Except when all the counts are tied, there is always a high count to bet against and a low count to bet WITH.

Those are the best and most logical bets in a random shoe.

RSAP ALWAYS sees those bets no matter how random a shoe is.

MDB+, not so much.

I lose sleep over that.

For instance, in a touch game, suppose the counts are 2 4 4 8.

MDB+ might see no bets at all.

But meanwhile RSAP is saying, bet 1's stay 1 and 3s stay 3 - both sound bets,

and we get 3 chances on both bets to be right.

We get our chance to bet on 1's with EVERY opposite, which is half the time.

And our bet that 3's won't go 4 comes up 9 times per shoe on average.

RSAP gets more bets than MDB+.

Unless 1's stay at 2 and 3s stay at 4, which is highly unlikely in a random shoe,

we win both progs while MDB+ may still be waiting for a bet signal.

Yep, I lose a lot of sleep over that.

Link to comment
Share on other sites

Ellis

RSAP definitely gives more betting opportunities than MDB+ and more winning bets in a random shoe.

As RSAP goes against the hi and with the lo count I would think in the 2448 example that you gave that I'd bet with the 2 going to a 3.

SAP would be going with the hi and against the lo.

Just want to make sure I have it right.

PurpleInk

Link to comment
Share on other sites

  • 2 weeks later...
Hi Ellis-

I have a trip planned to Vegas in about two weeks and this is the first time I will be there since learning MDB+. I live in South Florida, my home casino uses regular cards and is dealing mostly NOR friendly shoes.

I plan on using my first day (or at least part of it) in Vegas to do a little recon. I would like to use the SAP count to determine if the casinos I plan to play at (and more specifically the tables) are MDB+ friendly. So for MDB+ I would like to see the SAP counts to be pretty much even with little disparity correct?

Your input and feedback will be greatly appreciated. I asked the question here rather than privately because I'm sure your answer will help others as well. Thanks...

Hi Ntrl9, how was your Vegas trip? What did you observe? Play results?

Link to comment
Share on other sites

Hey Way-

It was a quick trip, I got in late Thursday night and I left Sunday night. It was a quiet at MGM but Aria definitely had more action. I played the high limit room in both.

Here are the tables that I played, I'm not going to break them down into 20 plays:

1- P21241154211122422211224124

2- P1415111222432181121221213111121

3- B113132142364121121131

4- P2311111121111512111412121331122123

5- B43141131112342221242212111113

6- B21131351425323142126421421214

7- B3111111161213112231215311111211111

8- P531111141312221112212

9- P11521145111121111111111323

10- B221311114121112321211

11- P11154111126331431112154

12- P222151211113131314123

13- B1121411131111111214332115

14- P111111122313211122411341211

15- P1232112421124211111421211111121132111

16- B311111116121311223121531(11)111121111

17- P431411311123422212422121111113

18- B212141154211122422211224124

19- B1415111222432181121221213111111121

20- B231111121111512111412121331122123

Ntrl9

Link to comment
Share on other sites

Wow, looks like a lot of 1's Ntri9 and low 3s in several. 18 has no 3s and 19 has only 2.

way2fast warned us about high 1's.

20 shoes in 3 days! You're dedicated!

So what did you play and how did you do?

Link to comment
Share on other sites

Ellis

RSAP definitely gives more betting opportunities than MDB+ and more winning bets in a random shoe.

As RSAP goes against the hi and with the lo count I would think in the 2448 example that you gave that I'd bet with the 2 going to a 3.

SAP would be going with the hi and against the lo.

Just want to make sure I have it right.

PurpleInk

Almost correct PurpleInk. In the 2448 random table example, the mean count is 4.5 (the avg of all 4 counts)

1's are very low so our strongest bet is that 1's stay 1. And that bet comes up with every Opposite - half the time.

Every time we see an opposite, we bet another opposite - that 1's stay 1.

2's are slightly low. So we don't want to bet 2s go to 3. We don't want to bet against 2s - We need 2's.

But once we see a third circle - not only are 3's slightly low, 4+s are high. Sort of a double whammy.

So we bet an opposite. We are not only betting 3's stay 3, we are also betting AGAINST 4+s because they are already high.

Are you getting it now?

Link to comment
Share on other sites

Wow, looks like a lot of 1's Ntri9 and low 3s in several. 18 has no 3s and 19 has only 2.

way2fast warned us about high 1's.

20 shoes in 3 days! You're dedicated!

So what did you play and how did you do?

Hi Ellis-

This thread is on the NOR forum so I am not going to go into specific play but I will give my thoughts... Dedicated?? Vegas has a lot of distractions but I was focused...

I must say I was a bit shocked after the first day... The SAP counts were all over the place and imagine my surprise when my very first shoe had

no 3's- NO 3's???? After my first shoe I was -5 due to no 3's but I ended the day +9.

The one thing I can say is that after my first day of play I kept an eye on the SAP count and did not chase LC events blindly assuming that they would even out. I missed out on a few bets but more importantly it kept me from losing progressions on shoes like the no or low 3's...

I am waiting for Way2fast to comment to see if this is what he is seeing regularly in Vegas. This was my first trip to Vegas since learning MDB+ and I must admit that I was a bit naive going in. I thought I was going to go home up 50 units, so much so that I was worried about traveling home with all that cash.

I am grateful that my first shoe had no 3's because it was a big time wake up call... I lowered my unit size to only play black for the remainder of the trip because I was not feeling very confident. In that sense it was not good but it forced me to keep my eye on the SAP count.

In summary I ended my trip up 19 units and I consider that a major victory only playing MDB+ given the shoes I faced. I posted 2 shoes 9 & 10 that I did not bet at all in the shoe. I know people are going to say +19 in 20 shoes is terrible but I went out to Vegas to play MDB+ and that is what I did.

To keep with the theme of this thread SAP can and will help you if you let it... I play NOR every day at my home casino because they deal regular cards and the shoes are mostly biased (some more than others). I use SAP in my normal every day play and in regular cards I use it to play MC/LC. This trip SAP saved me on a few of the crazy shoes. After this trip I am going to look at playing MDB+ triggers at my home casino on shoes when the SAP count is running close.

NTRL9

Link to comment
Share on other sites

Hey NTRL9, thanks for posting the shoes and a summary of how you did. I wouldn't say these shoes are out of character for Vegas, but it is a little unusual that in 20 shoes there is a pretty strong consistent theme of lots of 1s and low 3s. I would be interested what casinos these shoes are from, and whether they are touch games or no touch where the cards are re-used.

Just doing an initial scan of the shoes, I get +30 using MDB+ the way I prefer to play it with delayed progressions (2,4,2,1,5,-3,2,-4,0,0,1,3,1,1,1,2,3,4,4,1). Out of curiosity, I looked further at the two loosing shoes to see if SAP would have told me anything. On the first one (shoe6), at the point of decision the counts for 3s and 4s were three times the 1s. Using that as a sign of a biased shoe, you could have avoided a couple bets and probably finished up 1 or 2 units in the shoe instead of -3. In shoe 8, the counts were 7 6 8 8. Perfect randomness, yet in this case the ensuing MDB+ bets lost.

It is easier to sit through these shoes waiting for MDB+ bets if you are also looking for other betting opportunities. I am having very good results just looking for either S40 or OTBL setups and then looking to make a short sequence of bets to capture 2-3 units per setup. What's a set up? Well, I'm sorry there are no hard and fast rules, I'm really just going by experience. But if the shoe is showing periods of choppiness, I would look for something like a 12112 and would then bet opposite the 2. Again, this is an example, not a rule. I have to say, most of your 20 shoes look like they would have been rich in these type of setups, so I would like to think capturing another 20 units and having to carry home those 50 units was doable. Of course, it's easy to see this when looking at the shoes now. Real world is always harder, and really don't know how I would have played the shoes at the time.

BTW, this thread IS in the MDB forum.

Edited by ECD
Link to comment
Share on other sites

Hey Way-

Next trip I'll coordinate with you so we can meet up... I used your delayed trigger for the 2's but I used the original triggers for the others.

The shoes I posted are all touch games from Mansion High Limit Room @ MGM and the High Limit @ Aria. I'm not in front of the score cards but if I think the first 5 were from MGM and the others from Aria.

Ntrl9

Link to comment
Share on other sites

  • Baccarat Hall of Fame Member

Here' s a bit of Bac2TheFuture for those of you just wanting to win a few units per shoe, and STOP when you do...or Don't

I did not " invent" this, just putting it into context of today's Baccarat environment

Pre-shuffled, or not.

Look, 50% of all events should be 1-IAR'S, and 25% 2-IAR'S, over the course of your " session experience" , whether 1 shoe played at a single casino, or 20 shoes played out over 3 days at different casinos...

N.O. - it will not be exact, whether per-shoe, or for 20

But, unless the casino is plundering and pillaging relentlessly, or all of Vegas is " in cahoots" with one-another, it pretty much will be...

So here is an old-school " system" , resurrected from the bone-pile, with a modern-day twist ( takes into account NOR bias + RegressionTo The Mean attributes of MDB)

Just glance at the tote board and look at/keep track of three things:

OTBL

Opposite

Repeat

Rules:

Anytime last hand resulted in an OTBL " win", no matter what bet,OTBL again next hand

Anytime last hand DID NOT result in an OTBL win , bet THE SAME AS whether the last hand was an Opposite, or a Repeat of the previous hand.

Example:

Was last hand OTBL? Opposite? Repeat? ( of the previous hand)

If answer was :

OTBL - YES

O - YES

R-NO

You must bet The next hand will be an OTBL result.

If last hand was

OTBL - YES

O- NO

R - YES

You must bet the next hand will be an OTBL result.

Note: If next hand would be a repeat of the result from the prior hand ( OTBL + O, or OTBL + R), this indicates and even stronger bet on OTBL result for the next hand....but in any case, bet OTBL regardless if the last hand was an OTBL result...

Now, if last hand DID NOT result in an OTBL result compared to the previous hand, but instead was just an O or R result from the previous play, just bet that the next hand will repeat as an O or R result again.

Best use is for small overall wins per shoe ( 1,2,3+ units)...then move on to another shoe, leave casino, etc.

EZ to apply w/progressions, or not...

This is great " hit and run" baccarat, or moving table to table, as opposed to playing whole shoes or waiting for MDB triggers

Does well if shoe is producing lots of 1's , or 2/3's in a given section of the shoe

Or.....lots of 4+ steaks in a shoe..., with normal amount of 1s, 2's 3's as a % of normal distribution...

AND REMEMBER, best for " hit it and forget it" advantage play...( thanks, TRBFLA)

Good luck, and give it a quick try for just a few hands, selected randomly, from your previously played shoes...

Link to comment
Share on other sites

Must say I was surprised to see all the 1's, and 1's and 2's in these shoes. Not what I would have expected to see in Vegas based on MDB+ and the 'super random' type shoes I was told Vegas produces?

By glancing at a few of these shoes I would think you could navigate through then with just S40 and not a lot more?

This type of NOR short term capture thing is that not the way Oz plays?

If you read his posts it sounds like that's the way he plays?

Australian casinos are quite tricky and he's been able to beat them with just modified NOR rules?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Terms of Use