AdbAutoPlayer

AdbAutoPlayer is a tool that helps you bot Android games. It can do boring or daily tasks for you—like collecting rewards, tapping buttons, or repeating stages—automatically.

It works by using ADB (Android Debug Bridge), which lets your computer control an Android phone, tablet, or emulator.

Important

This tool only works with Android apps. You must use:

• An Android emulator (like MumuPlayer, BlueStacks 5), or
• A real Android phone or tablet

It does not work with:

• iOS devices (iPhone, iPad)
• Official PC or cloud versions of games

Modern & Customizable Interface

AdbAutoPlayer now features a modern, flexible interface designed for better control and visibility:

• Sidebar Navigation: Quickly switch between different profiles and games.
• Live Log Panel: Monitor bot actions in real-time with a dedicated log display.
• Customizable Themes: Personalize the look with a wide range of colors and dark/light modes.
• Flexible View Modes: Choose between Cards, Palette, or Accordion views to organize your tasks.

Check out the UI Guide for more details.

Key Features

• Game Automation: Handles daily quests, farming, and repetitive actions automatically.
• Multi-Game Support: Includes specialized bots for popular mobile games like AFK Journey and Guitar Girl.
• Easy Setup: Designed to be user-friendly and quick to configure with emulators or real devices.
• Cross-Platform: Officially supported on Windows and macOS.

Compatibility

• Tested on:

  • Windows with MumuPlayer and BlueStacks 5
  • Apple M1 Max using BlueStacks Air

Download

Important

Please check the user guides on the left before using the tool.

Contact

AFK Journey

Discord: Yaphalla
Channel: adb-auto-player

UI Guide

AdbAutoPlayer features a highly customizable and intuitive interface. This guide explains the various components and how to personalize your experience.

Main Components

1. Sidebar Navigation

The sidebar allows you to manage multiple profiles. Each profile can have its own settings and active game.

• Toggle Sidebar: Click the menu icon in the top left to expand or collapse the sidebar.
• Add Profile: Use the “+” button at the bottom of the sidebar to create a new profile.

2. Status Bar

Located at the top, the status bar provides quick access to global actions:

• Theme Customizer: Adjust colors and switch between Light/Dark modes.
• App Settings: Configure global application preferences.
• ADB Settings: Quick access to ADB configuration for the active profile.
• Game Settings: Manage settings specific to the currently detected game.
• Docs: Open this wiki!
• Debug: Run debug tasks to troubleshoot detection issues.

Settings Overlays

Clicking any settings button opens an overlay where you can modify configurations.

• ADB Settings: Configure your device connection.
• App Settings: General program settings like theme and language.
• Game Settings: Settings specific to the currently selected game.

ADB Settings

App Settings

Game Settings

3. Log Panel

Monitor the bot’s activity in real-time.

• Toggle Log: Click the terminal icon in the status bar to show or hide the log panel.
• Log Level: Choose how much information you want to see (Info, Debug, Error).

Customizing the Look

Theme Customizer

Click the palette icon in the status bar to open the Theme Customizer.

• Mode: Switch between Light and Dark themes.
• Accent Color: Use the slider to pick your favorite accent color for the UI.

View Modes

You can change how tasks are displayed in the dashboard by selecting a different view mode in the Theme Customizer:

• Cards View: (Default) Large, easy-to-tap cards for each task.
• Palette View: A more compact grid view.
• Accordion View: Group tasks by category in collapsible sections.

Palette View

Accordion View

Emulator Settings

Important

Cloud Emulators like BlueStacks X cannot be used

MuMuPlayer (Windows) ← Best

Note

MuMuPlayer does not require enabling ADB in settings.

Emulator Settings

• Display:
  • Resolution Setting: Select Mobile Mode (1080 × 1920).

BlueStacks 5 (Windows) & BlueStacks Air (MacOS)

Emulator Settings

• Display:
  • Display Resolution: Select Portrait (1080 × 1920).
• Advanced:
  • Android Debug Bridge (ADB): Enable this.

LDPlayer (Windows)

Emulator Settings

• Display:
  • Resolution: Select Phone (1080 × 1920).
• Others:
  • ADB Debugging: Enable Local Connection.

ADB Settings

Device ID: emulator-5554

MuMuPlayer Pro (MacOS)

Warning

