Evony bot setup on BlueStacks and MuMu Player, step by step

Running an Evony bot on a PC takes four things: an Android emulator, the game installed inside it, the bot app, and one emulator instance per game account. This guide covers BlueStacks and MuMu Player on Windows, which are the two emulators our apps support and document. Budget about twenty minutes for the first account; every account after that is a copy of the first.

Before you start

• A Windows PC with a few gigabytes of free memory per emulator you plan to run. A laptop runs one or two instances; a desktop with 32 GB runs a serious farm. Mac users: the Emulator Automation Tool has an Apple Silicon build, see the download page.
• Virtualisation enabled in the BIOS (Intel VT-x or AMD-V). Both emulators warn you when it is off; the fix is a reboot into the BIOS and one toggle.
• A bot account. Create one with your email or Google; the trial starts straight away.

Step 1: install the emulator

Install BlueStacks or MuMu Player from the vendor's site. Open the multi-instance manager (BlueStacks calls it Multi-Instance Manager, MuMu calls it MuMu Multi-Launcher) and create your first instance. Follow the exact instance settings from the Documentation: the bot is trained on a specific resolution and graphics mode, and a different one makes buttons land in the wrong place.

Two settings matter more than any other:

1. Resolution and DPI must match the documented profile, because the bot finds buttons by what they look like at that size.
2. Graphics mode. Keep the documented renderer. Low-spec machines sometimes render the game softer, which is handled, but switching renderers mid-week is not.

Step 2: install the game and sign in

Inside the instance, install Evony: The King's Return from the Play Store, sign in to your game account, and turn off automatic app updates in the Play Store settings. That last step is the one most people skip: an automatic game update at 3 am changes buttons the bot has not seen yet, and your night of gathering turns into a night of nothing. The Documentation has a page on disabling Play Store auto-updates for each emulator.

Let the game finish its first load, dismiss the pop-ups, and leave it on the city screen.

Step 3: install and connect the bot

Download the Emulator Automation Tool (the current interface) or ESB-TKR (the original interface) from the download page and sign in with your bot account, by username or email and password, or with Google. The app lists the emulator instances it can see; pick yours and assign a profile to it. A profile is the set of rules for that account: which tasks run, which generals and troops to send, how often to check.

If the instance does not show up, the usual reasons are that the emulator's ADB (the debug bridge the bot talks to) is off in the emulator settings, or a second emulator brand is installed and holding the port. The Documentation covers both.

Step 4: run the first tasks

Start with the low-risk tasks and watch them for a few minutes:

• Gathering with one or two marches, so you can see tiles get picked and marches come home.
• Daily chests and gifts, which show you that the bot opens menus and closes pop-ups correctly.
• Rally joining once you trust the march rules, because a wrong troop mix sends real troops to a real fight.

Then add the rest: boss setting, the tavern, the Black Market, dragon feeding, the Wheel of Fortune, daily materials, and the event buildings when they are open. Each task has its own page in the Documentation with the settings explained.

Step 5: add more accounts

Clone the first instance in the multi-instance manager, sign in to the next game account, and give it its own profile in the bot. Keep one account per instance. If you have more accounts than your PC can run at once, use emulator rotation: the bot runs a chosen number of instances at a time and rotates through the full list on a schedule, so every account gets its turn without twenty windows open.

Keeping it running

• Watch it from your phone with the Monitoring Package: every device from any browser, start and stop, uptime and restart counts.
• When the game updates, check Discord before you panic. Fixes are announced there, and you can keep running the previous game version until the new one is handled.
• Give the PC a restart now and then. Emulators leak memory over long runs; the bot restarts the game and the emulator when it detects trouble, but a weekly reboot keeps everything sharp.

Frequently asked questions

Does an Evony bot work with BlueStacks 5?

Yes. BlueStacks 5 is one of the two emulators our apps support. Create one instance per game account in the Multi-Instance Manager and use the resolution and graphics settings from the Documentation so the bot sees the screen it was trained on.

Is MuMu Player better than BlueStacks for bots?

Both work. MuMu Player tends to use less memory per instance, which matters when you run many accounts; BlueStacks has the longest track record and the most community help. Pick the one that runs the game smoothly on your PC and keep its settings as documented.

How many emulators can one PC run?

It depends on memory and CPU. Count on a few gigabytes of RAM per instance. A gaming desktop with 32 GB runs a handful of instances with headroom; with emulator rotation the bot can serve more accounts than that by running them in turns.

Why do I need to turn off Play Store auto-updates?

Because a game update changes buttons and screens the bot recognises. If the game updates itself overnight, the bot stops until a bot update ships. Updating by hand, after checking Discord, keeps you in control of the timing.

Can I use my phone instead of an emulator?

Our apps drive Android emulators on a PC or Mac, not phones. The emulator gives the bot a stable screen size, a debug bridge to send taps through, and the ability to run several accounts side by side.