MS4

[Kattila]

Quote :

**
I'm not really convinced that virtual betting to avoid strings of losses is beneficial in the long term.  All of those lost wins really add up.  **

Sometimes virtual bet will help and sometimes will not, i admit.
Let s take this  scenario(flat bet):
W is win from bet the next 4 spins after trigger
L-36 is lose from bet the next 4 spins after trigger

Start virtual play....L-36....L-36 ....W trigger....W....W....L-36....L-36....L-36 stop
wait virtual W .
So at the very start we avoid -72, and after the trigger win twice and then hit the 3Ls -36
now i wait that virtual W because after that 3Ls -36 can hit more Ls -36  , right ? Also can
hit some Ws but why take the risk to hit more Ls ? just stop and play after virtual win.
I know/admit ....even after virtual W can hit the Ls, but also can hit Ws.
At least i try to avoid some Ls not play non-stop and take all the Ls and Ws because
in long term i am sure the Ls will win.
Again sometimes virtual play do help and sometimes no matter how try can not
avoid L streaks , for that one is the stop lose.
Just my opinion.

[birdhands]

@Optimist, I don't know if this is what you were looking for but here is a nasty run of numbers (rng-practice) that I only survived because of the fibo (it went to step 14):


8,23,7,10,21,15,6,24,21,13,9,15,14,7,6,28,6,19,23,10,25,29,27,29,10,13,9,26,28,18,27,12,9,8,1,31,7,26,11,24,7,11,11,22,2,3,24,20,20,9,26,32,22,19,2,25,22,3,3,20,24,10,5,32,21


I ended up +60


@Katilla, thanks for your thoughtful response.  I am definitely leaning in your direction.  I'll try and test both ways.  I must admit that the virtual betting seems to have worked in your favor in all of your posted sessions.

[Kattila]

 
Another  real session flat ( probably the last i post like example)
-when start wait virtual W
-if have two triggers, choose the hotest
-at 3 x L-36 (or 2 x L-36)stop and wait virtual W
-when bet for real and hit L1L2L3L4 same mov. ( ex. r1r1r1r1) do
  not use r1 trigger, wait new trigger
-stop-loss around -120, target  +50 ( or +100)



[reveal]

19                        virtual play
7    r2
36  r2  trigger
26  b2  l
22  b2  l                                        b2 on wait
19  r1  l
23  r1  l  , bet b2                            r1 on wait
8    b2  w , start real play, bet r1
35  b2  l1
25  r1  w  +18
20  b1 
1    r2
2    b2  trigger
30  r1  l1
35  b2  w  +18
36  r1  trigger
1    r1  w  +27
19  r2  trigger
6    b1  l1
23   r1  l2
1    r1  l3                                   r1 on wait
9    r1  l4 -36 , bet r1
5    r2  l1
26  b1  l2                                   b1 on wait
0         l3
27  r1  w   0, bet b1
10  b1  w  +27
31  b1
26  b1  trigger
2    b1  w +27
32  r2
16  r2  trigger
35  b1  l1
21  r1  l2
36  r1  l3                                  r1 on wait
2   b2  l4 -36, bet r1
13  b1  l1                                 b1 on wait
6    b2  l2
35  b2  l3                                 b2 on wait
25  r1  w  0, bet b2 (hot)
4    b2  w +27
36  r1  trigger
0        l1
8   b1  l2
26  b2  l3
16  r2  l4 -36
13  b2  trigger
8    b1  l1                                   b1 on wait
17  b2  w  +18 , bet b1                       
33  b1  w  +27
35  b1
34  r1
29  b2
23  r2
32  r2  trigger
27  r1  l1
27  r1  l2
30  r1  l3                                         r1 on wait
25  r2  l4 -36 , bet r1
24  b1  l1
16  r1  w  +18                          w +63
11  b2
4    b2  trigger
9    r2  l1                                             r2 on wait
21  r1  l2
0         l3
35  b2  w  0,  bet r2
14  r2  w  +27                                     W  + 90  end


[/reveal]


good luck

[birdhands]

Please forgive me if I'm not clear on the concept, but the more I test this the more I wish I was able to capitalize on repeats.  I'm seeing a lot of movements repeating themselves.

[Kattila]

Please forgive me if I'm not clear on the concept, but the more I test this the more I wish I was able to capitalize on repeats.  I'm seeing a lot of movements repeating themselves.

Very true Sam, there are another(s) way(s) to play....
bet the last to repeat, bet the second last....flat bet...
but bet after virtual W or after a few Ls (ex. 3 or 4 Ls)
after W +27 or +18 bet again once and after 4 Ls stop wait new trigger.
Or use that Fibo but again play only after virt. W or after some Ls.


Ex. bet the last to repeat flat bet:
(this is the lost session i posted this days ended at -117).

[reveal]




26          virtual play                                                total
29  b2
32  r1 
11  b1 
4    b2 
2    b1 
6    b1  w virtual
8    b1  w +27
9    r1  l -9, wait
17  b1  l       
34  r1  l
25  r2  l  trigger 4Ls
11  b1  l1
31  b1  w  +18
8    b2  l -9 wait
1    r1  l                     
31  b1  l 
12  r1  l  trigger 4Ls
20  b2  l1
18  r1  l2
16  r2  l3
31  b1  l4 -36 wait
33  b2  l
35  b1  l
35  b1  w virtual
24  b2  l1
10  b2  w  +18
20  b1  l1 -9, wait
29  b1  w virtual                 
35  b1  w +27
2    b1  w +27
32  r2  l1 -9, wait
5    r2  w virt.                           
19  r2   w +27
0        l1 -9 , wait
6    b1  l
27  r1  l
29  b2  l
2    b1  l  trigger 4Ls
32  r2  l1
23  r1  l2
5    r1  w +9  wait                   
15  b2  l
2    b1  l
26  b2  l                             
16  r2  l trigger 4Ls
18  r1  l1
31  b2 l2
23  r2  l3
10  b1  l4 -36 wait
13  b2  l
4    b2  w virtual                           
31  b2  w +27
19  r1  l1 -9 wait
27  r1  w virt.
22  b1  l1
27  r2  l2 -18                     end at +36                   