I suggest using BlueStacks Air instead because it’s free.

Emulator Settings

• Display → Display Size Phone:
  • Set Device Display to 1080 × 1920.
• Other:
  • Enable ADB: Select Try to use the default port (5555).

Real Phone USB Debugging Setup Guide

A comprehensive guide to enable USB debugging on popular Android phone brands for AdbAutoPlayer.

Tip

On Android 11 or newer you can skip the cable: see Wireless Debugging (Wi-Fi).

Table of Contents

• ADB Settings
• Important Considerations
• Prerequisites
• Universal Steps
• Brand-Specific Instructions
  • Samsung
  • Google Pixel
  • OnePlus
  • Xiaomi/MIUI
  • Huawei/Honor
  • Oppo
  • Vivo
  • Sony
  • LG
  • Motorola
• Troubleshooting

ADB Settings

Device Settings in AdbAutoPlayer

Important Considerations

Warning

Security Notes:

• USB debugging grants full control over your device
• Always use trusted computers and quality USB cables
• Consider disabling USB debugging when not actively using automation
• Some banking and security apps may detect developer mode
• Always revoke USB debugging authorizations from untrusted computers
• Consider security implications before enabling OEM unlocking

Caution

Device Health Notes:

• Avoid using the bot when your device temperature is too high
• High temperatures can cause permanent damage to battery and components

Prerequisites

Before starting, ensure you have:

Universal Steps

These steps apply to ALL Android devices, regardless of brand:

Step 1: Enable Developer Options

1. Open Settings on your Android device
2. Scroll down and tap “About phone” or “About device”
3. Find “Build number” (location varies by brand - see brand-specific sections below)
4. Tap “Build number” 7 times rapidly
   • You’ll see countdown: “You are now X steps away from being a developer”
   • After 7 taps: “You are now a developer!” or “Developer mode has been enabled”
5. Go back to the main Settings menu
6. Look for “Developer options” (usually under System, Additional settings, or directly in Settings)

Step 2: Enable USB Debugging

1. Open “Developer options”
2. Toggle “Developer options” ON (if there’s a master switch at the top and it’s off)
3. Scroll down and find “USB debugging”
4. Toggle “USB debugging” ON
5. Confirm when prompted with “Allow USB debugging?”
6. Check if there are more options that start with USB debugging like “USB debugging (Security settings)” if yes Toggle ON

Step 3: Additional Developer Settings (Optional but Recommended)

While in Developer options, consider enabling these for better automation:

Brand-Specific Instructions

Samsung

Build Number Location:

• Samsung One UI 4.x and Samsung One UI 5.0+:

  Settings → About phone → Software information → Build number
  

• Older Samsung:

  Settings → About device → Build number
  

Additional Samsung Steps:

• After enabling Developer options, you may need to restart your phone
• In Developer options, look for “USB debugging” under the Debugging section
• Samsung devices may show additional security warnings - tap “OK” to proceed
• Some Samsung devices have “Developer options” under Settings → Developer options directly

Knox Security Note:

• Samsung Knox may interfere with automation
• If you encounter issues, try disabling Knox security features (this may void warranty)

Google Pixel

Build Number Location:

• Android 12+:

  Settings → About phone → Build number
  

• Android 8-11:

  Settings → System → About phone → Build number
  

• Android 7 and below:

  Settings → About phone → Build number
  

Additional Pixel Steps:

• “Developer options” appears under Settings → System → Developer options
• Pixel devices typically have the cleanest Android experience with minimal restrictions

OnePlus

Build Number Location:

• OxygenOS 12+:

  Settings → About device → Version → Build number
  

• OxygenOS 11:

  Settings → About phone → Version → Build number
  

• Older OxygenOS:

  Settings → About phone → Build number
  

Additional OnePlus Steps:

• OnePlus devices may require you to restart after enabling Developer options
• “Developer options” appears under Settings → System → Developer options
• Some OnePlus devices have additional security prompts

Xiaomi/MIUI

Build Number Location:

• MIUI 12+:

  Settings → About phone → All specs → Build number
  

• MIUI 11:

  Settings → About phone → MIUI version (tap 7 times instead of build number)
  

• Older MIUI:

  Settings → About phone → MIUI version
  

Optional Xiaomi Steps:

