No No
So regular bet is for example martingale 1sat 49.5 and 100% increase on loose
i there will be 2 over 99% in the row i wish to bet 10% of the balance opposite direction on 99%chance as there is low chance of getting the third one.
So the script should monitor for >99 and <1 and act if there is 2 in the row.
than it should count how many of this hi or low strikes was and let say after 5 it should bet only if there is the row of 3
Ahhhh ok, yeah... that makes way more sense!

You're looking for clusters of <1 or >99 rolls... and then wager 10% of current balance on the opposite, hoping you don't get 3x "<1" or ">99" rolls in a row.
But you're also wanting to count these clusters... so after 5 clusters, change so you only bet 10% if there were 3x "<1" or ">99" rolls..
well almost
it looks like it waits one bet before the correct bet i do not know why?
anyone knows why after 2 bets i am looking it does 3rd bet on 49.5% and then it does the 99% bet instead o directly after?
It's because the check for highCount >= 2 is effectively being done BEFORE the checking of the previous roll...
so, what is happening is that the script is checking if highCount >= 2... then it actually checks the previous roll and increments the count... it should be the other way around and increment first and then check... like this:
basebet=0.00000001
nextbet=basebet
chance=49.5
highCount=0
lowCount=0
previousbetBackup=basebet
function dobet()
if lastBet.Roll > 99 then
highCount = highCount+1
else
highCount = 0
end
if lastBet.Roll < 1 then
lowCount = lowCount+1
else
lowCount = 0
end
if highCount >= 2 then
bethigh = false
nextbet = balance * 0.1
chance=99.0
else if lowCount >= 2 then
bethigh = true
nextbet = balance * 0.1
chance=99.0
else
chance=49.5
if win then
nextbet = basebet
else
nextbet = previousbetBackup*2
end
previousbetBackup = nextbet
end
end