9Bot — Quick Start Guide

← Installation Guide

Set Up Your Emulator

Before launching 9Bot, your emulator needs two settings:

☐

Screen resolution — set to 1080 x 1920 (portrait)

BlueStacks: Settings → Display → Resolution → Custom
MuMu: Settings → Display → 1080x1920

☐

ADB enabled — allows 9Bot to control the emulator

BlueStacks: Settings → Advanced → Enable Android Debug Bridge
MuMu: Verify ADB is enabled in your installed version

Launch 9Bot

Double-click run.bat (Windows) or run.command (Mac) in the 9Bot folder.

First launch needs internet access for setup. Later launches may install updates or changed dependencies. Keep settings.json, .license_key and .9bot-state when updating.

Open the Game

In your emulator, open the game and wait until you're on the map screen (the main world view where you can see your castle).

Start Auto Quest and visual farming from the map screen. Do not manually tap the game while a routine is controlling it.

Place Your Markers In-Game

Before turning on Auto Quest, place personal markers on the world map so the bot knows where to go. Open the target menu in-game and set these up:

Friend Marker — place on the friendly tower you want to reinforce for tower/fortress alliance quests.

Open the target menu → Friend tab → set marker on your chosen tower.

Target Marker — place on an enemy tower for PVP quests. Also used by Pass Battle — place one on the open pass to defend or rally for.

Open the target menu → Enemy tab → set marker on the enemy tower or pass.

Tower/PVP quests need the corresponding valid marker. Keep one Friend marker and one Enemy/Target marker for these flows; duplicate or wrong-team markers can block them. Recheck targets when the map changes. Tower Quest is off by default; enable it in device Settings if wanted.

Turn On Auto Quest

In Broken Lands mode, find the Controls section under your device and enable Auto Quest. Check its help and spending settings first. It attempts the applicable alliance quest flows:

⚔

Titan & Evil Guard rallies — starts or joins eligible rallies; AP restoration follows saved settings

⛭

Tower / Fortress quests — reinforces a friendly tower using your Friend marker

⚔

PVP attack — sends a troop to the enemy tower on your Target marker

⚖

Gold gathering — sends troops to gather gold when nothing higher-priority is available

Quest checks depend on available troops and pending work; while troops are deployed, the periodic check is five minutes. Confirm actual quest credit in the game. Reserve the first 50 rewarded joins for Raging Crabs; avoid bot-generated Titan/other joins until that allowance is exhausted.

Other Modes

Controls depend on mode and feature access. Experimental options require Show experimental features; some also need the device protocol connection:

Mine Mithril

Runs the configured mining and recall timer; check troop and interval settings

Pass Battle

Protocol-dependent. Uses one Target marker (Enemy tab) on an open pass: defends it while your team holds it and joins war rallies while the enemy does. Sends troops by default; turn on Preview in device Settings to check first.

Occupy Towers

Experimental Broken Lands territory flow; configure the intended team and targets

Reinforce Throne

Experimental recurring reinforcement; requires the intended throne and setup

Start one useful workflow and verify its outcome before adding modes. Keep native Auto-Rally on with its existing filters. New Fishman/Secret Quest/own-crab controls have separate limits in the supplied README and release notes.

Control from Your Phone

Enable Remote Access in Settings and restart if changed. When the access strip shows a connected relay, use Copy or QR to open that relay link on your phone.

The bot computer must stay awake and connected. The owner dashboard is loopback-only at 127.0.0.1:8080; a Local/LAN link does not work directly from your phone, even on the same Wi-Fi.

To grant someone access to one hosted device, use Share and choose Full Control or View Only. Share only the intended device link; it grants access subject to owner permissions, not owner-only controls.

Good to Know

💡

Stop All signals tasks to stop. An input already in flight or march already sent may finish; keep uncertain results and saved state instead of blindly retrying.

💡

Settings page lets you customize intervals, AP restoration, team color, and more.

💡

Live View button on each device card shows what your emulator screen looks like right now.

💡

Status colors tell you what's happening: cyan = working, amber = waiting, red = stopping, gray = idle.