7.2.1. Additional settings

Additional settings will be available after clicking the white gear icon with a plus visible in the upper left corner of the module.

This section of the module contains the following parameters:

• “1 – Mouse cursor movement speed factor” – this parameter determines the speed at which the mouse cursor will move during the operation of the “AutoMat” betting module. The range for this parameter is 1-10 where the more, the faster.
  

• „2 – Mouse cursor speed factor for a numerical field” – this parameter determines the speed with which the mouse cursor will move over the numerical field of the table in order to add or remove chips. The range for this parameter is 1 – 20 where the more, the faster. The parameter is available from version 1.0.8.519

• “3 – Changing the speed factor to express (how many chips?)” – setting this parameter, e.g. to 5, will cause the mouse cursor speed factor – (cursor movement speed) to be automatically set to the maximum value, i.e. 10 when the total number of chips to be placed and removed by the “AutoMat” betting module will be five or more. It is necessary because in the case of some roulettes available online, there may be a situation in which “AutoMat” will have to bet on, for example, 20 different numbers and will not be able to do it, because the basic setting of the speed factor was too slow. Thanks to this parameter, we will avoid such situations. The range for this parameter is 0 – 36.

*This parameter is most important in the case of “Live” tables, where we are not responsible for starting the next spin, but e.g. the dealer, but it can also be used on “RNG” tables if we want to bet more chips faster – ( of course, after exceeding the threshold, measured in the set number of tokens activating the express mode). You can also try to immediately set the speed factor to 10, which is the maximum value, but the point is that our “AutoMat” behaves as naturally as possible – (humanoid), so we only rush when the situation requires it.

• „4 – Mouse cursor movement speed factor during chip removal” – this parameter determines the speed with which the mouse cursor will move while removing chips (technique No. 2 in the map creation process). The range for this parameter is 1 – 10 where the more, the faster. – Parameter available from version 1.0.7

• “5 – Click point randomness factor” – this parameter is used to randomize the click point and is measured in pixels. Setting this parameter to 5, for example, will cause that each click on places such as buttons, numeric fields when betting or chips will be clicked in a slightly different place each time. In this case, all points indicated in the table mapping process that need to be clicked will be randomized each time in the X and Y axes, in the range of 0 – 5 pixels. Setting this parameter to zero will mean no randomization, i.e. in fact clicking on the same points each time is not recommended. The range for this parameter is 0-50.

!One should be careful with this parameter, because it is always randomized from 0 to the set range. If we set too many pixels, it may turn out that the betting module will bet on the number 8 instead of the number 5. The rule is that the smaller the numeric fields, the smaller the value of this parameter should be.

• “6 – Maximum number of tokens to be removed” – this parameter indicates the number of tokens that can be removed from the table using the technique selected during mapping. While in the case of removing tokens, e.g. by right-clicking the mouse, the thing happens quickly and efficiently, so in a situation where during the mapping of the table we chose the option “left mouse button pressed with movement to a specific point” – (sliding the tokens off), we may not have enough time to remove e.g. 20 chips from the table. With this parameter, we inform the betting module how many chips can be removed by the selected technique, and after exceeding this value, “AutoMat” will bet on all attacked numbers, excluding the inactive ones, which will be a much faster solution. The range for this parameter is 0 – 37.

*This parameter is also the most important in the case of “Live” tables, where usually the dealer starts the next spin, and the time of starting the next game is not dependent on us.

• “7 – Number identification timeout” – this parameter indicates the time limit for the identification of the number, counted from the moment of detecting the state of the game “betting”, our betting marker. As a rule, the identification of the number occurs before the detection of the betting marker, but there are so many different roulettes on the network that it is difficult to predict whether this parameter will be needed for any table. As an example, you can give here the “Live” roulette, in the Polish casino “Total casino”, where when changing the dealer, there is not always a graphic change, thanks to which “Monitoring” can identify the number. If the number is not identified after detecting the betting marker and after using the time limit set in this parameter, we will be informed by voice that the number drawn in this game has not been detected, but the session will continue. The range for this parameter is 0 – 999. The value of each unit is 10 milliseconds (100 = 1 second).

!Check whether the graphic change by which “Monitoring” identifies the number occurs before or after the detection of the betting marker. If so, you should set an appropriate limit, during which the module will try to identify the number after detecting the state of the game “betting”.

