Performs poorly with Steam version at least

[BullyWiiPlaza]

I'm using this bot using the Steam version and on Windows 10 but the bot barely does anything. It keep checking things which are not on the screen and it is idle for the most part. Sometimes the bot clicks on something like the event details but overall not much happens. The bot didn't even start a duel in over 1 minute of running time either even though NPCs existed which makes the bot pretty pointless.

Am I doing something wrong? Does it need to be configured in some way after the installation or is it just not working well?

Here is the bot log:

2018-05-13 21:25:38 - INFO - bot - APScheduler failed to schedule run, forcing run now
2018-05-13 21:25:38 - DEBUG - bot - Value stop modified
2018-05-13 21:25:38 - DEBUG - bot - Value run_now modified
2018-05-13 21:25:38 - INFO - apscheduler.scheduler - Scheduler started
2018-05-13 21:25:39 - DEBUG - bot - Value next_run_at modified to 2018-05-13 21:25:40.510328
2018-05-13 21:25:39 - INFO - apscheduler.scheduler - Added job "DuelLinkRunTime.in_main" to job store "default"
2018-05-13 21:25:39 - INFO - bot - Next run at 2018-05-13T21:25:40.510328
2018-05-13 21:25:40 - INFO - apscheduler.executors.default - Running job "DuelLinkRunTime.in_main (trigger: date[2018-05-13 21:25:40 CEST], next run at: 2018-05-13 21:25:40 CEST)" (scheduled at 2018-05-13 21:25:40.510328+02:00)
2018-05-13 21:25:40 - INFO - apscheduler.scheduler - Removed job cron_main_at_2018-05-13T21:25:40.510328
2018-05-13 21:25:40 - DEBUG - bot - Value last_run_at modified to 2018-05-13 21:25:40.529551
2018-05-13 21:25:40 - INFO - bot.provider.Steam - Passing Through Start Screen
2018-05-13 21:25:42 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:25:45 - INFO - bot - starting auto play through
2018-05-13 21:25:45 - INFO - bot.provider.Steam - starting auto run through
2018-05-13 21:25:45 - DEBUG - bot.provider.Steam - Run through 1
2018-05-13 21:25:45 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:25:48 - DEBUG - bot.provider.Steam - Tapping at location (1119,455)
2018-05-13 21:25:50 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:25:53 - DEBUG - bot.provider.Steam - Tapping at location (792,652)
2018-05-13 21:25:59 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:26:02 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:26:04 - INFO - bot.provider.Steam - NPC Battle Mode,Points: (792,652) at location: (1), message: failure/Close-Button
2018-05-13 21:26:04 - DEBUG - bot.provider.Steam - Tapping at location (811,840)
2018-05-13 21:26:05 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:26:08 - DEBUG - bot.provider.Steam - LOOK FOR WORD 'OK', HIGH CORRERLATION
2018-05-13 21:26:14 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:26:17 - DEBUG - bot.provider.Steam - Tapping at location (920,768)
2018-05-13 21:26:23 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:26:26 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:26:28 - INFO - bot.provider.Steam - NPC Battle Mode,Points: (920,768) at location: (1), message: failure/Close-Button
2018-05-13 21:26:28 - DEBUG - bot.provider.Steam - Tapping at location (804,823)
2018-05-13 21:26:29 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:26:33 - DEBUG - bot.provider.Steam - LOOK FOR WORD 'OK', HIGH CORRERLATION
2018-05-13 21:26:38 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:26:42 - DEBUG - bot.provider.Steam - Tapping at location (748,796)
2018-05-13 21:26:48 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:26:51 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:26:53 - INFO - bot.provider.Steam - NPC Battle Mode,Points: (748,796) at location: (1), message: failure/Close-Button
2018-05-13 21:26:53 - DEBUG - bot.provider.Steam - Tapping at location (804,823)
2018-05-13 21:26:54 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:26:58 - DEBUG - bot.provider.Steam - LOOK FOR WORD 'OK', HIGH CORRERLATION
2018-05-13 21:27:03 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:27:07 - DEBUG - bot.provider.Steam - Tapping at location (856,796)
2018-05-13 21:27:13 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:27:16 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:27:19 - INFO - bot.provider.Steam - NPC Battle Mode,Points: (856,796) at location: (1), message: failure/Close-Button
2018-05-13 21:27:19 - DEBUG - bot.provider.Steam - Tapping at location (804,823)
2018-05-13 21:27:20 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:27:24 - DEBUG - bot.provider.Steam - LOOK FOR WORD 'OK', HIGH CORRERLATION
2018-05-13 21:27:29 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:27:33 - DEBUG - bot.provider.Steam - Tapping at location (734,732)
2018-05-13 21:27:39 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION
2018-05-13 21:27:43 - DEBUG - bot.provider.Steam - LOOKING FOR CLOSE BUTTON, HIGH CORRERLATION
2018-05-13 21:27:47 - DEBUG - bot.provider.Steam - LOOK FOR WORD 'OK', HIGH CORRERLATION
2018-05-13 21:27:53 - DEBUG - bot.provider.Steam - LOOKING FOR BACK BUTTON, HIGH CORRERLATION

The entire time it did absolutely nothing besides check the event page/missions.

[will7200]

Yes, I am aware that the Steam version does not perform as well as its Nox counterpart. This is due to the algorithm being optimized for Nox's resolution and not Steam. I honestly have not looked at it since I am rewriting the bot into go. Many people have issues with just installation alone. I will get to it once the new version is out.

[BullyWiiPlaza]

@will7200
Unfortunately Nox and all other Android emulators take forever to download the update files for some reason and their performance is poor on PC in general since they emulate. Only Steam works fine since it's a "native" process. Maybe you know how to fix the update downloading issue? It's fine on Steam and a real Android phone but not in emulators. Even after hours, the update seems to fail and I have to re-download it so I can't even use this bot at all right now. :(

Maybe I'll let it download over night while not starting up Duel Links at all to avoid possibly interrupting the download due to concurrently accessing the same account.