• Disable MIUI Optimizations (for better ADB functionality):
  • In Developer options, find “Turn off MIUI optimization”
  • Toggle it OFF and restart your device

Huawei/Honor

Build Number Location:

• EMUI 10+:

  Settings → About phone → Build number
  

• EMUI 9:

  Settings → System → About phone → Build number
  

• Older EMUI:

  Settings → About phone → Build number
  

Additional Huawei/Honor Steps:

• Huawei devices usually have strict security measures
• After enabling Developer options:
  • “Developer options” appears under Settings → System → Developer options

Oppo

Build Number Location:

• ColorOS 12+:

  Settings → About device → Version → Build number
  

• ColorOS 11:

  Settings → About phone → Version → Build number
  

• Older ColorOS:

  Settings → About phone → Build number
  

Additional Oppo Steps:

• Oppo devices require additional verification steps
• After enabling Developer options:
  • “Developer options” appears under Settings → Additional settings → Developer options
  • Enable “USB debugging”

Oppo-Specific Requirements:

• You may need to be logged into your Oppo account
• Some features require account verification similar to Xiaomi

Vivo

Build Number Location:

• Funtouch OS 12+:

  Settings → About phone → Software version → Build number
  

• Funtouch OS 11:

  Settings → About phone → More parameters → Build number
  

• Older Funtouch:

  Settings → About phone → Build number
  

Additional Vivo Steps:

• Vivo devices have similar restrictions to Oppo
• After enabling Developer options:
  • “Developer options” appears under Settings → System → Developer options

Vivo-Specific Requirements:

• Vivo Account Verification:
  • Login to your Vivo account may be required
  • Some security features require account verification

Sony

Build Number Location:

• Android 10+:

  Settings → About phone → Build number
  

• Android 8-9:

  Settings → System → About phone → Build number
  

• Older Android:

  Settings → About phone → Build number
  

Additional Sony Steps:

• Sony devices typically follow stock Android closely
• “Developer options” appears under Settings → System → Developer options
• Sony devices generally have fewer manufacturer restrictions

LG

Build Number Location:

• LG UX 9+:

  Settings → General → About phone → Software info → Build number
  

• LG UX 8:

  Settings → About phone → Software info → Build number
  

• Older LG UX:

  Settings → About phone → Build number
  

Additional LG Steps:

• LG devices may require restart after enabling Developer options
• “Developer options” appears under Settings → General → Developer options
• Some LG devices have additional security prompts

Motorola

Build Number Location:

• Android 10+:

  Settings → About phone → Build number
  

• Android 8-9:

  Settings → System → About phone → Build number
  

• Older Android:

  Settings → About phone → Build number
  

Additional Motorola Steps:

• Motorola devices typically follow stock Android
• “Developer options” appears under Settings → System → Developer options
• Minimal manufacturer restrictions typically apply

Troubleshooting

Common Issues and Solutions

Advanced Troubleshooting

For Huawei/Honor devices:

• Disable protected apps feature
• Check if HMS Core is interfering

For Oppo/Vivo devices:

• Verify account login status
• Disable aggressive battery optimization
• Check auto-start management settings

Wireless Debugging (Real Phone over Wi-Fi)

Run AdbAutoPlayer on a real Android phone without a USB cable. The phone and the PC talk over your home network using Android’s built-in Wireless debugging.

Table of Contents

• Before You Start
• Step 1: Turn On Wireless Debugging on the Phone
• Step 2: Pair the Phone with AdbAutoPlayer
• Step 3: Check That It Worked
• Step 4: Screen Settings for Real Phones
• Everyday Use
• Troubleshooting

Before You Start

Note

You only need to pair once. After that, turning Wireless debugging on is enough.

Step 1: Turn On Wireless Debugging on the Phone

1. Open Settings on the phone.
2. Open Developer options:
   • Google Pixel / stock Android: Settings → System → Developer options
   • Samsung: Settings → Developer options (at the bottom of the list)
   • Other brands: see where Developer options is for your brand
3. Scroll down to the Debugging section and tap the words “Wireless debugging” (not only the switch).
4. Turn the switch ON.
5. The phone asks “Allow wireless debugging on this network?”
   • Tick “Always allow on this network”
   • Tap Allow

You are now on the Wireless debugging screen. Near the top it shows “IP address & Port”, for example 192.168.1.50:37123. Write this down: it is your Device ID.