• “8 – Random number of empty spins” – two parameters determining the range in which the number of empty spins will be drawn. If, for example, in the left edit field we set the value 10 and the right edit field the value of 25, then the number of empty spins can be from 10 to 25. To draw the next number of empty spins from the set range and reset empty spins, which took place always after placing a chip supporting the game . Only the counter of empty spins that have been made will be reset when the main chart attacks, resulting in the bet on the roulette table. The standard range for this parameter is 0 – 999. The value of zero in the right edit field is synonymous with the inability to release empty spins, ie those where it is not possible to start a spin without placing even a minimum bet. There is also the “Unlimited” mode, which can be activated by clicking the button with the same name. This option, when active, allows for an unlimited amount of empty spins. When the “Unlimited” option is active, the font of the button with which this option is activated will change its color to light green.

!Before we set the value of this parameter, check how many empty spins the table allows us to do. If, for example, after 40 empty spins, we are informed by the casino that due to the lack of action we have been disconnected from the casino servers, it will mean that this is the number of empty games we can afford on this table. When setting this parameter, it is worth subtracting a few units from the upper limit and entering 32 instead of 40. “Live” roulette usually allows you to observe the game for some time, while in the case of “RNG” tables it is different. If the “RNG” roulette is unable to play empty spins, you need to set the value of the parameter in the right numeric field to zero.

• “9 – Random delay before clicking” – two parameters that determine the interval in which the delay before clicking on numeric fields will be randomized during betting and removing chips. One unit is 10 milliseconds. As in the previous parameter, the delay value is randomized from the range specified in the edit fields. The delay is randomized before each click. The range for this parameter is 0 – 99, so the maximum possible delay is 0.99 seconds.

!Please note that this parameter is important for the execution time of the entire betting procedure.

• “10 – Random delay before clicking (in express mode)” – two parameters determining the interval in which the delay before clicking on numeric fields will be randomized during betting and removing chips, with the difference that the settings of this parameter will be taken into account, when the betting module is switched to express mode. This mode is used for fast betting, so the delay before clicks should be lower. One unit is 10 milliseconds. As in the previous parameter, the delay value is randomized from the range specified in the edit fields. The delay is randomized before each click. The range for this parameter is 0 – 99, so the maximum possible delay is 0.99 seconds.

*Why any delays before clicking on numeric fields? Because, as we wrote earlier, it is very important that we make the betting process as natural as possible. It may also happen that any table without the above delays will not work well or at all. A manually betting player always generates a certain delay between hovering over the target and clicking it, so let’s stick to the laws of nature. However, delays should not be overdone so that the entire betting process does not take too long. The delay for this parameter should not exceed 80 milliseconds, and in the express mode 40 *, i.e. by setting in the editing fields 2 in the left and 8 in the right, the computer will randomize the delay in the range of 20 – 80 milliseconds before each click, because one unit is 10 milliseconds. *

• “11 – Random delay before clicking (buttons)” – two parameters that determine the interval in which the delay before clicking on buttons or chips will be randomized. As a rule, this delay should be longer than when clicking on numeric fields. It is often the case that the function buttons or game chips on the roulette table appear or become active only some time after you hover over them, so it’s worth taking a good look at how the buttons of your favorite roulette table behave. Setting the order of 0.5 to 2 seconds in this case is not unusual, but before entering any values here, it is worth checking the response time of the buttons in different situations. The range for this parameter is 0 – 999, which is the maximum possible delay is 9.99 seconds.

*From version 1.0.8.519, the operation of parameter 11 has changed. From now on, the delay applies to clicking buttons as well as token selection (playing, sustaining or cleaning token). The random delay from the selected range will now apply to actions before and after clicking a button or token, instead of just pre-clicking.

• “12 – Random delay after clicking” – two parameters that define the interval in which the delay after a click will be randomized. This parameter is common to all clicked points on the table. The range for this parameter is 0 – 99, so the maximum possible delay is 0.99 seconds.

*There is another such thing as a delay between pressing a mouse button and releasing it, but this parameter was predetermined by us. It is also randomly selected each time the individual mouse buttons are clicked (or rather simulated clicking) and it is randomized in a range similar to the natural one.

• “13 – Simulation of human mouse movements, only for numerical fields” – this option, when active, will make humanoid moving the mouse cursor only within numeric fields, while the cursor will appear immediately on buttons without using the cursor movement on the screen. When this option is disabled, the movement of the cursor towards the buttons will also make the cursor move naturally on the screen. To activate this option, click on the “ok” button. When this option is active, the font of the “ok” button will be light green.

