7.2. Modus Operandi module

Once we map the roulette table, we must ensure that all operations related to identifying numbers or placing chips are performed in a timely manner. For this purpose, among other things, the module “Modus Operandi” is used. Modus operandi literally translated from Latin means “* way of acting *”. This module is a place where, apart from various parameters, there is also a graphical interface for the workflow of the “Monitoring” and “AutoMat” modules, which shows the way they work together with the clocks set by the user. They are used to delay the execution of certain procedures in the “Monitoring” and “AutoMat” modules. The module is divided into five sections:

• “Table name” – this section contains the name of the currently loaded map. It is identical to the one we entered in the “Mapper” module at the beginning of the table mapping process.

• “Synchronization” – synchronization is a process necessary for the correct operation of all modules. This process takes a maximum of 2 spins. It is a process that is carried out automatically without user intervention and takes place right after starting the “Monitoring” module. In this section we can check if the module is synchronizing or not.

*In the case of “Live” tables, after starting the “AutoMat” module, this module must also be synchronized with the game state. This process is automatic and also takes up to two spins. This process does not have a graphical progress indicator. Remember that after activating the “AutoMat” module on the “Live” table, it will start working from the next spin, while in the case of the “RNG” table, the betting module will start working immediately after it is started.

• “Monitoring” – this section informs about the course of operation of the “Monitoring” module. In this section, apart from the graphical presentation of the module’s workflow, there are also two user-set clocks No. 1 and No. 2, which are used to delay before downloading the identification points of numeric fields. This process is described in detail later in this thread.

!Identification of numbers by means of the “Monitoring” module will start after the synchronization process is completed.

• “AutoMat” – this is the section informing about the course of work of the “AutoMat” betting module. In this section, apart from the graphical presentation of the module workflow, there is a user-set delay timer No.3, which gives the user time to react after drawing the number. This delay is described in more detail later in this thread.

!The “AutoMat” module can be launched only after the synchronization process is completed.

The procedures of the “Synchronization”, “Monitoring” and “AutoMat” sections during their work inform us in what state they are currently in.
The possible states are:

• Task in progress
  

• Execution of the task without error
  

• Error while executing the task
  

Errors can only occur in the operation of the “Monitoring” module whose task is:

• Identification of numbers
• Identification of the correctness of the table format
• Identification of a betting marker
• Synchronization with clocks (setting desired delays)
  

The most common errors are:

• Incorrect table format – usually caused by starting the “Monitoring” module, when the roulette table has not been started before, it has a different location or size than during
  mapping process. A table identification error may also occur when for a long time no action takes place on a correctly launched roulette table and a window appears with a message that the user is disconnected from the casino server, which is usually accompanied by a change in the color scheme or the colors of the four identification points of the table indicated during the mapping process. . There is also a possibility that during the table mapping process, we indicated one of the four table identification points in the wrong place, where the colors are not constant – (changing) and this is a condition that must be met for the whole to work properly.

• More than one identified number – as we wrote earlier, the number is identified when, after drawing the number, some kind of change in the graphic field of a given number occurs. When two points on the numeric field at the right moment change their color, they will be correctly identified. If for any reason more ID points change their color after drawing the number, you will get an error. Such a situation may occur when, for example, the collection of identification points takes place at the wrong time – (clock no.1 or no.2 incorrectly set). Another reason may be an incorrectly created table map, where, for example, we indicated identification points in the wrong places. Useful in such a situation may be the “Map test” function, after which all points drawn during mapping will be displayed on the graphic screenshot.

The picture above shows an example of a window displayed when more than one number is detected.

Rare errors are:

• Incorrect identification of a number – such a situation may occur when, for example, when creating a table map, we did not keep the correct order of the mapped numeric fields. The order must be consistent with the one displayed in the information section of the “Mapper” module during the table mapping procedure. Timer settings # 1 and # 2 can also play a role in this kind of error.

• Betting Marker Identification Timeout Exceeded – “Betting Marker” is used to detect two states of the game: “betting” and “end of betting”. An error can occur if, for any reason, any of these conditions takes longer than five minutes to wait.

• Number identification time limit exceeded – similar to a betting marker, if for any reason during the ‘Identify Number’ procedure it is not recognized within five minutes, you will get an error.

Examples are:

• Live roulette is sometimes cleared by the game staff during the game, and if it takes longer than five minutes, it will time out and result in an error.
• There may be a situation where the table’s identification points match the mapped ones, despite the fact that, for example, roulette stopped working because there was a technical failure on the casino’s side. In such a situation, the “Monitoring” module, having data informing that the table format is compatible, will wait for one of these three states of the game and an error will occur after the time limit is exceeded.
  

*The time limit mentioned above depends on the speed of your computer. 5 minutes is the minimum waiting time and may be longer on older computers.

• “Map test” – in this section there is a “Test” button, clicking which will take a screenshot of the roulette table running. All points plotted in the process of mapping the table will be presented on the screenshot of the table. From version 1.0.5 there is also a button “Last Screenshot”. After clicking this button, the last screenshot will be displayed, which may be helpful in diagnosing map errors.