Step 2: Pair the Phone with AdbAutoPlayer

2.1 Get the pairing code (on the phone)

1. On the Wireless debugging screen, tap “Pair device with pairing code”.
2. A popup shows:
   • Wi-Fi pairing code: 6 digits, e.g. 482915
   • IP address & Port: e.g. 192.168.1.50:41001

Important

Keep this popup open until pairing is finished. The code and port stop working as soon as the popup closes. Opening it again gives you a new code and port.

Warning

The popup’s IP address & Port is not the same as the one on the main Wireless debugging screen: the IP is the same but the port is different.

• Popup (pairing) → goes in Pairing Address
• Main screen (Step 1) → goes in Device ID

2.2 Enter the details in AdbAutoPlayer (on the PC)

1. Open AdbAutoPlayer and click the ADB Settings button (its tooltip reads ADB Settings).
2. In the Device section:
   • Device ID: the address from the main Wireless debugging screen (Step 1), e.g. 192.168.1.50:37123
3. In the Wireless Debugging section:
   • Enable Wireless Debugging (Android 11+): turn ON
   • Pairing Address (IP:Port): the address from the popup, e.g. 192.168.1.50:41001
   • Pairing Code: the 6 digits from the popup, e.g. 482915
4. Click Save Settings.

Within a few seconds AdbAutoPlayer pairs with the phone and connects to it. You don’t have to start a task for this.

Step 3: Check That It Worked

You should see all of these:

• On the phone: the pairing popup closes by itself, and your PC appears under “Paired devices” on the Wireless debugging screen.

• In the AdbAutoPlayer log:

  Wireless Debugging: paired with 192.168.1.50:41001
  

• In the profile list (left sidebar): your profile shows the phone’s address instead of “no device”.

When it works:

1. Open ADB Settings again.
2. Clear the Pairing Address and Pairing Code fields (leave Enable Wireless Debugging ON).
3. Click Save Settings.

Clearing them stops the app from retrying an old, expired code when the phone is off, which would otherwise fill the log with pairing warnings.

Step 4: Screen Settings for Real Phones

The bot is designed for a 1080x1920 portrait screen. Most phones have a different resolution, so in ADB Settings → Device:

To give the phone its normal resolution back, use the Reset Display Size button shown in ADB Settings.

Warning

Vertical Screen Offset: when taps or text reading are slightly off

On some phones, after Resize Display, the game is drawn a little higher or lower than the bot expects. This is usually caused by the status bar, a notch or the camera cutout. When this happens you will notice that:

• taps land a bit above or below the button they were meant for;
• scans (for example guild or hero scans) miss rows or read the wrong text.

Vertical Screen Offset corrects this. It shifts everything the bot sees and taps by that many pixels:

• positive value (e.g. 40): the game content is lower than expected;
• negative value (e.g. -40): the game content is higher than expected.

Some AFK Journey scans detect this for you. If the log shows a message like “Your device’s display may be misaligned — try setting ADB Settings -> Device -> Vertical Screen Offset to approximately 38”, enter that number and run the scan again.

Otherwise, change it in small steps (10–20 px), save, and test again. Only change it if you see these problems. A wrong offset makes every tap miss. Emulators should always stay at 0.

Everyday Use

• Turn Wireless debugging on each time you want to use the bot. Many phones switch it off after a restart or when you join a different Wi-Fi network. You do not need to pair again.

• The port changes every time Wireless debugging is turned on, so your saved Device ID gets outdated. With Enable Wireless Debugging ON, AdbAutoPlayer finds the new port by itself. The log then shows:

  Wireless Debugging: connected to 192.168.1.50:40211. You can set it as Device ID in the ADB Settings.
  

  Updating the Device ID is optional, but it makes connecting faster.

• The Scan button next to Device ID also finds the phone (with the option ON and saved). It suggests the first device found: if an emulator is running too, it may suggest the emulator instead.

• Keep the phone awake and charging during long runs. Enable “Stay awake” in Developer options, and keep the phone cool (see the Real Phone Guide).

Caution

Anyone on the same network who has been paired can control the phone while Wireless debugging is on. Turn it off when you are not using the bot, and never turn it on over public Wi-Fi. To remove the PC, go to Wireless debugging → Paired devices, tap the PC, and choose Forget.

Troubleshooting

