Imagine an even chance bet selection that -just like any other- has scheduled a rate of 50/50 "in the long run", but in the short term has runs of 50 spins of dominance and 50 spins of barely showing (yes, that's the ultimate streaky one).

This 50/50 represents a balanced spot, but do notice the lesser numbers you cover, the more extreme things tend to be in regards to clumps.

They say all bet selections are equal... long term.

While it is true all bet selections are scheduled to even out "in the long run". Let's shift the focus to the short run, using bet selections as part of a STRATEGY, not sticking to them like a robot while they are losing the lot, only when they are presenting a good (measurable) strike rate.

Quote from: esoito on October 31, 2012, 04:29:50 AM
There's always something worth learning -- even if it's learning what NOT to do.

The most important part is learning without costing you a very HIGH-PRICED lesson at the actual gaming table.


Perhaps this is the most important part of testing. SAVING people money.

Quote from: albalaha on October 31, 2012, 03:57:50 AM
If we want to get something positive and constructive, joint and constructive efforts are required from various topic starters, testers and programmers.

Agreed.

Ideally, the cycle being: ways to bet are posted, methods are tested, conclusions are made.

One barrier I see is the amount of effort required to make proper tests. Manual testing is time-consuming, automated testing requires programming efforts, which either cost money or time to somebody, and since it involves costs the resulting program isn't likely to be given away to the general public (that's not the way it should be, but that's the way it is in real life. The case of someone hiring a programmer for giving the resulting program away are RARE... very rare).

Having said that, a way to solve this scenario is to have one main programmer creating and maintaining a framework, with several programmers creating tiny extensions/modules, consisting of only the pertinent parts to be test: namely only the extact code of the bet selection and/or the progression.

This way the main burden is centralized so the other programmers don't have to re-invent the wheel for things like data input/output, charts, optical number recognition, clicker, and the like. Focusing instead on the nitty-gritty of the method at hand.

This is what I aim to achieve with this site here. A centralized lab for testing, and ultimately betting via bots.

Would it succeed? Who knows. It's a paid project, funded by the subscriptions of this very site. It's still unclear whether or not would it have acceptance among the programming-able folks, but it should once the learning curve is taken. It's the difference between working with bare metal versus having an operative system.

---

Posters elaborating on their ideas, programmers relieved and focused on only working-out the very minimum of the posted bets and the users enjoying the conclusions.

Quote from: Wally Gator on October 29, 2012, 03:20:16 AM
I thought a loss at any level regresses to the next level, not back to the even chance.

The order from previous to next location is this:

PREVIOUS

Even chance.
Dozen/Column.
Double-street.
Quad/Corner.
Street.
Split.

NEXT

From previous (lower-paying) to next (higher-paying), we say we progress.

From higher-paying location to lower-paying, we say we regress.

Remember: The progression we are are talking about being "Progression in risk". The higher-paying location covers less numbers and hence the RISK rises/progresses.

---

Quote from: Wally Gator on October 29, 2012, 03:20:16 AM

Am I missing something here?  If we miss 3 spins and go back to the even chance level, how would we ever get to the splits level?

This is a *delayed* parachute, with a "conscious twist".

We're always hoping we wouldn't need to get to the splits level and all the bets resolve previous to it.

---

There are two things going at once: the unit size and the current location's payout.

You are positively mixing a progression in unit size with a progression in risk.

-Yes- The math is kinda fuzzy since it's not an straightforward progression; your unit size changes as well as your current bet location's payout.

In this scenario it's all about the bankroll balance and checking if the bet was a profit or a break even in order to stop/reset.

One last thing. You can reduce your betting unit, but you'll soon notice the higher units on the higher-paying locations during hits are the ones that make the best "upward spikes" for an exit point in the cycle 

The rationale of the delayed parachute:

If it goes poorly, you will be covering locations with more numbers, giving yourself a better chance to getting some hits and "fluctuating" until the tide turns so you can maximize the chances to "be there". i.e. bankroll preservation.

On the other hand, you will catch the good streaks naturally covering higher-paying locations to increase your chances of a recovery and a successful session-end or reset point.

Example:

You start at the even chance level. Using one (1) as your base unit, and stay there until you get a hit.

When you get a hit, you check your balance.

If your hit makes you a profit or breaks even, then you call it a reset and stay at the even-chance level.

If after your hit you are below your starting balance, then rise the betting unit +1, to 2 units, and move your bets to the dozens/column level.

If you miss 3 spins (a full dozen's cycle) you regress and take your bets back to the even chance level.

If you hit while betting the cycle, you check your bankroll balance.

If your hit makes you break even on the initial balance or makes you any profit, then it's time for a reset.

If -on the contrary- you are still below your initial balance, then rise +1 (to 3 units) and move your bets to the double-street level.

And there the same procedure for each level goes again.

If you miss 6 spins (a full double-street cycle) then regress your bets back to the dozens level.

If you hit, check your balance. If breaking even or in any profit, then it's time to reset.

If on the contrary you are still holding a deficit, then rise your unit +1 (to 4 units) and move your bets to the  corner/quad level.

Repeat the procedure for the level.

If you miss 9 spins without a hit, go back to double-street level.

If you hit, check your bankroll balance for a break even or profit.

If it's a deficit, then rise +1 and move to the next higher-paying location level.

Same procedure for the rest of locations.

Always using the cycle = payout to know how many spins to hold your bet on a location.

The base methodology is this:

   
• Rise unit +1 on a hit.
• Use the next higher-paying location on a hit.
• Go back to the previous lower-paying location ON A MISSED CYCLE.
• If your last hit gives you a profit or makes you break even, you reset to the even chance level (i.e start over).

The cycle for each level/location is equal to its payout:

   
• Even chance: 2 spins.
• Dozen/Column: 3 spins.
• Double-street: 6 spins.
• Quad/Corner: 9 spins.
• Street: 12 spins.
• Split: 18 spins.

You never go to straight-up level with the delayed parachute.

This one is based on the "parachuting" methodology.

For those who might not be familiar with it, the parachute is a progression in risk, simply going to the next location of the following ladder:

   
• Even chance.
• Dozen/Column
• Double-street.
• Quad/Corner
• Street
• Split.

This is delayed because it's based on CYCLES, unlike the traditional 36-unit parachute which is based on SPINS.

This could be used with Ignatus' suggested system from youtube: http://rouletteforum.cc/index.php?topic=10506

Of course, the "real" bets would have to be risen according to the ones on the 9-element ATILA line, even as not all numbers on the ATILA line are wagered with chips each spin.

---

i.e.

Your ATILA line is like this:

2 2 2 1 1 1 1 1 1

You would make your real bets for next cycle like this (in parenthesis).

Spin #1:

(2) 2 2 1 1 1 1 1 1


Spin #2:

(2) (2) 2 1 1 1 1 1 1


Spin #3

(2) (2) (2) 1 1 1 1 1 1


Spin #4

(2) (2) (2) (1) 1 1 1 1 1


Spin #5

(2) (2) (2) (1) (1) 1 1 1 1


Spin #6

(2) (2) (2) (1) (1) (1) 1 1 1


... repeating the bet from the start as the real bets end up.

---

It is a must to check on the bankroll at all times.

Given there are bets on less than the whole numbers in ATILA line when beginning the cycle, the profit/deficit derived from the line varies as well.

Juicier earnings and an accelerated recovery would happen shall a hit come in the beginning of the cycle.

Quote from: cristal2000 on October 28, 2012, 08:54:46 PM
but it does not work because playtech has updated the table layout

I recall it was the case with "fixed" clickers...

Self-configurable is the way to go now.

Hello dear WannaWin.

GUI can be released as a framework module when it's "usable".

---

Also, I could mash a tiny console/text-mode app if you are in dire straits...

If you can ram the description of a tracker in a small paragraph, I can give it a go.
One-liners would be better 

I'm talking the type:

- Tracker for last 5 double-streets to repeat.
- Tracker for hottest split in the last 36 spins.
- Tracker for the most regular dozen/column in the last 10 cycles.

You get the gist!

---

At times I like a small release. Perhaps to try a new approach, language or technique when building it...


Your proggie gets delivered as a free release for the community to enjoy.

Vic