kingstar

Hi Ellis, Count me in too. Looking foward to it

Hi Ellis, In the MDB+SAP thread, you stated this rule: "For every event(s) a shoe is high in, the shoe MUST be equally low in other event(s)" I am not quite sure what it is about. could you please elaborate it a bit more? Thanks

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

I think you can send an email to Keith to request for it.

In my opinion, after re-shuffle, every shoes should be seen as an independent shoe, we cannot consider previous shoe's last result as the previous hand of current shoe's first hand.

Hi brad01, I have tried to practise the shoes Pando posted with both MDB and NOR. MDB does not have many signals but can win just a few units in most of the shoes (I use three occurrence of events), while play NOR will win much more units in most of the shoes without big draw down.

Master Ellis, You are right. I have been quite busy for the past few days. I've read many good post in the private forum and think about how i can apply those method into my play while playing the real shoes posted by other members. It has been a great learning experience. For those guys who are serious about playing baccarat, i will say: Joining the private forum is just the first step, if you want to really improve your play, you must spend time to learn those method or system designed by Ellis. And practise a lot before entering casino to beat it Regards, Kevin

After joining the private forum for less than 2 weeks, i am slowly building up the system that meet my risk tolerant level through reading those valuable post by our master Ellis and other members. In this 2 weeks, i learned more than what i have learned from the public forum for the post 10 months since i first joined BTC (although for the first few month, i was still in doubt that can i really beat casino?). I wish that one year later, i can also start a thread like MVSeahog to say that i have win some money as compared to one year ago Regards, Kevin

Initially i don't quite understand why Ellis recommend S4 for PBPB. Now after going through some thinking, i think i might get why Ellis say so. Just to share my thought here (all comment are welcome): We start S4 for PBPB, once we see the first confirmed 2s or 3s, we can switch to normal S1 (if 1s is still the highest). This way it reduce the loss caused by 3s and 4s although it get less profit for the first 2s, play this way it is of much less risk. Regards, Kevin

thanks, Brendan I tried to search for SAP counts but did not get what i want. I think 3zz run should be same as 3s which occurs once every 16 play but just not sure whether it is correct or not

Hi Paul, You'are welcome. We learn from each other. I can practise and learn from your shoes. Regards, Kevin

Hi Ellis, Thanks for the correction. I will follow your suggestion to avoid betting on 4 or more altogether.

Hi Ellis, Could you please provide on average, one 3ZZ, 4ZZ or 5ZZ occurs in how many plays? I can't figure it out by myself. Thanks Regards, Kevin

Duplicated post................

Hi Paul, For me, if i see 2 4s+ event appears in the very beginning of a game (which mean under pure random case, there should be 8 2s and 4 3s followed it). I will expect that there will be quite many 2s coming out later. So the best is to apply 3 2s event then bet on next 2s go to 3s (which is same as use 3 2s event to bet the next 1s stay 1). Although you may lose the some opportunity, but you will reduce the risk. Only after 2s events normalize (for example, there is in total 4 2s event, i may consider to use back 2 2s event then bet on next 2s go to 3s) Regards, Kevin