*If the mouse cursor is on the second monitor, then when the betting module needs to perform some action on the main monitor, for example placing chips, the cursor will immediately appear on the main monitor in one of the programmed places. When the mouse cursor jumps between monitors, it does not move on the screen.

• “14 – (SemiAutoMat) – only last bets (and spin for RNG)” – this option, when enabled, restricts the operation of the “AutoMat” betting module to repeat bets only and to clicking the “Spin” or “Repeat / Spin ‘for’ RNG ‘tables. We can use this option when, for some reason, we want to manually bet on our chips, and the role of the betting module will only be to continue the game. For this way of playing, it is recommended to use the manual mode selected in the strategy selection window, because only then the chips we place manually will be reflected in the attacked numbers, provided that we take care of a manual attack on these numbers in the windows responsible for them. In short, all the numbers that we place manually on the roulette table in the “SemiAutoMat” mode should be attacked manually in the platform windows.

*The button that activates the SemiAutoMat mode is also on the “Live” session panel in the main platform window and has the description “Semi”.

• “15 – Quick data download from numeric fields” – this option, when active, slightly changes the sequence of execution of procedures in the “Monitoring” module. We previously wrote that for tables with variable number field formats, the colors of the numeric fields to identify the number must be retrieved before they change their format to the spin time, in the “betting” state of the game. Tables with variable format of numerical fields include tables whose numerical fields change their size, color, become invisible during the spin, etc. This option is also activated by clicking the “ok” button. When the option is active, the font of the “ok” button will be light green.

Standard data download from numeric fields. In this case, data from numeric fields are downloaded during the spin. This is a solution for tables that do not format numeric fields during the spin. In the above picture, the procedure for delaying the fetching of data from the numeric fields is performed as the fourth, and the fetching of data will be performed in step five.

Quick download of data from numeric fields. In this case, the download of data from the numeric fields is still in the “betting” state. This is an option for tables that change the format of the numeric fields during the spin. In the above picture, the procedure for delaying the fetching of data from the numeric fields is performed as the third one, and the fetching of the data will be performed in step four.

*When the “AutoMat” module is active and the main graph of the platform is attacked, when identifying the state of the game “betting”, the procedures of the betting module will be performed first, followed by the procedures of the “Monitoring” module.

*The “* Quick data retrieval from numeric fields *” option has been implemented to work together with the “Variable numeric field format” function active, but it may turn out that some user concludes that the table mapped by him may only need this option for proper operation. It is important to understand how individual functions work so that they can be used consciously during the automation process.

• “16 – Variable format of numeric fields” – this option, when active, ignores the fact that many identification points of numeric fields have changed their color during the spin, which would normally mean an error in identifying the number and stopping the operation of the “Monitoring” modules and “AutoMat”. In the event that we activate this option, before the identification of the drawn number is attempted by the “Monitoring” module, two conditions must be met, which will mean that after the spin ends, the format of the numeric fields has returned to the state in which it was mapped and this is the state, which allows the identification of the number. Here they are:

• The number of identification points for numeric fields must be equal to or greater than that set in the edit field. This means that when the “Monitoring” module recognizes that the number of identification points set by the user, and specifically their colors, matches those previously downloaded, it will mean that the table format has returned to the state in which the colors of identification points were downloaded and this is the state where “Monitoring” can start identifying the number, but before that, we can set an additional delay described in the next point.
  There is an edit field (on the left) where you set the number of points to be identified. The range is 1 – 74. The optimal value for this parameter for most of the known variable numeric field tables is around 50 to 60 points. This value should not be less than 30 and greater than 70 points.

• After the required number of identification points has been recognized, the set time period must pass. This is a user-set delay. In the case of some tables, the return to the format of numeric fields enabling identification of a number may take, for example, some animated form, and therefore, after recognizing the necessary number of identification points, it is worth applying a delay that gives us a guarantee that the format of the number fields is 100% compatible with were downloaded by the “Monitoring” module before the table format was changed for the duration of the game.

When selecting the delay, we have the following buttons:

• 10 – 100 milliseconds or 0.1 seconds.
• 50 – 500 milliseconds or 0.5 seconds.
• 100 – 1000 milliseconds or 1 second.
• FX – (Flexible) – for this option we define the delay ourselves.
  

The font of the active option is light green.

*Each unit of this delay has a value of 10 milliseconds, so to set a delay of one second, set the value of the “FX” edit field to 100. By clicking the edit field arrows in the case of setting “FX”, change this value every 10, i.e. 100 milliseconds – ( 0.1 seconds).