Still stuck? See the general Troubleshooting page, then click Show Debug info in the app and include the log when asking for help.

Windows Setup Guide

Important

Check Emulator Settings if you haven’t already!

Installation

• Downloadthe latest release of AdbAutoPlayer: AdbAutoPlayer_x.y.z_x64_en-US.msi (it will show the actual version instead of x.y.z)
• Run the Installer.

Starting AdbAutoPlayer

When launching AdbAutoPlayer, Windows Defender SmartScreen may block the application. To proceed:

1. Click the More info link.
2. Click the Run anyway button that appears.
3. Wait for the application to start.

Windows Security pop up

If this pop up appears simply click Allow. If you want more info read here: ADB (Android Debug Bridge)

Continue to the Troubleshooting Guide

macOS Setup Guide

Important

Ensure you have reviewed the Emulator Settings before proceeding.

Installation Steps

1. Install Homebrew
   Download and install Homebrew by following the instructions on their official website.

2. Install ADB
   Use Homebrew to install Android Debug Bridge (ADB):

   brew install --cask android-platform-tools
   

3. Install Tesseract
   Used for optical character recognition (OCR):

   brew install tesseract
   

4. Download AdbAutoPlayer

   • Visit the AdbAutoPlayer GitHub releases page to download the latest AdbAutoPlayer_aarch64.app.tar.gz.
   • Extract the .tar.gz file to a folder on your computer.
   • Follow the Instructions in the MACOS_READ_THIS_IMPORTANT.txt you can also find in the releases page AdbAutoPlayer GitHub releases page

Additional Information

• Build Locally (Optional)
  To build the app from source, follow the instructions in the Dev & Build Guide.

Linux Setup Guide

Important

Linux is not officially supported.
None of the maintainers use Linux, and we do not provide Linux builds, troubleshooting, or assistance.

If You Still Want to Try:

1. Build It Yourself

   • You can try following the Dev & Build guide.
   • No support will be provided—you’re on your own.
   • Functionality is not guaranteed, and you may encounter Linux-specific issues.

2. Contribute Proper Support

   • If you’re willing to maintain Linux builds, fix issues, and document setup, contact us.
   • Without an active Linux maintainer, official support will never happen.

We will not answer questions about Linux builds. Check back if community contributions change this in the future.

Troubleshooting

General try disabling Device Stream

If Device Streaming is active try disabling it in ADB Settings if you encounter performance issues.

Emulator

Note

Test both MumuPlayer and BlueStacks 5

This bot only works in Portrait mode

1. Please double-check your Emulator Settings.
2. If the game automatically switches to Landscape on start, use the Rotate Menu and select Portrait.
   

Missing files

This issue usually occurs due to one of the following reasons:

1. Windows Security or another Antivirus software flagged a false positive and deleted/quarantined one or more files. Learn more about false positives.
2. An error occurred during the update process, preventing all files from being properly installed.

Make sure to extract all files and check your antivirus settings to prevent accidental deletions.

File contains a virus or potentially unwanted software

1. Search Windows Security
   
2. Select Virus & threat protection
   
3. Click allowed threats
   
4. Search for a Threat that has AdbAutoPlayer or adb_auto_player in the file name or path then click Actions and Restore
   
5. If you have no Threats click Protection history and check there then do the same as step 4.
   

Tap to restart this app for a better view

Some games will not automatically scale when the resolution changes. You simply have to press the button and the bot will work.

AFK Journey

Support Game Languages:

• English

Supported Resolutions:

• 1080x1920

Bot Features

AdbAutoPlayer provides a comprehensive suite of automation for AFK Journey:

• Daily Routine: Automatically perform all daily tasks in one click.
• Stage Pushing: Push AFK stages with automatic team formation and retries.
• Arena Battles: Automate your daily arena matches.
• Dream Realm: Collect rewards and participate in Dream Realm battles.
• Legend Trial: Progress through the various towers.
• Arcane Labyrinth: Clear the labyrinth levels automatically.

In-Game Recommended Settings

To improve performance and reduce lag, adjust the following in-game settings:

• Set Graphics to Minimum while keeping high-performance Power Mode.
• Disable Battle Texts: Go to Battle > Combat Text > Off. This prevents excessive on-screen text, reducing emulator lag.
• Disable Battle Logs: Under Combat Text, turning off battle logs minimizes post-battle processing and improves overall game performance.

