What is an Evony bot? How automation works in Evony: The King's Return
An Evony bot is a program that plays the repetitive parts of Evony: The King's Return for you on an Android emulator. Here is what it does, how it works and what to expect.
An Evony bot is a program that plays the repetitive parts of Evony: The King's Return for you. It runs the game inside an Android emulator on a PC or Mac, looks at the screen the way you would, and taps the same buttons you would tap: join rallies, send gathering marches, open chests, feed the dragon, set bosses, collect the daily rewards. You decide what it should do and when; the bot does the clicking around the clock.
In short: an Evony bot is screen automation. It does not change the game, it does not talk to the game servers directly, and it does not give you anything the game would not give a player who sat there and tapped all day. It gives you that player's time back.
What an Evony bot actually does
Evony rewards presence. Rallies fill in minutes, resource tiles sit on the map until someone gathers them, bosses spawn on a schedule, and most daily tasks are a loop of "open menu, tap, confirm, close". A bot works through that loop on a schedule you set. The common jobs are:
- Rally joining. Watching the alliance rally list and sending a march to the rallies you want, with the generals and troop mix you chose.
- Farming. Finding resource tiles of the right level near your keep, sending gathering marches, and sending them again when they come home.
- Boss setting. Starting rallies on boss monsters yourself (an "auto setter"), or soloing the bosses your marches can handle.
- Daily upkeep. Chests, gifts, the tavern, the Black Market, the Wheel of Fortune, dragon feeding, materials, and the event buildings that open for a few days at a time.
- Keeping the game alive. Restarting the game when it freezes, dismissing pop-ups, and handling the "your account signed in elsewhere" screens.
How the bot sees the game
A modern Evony bot does not read the game's memory. It takes screenshots of the emulator many times a second and finds buttons, icons and numbers in those images with computer vision: template matching for known icons, and optical character recognition (OCR) for text and numbers such as march times, troop counts and stamina. When it recognises the state of the screen it decides what to tap next. That is why the game version, the emulator resolution and the graphics quality all matter: the bot has to be trained on what the screen looks like. How computer vision and OCR run a modern bot goes deeper.
What you need to run one
- A PC or a Mac. The Emulator Automation Tool runs on Windows and on Apple Silicon Macs; ESB-TKR runs on Windows.
- An Android emulator. BlueStacks and MuMu Player are the ones we support and document. The bot controls the emulator window and runs the game inside it. The setup guide walks through it.
- One emulator instance per account. Farm accounts each get their own instance; the bot can run several at once, and even rotate a larger set of accounts through a smaller number of emulators on a schedule.
- An account with the bot. The apps share one account and one subscription; a trial starts the moment you create the account.
What to expect, honestly
A bot will not win Server versus Server on its own and it will not make a weak keep strong overnight. What it does is remove the hours of tapping that keep most players from ever enjoying the strategic side of the game: your gathering never stops, your rallies get joined while you sleep, your dailies are done when you log in. Players who run bots describe the difference as "I log in to make decisions, not to tap".
There are also real risks. Automation is against the game's terms of service, like it is in every mobile strategy game, and the game does ban accounts it believes are automated. The sensible rules are the same everywhere: one account per emulator, hours that look like a person, no shared accounts, and no bots that talk to the game servers directly. Our checklist for choosing a bot covers what separates careful tools from reckless ones.
Frequently asked questions
Is an Evony bot the same as a map scanner bot?
No. A map scanner or alliance scanner is usually a Discord bot that reports enemy keeps and monster spawns to your alliance chat; it does not play the game. An Evony bot plays the game inside an emulator: it joins rallies, gathers resources, sets bosses and does the daily tasks for you.
Does an Evony bot need my game password?
No. The bot taps inside an emulator where you signed in to the game yourself, the same way you would on a phone. The bot account at emulatorautomation.com is separate from your game account and is only used to sign in to the bot app.
Can I run more than one Evony account?
Yes. Each account runs in its own emulator instance and the bot handles several instances at once. How many you can run depends on your subscription's device count and on how much memory and CPU your PC has; a typical gaming PC runs a handful of emulators comfortably.
Does the bot work on a Mac?
The Emulator Automation Tool has a macOS version for Apple Silicon Macs. It is newer than the Windows version and some features are still being finished, so Windows remains the reference platform.
How is an Evony bot different from an auto clicker?
An auto clicker repeats fixed taps at fixed positions and breaks the moment a pop-up appears. An Evony bot reads the screen first, so it knows whether the rally list is open, whether a march is home, or whether a pop-up is in the way, and it acts on what it sees.