[/reveal]

[ophis]

Hi Kattila.

Just now I'm in the middle of coding MS4 into MST.
Its not ready yet but when i was testing things that are already done i have found something rather interesting.

You may actually use it as a base for some new mod.

--------

This is sort of HALF MS4. Tracking/Assigning movements are identical to MS4.
The only thing that is not yet coded are YOUR triggers.

Basically what it does now is:
Its looking at X amount of movements back, picking up the HOTTEST movement and betting it regardless of previous LW. If there is more than one hottest movement it is NOT betting at all.

I did some tests about how much movements back is the best to track.
i did test 6,12,24,36 movements back.

I won't post all of the results here but just the one that seems to be working.
According to my tests the best results i had was with tracking of last 12 movements.
Then Z-Score was highest.

[attachimg=1]

[attachimg=2]

----
Another modification which i have tested was:

If there is more than 1 hottest movement (2) then bet 2 hottest movements (18 numbers).
Again the best was with tracking of 12 movements back.

[attachimg=3]

[attachimg=4]

----

SPINS SOURCE:
10 000 - Live Wheel
20 000 - Playtech (not sure if Live)


All test are made using FLAT bets.

[birdhands]

Ophis, this is great.  In my opinion it is more true to the system to play the hottest movement in this way.  Way to go.

[Hermes]

It looks like stocks or Forex trading.
Hermes

[Kattila]

 
Thanks for your hard work Ophis,
keep us updated about the best way(s) to play
this method. I agree that( bet the hottest) is one of the best ways
to play this method and there is another very similar method ( 6G/6A)same
principle and i do play the most hot (one or two)movements from the last 6-12 spins
flat bet or sometimes using progression (around 20 steps for 6 numbers/one movement).

cheers

[ophis]

About progression.

I do have respect to all great mind of progression developers but since there is so many of them i have decided that from now on I will implement ONLY DYNAMIC progression.
-----
So basically you have options to setup:
Minimum profit per bet
Maximum unit size per number/street/line etc. to bet

Reset/Stay at max units on progression loss.
----
Progression is calculated by MST according to those setting on each spin.
In my opinion this is the best way to get most optimal progression regardless of amount of numbers to bet
(important on some systems where amount of numbers is changing on each spin).

And it is also convenient because you can simply setup MaxUnitSizeToBet on 1 to have flat bet
(which is what I mostly use).

----------

Also Kattila could you suggest which way should be coded?

In case we have 2 triggers like here:
14 
26  B1  (26 is B1 from 14)
14  R2  (14 is R2 from 26)
32  R1  (32 is R1 from 14)
24  B2   ......so on....
29  B1  trigger
17  B1  W +27
34  R1  trigger
18  R2  L1
18  R1  W  +18
30  R2  trigger
we have 2 triggers here R2 (appeared 2) and R1 (appeared 4) in this case.... should we bet on LATEST(R2) trigger... or on HOTTEST(R1)?
I know there have been some modification and I need to have it clarified before I will move forward with coding.

[ophis]

hmmm guess I can code both ways and include it as an option to chose...

just now it is coded to bet on HOTTEST movement and this is the way it looks on my 10k live spins.

THIS IS IMPRESSIVE.

[attachimg=1]

FLAT BET ofc.

[Kattila]

So many ways to play this movements .....

In that case( after w on r1) i don t consider r1 trigger anymore, i take the next
trigger. So after win on one movement i don t bet that one exception is if that
movement hit again twice, then is trigger.
And if i have to choose between two new triggers then i choose the hottest.
I already posted  rules in the last posts:

-when start wait virtual W
-if have two  new triggers, choose the hotest
-at 3 x L-36 (or 2 x L-36)stop and wait virtual W
-when bet for real and hit L1L2L3L4 same mov. ( ex. r1r1r1r1) do
  not use r1 trigger, wait new trigger
-stop-loss around -120, target  +50 ( or +100)


------------------------------------------------------------------------------
Another way is stay on the winner until hit -36, then wait new trigger and bet
for the next 4 spins, if win stay if not take new trigger. ( rules for flat bet and
progression, so stay on the winner, if lose L1L2L3L4 take new trigger  and next progr. steps).
Take your time with this one (way)....

We need to find the best one,maybe the best until now is that you already coded
time will tell...

thanks

[ophis]

So basically what should I do is to code it as it is described and given example in reply number 49?

Ok. Because first I was doing what was said in 1st post.

by the way: Your systems are great but those Virtual Wins and triggers are pain in the a** to code

[Kattila]

So basically what should I do is to code it as it is described and given example in reply number 49?

Ok. Because first I was doing what was said in 1st post.

by the way: Your systems are great but those Virtual Wins and triggers are pain in the a** to code

We try to find the best way , tweak , improve to better....
and i know is not easy for you...take it easy...take your time...

[maestro]

just quick question,how many numbers you bet mr.kattila when you have your trigger...your system looks immpresive