Guest Posted March 23, 2012 Report Share Posted March 23, 2012 Guys, I'm thinking that I'm totally confusing you talking about two totally different Net Bet systems at the same time.The first one we discussed was a filler for XDX to be deployed when your SAP counts are tied leaving you with no advantage bets. That is NOT a losing shoe as PJ declared! Not even close.It is a gift shoe from the casino that you can almost always beat substantially. It will often be your best shoe of the day. Look, when your 4 SAP counts are tied or running neck and neck, SAP is NOT telling you this shoe is no good. Just the opposite. SAP is telling you this is a great shoe, just net bet Opposites vs Repeats.Why? Because it is mathematically impossible to have a tied SAP count W/O also having a tied or Zero OR count. Likewise, a neck and neck SAP count ALWAYS produces a neck and neck OR count. And such a count is ideal for O vs R net betting. And this form of net betting is so simple I could list all the rules in a single sentence.So no, I can't have PJ insisting that you take the loss and throw out the best shoes you are going to see all day. Beating them is as close to a sure thing as anything you will ever see in a casino. The idea of throwing them out is preposterous. This is not about personalities at all. It is about pure math.NOR already has a solution for such shoes - OTB4LXDX, as presented, had no solution other than try to keep your loss small. I've got a better solution: Try to keep your win BIG!I've played tables where the OR count stayed between -4 and +4 all day long every shoe. You can easily average +15 every shoe at such a table. And you'll probably want to consider raising your unit.The rules are as simple as rules get:Start anywhere but you'll find is best to start right in the middle of a ZZ or straight run.BET a 1230 up as you lose red prog on Opposites and the same in blue on Repeats. Whenever a prog hits it goes back to 1. When a whole prog loses it stays at 0 until it hits and then starts over at 1 while the other prog keeps on trucking at 1 unit. At each play subtract the low entry from the high entry and table bet only the difference on the side of the higher entry. Your highest possible bet is 2. That's it.Now, if you want to get a little cuter than that you can note if a 4 entry on either or both progs would have usually won. If so, fine, make the appropriate 4 entries. Now you are playing it 3 Hi. End of story.You don't need a manual or even a thread. The whole thing is as simple as pie.Recognize that a tied SAP count Always means a 0 OR count. These are your best Net Bet games. But you can also have a 0 or hovering 0 OR count W/O a tied SAP count. These are your second best games.Now, when we are discussing a random cards net bet scheme that is a whole different kettle of fish. There we would be also introducing P vs B net betting and also low side net betting.The problem with SAP in random cards is that you usually don't generate much disparity and SAP funtions on increasing disparity. Net betting functions on the exact opposite - decreasing disparity. But net betting can be designed to also function on increasing disparity. I'm trying to figure out just what kind of cards you guys are seeing in Singapore. For instance, if you were to tell me that your SAP counts are usually running closer than the shoes you see posted here, that would be a big help in designing a net bet system to your application. On the other hand, if you are seeing high SAP disparity, that would tell me your cards aren't really all that random. In that case SAP should work just fine. Just add the above Net Bet scheme to your quiver and deploy it when SAP is generating little disparity. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.