Guitar Girl

Bot Features

AdbAutoPlayer helps you with the tapping in Guitar Girl:

• Auto Tapper: Automatically taps to generate likes.
• Skill Activation: Uses skills as they become available.
• Daily Collection: Collects daily rewards and bonuses.

Supported Resolutions:

• 1080x1920

Blue Protocol Star Resonance

Bot Features

AdbAutoPlayer provides automation for various activities in Blue Protocol Star Resonance:

• Fishing: Automate the fishing minigame to collect resources.
• Simple Gathering: Automatically gather resources from the world.
• Wondrous Tag: Automate the Wondrous Tag activities.
• Devourer: Help with Devourer related tasks.

Supported Resolutions:

• 1080x1920

Dev

1. Install Python
2. Install Rust & Cargo
3. Install Node
4. Install pnpm
5. pnpm install
6. Follow the PyTauri Tutorial

After setup, you should be able to run the GUI via:

pnpm pytauri dev

Setup pre-commit

uv pip install --group dev -e src-tauri
uvx pre-commit install

Check if it’s working:

uvx pre-commit run --all-files

Troubleshooting

If running the development server fails with the error:

No module named adb_auto_player

You can fix it by reinstalling the Tauri package:

uv sync --reinstall-package=tauri-app

Common pre-commit Fixes

TID251 time.time is banned

Use this prompt with an AI to fix it instantly:

Replace any wall-clock-based elapsed-time logic (`time.time()`, `datetime.now()`) with monotonic timing. Keep the same durations but use `time.monotonic()` or `time.perf_counter()` for comparisons. Do not change logging or timestamp code.
```python
#TODO your code snippet
```

TID251 cv2.split is banned

Use this prompt with an AI to fix it instantly:

Replace `cv2.split()` with direct numpy array indexing for better performance. OpenCV uses BGR format, so use `image[:, :, 0]` for blue, `image[:, :, 1]` for green, and `image[:, :, 2]` for red.
```python
#TODO your code snippet
```

Translations Guide

This guide explains how to add new languages, update translations, and maintain the internationalization system for AdbAutoPlayer.

📁 File Structure

frontend/src/lib/i18n/
├── README.md          # This guide
├── i18n.ts           # Translation system core
├── locales.ts        # Language configuration
├── jp.json           # Japanese translations
└── vn.json           # Vietnamese translations

🌐 Currently Supported Languages

• English (en) - Default language
• Japanese (jp) - Partially translated
• Vietnamese (vn) - Partially translated

🚀 Quick Start

Adding a New Language

1. Create translation file: frontend/src/lib/i18n/[language-code].json
2. Update locales.ts: Add language to enum and import
3. Update backend constraint: Add language option to Go backend
4. Test the implementation

Updating Existing Translations

1. Edit the JSON file: Modify translations in existing language files
2. Test in application: Build and verify changes
3. Commit changes: Submit via pull request

📋 Detailed Instructions

1. Adding a New Language

Step 1: Create Translation File

Create a new JSON file: frontend/src/lib/i18n/[language-code].json

{
  "Stop Action": "Your Translation",
  "Language": "Your Translation",
  "Device": "Your Translation",
  "Update": "Your Translation",
  "User Interface": "Your Translation"
}

Step 2: Update Frontend Settings

Edit frontend/src/lib/i18n/locales.ts:

// Add import
import newLang from "./[language-code].json";

// Add to enum
export enum SupportedLocale {
  EN = "en",
  JP = "jp", 
  VN = "vn",
  NEW_LANG = "[language-code]", // Add this line
}

// Add to locales object
const locales: LocaleDictionary = {
  [SupportedLocale.EN]: {},
  [SupportedLocale.JP]: jp,
  [SupportedLocale.VN]: vn,
  [SupportedLocale.NEW_LANG]: newLang, // Add this line
};

Step 3: Update Backend Settings

Edit internal/ipc/constraint.go:

"Language": NewSelectConstraint([]string{
    "en",
    "jp", 
    "vn",
    "[language-code]", // Add your language code
}, "en"),

2. Updating Existing Translations

Edit Translation Files

Open the appropriate JSON file and modify translations:

{
  "Old Key": "Updated Translation",
  "New Key": "New Translation"
}

3. Adding More Translations

