search

linus-jansson / btd6farmer

A tool to make autonomous macros in Bloons Td 6. Relies on OCR and template matchmating for navigation. Made in python
https://discord.gg/qyKT6bzqZQ
MIT License
32 stars 11 forks source link

Bot skips instructions causing the bot to fail #23

Closed jason00-r closed 2 years ago

jason00-r commented 2 years ago

the bot lost at round 78 and is not handling the defeat screen. options for home, restart, review map, and continue. and the cmd window just prints the following while it clicks around missing any actual buttons:

selecting map
Game start
selecting map
Game start
selecting map
Game start
selecting map
Game start

map review: image

defeat screen: image

linus-jansson commented 2 years ago

Should be fixed now, realized that I never added a button for the defeat screen. So it just handled it as a victory and thought it went to back to the main menu..

Were there any reason that you got defeated?

jason00-r commented 2 years ago

Should be fixed now, realized that I never added a button for the defeat screen. So it just handled it as a victory and thought it went to back to the main menu..

Were there any reason that you got defeated?

I'm not sure why I lost that game. I didn't look too closely at the towers before I went home. If it happens again I will note tower upgrades to see if something was not done correctly.

jason00-r commented 2 years ago

Should be fixed now, realized that I never added a button for the defeat screen. So it just handled it as a victory and thought it went to back to the main menu..

Were there any reason that you got defeated?

just lost on round 52 this time... here are the tower levels:

dart monkey 0-0-2 and 0-0-0 monkey village 0-0-1 and 0-0-2 super monkey 0-0-0 obyn level 10, almost 11 alchemist 3-0-0 both monkey subs 2-0-3

screenshot of placed towers and the bloons that made it by shown on the defeat screen:

image image

I didn't use the newest commit that fixed clicking off the defeat screen since I wanted to be able to look at the towers if I lost again.

linus-jansson commented 2 years ago

It seems like its skippping instructions, mentioned in #21

The problem I have with debugging this is that I cannot reproduce it.. Could still be a possibility that its tesseract that is having issues with retrieving the current round..

Have you played multiple matches before this happens or is this after the first try? If its your first match that you are loosing on, could you please check if rounds 14, 21 and 22 anything happens & also 45, 46, 47 and 49 which should upgrade the super monkey..

In #21 aranthel09 mentions that the bot opens the menu but doesn't upgrade.. Could you check if you get the same behaviour?

EDIT: If you are unsure about when the bot is loosing, you can run the bot with the --debug flag by either putting it in the Run.bat file or as an argument when running from the CMD. It will generate a statsfile that tells you how many matches the bot has lost and won.

Also if you could try if this problem persists in the latest release

jason00-r commented 2 years ago

It seems like its skippping instructions, mentioned in #21

The problem I have with debugging this is that I cannot reproduce it.. Could still be a possibility that its tesseract that is having issues with retrieving the current round..

Have you played multiple matches before this happens or is this after the first try? If its your first match that you are loosing on, could you please check if rounds 14, 21 and 22 anything happens & also 45, 46, 47 and 49 which should upgrade the super monkey..

In #21 aranthel09 mentions that the bot opens the menu but doesn't upgrade.. Could you check if you get the same behaviour?

EDIT: If you are unsure about when the bot is loosing, you can run the bot with the --debug flag by either putting it in the Run.bat file or as an argument when running from the CMD. It will generate a statsfile that tells you how many matches the bot has lost and won.

Also if you could try if this problem persists in the latest release

For me this behavior happens after many many rounds, like if I leave the bot unattended for 4+ hours, and even then it seems random when/if it will happen.

I will try the latest release and run with the debug flag to see if this still happens.

linus-jansson commented 2 years ago

For me this behavior happens after many many rounds, like if I leave the bot unattended for 4+ hours, and even then it seems random when/if it will happen.

I will try the latest release and run with the debug flag to see if this still happens.

Will try to get to the bottom of this with #25

linus-jansson commented 2 years ago

I will close this because the main issue is fixed and the other mentioned issue is in #21