Credits to Notto 8)
Tried his famous bet, (10 numbers, wasn't sucessful)...Then i tried *12* numbers, that worked better... :)
Progressionline 1,1,1,1,1,1,1,2,2,3,4,5 STOP
Procedure: Bet every number that hits, until 12 numbers bet, (Then STOP/Restart procedure)
BR/Stoploss: 200u
Wingoal: 200u
It's not a long-term winner (it's hit'n run). Winrate is not impressive either (?) But it wins more than it lose, that's the point.
Test1. (Randomspins)
WWWLLWLLWLWWWLWLWWWLWW 14/22 = 64% Winrate
O0
RX-Code
system "Nottogame 12"
method "main"
begin
while starting a new session
begin
Set List[1,1,1,1,1,1,1,2,2,3,4,5] to Record "progression" Data
Set List[1,2,3,4,5,6,7,8,9,10,11,12,13,14] to Record "Spin Counter" Data
end
while on each spin
begin
if any inside bet won each
begin
clear Record "last12" layout
put 1 on Record "Spin Counter" Data Index
put 1 on Record "progression" Data Index
end
Track last Number for 12 spins to
Record "last12" layout
Put 100% of Record "progression" Data to Record "last12" layout list
add 1 on Record "progression" Data Index
add 1 on Record "Spin Counter" Data Index
if Record "Spin Counter" Data = 13 each time
begin
clear Record "last12" layout
put 1 on Record "progression" Data Index
put 1 on Record "Spin Counter" Data Index
Put 100% of Record "progression" Data to Record "last12" layout list
end
if total bankroll >= 200 each time
begin
stop session
end
if total bankroll <= -200 each time
begin
stop session
end
If Record "progression" Data Index >
Record "progression" Data Count
Begin
clear Record "last12" layout
Put 1 on Record "progression" Data Index
put 1 on Record "Spin Counter" Data Index
End
end
END
I would like to try….but Type: End Session
Quote from: Face on Nov 01, 03:31 PM 2018
I would like to try….but Type: End Session
Well? sry? i said -it's not a long-term winner? it's hit'n run, ..+200/-200 is very high wg/sl for this bet.
I don't understand when you code the systems and just test a couple of games, when you can simulate your systems for longer terms so here's something you can do, taking the code you wrote as an example:
If you look at the total bankroll amount if-statements. Instead of using end session you can do this:
if total bankroll >= 200 each time
begin
add 1 to record "won sessions" Data index
put 0 on total bankroll
put 1 on Record "progression" Data Index
put 1 on Record "Spin Counter" Data Index
end
if total bankroll <= -200 each time
begin
add 1 to record "lost sessions" data index
put 0 on total bankroll
put 1 on Record "progression" Data Index
put 1 on Record "Spin Counter" Data Index
end
That way you can download a whole chunk of spins and when the total bankroll has reach is lower or upper limit, the bankroll gets reset to 0 and the rest has been reset so the simulations makes each session short term. What's also good about it is that the summary don't gets messed up either so you can also see what your net % and all other states looks all sessions combined for long term result.
Now you can test the systems and not having to import a new spin file when you won or lost the sessions.
Attach a run of 10000 spins and summary as an example.
Quote from: celescliff on Nov 01, 06:38 PM 2018
I don't understand when you code the systems and just test a couple of games, when you can simulate your systems for longer terms so here's something you can do, taking the code you wrote as an example:
If you look at the total bankroll amount if-statements. Instead of using end session you can do this:
if total bankroll >= 200 each time
begin
add 1 to record "won sessions" Data index
put 0 on total bankroll
put 1 on Record "progression" Data Index
put 1 on Record "Spin Counter" Data Index
end
if total bankroll <= -200 each time
begin
add 1 to record "lost sessions" data index
put 0 on total bankroll
put 1 on Record "progression" Data Index
put 1 on Record "Spin Counter" Data Index
end
That way you can download a whole chunk of spins and when the total bankroll has reach is lower or upper limit, the bankroll gets reset to 0 and the rest has been reset so the simulations makes each session short term. What's also good about it is that the summary don't gets messed up either so you can also see what your net % and all other states looks all sessions combined for long term result.
Now you can test the systems and not having to import a new spin file when you won or lost the sessions.
Attach a run of 10000 spins and summary as an example.
Wow! Very nice! Thanks :love:
Now Run this on what i just finished (my most serious RX.coding project) "SUPERTRACK15", (see post soon!)
i believe this is the HG. ;D
cheers O0