Blue Eye Macro

I don't really see anything wrong in the code; the only sketchy thing I see is here:You should probably put a "macro.pause" in there so it has time to register the clicks for each bet. That may be why instead of 4 it's only going to 3 because one of the clicks is not registering...but that doesn't explain what's happening in the last images.

I think you posted the black15 twice instead of the black26 so I can't see the multiple there...but what would really help is to view the execution log. You will be able to tell what it's doing and what part it's messing up on. From what you posted it's either the variable.math is messing up (which I've never seen), it's not registering a win properly (the color), or it's what I put above. If you post the execution log, I would be able to tell.

Hi,

Thanks for your reply.

I put some pause and it worked .

Another problem is that sometimes it does't check the results (correctly or at all) or does not double the bet (from black to Red). I ran two tests and here comes the execution log (I have removed actions which are not important), another problem, I can not install virtual drive, when I try to do that, it shows a list of keyboards and mouses that are match with XP or Vista, there is no windows 10 that I can choose, I thought maybe it affects the performance.
1
Executing: Function.Execute(Name: Place bet on Red)
Executing: Function.Execute(Name: Check if we won Red)
Checking if: Variable.Is equal to(Variable name: won, Value: no)
Result: Yes
Executing: Macro.Report progress(Progress: We lost! Doubling bet)
Executing: Variable.Multiply (Math)(Variable name: bet, By: 2)
Executing: Function.Execute(Name: Place bet on Black)
Executing: Function.Execute(Name: Check if we won Black)
Checking if: Variable.Is equal to(Variable name: won, Value: yes)
Result: Yes
Executing: Macro.Report progress(Progress: We won! Resetting bet)
Executing: Function.Execute(Name: Place bet on Black)
Checking if: Variable.Is equal to(Variable name: won, Value: no)
Result: No
// No doubling//
Executing: Function.Execute(Name: Place bet on Red)
Executing: Function.Execute(Name: Check if we won Red)
Checking if: Variable.Is equal to(Variable name: won, Value: yes)
Result: Yes
Executing: Function.Execute(Name: Place bet on Red)



2
Executing: Function.Execute(Name: Place bet on Red)
Executing: Function.Execute(Name: Check if we won Red)
Checking if: Variable.Is equal to(Variable name: won, Value: yes)
Result: Yes
Executing: Function.Execute(Name: Place bet on Red)
Checking if: Variable.Is equal to(Variable name: won, Value: no)
Result: No
Executing: Function.Execute(Name: Place bet on Red)
Executing: Function.Execute(Name: Check if we won Red)
Checking if: Variable.Is equal to(Variable name: won, Value: yes)
Result: No
Checking if: Variable.Is equal to(Variable name: won, Value: no)
Result: Yes
Executing: Variable.Multiply (Math)(Variable name: bet, By: 2)
Executing: Function.Execute(Name: Place bet on Black)
Executing: Function.Execute(Name: Check if we won Black)
Checking if: Variable.Is equal to(Variable name: won, Value: yes)
Result: Yes
Executing: Function.Execute(Name: Place bet on Black)
Checking if: Variable.Is equal to(Variable name: won, Value: no)
Result: No
//No doubling//
Executing: Function.Execute(Name: Place bet on Red)

From the execution log it seems as it is working fine...or at least accurately to what is scripted.

In your first example at the top you have a value of "no" and result of "yes", it prompted you with "we lost" and doubled the bet. Near the bottom where you wrote that it did not double, it has a value of "no" and result of "no" which means the criteria was not met and therefore would not double. If you look at the second example in which you stated that it did not double, the value was "no" and result was "no" so it's the same here...the criteria was not met.

*At this point I would like to mention that this execution log does not match the script you provided. It is performing different actions and calls functions that were not provided in your original script. The script you posted would only bet on one color, but this execution log shows that it is changing the color to bet on.

With this in mind, I would assume that you have two different "check if we won" scripts - one for each color. So two things are possible. One is that you didn't script the logic correctly to take into account the color change; meaning it's not behaving as you want it to, but it is running correctly according to how it was written. Since you haven't posted this, I couldn't tell you for sure. The second possibility is that it's not recognizing the color that won correctly. But again since you, "...removed actions which are not important" I can't view the entire log to know for sure.

Do a forum search for installing Win7 virtual drivers in compatibility mode for Win10.

Hi,

Sorry, I have changed the original script to make it more challenging but forgot to mention it, I appologize.

As you said, in my new script, in case of losing the bet, color is changed and value is doubled, it´s what I have in my mind.

I have tried to list all problems which are like not doubling or switch colors not according to the instruction but as you mentioned, it seems there is a problem with checking function and specifically color recognition.

Function basically checks if the yellow box is there, then try to recognize the color inside the box, It works but not always.

I attach the script and a complete execution log and also a summary of log.

I don't get it why sometimes in execution log, it 's writtem after placing bet that "check if we won red/black" and sometimes there is only results.

Is setting of the program important and can it affect the results? for instance, I couldn't install the virtual drive or "DirectX rendered" is in N/A status.

I really appreciate your help.

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.

Is it complete or only an example?
Thank you

Example of bot working on live roulette



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

thanks

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

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.