Chain Warden · Setup Guide
Chain Warden runs Rise of Kingdoms inside LDPlayer, a free Android emulator for Windows. This guide walks you through installing it, flipping the handful of settings that matter (root and the right resolution), and activating your Aurora license.
Before you start · what you need
Windows 10 or 11. 8 GB RAM is comfortable for one instance; more if you run several.
The free Android emulator the bot controls. We install it in Step 1.
Logged into Rise of Kingdoms at least once, sitting on the world map.
From your subscription — activated by signing in to Chain Warden (Step 4).
LDPlayer is a free Android emulator. Chain Warden runs your Rise of Kingdoms account inside it and controls it from your desktop.
Four settings make Chain Warden able to see and control the game. Get these right and everything else just works. Here they are at a glance, then step by step:
| Root permission | ON |
| ADB debugging | Enable local connection |
| Resolution | 540 × 960 (DPI 240) |
| CPU / RAM | 2 cores / 2048 MB (baseline) |
Open the settings panel: click the ☰ menu at the top-right of the LDPlayer window, then choose Settings.
The ☰ menu (top-right of the emulator) → Settings.
In the Others tab, switch Root permission on and click Enable local connection next to ADB debugging.
Settings → Others. Root permission ON; ADB debugging → Enable local connection.
In the Display tab, choose the Phone layout and select 540 × 960 (DPI 240).
Settings → Display. Phone → 540 × 960 (DPI 240). FPS can stay on Standard (60).
In the Advanced tab, 2 cores / 2048 MB is a solid baseline that runs RoK fine. Give it more for smoother play on a strong PC — or keep it low per instance when running many at once.
Settings → Advanced. 2 cores / 2048 MB baseline.
Inside LDPlayer, install the game and sign into the account you want the bot to run.
Chain Warden is a desktop app that finds your LDPlayer instances and runs the chaining.
Chain Warden deploys through Rise of Kingdoms' own march presets — so build your chaining pairs in‑game first, then just pick them in the app.
You're set. From here it's three clicks.
Chain Warden settings · quick reference
Sensible defaults are set for you. Here's what the main controls do.
The smallest cluster the bot will commit to. Lower it to chain nearby pairs; raise it to hold out for bigger groups.
Break the chain and recall to heal when the march drops to this health, then redeploy.
Automatically sends the same commander pair back out to keep the field full.
The action-point ceiling for the run — recovery items included. 0 means no cap.
Never open AP bottles — chain in bursts with what the account has, then wait for it to refill.
How long the bot runs before recalling everything and stopping.
Troubleshooting
The common snags, and the fix.
Almost always Root permission is off. Open LDPlayer → Settings → Others → turn Root permission ON, Save, and let the instance restart. Also make sure you clicked Enable local connection under ADB debugging.
The instance isn't at the calibrated resolution. Set LDPlayer → Settings → Display → Phone → 540 × 960 (DPI 240), Save, restart.
Make sure the LDPlayer instance is running, ADB local connection is enabled, and you're using LDPlayer 9. Then click SCAN again.
The app is safe but not yet code-signed, so SmartScreen warns on first run. Click More info → Run anyway. It won't ask again.
A license runs on one signed-in PC at a time. Sign out on the other machine (desktop status bar → Sign out), then sign in here.
Usually it's out of AP. Check Max AP / Only use available AP in Settings — with “only available AP” on, it waits for AP to refill to your restart threshold before resuming.
Our Discord is the fastest way to get help — and where your license key is issued.