jazzmoon/btd6_autoplay

A Bloons TD6 farming script that allows the dynamic loading of various maps. Be warned, Ninja Kiwi doesn't support farming scripts and reserves the right to ban accounts that use them.

btd6_autoplay's Issues

Error try exec run.bat

Pyautogui issues - Fixed in latest release

After a long hour of debugging why tesseract wouldn't work (was my fault, luckily) everything seemed to work. Opening the run.bat shows a happy console and allows me to type in "darkcastle" and "easy". After that, it appears to be trying to start - yet all it does is crash as soon as I open the heroes selection menu in-game. If I do nothing, the program also does nothing, and once I select the hero selection menu, it shows me this:

Anything I probably did wrong?

requirements and python version

1. Add a requirements.txt for #dependencies
2. Update readme with python 3.8 because of assignment expression:

while (key := input('Press 1 for startUp, and 2 for darkCastle\n------------------\n>>>')):

rework

Hello there,

I have made a ton of changes to the behaviour and functionality of the bot. I have made a privately forked repository to do so, and had an extra tester to ensure everything worked as expected.

Just now I have made the repository public, including allowing contributions. This seems kind of unfair, so I think it would be nice if I could push my changes to this branch (perhaps have a look at it together) and see if these are changes you would want in the bot.

https://github.com/remyvanlis/btd6-bot

If you don't want me to keep this repository public, please respond to this issue. I absolutely respect your wishes if you'd rather have it remain private.

Improvement suggestion for delays

Hi guys,

Good job guys on the improvements, appreciate the new modular and extensible architecture! I have a small suggestion for the tower placement and upgrades delays. Determining how many seconds we need to wait is rather tedious for someone to check. Additionally, if I check the moveToRest function, time wait is not accurate because click and press actions are performed every "second" too. Instead, I would add a functionality for round and specific current tower upgrade detection. For example, when doing dart.upgrade('/', 2) , you would wait indefinitely inside a loop until the upgrade is available (which can be easily differentiated with the green and grey background). As for tower placement, I'd wait until a particular round is reached to place it.

The advantage of proceeding this way is a user only needs to add rounds for placement/upgrades in settings.json. This makes it much more user friendly.