FEH GHB adb guide

==== INSTALLATION ====
Download platform-tools from https://developer.android.com/studio/releases/platform-tools and extract it somewhere
Go to phone settings > about phone > build number
Tap build number repeatedly until developer options are enabled
Go to phone settings > developer options (turn on) > USB debugging (turn on)
Connect phone to computer through USB
Install phone drivers on computer if necessary - some do it automatically, others need you to find it yourself. Try searching for your phone's manufacturer.

==== VERIFY ====
Open a cmd prompt
Navigate to your platform-tools folder by using the 'cd' command (ex. cd desktop/platform-tools)
Run 'adb devices' (type it into the cmd prompt and press enter) to confirm that your phone is recognized (some ID should show up under the list of devices)
If your device is not recognized, make sure you have appropriate drivers installed. If you do, try turning developer options and/or USB debugging off and on. Another thing to try is to change your "Use USB for" settings (swap around between Charging, File and Photo transfers, and MIDI).

==== IN GAME SETTINGS ====
"Auto-Battle Button" - "All Locations" or "In Button Bar"
"Auto: No Animation" - "On"
"Starting a Map" - "Go into Battle" - If you really want to keep "Swap Spaces", then add in an extra tap/wait command before the tap for the auto battle button (after line 16 in the template). This will slow down your macro.

==== BAT SCRIPT ====
On your phone, in developer options, you can enable "Pointer location" to find exact x/y coordinates you want to tap.
Create a text file inside the platform-tools folder and open it with a text editor
Follow the template from https://pastebin.com/Y9V6xsFC to create your own script (ie. just copy/paste it into your text file)
Rename your text file's file extension to .bat - you can still edit it afterwards, but you'll need to right click and "open with" a text editor

rem // This is a comment
"adb shell input tap x y" will tap at position x y
"timeout /t x" will delay the next command for x seconds
":loop
	...commands...
	goto :loop" will make an infinite loop

==== RUNNING IT ====
Double click the .bat in your platform-tools folder while keeping your phone connected to your computer with USB debugging enabled. You may need to re-enable USB debugging each time you reconnect your phone. The cmd prompt that shows up must be left open to keep the script running. Close it to stop the macro.

==== APPENDIX ====
If the macro breaks out of the loop and goes to the shop screen when you leave it on overnight, it is most likely due to you having inconsistent load times. There are two load times in total - one after tapping the Fight! button (to load into the battle) and one after tapping anywhere for the Stage Clear! screen (to load the GHB menu). To be specific in terms of the template, they are the two delays of 5 seconds each (timeout /t 5 /nobreak) on lines 10 and 25. To make the macro more consistent, increase these delay times.

In the provided template, I have tried to position the tap coordinates for the macro to be as "safe" as possible, even when the loop breaks.
When tapping the auto battle button, the coordinates must align with the shop button (if you are not in a battle). This is absolutely unavoidable, and your macro may take you to the shop screen if the loop breaks.
Therefore, all other tap coordinates in the entire loop were set to tap in "safe" spots on the shop screen -  ones that will avoid buying or spending orbs.
However, I have not found a way to avoid tapping the restore dueling swords button. It is impossible to tap in between two buttons on the shop screen (between restore dueling swords and expand barracks), so the macro may waste a single dueling crest if your swords are empty. A simple solution to this is to only do only two arena battles per day, since you only need two for the daily quest anyways. If your swords are not completely empty, it will not let you spend any crests.