All,

   I have a question that may have consequences down the road, assuming the stars align and all that.

  The question is:  What are the primary duties of a bot with regards to your roulette programming?

  Are you placing individual numbers?  Reading numbers?  Reading results?  Reading a screen position?  Multiple positions?

  Approximately how many "spots" or "areas" do you have to monitor to get the data you need to perform any calculations and place a wager?   That last question is probably the main one I have at this time.

  I currently have no need for a "bot" and don't forsee one in the future but knowledge is golden so I'm asking in preparation for an idea session that's coming up.

  If there is a link to a "bot" wiki or something, I'd like to take a look.

  AD

Most bots read and store the last spin result number, since that is the primary function
of any program to do with Roulette wheel.
(Building a data base of numbers, since it started to read them.)

Once the number has been read (red) and memorised, its then down to the program commands
set in the program software, as to what happens next.
It could read and store hundreds of numbers before actually doing anything with that information.


Its can be as easy as this:-


1. Find and read last result.
2. Remember that result.
3. Remember next spin result.
4. If lastspin result was Red....then bet Black
or
5. If lastspin result was High...then bet Low
or
6. If lastspin result was #13...then bet # 3, #13, #23, #33
or
7. and so on.........


U tell the program what to do with the info U have "put into your memory bank"


The bot only needs to read one image, the last spin result, the rest, as the saying goes.....is All History!! lol
(sorry for the pun!)


[reveal=Notes/Additional Info on Bots] Other info is stored in any bot too, like bank roll, stop loss, win stop position, and other various variables, but in essence, the only thing the bot needs,
to do its job, is to give it the spin result(s).
Bet placement, or "Clicking" is a function of remotely operating the mouse button,
in an ordered, programmed fashion........ according to the set program U have asked it to perform![/reveal]


I have edited this post.

Quote from: ADulay on April 27, 2013, 03:51:16 PM
If there is a link to a "bot" wiki or something, I'd like to take a look.

It is known "bot creators" aren't actively making tutorials    But don't worry, you can ask the fellow coders around to assist you on where to look in order to achieve what you need. All the way from reading numbers to placing bets.


Coders are usually a most-helpful bunch.

A bot can consider the the last three outcomes and bet accordingly.  I know because Nick wrote me just such a sheet.

I have no idea what else it might consider, but I would never assume it only needs to know the last outcome.

@ Sam.


I didn't mean for the bot to Only read the last outcome.
I mean, the bot only reads ONE thing on the table/felt/wheel/GUI interface that the casino shows U in the game,
and that is the last number spun.
Its doesn't need to know anything else from the GUI, apart from where the table is to enable chip bet placement.
It remembers all other spins (past) and accordingly, begins to perform what ever 'trick', consideration, or 'thought' U have asked it to do.

Its really a list of commands, all started from the spin results.

OK, Chris...

Just had to throw my two cents worth in.

Sam

A bot from start to finish

Main part of the bot is to read the number spun
It can then store (add that result to an array) you can program the bot to store as many or as little of the last spun number/s, this depends on what you do next.

EG if you were being stupid and waiting for 24 reds/blacks you would keep an array with a size of 24 and do the following

if arraysearch(my_main_array,for what=red) not found then
do this=bet red
elseif arraysearch(my_main_array,for what=black) not found
do this=bet black
else
keep waiting and check after each spin

The way I have my bits setup is like this, for any customer I send a setup tool which just spins the game reading an AREA for the last spun result, it spins and spins UNTIL it has either 36 on NO ZERO or 37 numbers on european roulette, when it has seen all of the numbers it asks the user to assign a number to each snapshot it took, this all gets written to an ini file like this

3655294628=6
1100174932=4
4284120404=13
474124401=35
3019337551=17
3067779567=20
1365523777=27

The long numbers are the actual checksum of the rectanglular area the number is printed in, the =17 is that that checksum value is number 17 so when the bot plays it gets a checksum of THAT area and checks the ini file for what that checksum actually is number wise.

that's the basic function for the bot itself, I also have what I call a whatbet file, this file can be changed to any method/system we can come upw ith so that's the onyl file I ever need to change for a new bot, in total I have 4 files MAIN, GETNUMBER, BETLOCATIONS and WHATBET all caled via #include BETLOCATIONS holds all the x,y coordinates of each bet location for the table in question, as I said before, the main file does all the main bits n bobs, it finds/locates the game window, gets its sizes/coordiantes on the screen and sets it active before the bot actually does anything.

Hope that helps

Quote from: Superman on April 27, 2013, 06:32:38 PM

The way I have my bits setup is like this, for any customer I send a setup tool which just spins the game reading an AREA for the last spun result, it spins and spins UNTIL it has either 36 on NO ZERO or 37 numbers on european roulette, when it has seen all of the numbers it asks the user to assign a number to each snapshot it took, this all gets written to an ini file like this

3655294628=6
1100174932=4
4284120404=13
474124401=35
3019337551=17
3067779567=20
1365523777=27

The long numbers are the actual checksum of the rectanglular area the number is printed in, the =17 is that that checksum value is number 17 so when the bot plays it gets a checksum of THAT area and checks the ini file for what that checksum actually is number wise.

that's the basic function for the bot itself, I also have what I call a whatbet file, this file can be changed to any method/system we can come upw ith so that's the onyl file I ever need to change for a new bot, in total I have 4 files MAIN, GETNUMBER, BETLOCATIONS and WHATBET all caled via #include BETLOCATIONS holds all the x,y coordinates of each bet location for the table in question, as I said before, the main file does all the main bits n bobs, it finds/locates the game window, gets its sizes/coordiantes on the screen and sets it active before the bot actually does anything.

Hope that helps

Aha.  That makes sense.  Giving a checksum to a previously detailed number or "symbol" seems correct.

So, not only can a "number", as it were, be determined by pattern and therefore pretty much anything on the screen can be identified, assuming its position on the screen remains constant.

My thanks to all who answered this query.

AD