!The “Map test” function can be used before the “Monitoring” module is started, while the “Last screenshot” function can be used after an error in the “Monitoring” module.

Above is an example of using the “Map test” function.

*As our map is about the “RNG” table, there should also be a “Spin” button in the above screenshot. You can not see it there, because the “Repeat / Spin” button has the same position in this case, so these points are superimposed here together with their descriptions. In this case, the last mapped button will be visible in the screenshot. It is possible because they appear after drawing the number interchangeably depending on whether we made a bet before or whether it was a game without placing a bet – (empty spin).

*The positions of “A” and “B” tokens and their values will be visible in the screenshot, provided that we have indicated their position and values in the “Live” session panel in the main window of the platform.

*If necessary, you can use the “Magnifier” application available in Windows. It is an image zoom application, which can be useful while mapping a table or testing points of an already created map.

!Before we can use the “Map test” function, we need to start the roulette table for which the map relates. Roulette must be run on the main screen – (if we have more than one) and it must be the same size and position as when creating the map. Therefore, we always create the map in a maximized browser tab or in full screen mode, if one is available.

Now we will describe step by step what activities take place in the “Modus Operandi” module during the “Live” session.

After activating the “Monitoring” module, the synchronization process will start. In the “Synchronization” section you will see an animated progress indicator. In the case of “RNG” roulette, the spin will be released at this point by clicking the “Spin” button. If there is a possibility of empty spins on a given “RNG” table, no chip will be placed in this place, otherwise, before a spin is made on the numerical field of zero, the “A” chip will be placed – supporting the game. In the case of the “Live” tables, this is not a problem because there a certain amount of empty spins is always possible. The number of empty spins can be set in the additional settings of the “Modus Operandi” module. Zero means no empty spins can be released.

*Empty spins in the case of “RNG” roulette is when we can use the “Spin” button without placing any bet beforehand. In the case of “Live” roulette it is simply being able to watch the game when we are not placing any bets.

!There may be a situation where the user played roulette before launching the “Rouletronic” platform, betting classic – (manually) chips. In this situation, in the case of “RNG” tables, it may happen that instead of the “Spin” button on the table, the “Repeat / Spin” button will be available due to the last game remembered, therefore after starting the “Monitoring” module on the “RNG” table in which there is the possibility of releasing empty spins, the betting module will place a bet on the “A” token – supporting the game, and then remove it, which eliminates the problem with access to the “Spin” button and the memory of any previous game. Only the “RNG” tables are affected.

In the “Monitoring” section, the following are performed in sequence:

• “1 – Table identification” – here the module checks if the 4 identification points of the table – (specifically their colors) match those mapped.
• “2 – Point identification – (betting)” – here the module waits for the appearance of the betting marker, after which the “AutoMat” module, if it has been launched, will be able to bet chips automatically. Bets will take place after the delay set in clock # 3 in the “AutoMat” section. The interval for this clock is one second so a delay set for example to 5 will give us a five-second delay. If the “AutoMat” module is active, it will jump to the “AutoMat” section where all betting activities will be performed, then the module will return to the “Monitoring” section to continue with the number identification. During the jumps between the “Monitoring” and “AutoMat” sections, red and green arrows will be visible, indicating the active sections of the module. These arrows will be visible from the moment of starting the “AutoMat” module.
• “3 – Point identification – (end of betting)” – in this point, “Monitoring” waits for the color of the betting marker to change, indicating the state of the game, in which it is no longer possible to bet on chips and the next spin will take place soon. After detecting a change, the module goes to the point no. 4 – “Delay”.
• “4 – Delay 1, Delay 2” – this is the moment when there is a delay between the detection of the game state “end of betting” and downloading from all numerical fields their identification points – (specifically their colors), which will then be analyzed for a change to detect the drawn number. Clock no. 1 is responsible for the delay when only the “Monitoring” module is activated, while when both modules: “Monitoring” and “AutoMat” are active, clock no. 2 is responsible for the delay before downloading the colors. Thanks to the use of two timers delaying the collection of points identification, we have more options to set the delay, which may be necessary in some cases. For clocks 1 and 2, the interval is theoretically 10 milliseconds, but since clocks 1 and 2 work in cooperation with a rather time-consuming internal procedure, the actual delay time is slightly longer and depends on the CPU power of the computer. So in order to set the appropriate value for these clocks, you have to look at their indications during the countdown. An example of a video of the correct setting of the clock can be seen in the thread 7.2.1., Where a movie with the course of work of the “Modus Operandi” module was presented on the example of a table with variable format of numeric fields. We wrote about tables with variable format of numeric fields later in this thread and in section 7.2.1 Additional settings.
• “5 – Getting data from numeric fields” – at this point the colors of all numeric fields are collected. The download of colors must take place when all numeric fields are devoid of any shadows, animations after e.g. placing chips etc. that is, when they have their natural colors. The moment of download can be precisely set with the clocks described above.
  

