"1:35 max 200" chip flies off in Betvoyager

When the robot places a bet on the field, a black rectangle "1:35 max 200" appears near the cursor. I still don't understand whether it is there or not. Sometimes it is late. When the robot places a chip and hits this rectangle, the chip at the bottom goes out and then the robot clicks blanks for the entire bet. After the spin, the robot thinks that everything was standing, but in fact it was not. Confusion with wins and losses begins. In the end, the robot earned me even more than it wrote. But I was lucky, it could have been the other way around.

Thanks for the detailed description. After the redesign, BetVoyager changed the tooltip objects and now it has become a problem. Pauses in the arrangement will greatly delay the game in time. We will look for a rational solution.

The situation is 1 in 1 as mine. Another request - can you make the recognition of the dropped number not on the board, but where the data on the current spin goes? Like in the file - the number 7 is much larger in this yellow block, which contains the info on the last spin.

The issue has been resolved - now the bot can wait for casino tips to close betting numbers. It should be said that the task turned out to be non-trivial, since tooltips have a number of features: they are there, then they are not, they can appear with a delay, they can blink, etc. Strange programmers work at the Betvoyager casino :blink: A new version of the bot has been released! * * * Download a fresh archive. It is enough to replace the *.EXE file, all the old settings are suitable.

Sumiala left a note on the Admin wall

We haven't gotten rid of the error completely. In many cases, the bot correctly solves the 35:1 problem, but there are setups when it still clicks on the black rectangle and the chip flies off. It's good that before a new move, it turns on the chip itself. This minimizes discrepancies.

I haven't looked at the bot yet. Maybe enable the feature when placing each new number? Will that not solve the problem? And speed up the cursor movement so that the overall placement time doesn't drop.