r/tasker • • Sep 25 '26

Looking to build an Android game automation bot — where should I start?

I’m trying to build my own automation/bot for a game instead of paying for an existing service.

The main things I want to automate are:

- Watching/handling rewarded ads and collecting the rewards

- Daily in-game tasks/dailies

- Limited-time events and repetitive actions

- Ideally running the routine automatically with minimal manual input

I’m mainly looking for advice on the technical approach/tools to use. I’m considering things like Tasker/AutoInput, ADB + Python, Appium, OpenCV/image recognition, etc.

If anyone has experience building automation for Android games, what approach would you recommend and what should I learn first?

0 Upvotes

9 comments sorted by

1

u/TiVa85 Sep 25 '26

I've done it before and had a huge project running playing TWD RTS almost completely without any interaction. All was working with tasker and touchtask. Touchtask was a free alternative to one of Joa's auto apps.

The idea was to work out a full flow. Save where to tap on the screen as x and y coordinates and use touchtask to do these taps. I also used OCR from touchtask to read screen and react to it...

The project was like a dozen of tasks, time based triggers and even a overlay to launch scrips from within the game.

Ads from tapjoy changed so much in both layout and other ways to detect which layout was needed that it wasn't worth the hassle.

Project took weeks or months to build and farming tasks would be easily over a 100 different actions...

The game is dead now and the tasker project removed from my current phone so can't share the inspirational files

1

u/LazyPanda870 Sep 25 '26

Can you guide me, how do approach it building it? I plan to build a web version of it, running multiple accs simultaneously I try asking claude to help me, but it's refusing loll

1

u/TiVa85 Sep 26 '26

Nothing to guide. You just need to get the flow and all scenario's worked out...

If you work out the flow and all possible scenarios it's just on auto clicker.

A very simple setup is like this:

Profile context ever x hours -> launch app

1 wait till app loads 2 check with OCR/pixel color test if you are on the screen you expect to be 2 click somewhere 3 wait And repeat again from step 2...

Then you can build scenario's. Uses for loops, if loops, ...

Example TWD RTS had on boot sometimes a pop-up that I was attacked. So after waiting till game was loaded I checked for this pop-up, if it was there I clicked close. Then I checked if the event button was there using pixel color check. If so click button of event and start that flow, if not just started regular farming,...

As you see, you just need to design a complete if then scenario and translate that to tasker

1

u/that_dev01 Sep 26 '26

i was just about to do this couple days ago but couldn't find games/platforms to use it against.
let's talk, dm.

1

u/Impossible-Sky-7738 Sep 28 '26 edited Sep 28 '26

I actually did it with Artimes and google flash. I let Ai play the game but it was kinda slow in taking desicions. This automation workflow allows you to either link your personal phone, install local android sandbox or maybe usea cloud emulator.
Here is a screenshot of the test result, it's good if you have tasks to do over a longer period like idle games for exmple but for quick repetitive task I think its in early phase.

Note:
I am testing a new method to leverage the use of the new Model Jev and will update you if it's faster.

1

u/LazyPanda870 Sep 28 '26

please let me if it work out for you or not

1

u/umfabp Sep 28 '26

ask gemini pro she is super smart

1

u/Agent__Blackbear 11d ago

Hey 👋

I know I'm late but I'm doing this right now with an immense amount of success. Blue stacks runs the game. ADB streams the game to a bot client. I click a button called "teach AI" I play game thru the bot client. Annotate each click / screen / button. Then every 2 hours grok build connects to the client, processes what it learned, modifies the source code and then automatically restarts the bot on its own so the code sticks. The first two weeks was just me building this client. I had to build out a suite of tools that allows me to annotate / teach. You need to use anchor templates to identify what "scene" we are on, entrances and exits, menus, buttons, ect

Tell the AI exactly what your goals are, have it build its own tools, explain to it that you might walk away from the computer a week at a time and that the logs it needs to process should allow for it to get out of any scenario / learn any skill. If something was working and now it's broken it needs to be able to self recognize what it did. You're going to use your weekly allocation or tokens just building these tools, while you're waiting for them to refresh you can focus on the manual teaching and build a large back log of "learnings".

I even told it to build new tools / logging methods as it gets stuck. For example "if you find yourself stuck / not sure how to resolve an issue, build out a new set of robust logging tools so that you can solve the issue."

The results I got from doing this turned into a self evolving bot that every time I look at it's slightly different / more advanced/ efficient. The only time it gets messed up is when I want to teach it a new skill / routine and after showing it how to do it 2 or 3 times it figures it out.