Let’s look at the settings above for example. The value for identification points was set to 54 – (we all have 74, because 37 numeric fields 0 – 36 and two identification points on each of them).
To sum up, the procedure identifying the drawn number will start its work when at least 54 identification points – (specifically their colors) of the numeric pools will match those collected before the format change, and 500 milliseconds – (0.5 seconds) of time elapses from that moment.

!In the case of tables with variable format of numeric fields, it is important that the graphic change of one of the 37 numeric fields allowing for the identification of the drawn number takes place when the format of the numeric fields has the same form as it is when it is possible to bet on chips, i.e. it is the same as the format when the identification points are collected by the “Monitoring” module. Also, during the table mapping process, you need to remember that the numeric fields are mapped when their format is the same as the one in which there is a graphical change that allows for the identification of the number. In short, when mapping a table with the “Mapper” module, before using the “Target” function, we need to be sure that the table format is appropriate. If during the mapping process we take a graphical screenshot of a table during a spin that has changed its format for the duration of the game, then such a map will be useless. Each of the drops must be made in the game state “active bets”, when it is possible to bet. It is worth recalling that often roulette tables in online casinos may have the option to change the graphic format of the table. It is therefore worth checking if there is an option to change the graphic format of the roulette table in the graphic settings of the table, before we start the mapping process and selection of parameters, because it may turn out that one of the available formats may be less demanding in the automation process.

Above is an example of a table video with variable format of numeric fields. The “Monitoring” module starts during the spin. Below, in the sub-sections, we have described what activities took place in the displayed video:

1. The module checks the table format – 4 identification points indicated during mapping.
2. The synchronization process begins.
3. The module waits for the active betting marker – (betting marker) to appear, which is in fact the appearance of a pixel of the same color as the one we indicated when mapping the table at a specific point.
4. As the betting module is not active, there is no bet betting and the module goes straight to the delay with timer # 1 – (in this case the timer is set to 200, which theoretically means a delay of two seconds, but as we wrote earlier in the case of delay clocks 1 and 2, their speed depends on the speed of the computer).
5. After the delay (200 clock units) , the colors of the identification points are retrieved from all numeric fields. It is worth noting that the circle that appeared in the numerical field of the drawn number “19” disappears before the colors of the identification points are collected. If the delay timer was set e.g. to 100, then in the case of the numeric field 19, the colors of identification points would be incorrectly acquired, because the animated circle is still displayed in the field of this number at this time. The delay clocks are there to precisely set this moment.
   

!We remind you once again that the colors of the identification points of numeric fields must be downloaded when the numeric fields are devoid of any animations, shadows, etc., i.e. when they have their natural colors, and in the case of tables with variable format of numeric fields, the download must take place before the table will change its format for the duration of the game.

6. The module waits for the disappearance of the active betting marker – (betting marker), that is, in fact, for the pixel color to change to a different color than the one we indicated when mapping the table at a specific point.
7. Since in this case we are dealing with a table with a variable format of numerical fields the module instead of immediately analyzing all numeric fields in order to detect the color change and thus detecting the number, first waits until the two conditions for which it was met are met the speech before that means:

• The module checks if at least 54 identification points (specifically their colors) are in the right place.
• After detecting the minimum number of colors in the appropriate places – (54 in this case), meaning that the format of the numeric fields has changed to the correct one, there is a set delay, after which the attempt to identify the number begins.
  8. After detecting the number for the first time and then detecting the active bet marker, the synchronization process is completed. At this point the betting module “AutoMat” can be started.
  

!In the video above, the synchronization process is completed only when the identification points of the numeric fields are retrieved, and not when the game state is detected, “betting” after the first detection of the number, as we wrote earlier. This was a bug in the code that has now been corrected. You should also remember what we wrote earlier that the “AutoMat” module also needs one game per synchronization.

In the photo above, we can see all points of the table map presented earlier in the video. It is worth paying attention to where the “active bet marker” was set. This is the area of the numerical field of the number zero, which changes its size to a smaller size for the duration of the spin, then after drawing the number it returns to its original size and, as in this case, can be used as an “active bet marker” – (also known as a betting marker).

*The position of the game tokens are not displayed in the map screenshot, as they have not yet been indicated.

*All set parameters relate to a specific map and are saved to the file when the “Modus Operandi” module window is closed.

Copyright © 2023 aDifferentView — Powered by