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

This is a most-relevant question for our software.

True; with the advancement of virtualization, the limits of "platform the software runs on" are getting "blurry"; but still, this is important to determine the native platform to program our software for.

If you use multiple platforms, you can tick the one you use the most.

Quote from: esoito on October 27, 2012, 11:00:24 PM
Victor is pretty busy at the moment

Indeed. Local business is thriving which makes me happy in one part; on the other side, it slows things down on the online endeavors.

I would very much prefer to work more online. Let's see if this and HobbyCode can eventually turn the tides

Quote from: esoito on October 27, 2012, 11:00:24 PM
but once he's more available....

...I can put it on the queue.

Wow, you still have that oldie.


Yes, it is possible. I hope to have good news about it soon.

Great compilation E-MAN

This selection is very easy to use, even without a tracking sheet.

The following are the transformed #'s (figures):

1: 1, 10, 19, 28
2: 2, 11, 20, 29
3: 3, 12, 21, 30
4: 4, 13, 22, 31
5: 5, 14, 23, 32
6: 6, 15, 24, 33
7: 7, 16, 25, 34
8: 8, 17, 26, 35
9: 9, 18, 27, 36

The selection is based on the last 9 spins.

You keep track of the last figure to repeat within that 9-spin window and bet it for -at most- 9 further spins at most. A hit closes the attack. You should never go past 9 spins; it's the break even point.

You only bet the last two figures that have repeated (eight numbers max., hence the name). Replacing the oldest figure with the newest one enabled.

Each new figure starts its own "bets counter" afresh, with its own 9 spins of attack.

---

Don't dismiss it because of its simplicity. This can be a streaky bet.

Since this is a time dimension selection, you use strictly the last 9 spins. One full cycle for the 4-number figure.

You are attempting to catch the "bursts" of hits and are "going with the numerical stream".

---

This is another one to be added to the framework.

Quote from: esoito on October 24, 2012, 07:29:44 AM

   
• If yes, where and how much?

Here and for free: [attachmini=1]

Base for 3rd cycle:


[attachimg=1]


We do this one later. It's 2 a.m. here.


Numbers bet: #35 / Cycle balance: 0 / Units per number: 1

---

Hopefully by now you got the gist of it

These two cycles have been benevolent. It isn't always the case. It can go past 30 spins without a hit, with over 7 numbers bet.

The progression is limited (37 spins max) so there is an exit point set in stone, which is good with progressive methods.

Let's retrack for the new cycle.

34 / Numbers bet: only #2 / Cycle balance: -1 / Units per number: 1


[attachimg=1]



7 / Numbers bet: only #2 / Cycle balance: -2 / Units per number: 1


[attachimg=2]


16 / Numbers bet: only #2 / Cycle balance: -3 / Units per number: 1


[attachimg=3]


33 / Numbers bet: only #2 / Cycle balance: -4 / Units per number: 1


[attachimg=4]


29 / Numbers bet: only #2 / Cycle balance: -5 / Units per number: 1


[attachimg=5]


16 / Numbers bet: only #2 / Cycle balance: -6 / Units per number: 1


[attachimg=6]


2 / Numbers bet: only #2 / Cycle balance: +29 / Units per number: 1


[attachimg=7]


[attachimg=8]



HIT!


Ending balance for the cycle: +29.

After the hit we re-use previous numbers until there is a new eligible bet.


We have a bet by "looking back" up to #21:


[attachimg=1]


The number to bet is #2:


[attachimg=2]


Which would make zone 3+ on both the wheel and wheel-felt:


[attachimg=3]



We start another cycle now.

Numbers bet: only #2 / Cycle balance: 0 / Units per number: 1

We continue working with the set of actuals:


13 / Numbers bet: #3 only / Cycle balance: 0 / Units per number: 1


[attachimg=1]


8 / Numbers bet: #3 only / Cycle balance: -1 / Units per number: 1


[attachimg=2]


10 / Numbers bet: #3 only / Cycle balance: -2 / Units per number: 1


[attachimg=3]


3 / Numbers bet: #3 only / Cycle balance: +33 / Units per number: 1


[attachimg=4]


[attachimg=5]

HIT!

Ending balance for the cycle: +33.