The bot can detect if a game starts or has just ended, so every 0.5 seconds a screenshot of your OBS window has to be done. The bot will then check this screeshot with image recognition for the status (therefore the bot must always bring the OBS window to the same size). This is an optional feature.
The bot uses small snippets from the OBS window of your game. I call this snippets "Auto-Bet-Trigger". Since the bot should not read the whole window (it would take too much CPU power), you also have to set the OBS scanning area, the Bot helps you with the Auto-Bet-Trigger Editor, but you should understand the way to get best results.
- The OBS window size must not change. Configure and test first the Move OBS Config
- The bot can read the obs window in the background - but you need to enable Windows Aero for this function (only if you also have problems with overlays).
- Do not worry, it's easy;)
- If it does not always work flawlessly, just do several alternative trigger
- But don't use to much alternatives. Each image needs CPU performance.
- You have to make your own trigger. Your game resolution, your addons, interface scaling, and many other factors make 'Auto-Bet-trigger" by other users unfortunately unusable.
Example World of Warcraft
To detect the "Game start, open Bet" moment of a World of Warcraft Arena game or BGs, the bot could use a trigger from the "loading bar" at the top of the arena, like this:
These are the extreme left of the snippet. So the bets can always start.
Upon detection of the end, or whether the game was won or lost, it is unfortunately a bit complicated for WoW Arena. The game (without special Addons) only indicates which team won (green or golden) and in the list is your character name is the appropriate color.
But we can also teach the bot to recognize this. For this we set the Bot to "Auto-Bet-Trigger System: Start/End/Team selection".
The bot needs now four different images. One for Team A / Team B won and one depending on what team you are (since the detection is not 100% accurate, cause of the scaling by OBS, it is also recommended to do a new trigger, if an error has occurred, to add as alternative detection images). This sounds complicated, but once you have the Bot "trained", you can easily just sit back and play. The rest is automatic.
Original OBS Screenshot
To identify which team won, the bot can recognize the font color at the top of the statistics screen (highlighted in yellow above on the original OBS Screenshot).
Team A wins
Team B wins
Additional a trigger from the table for each character has to be made, here my Paladin named "Blackmooredd" (highlighted in blue above on the original OBS Screenshot)
You are in Team A
You are in Team B
- Take a look so you dont have the frame of the table on your trigger.
- I can use the class symbol to prevent false positives.
- In the top of the original OBS Screenshot marked orange you see the overlay of the current betting participants. Pay attention to the correct position, the area the bot is detecting should not be covered! Even your mouse can sometimes be a nuisance.
- If the bot detects the end of the arena, the statistics are also shown. You can set under "Bet configuration" to take a screenshot from one of your screens. This is then displayed directly in the gamehistory. Btw if an inappropriate screenshot was captured, you can delete it in your game history.
Example League of Legends
In LOL, recognizing the Game start, open bet is unfortunately dependent on the card or the loading screen. I have always used the "VS" from the middle of the loading screen. But there are certainly other possibilities. In LOL unlike WoW no team selection is necessary, therefore, set the trigger setting to "Start / End".
Example "Game start, Open Bet" Trigger:
In another map, the background is dark, so you must also produce another trigger:
Luckily, the number of loading screens is manageable ;)
I would recognize the end of a League of Legends game on the statistics screen. So a fitting screenshot with an appropriate value for the viewer can be uploaded directly into your game history.
The Statistics screen depends on your language, but otherwise should always look the same. But caution, by the scale of OBS there could be problems anyway. Watch out and just do a new trigger and add it as an alternative, then it very quickly without errors.
For the victory detection the "Victory" Text from Statistics screen is good:
With defeat, it's actually the same: