What Forge of Empires automation actually covers in 2026, which parts are worth automating, which parts no tool should touch — and the risk that comes with all of it.
FoE automation is software doing the repetitive half of Forge of Empires for you: choosing Guild Battlegrounds targets and swinging at them, grinding Guild Expedition encounters, collecting finished production, feeding Forge Points into Great Buildings. The game is played through a browser, so most of it is done by browser extensions.
It is worth being precise about one distinction, because a lot of search results blur it. A helper is not a bot. FoE Helper — easily the best known tool in this game — shows you information and leaves every click to you. Forge of Empires automation performs the action instead of you. The rules treat those two very differently, and so does the risk.
The honest test for any Forge of Empires automation is whether the task is repetitive rather than interesting. Four things pass it:
Hundreds of near-identical fights a season, where the only real decisions are which province and when. Attrition-aware targeting, waiting on a locked sector and striking the moment it opens, topping the army back up between fights.
Encounter after encounter, wave by wave, collecting the chests and relics along the way. Attacks only — see below for why negotiation is left out.
Collecting what has finished and starting it again. No judgement involved, and it has to happen on the game's clock rather than yours — which is exactly what software is for.
Watching contribution levels and placing Forge Points at the moment a place is worth taking. The watching is tedious; the timing matters.
Not everything repetitive is worth handing over, and a tool that automates everything is usually telling you it has not thought about any of it.
There are two broad approaches, and the difference matters more than any feature list.
Forging requests from outside the game. A script talks to the game's servers directly, without the game running. It is the more powerful approach and the more fragile one: every request has to be reconstructed correctly, and the moment the protocol shifts it breaks, or worse, sends something no real client would send.
Driving the game's own client. The automation runs inside the page with the real game loaded, and asks the game's own code to do the work. There is less control over the exact shape of a request, and the upside is that there is nothing to reconstruct and nothing that distinguishes the request from a real one at the point it is made. This is the approach SentryFoE takes.
All FoE automation breaks the Forge of Empires Terms of Service, and accounts do get actioned for it. Nobody can promise you otherwise, and this site will not. The long answer on ban risk is here.
Most people looking into Forge of Empires automation are looking at one thing and calling it everything. If that thing is GbG, breadth is not what helps — attrition management, sector timing and army handling are, and those only come from a tool built for it. Compare what is out there, or read how the GbG side works.
FoE automation means having software carry out the repetitive parts of Forge of Empires for you — picking Guild Battlegrounds targets and attacking them, fighting Guild Expedition encounters, collecting finished buildings, or contributing Forge Points to Great Buildings. It is not the same as a helper extension: helpers show you information and leave every action to you, while automation performs the action.
No. Automating gameplay breaks the Forge of Empires Terms of Service, and accounts do get actioned for it. Any tool claiming otherwise is selling you something. Information-only helpers sit in a different, greyer category because they do not act for you.
In practice: Guild Battlegrounds attacks with attrition-aware target choice, Guild Expedition encounters wave by wave, collecting finished production and starting it again, and sniping Great Buildings with Forge Points. Guild Expedition negotiations are deliberately left alone — they are a guessing game, not a repetitive one.
Browser-extension automation needs a desktop browser, because that is where extensions run. SentryFoE runs in Chrome on a computer; you can start, stop and watch a run from your phone through the dashboard, but the game tab itself stays on the desktop.
Yes. The automation runs inside the game page, so the tab has to stay open — though it can sit in the background, and the bot will tell you when the browser is throttling its timers because the tab is hidden.