What Rare Events (If Any) Actually Matter When it Comes to System Designing

[Mr J]

Another thing for anyone reading........follow the question. What "type" of person do you think would post "bitter" to another poster who is doing well? Think about it, easy answer.  Ken

[Mr J]

Another thing >>> What are the averages for some of the posters here? This is my GUESS, if this is NOT you, I apologize......... 1-2 visits to the casino per MONTH. 2-4 hours of play. Using dollar units. There is NOTHING wrong with those averages but people fall over when I tell them mine. lol You have to understand, I have plenty of cash for playing, plenty of free time. No kids/wife to support, no car payment etc. I live about 20 minutes from the casino. I play like I post and have few worries. If some feel threatened by all that, tough, you'll get over it. Ken

[xman1970]

I'm NOT pointing my finger at anybody but....


Let's keep it civil pls guys.....


Ok @ the moment, but we can ALL do without it boiling over....

thanking you in advance.....

[Spike]

"Your bet selection is flawed and useless" >>> You dont even know it.>>

You have a progression and no bet selection, actually. No big deal.

Ever see a plane fly over your house? Know what keeps it in the air? Math. Oh, metal and engines help, but without the proper math, it would not get off the ground. You can't argue with math, it never ever EVER lies. So if what you're doing seems to be beating the math, its an illusion. You're having a lucky streak. And all lucky streaks end.

I'm glad you're winning, Ken, I'm not jealous in the least. But be aware of whats happening, you'll feel better for it.. Its hard to conceptualize it will ever turn on you, but I know you know it will, I can tell by the questions you ask. You think people here HOPE it will, and thats not really true. When you have a bad water heater in your basement, you can tell yourself all day long theres nothing to worry about, but you really know better..

[bombus]

While this is true Bombus, when I asked the question posed in the topic of this thread, I was more referencing what events can we design a system around.  

You can't design a system around progression busting corrections until you actually have a system.  Then you can work in the corrections for the progression.

I'm more or less asking what "rare events" can we take into account for the initial design of a system.  We can work in the rest after that.

Yes RJ.

That's why I said partially answered. If you are to use them, then progression busting possibilities are important and should be right up there in the design stage.

As for the events you are focusing on, it's very difficult to be specific because there are just so many variables.

I think, worthy of close observation is, how long an event can be sustained, and how close together can similar events occur.

So for argument sake let's say the event is something as simple as,

Game 1) Street 1-3 is dominant after 28 spins.

Game 2) Street 1-3 remains clearly dominant for the next 28 spins.

Game 3) Street 1-3 remains dominant for the next 28 spins.

Game 4) Street 1-3 sleeps for the next 28 spins.

1 street sustaining dominance for 3 game cycles is an event of sorts.

Switching off in game 4 is an event of sorts.

So designing when to jump on an event, and for how long matters.

Game 1 you track, game 2 you bet street 1-3 for a win, game 3 do you continue with the legitimate bet on street 1-3, or do you look for another bet in anticipation of the event switching off?

What would be a similar event to switch on to? Perhaps the second dominant street?

And so on.

Switching mechanisms would be very important for event betting. Make it multi layered event betting with multi layered switching mechanisms.

A lot like a railway system that has a multitude of tracks to shunt between. The more tracks the better.

Food for thought anyway.

Cheers.

[rjeaton1]

Yes RJ.

That's why I said partially answered. If you are to use them, then progression busting possibilities are important and should be right up there in the design stage.

As for the events you are focusing on, it's very difficult to be specific because there are just so many variables.

I think, worthy of close observation is, how long an event can be sustained, and how close together can similar events occur.

So for argument sake let's say the event is something as simple as,

Game 1) Street 1-3 is dominant after 28 spins.

Game 2) Street 1-3 remains clearly dominant for the next 28 spins.

Game 3) Street 1-3 remains dominant for the next 28 spins.

Game 4) Street 1-3 sleeps for the next 28 spins.

1 street sustaining dominance for 3 game cycles is an event of sorts.

Switching off in game 4 is an event of sorts.

So designing when to jump on an event, and for how long matters.

Game 1 you track, game 2 you bet street 1-3 for a win, game 3 do you continue with the legitimate bet on street 1-3, or do you look for another bet in anticipation of the event switching off?

What would be a similar event to switch on to? Perhaps the second dominant street?

And so on.

Switching mechanisms would be very important for event betting. Make it multi layered event betting with multi layered switching mechanisms.

A lot like a railway system that has a multitude of tracks to shunt between. The more tracks the better.

Food for thought anyway.

Cheers.

It's actually pretty funny, I didn't even see the "partially" part.   My eyes just saw "I think you've just answered your own question".  Sorry about that.

Although, I'm happy I said it, as you've given some very valuable (in my opinion anyway) input.  I appreciate you taking the time to type all that out, haha.

It's this kind of thing I was looking for.  Any foundation upon which I/we can build upon...good stuff.  Thanks again.

[pins]

another rare event is three in a row.  1.1.1.

[rjeaton1]

@ Pins>> It's actually interesting that you said that.  I designed another system around the rare event of three in a row.  Although it probably isn't what you'd expect.

You don't bet, only track spins until you see two of the same number come out back to back (I.E. - 23,23).  Then, you bet that number.

You'd be surprised at how often 3 in a row actually happens.  You can test this sytem out yourself using the .DGT file I uploaded (its in the thread "Ultimate RXtreme .DGT File - Test any inside numbers system you can think of).

The reason that system is successful is because yet again, that is an event that WILL happen...the problem is when.

But, as you're only betting on one number for one spin, until a bet trigger is signaled, the progression is VERY LIGHT on you BR.

It can get pretty steep however, as the gap between one win and another can sometimes go VERY long.

[Mr J]

  "and no bet selection" >>> Spike, are you asking or telling me this?  Ken

[bombus]

End of the day, I think you should be doing the opposite of the obvious.

Build your methods around common events, not rare events.

Rare events are just that, rare, and therefore very sporadic in nature. Unreliable to say the least.

Common events are far more dependable.

A common event could be the ball landing within a 5 or 7 pocket section of the wheel more than once in 5 or 7 spins.

Using continuous tracking would instigate a very fertile betting formula.

[bombus]

-