Find Untranslated Text

1. Run the application in your target language
2. Look for English text that should be translated
3. Check the source code for text strings used with $t() function

Add Missing Translations

Add new key-value pairs to the JSON file:

{
  "Existing Translation": "Existing Value",
  "New English Text": "New Translated Text"
}

🔍 Finding Text to Translate

Common Locations

Note

Check any of the existing translation files!

• Button labels: Look for buttons still showing English text
• Error messages: Check error dialogs and notifications
• Settings labels: Settings form field names
• Menu categories: Section headers and groupings
• Tooltips: Hover text on buttons and controls

Search in Code

Look for these patterns in the codebase:

// Direct translation calls
$t("Text to translate")

// Template usage
{$t("Text to translate")}

// With interpolation
$t("{{game}} Settings", { game: gameName })

🧪 Testing Your Changes

Verification Checklist

• Language appears in dropdown
• All buttons are translated
• Application builds successfully
• Language switching works smoothly

📝 Example: Complete Translation File (Vietnamese)

{
  "Stop Action": "Dừng Hành Động",
  "Language": "Ngôn Ngữ",
  "Device": "Thiết Bị",
  "Update": "Cập Nhật",
  "User Interface": "Giao Diện Người Dùng",
  "Something went wrong": "Đã xảy ra lỗi"
}

Happy translating! 🌍

Frontend README

Node

Install the latest version here: https://nodejs.org/en/download/

Svelte with SvelteKit and Skeleton

This project is built using Svelte with SvelteKit.
We also use Skeleton, a UI toolkit for Svelte, to help with styling and components.

Setup

Follow Dev & Build

Contributing

Nothing here yet—PRs are welcome.

Writing Bots

Important

Work in Progress.

Check out Dev & Build if you need help with setting up the project in general.

📝 Contribution Opportunities

🔧 Backend Development

Android Multi-Touch Gesture Implementation (PoC)

Library: uiautomator2

Challenge:
ADB lacks native multi-touch gesture support. uiautomator2 offers:

• Coordinate-based tapping (d.click(x, y))
• Screenshot capture (d.screenshot())
• Advanced gestures (swipe, pinch, etc.)

Goals:

• Develop PoC for multi-touch gestures
• Prioritize pinch-to-zoom for game automation

Extended Opportunities:

1. Explore additional uiautomator2 game automation features
2. Performance comparison: uiautomator2 vs standard ADB
3. Benchmark tests for shared functionality (tap, screenshot, swipe)

Desktop Client Support Investigation

Current Understanding:

1. Mouse click simulation limitations (requires actual cursor movement)
2. Screenshot challenges with display scaling/multi-monitor setups
3. Higher detection risk compared to ADB (if Lilith starts to care about botting)

Implementation Needs:

1. Device abstraction layer (Android vs Desktop)
2. Unified input mapping system

   # The actual bot code should not end up looking like this.
   if device.platform == "Android":
   device.press_back_button()
   elif device.platform == "DesktopApp":
   device.keyboard.press("ESC")
   

3. Complete desktop interaction logic

🖥️ Frontend Development

Global Hotkey Settings Component

Create a Svelte Component to edit a single Global Hotkey in the Settings.
You can decide what format it should be stored in, in the Settings too.

📖 Documentation

Emulator Setup Guides

Format: Individual .md files per emulator

Needed Guides:

• MuMu Player
• BlueStacks
• LDPlayer
• MuMu Pro (Mac)
• BlueStacks Air (Mac)

Guide Requirements:

• Default device ID setup
• ADB enabling steps
• Recommended Settings
• Multi-instance device identification

Custom Routine Documentation

Content Needed:

• Feature explanation and workflow
• Practical examples (AFK Journey reference)

🎮 AFK Journey Specific

Arcane Labyrinth Optimization (Difficulty 15+)

Goal: Consistent Floor 16 clears

Suggestions:

• Coordinate with Arcane Lab channel for team comps
• Develop rune/crest priority system

Fishing

This is 80% done only needs logic to navigate to fishing spots.

Feature Documentation

Scope:

• Complete feature catalog
• Usage instructions
• Settings options
• Visual examples

🚧 In Progress

• AFKJ Manual Stage Agent - @valextr

💬 Getting Help

• Discord: Use the badge above
• GitHub: Create issues for bugs/feature requests