!There are two variants of retrieving identification points that enable identification of numbers.
Standard – points are deducted when the game enters the “end of betting” – (betting marker changes its color to a different color than the one we indicated when mapping the table), spin starts, delay timer # 1 or # 2 delays download identification points – (the countdown starts immediately after the color of the betting marker changes), then data is collected from the numeric fields
Quick download of data from numeric fields – in this case, the module does not wait to download identification points to start the spin, but they are downloaded after counting the delay by clock 1 or 2 before starting a new game, i.e. during the game state “betting” – (if the “attack” of the main chart is active and the “AutoMat” module has been triggered, then after the bet or after the support bet, if any), before the betting marker disappears. This option is useful in the case of tables that change their graphic format during the game, e.g. numerical fields get smaller or disappear from the screen at all. In this case, identification points must be retrieved from numeric fields before they are no longer visible or change their format. This option is available in the additional settings of the “Modus Operandi” module and it supplements the option: “* Variable format of numerical fields *” also available in additional settings. Both options are described in detail in thread 7.2.1. Additional settings.

• “6 – Number identification” – during this procedure, the “Monitoring” module analyzes all identification points in terms of changing their colors. If the colors of two identification points change on one of the 37 numeric fields, it will mean the correct identification of the drawn number. If the module detects more than one number, a window will appear with a graph showing which numbers have been detected. Knowing which numbers are detected in error will help us understand when we went wrong.

*Correctly identified numbers will start to be added to the session after starting and after the synchronization process of the “AutoMat” betting module. As mentioned earlier, the synchronization process of this module only applies to “Live” tables. In the case of “RNG” tables, the betting module does not need synchronization, so correctly identified numbers will start to be added to the session from the first correctly identified number if the “AutoMat” module has been started before.

!If our map with the parameters in the “Modus Operandi” module has been working flawlessly so far and at some point it stops working properly or the graphic interface of the roulette table stops communicating with the “Monitoring” module at all, it will mean that the casino has changed the table’s graphic interface a bit. These are mostly changes that cannot be seen with the naked eye. In this case, you will have to map the roulette table one more time. Such changes may occur in some casinos even several times a year.

In the “AutoMat” section, the following are performed in sequence:

• “7 – Delay” – here there is a delay in seconds, which occurs after the random number is recognized and the state of the game is identified by the “Monitoring” module. Thanks to this delay timer, we have time for all kinds of actions related to game control in the windows of numbers, groups, series and on the main interface of the platform. After the clock counts down the set value, all functions related to the attack of numbers, groups, series and the main chart for the spin time will be blocked and if the main chart has been previously attacked, numbers will be bet by the “AutoMat” module.
  

*As timer number 3 is counting down, you will hear beeps to warn you that the time for user response will soon run out. When the delay is set to more than two seconds, we will hear four warning sounds at the end of the countdown – three countdown and one finish, which are different, otherwise we will hear one finish sound. After hearing the ending sound, you can no longer use the mouse, because the “AutoMat” module takes control of the cursor. Whether the countdown sounds will be audible or not can be set in the main platform settings window. However, we recommend that you leave this option active.

• “8 – Betting” – this is where the betting procedure is performed, in which the “AutoMat” module places bets, removes or adds chips to the roulette table according to the current state of our strategy.

• The cursor will be moved when the “AutoMat” betting module is finished.

• If the mouse cursor is left somewhere in the numeric fields section after the module is finished, the cursor will be moved to one of two places:
  1 – if we have not set the return point of the cursor on the “Live” session panel in the main platform window and this function is inactive, the cursor will be moved to the center of the “A” token.
  2 – If, however, the cursor return position has been previously set and this function is active, the cursor will appear in the previously indicated position.

• If the mouse cursor remains on any of the buttons after the module is finished, the cursor will be moved only when the return function on the session panel “Live” is active.

*Moving the cursor after betting or any other activity related to the operation of the “AutoMat” module may be necessary for some tables. For example: the module has bet on the numbers 3,4 and 5 on the “Live” table (ie it did not have to click the “Spin” button) and stayed on the numeric field of the last bet number. With many tables you will notice that when the mouse cursor is somewhere in the betting area section, the entire section becomes active and changes its colors, for example. In order to get the colors of identification points correctly, you need to move the mouse cursor to some neutral place and thanks to this function we have such a possibility. The standard cursor escape point is the center of the “A” token, but as we wrote a moment ago, we can indicate the cursor escape point ourselves.

• “9 – Spin” – if we play the “RNG” roulette, then the “AutoMat” module will click the “Spin” or “Repeat / Spin” button to start another game. In the case of “Live” tables, this procedure will be skipped and the description color will be red.

• “10 – Synchronization betting – (only RNG)” – we wrote earlier that if in the case of the “RNG” tables it is not possible to release empty spins, in order for the synchronization to occur, the “AutoMat” module will have to place the “ A ”- supporting the game. This is where this procedure will be performed if these conditions are met. Otherwise, this procedure will be skipped and its description will be red.

Let’s see in the video above how the workflow in the module “Modus Operandi” looks like.

*In the above video, we are dealing with a standard technique of collecting identification points, because the table does not change its format during the spin. An example of a video showing the technique of quick retrieval of identification points in combination with the “variable format of number fields” option on a table where the format of number fields is variable can be seen in thread 7.2.1. Additional settings.

Copyright © 2023 aDifferentView — Powered by