- ADB client (connect, tap, swipe, screencap, app control) - Vision module (in-memory screenshot + OpenCV template matching) - Action loader (auto-discovers .py files in actions/) - Engine (screenshot → detect → act loop with YAML playbook) - 12 built-in actions: tap, click, wait, swipe, find, find_and_click, wait_until, click_seq, keyevent, app, log - Example custom action template - Debug screenshot tool for template creation - Detailed plan.md with 20 actions across 9 phases - Sample playbook with 10 steps
28 lines
1.2 KiB
Plaintext
28 lines
1.2 KiB
Plaintext
# Place your reference template PNGs here.
|
|
#
|
|
# Naming convention:
|
|
# main_screen_marker.png — a unique UI element that identifies the main screen
|
|
# collect_btn.png — collect / gather button
|
|
# heal_btn.png — heal troops button
|
|
# train_btn.png — train troops button
|
|
# upgrade_available.png — green upgrade indicator over a building
|
|
# upgrade_btn.png — the "Upgrade" button in the building dialog
|
|
# attack_banner.png — attack warning banner
|
|
# shield_2h.png — 2-hour shield icon
|
|
# confirm_shield.png — confirm shield deployment
|
|
# close_ad.png — close button for ads/popups
|
|
# dialog_close.png — X close button for dialogs
|
|
#
|
|
# How to create templates:
|
|
# 1. Let the bot take a debug screenshot:
|
|
# python -c "
|
|
# from core.adb import AdbClient; from core.vision import Vision
|
|
# a = AdbClient('127.0.0.1', 5555); a.connect()
|
|
# v = Vision(a); v.capture()
|
|
# v.save_debug_screenshot('debug_screen.png')
|
|
# "
|
|
# 2. Crop the relevant button/icon with an image editor
|
|
# 3. Save as PNG in this directory
|
|
# 4. Reference the filename in playbook/default.yaml
|
|
#
|