Blue Eye Macro

I finally figured out what the problem is. There is a variable in the loop that will always place "Place bet on red" after some time, regardless of what came before, because it is the beginning of the "loop". The loop should start with a variable that will determine what the loop ended on - a loss or a win. I have no idea how to do this.

I SEE

Hi Guestnick,

I hope you are doing well with your Strategy by doubling 8 times on a Colour

Please don't get me wrong if I do questions on behalf, but to be honest I'm

Math is not an opinion Right?
Why is the maximum bet 64 if we take 1 and double it 8 times



The Calculator says 256 should be the maximum Bet

Subsequently you need a Wallet of 256 * 2 - 1 = 511 Units to cover 9 Steps for One Color

Whenever you Hit.... you are getting 1 Unit Profit but if you lose once you will never recover again

Now just to clarify if your Max Bet should be 64 it is appropriate to say.....

we take 1 and we double 6 Times to cover 7 Steps

Subsequently we need a Wallet of 64 * 2 - 1 = 127 Units to cover 7 Steps for One Colour * 6 Colours (Black/Red/Even/Odd/High/Low) = 762


Pretending to get 10% profit out of it....
This could be a real scenario


Please try yourself and let me know



Predifine the variables like this



A friendly Advise.....
Never double when we lose But when we Win
Cheers

Hi Guestnick,

I hope you are doing well with your Strategy by doubling 8 times on a Colour

Please don't get me wrong if I do questions on behalf, but to be honest I'm

Math is not an opinion Right?
Why is the maximum bet 64 if we take 1 and double it 8 times

In the script you provided, you have functions for both place bet and double bet.
- "place bet" has a loop that will loop "bet" times
- "double bet" does not have a loop and will only run once

It looks like the way you are using it you need to reverse this. Use "place bet" to only bet once at the beginning and "double bet" in a loop for "bet" times (or as you have it, "double" times)...It doesn't look like you're using the variables "double" or "doubleButton".

It also looks like you're missing the math to increase "MinimumBet". In the original code it's at the top in the "if Variable.Is equal to("won", "no")" part. You need to multiply it by 2 there...or use those variables for double/button.

Hi there,

Hopefully someone will still read this, it's been a while. I have been trying to implement the source code and it works amazing! However, since this is a perfect way to 'grind' roulette, doubling by multiplying the minimumbet simply takes a while. I mean, if I double 8 times, it has to place the minimumbet 64 times.

So I tried to write a new function to make use of the automated double bet button. This works. It reads when I lost and then doubles it, but only once. If I lose again it just skips back to minimumbet.

Am I doing something wrong with looping my double bet function?

Thanks in advance!

begin
Variable.Set("bet", "{MinimumBet}")
Variable.Set("double", "{DoubleButton}")
Function.Execute("Reset window location")
begin loop()
Function.Execute("Place bet")
Function.Execute("Check if we won")
if Variable.Is equal to("won", "yes")
begin
Macro.Report progress("We won! Resetting bet")
Variable.Set("bet", "{MinimumBet}")
end
if Variable.Is equal to("won", "no")
begin
Macro.Report progress("We lost! Doubling bet")
Function.Execute("Double bet")
end
end
end

function("Reset window location")
begin
Window.Set location("Playtech - 0AR8584234 - Classic Roulette - Google Chrome", "yes", "1", "1")
Window.Bring to front("Playtech - 0AR8584234 - Classic Roulette - Google Chrome", "yes")
Macro.Pause("6000")
end
function

function("Place bet")
begin loop("{bet}")
Mouse.Click at coordinate relative to window("547", "567", "left", "Playtech - 0AR8584234 - Classic Roulette - Google Chrome", "yes")
Variable.Set random number("ms", "700", "1500")
Macro.Pause("{ms}")
end
begin
Mouse.Click at coordinate relative to window("516", "734", "left", "Playtech - 0AR8584234 - Classic Roulette - Google Chrome", "yes")
Macro.Pause("4000")
end
function

function("Double bet")
begin
Mouse.Click at coordinate relative to window("415", "735", "left", "Playtech - 0AR8584234 - Classic Roulette - Google Chrome", "yes")
Variable.Set random number("ms", "2000", "2200")
Macro.Pause("{ms}")
end
function

function("Check if we won")
begin
Variable.Set("won", "no")
if Color.At coordinate is within (RGB range)("61", "61", "61", "10", "884", "162")
begin
Variable.Set("won", "yes")
end
end
function

thanks

Example of bot working on live roulette



https://www.youtube.com/watch?v=cDNAbrO0jsY

Is it complete or only an example?
Thank you

I'll take a look at the files.

Some settings definitely affect the performance, but in this case (for the ones you listed) I would say "no."

Virtual Drivers are mainly for games that will not accept the Windows OEM drivers, but you have this working so there really isn't a need for them...and no they wouldn't affect the performance. If the game recognized that the inputs were from a 3rd party and they either wouldn't allow any input or gave you a message that stated something like "a macro has been detected" then that's where you could use the virtual drivers to get around this. In your case you are already running the macro and the game is accepting the inputs so you are fine with the Win API drivers.

DirectX is sort of the same way. If the game was rendering in DirectX and you tried to take a screenshot (like with the Investigator tool), it could just give you a blank screen. So if you were unable to take screenshots because the game is rendering in DirectX, then you could enable DirectX capturing in BEM to get the screenshots for the Investigator tool. But again, you seem to have this working also, there's no need to enable DirectX capturing.

If it doesn't always recognize the correct color, you just may need to do some adjusting. In your script sometimes you use "to be (RGB)" and sometimes "within (RGB)". Using "within range" is much better if the script is not recognizing the colors correctly; one is exactly that color and the other is a range or more values that are approximately that color. So in your original script (I haven't reviewed your new files yet) you are using a range of "10"...so maybe try "15" or a little more. *Well, first I would review the execution log to see if it's having an issue with one particular color or both and of course only adjust the ones it is having issues with.

To be honest, if that's the only problem you are having now, adjusting the color range should fix it. I'll review the files but try that and see if it helps. I'll let you know if I see anything else.