Is roulette spins truly random ?

[gizmotron2]

It took me more than 1year of research to understand fully the crap that TurboG wrote.

That's funny to me. I spent 6 months on his hot number stuff and wrote software that I thought confirmed it. There was one line of code out of place that screwed the results. After I discovered that flaw it failed.

This list is from 76 spins, 2 cycles of 38. It shows each number and how many times it hit in the two cycles.

8 0,31 0,34 0,16 1,18 1,4 2,11 2,12 2,15 2,17 2,25 2,33 2,36 2,6 3,9 3,1
4 3,19 3,22 3,23 3,27 3,28 3,29 3,32 3,37 3,38 3,1 4,2 4,3 4,7 4,13 4,
20 4,30 4,35 4,10 5,21 5,5 6,24 6,26 6, -- So #8 hit zero times and #26 hit six times.

[ignatus]

Did some testings (not exactly the same, but similar)

works pretty well 

[ati]

works pretty well 

I don't think something works well if it breaks even or loses for 20-30,000 spins 
At least it's a long term test that shows the reality and not a lucky sequence of 200 spins.
Yesterday I had an idea that I couldn't code, so I started doing a spin by spin test in excel. It's all flat bet, covering 9 numbers. I thought this is it.
Today I thought what the hell, I'm gonna do a real money test. It didn't take long for the casino to find the spins that make me lose. 
Deep down I knew it couldn't work. Somebody said it many years ago. Is there a permutation that can make my system lose? Then I can be sure that roulette will find it.

[MoneyT101]

I don't think something works well if it breaks even or loses for 20-30,000 spins 
At least it's a long term test that shows the reality and not a lucky sequence of 200 spins.
Yesterday I had an idea that I couldn't code, so I started doing a spin by spin test in excel. It's all flat bet, covering 9 numbers. I thought this is it.
Today I thought what the hell, I'm gonna do a real money test. It didn't take long for the casino to find the spins that make me lose. 
Deep down I knew it couldn't work. Somebody said it many years ago. Is there a permutation that can make my system lose? Then I can be sure that roulette will find it.

Many people are just coming up with an idea and then testing it. 

But where’s the logic??

Look at your template and based on your template what happens do a step by step on what you’re seeing.  And take logical steps.

How can you beat those bad permutations? Or how can you play in a way in which you don’t lose as much?

[ignatus]

I publish this now, (yes, im a fool) but then it´s not my system, the original idea was Gizmotron, so credits to Him....but then, i don´t know if it´s a "good system" because i´ve seen many losing sessions also, winrate is not higher than 70%... also, you would need a pretty large BR about 1500-2000u played with 1u bets.

I play this with a 107 spin cycle, with the positive progression 1,3,5,8 STOP (An alternative positive progressionline is 1,3,5 STOP)

How i´ve coded it. This system looks for how many times a  single Hotnumber (number hit 2 times within a 20 spin cycle) will hit again within a 107 spin cycle.

That seems to work, as i said "sometimes", when it wins, usually it wins big, ...Hit and Run, as always, could work may be

TEST 1-5 Livespins

RX.code

Code Select Expand

system "HotCycle"
// © ignatus 2019 ©

method "main"
begin
  while starting a new session
  begin
       Set List[1,3,5,8]
              to Record "progression" Data


  end
   put 0 to Record "Highest Bankroll" Data


  while on each spin
  begin
   Track last Number for 20 spins to Record "last" layout
   

   
  IF flag "bet" true each
  begin
  Track last Number for 110 spins to Record "last1" layout
   IF Record "last1" layout index >= 107 each
   begin
      set flag "bet" false
      clear Record "last1" Layout
      put 1 on Record "progression" Data Index
      clear Record "bet" layout
   end
  end

      IF any inside bet lost each
  begin
   // add 1 on Record "progression" Data Index
   end




   If any inside bet won each
  begin
   add 1 on Record "progression" Data Index
  {   clear Record "bet" layout
     clear Record "bet1" layout
    Reset all flags false
      add 1 on Record "progression" Data Index

       if Bankroll >= Record "Highest Bankroll" Data
     begin
        clear Record "Highest Bankroll" Data
        put 100% Bankroll to Record "Highest Bankroll" Data
        put 1 on Record "progression" Data Index
     end
   }
  end






IF Record "last" layout is found within Record "secondlast" layout each
begin


if flag "bet" false each
begin
set flag "bet" true
put 1 on Record "progression" Data Index
clear Record "last1" Layout
          copy Record "last" layout to Record "bet" layout

         Put 100% of Record "progression" data to Record "Bet" Layout list

end
end

If flag "bet" true each
begin
  Put 100% of Record "progression" data to Record "Bet" Layout list
end


{ if total spin count >= 300 each
  begin
  stop session
  end
  }
 
  if total bankroll <= -2000 each
  begin
    stop session
  end

  if total bankroll >= 300 each
  begin
     //stop session
  end

  set flag "clear" false


If Record "progression" Data Index >
  Record "progression" Data Count  each
    Begin
      set flag "bet" false
      clear Record "bet" layout
      Put 1 on Record "progression" Data Index
     End
   
   Track last Number for 20 spins to Record "secondlast" layout
  end
END

[gizmotron2]

I publish this now, (yes, im a fool) but then it´s not my system, the original idea was Gizmotron, so credits to Him....but then, i don´t know if it´s a "good system" because i´ve seen many losing sessions also, winrate is not higher than 70%... also, you would need a pretty large BR about 1500-2000u played with 1u bets.

I'm not sure what system you are referring to? There is no way that you programmed reading randomness. Perhaps it was on my adventure into Turbo's law of thirds distributions?

What is it?

[gizmotron2]

Interesting. This is the first time I've looked at this scripting language. It's session oriented for simulating Roulette.

It's not reading randomness. It's some kind of progression with stop points.

[ignatus]

What is it?

It´s a system based on your idea, "how many times a hotnumber repeats within a 72 spin cycle", now i use a 107 spin cycle...for a hotnumber.

positive progression 1,3,5,8 STOP (An alternative positive progressionline is 1,3,5 STOP)

How i´ve coded it. This system looks for how many times a  single Hotnumber (number hit 2 times within a 20 spin cycle) will hit again within a 107 spin cycle.

[gizmotron2]

Interesting, I morphed it from Turbo.