SentryFoE — Forge of Empires GbG Automation Bot

Features

One panel. Nine ways to wreck the map.

Hover a tab to see exactly what it does — no fluff, just what's actually in the panel.

Targets

Auto mode fights your best case first — part-finished conquests, then lowest attrition, then highest VP. Or switch to Manual and pick provinces straight off the map, with a live sortable board and hide-mine / hide-locked filters.

Army

Set your army in the game, hit Record current once, and it is applied before every attack. Every attack after that replays it against your current roster — an allow-damaged switch and a minimum-HP threshold control exactly how picky it is about full health.

Combat

Manual, Auto, or Autopilot — attack delay with jitter, tries-per-province, attrition caps, and an attack budget. Skip provinces your guild flagged ignore, or hit only the ones flagged focus. Beast mode sits behind its own switch: zero delay, maximum speed, power users only.

Alerts

Drop in a Discord webhook and get pinged the instant any province locks — yours or not — with a live countdown and every participating guild's progress. Test button included so you're never guessing if it's wired up right.

Sniping

Scans your Friends, Guild, and Neighborhood for other players' open Great Buildings and works out which reward slots are actually worth taking — your Arc bonus, whether the contribution locks the slot for good, and a minimum ROI you set. Snipe one by hand, run auto-snipe on the whole list, or go instant and take a slot the moment a scan finds it. FP caps and a blacklist keep it inside whatever bounds you set.

Log

Everything the panel's done, live, right there to copy or export. If something breaks, Send report attaches your recent log automatically — no need to explain what happened, we can just see it.

Build

Pick the buildings you want on a sector once and it places them the moment you capture one, in the order you set. It can clear what the previous owner left behind first, and finish construction instantly with diamonds — only if you switch that on.

Guild Expedition

Fights the encounters wave by wave and collects the chests between them. A small popup appears when you open GE in the game — pick your expedition army, press start. It can buy more attempts with medals if you let it, capped by how many and how much you are willing to pay.

Remote control

Start or stop the bot and check live stats from your dashboard, from your phone or any browser — no need to keep the game tab open.

Changelog

What's shipped

v2.4.8

Latest

New: the same building can go in your build order twice. Two Field Camps on one sector, for example

v2.4.7

New: “secure targets” — the bot stops losing the sector it was waiting for. When waiting for a locked sector to open, it now prefers ones it’ll still be able to reach when they do, instead of waiting on one whose launch point gets captured out from under it — the “fought less than it should” and “saw the bar move but nothing on mine” cases
It’s a preference, not a filter: if nothing securable is going, it still fights the best of the rest. New Prefer secure targets switch in the combat panel, on by default

v2.4.6

Fixed: crashes from other extensions are no longer reported as SentryFoE errors. If FoE Helper (or another extension) trips over one of the game’s hiccups, it’s now attributed to whichever extension actually crashed — not the bot
Changed: the game’s own “try again later” error is no longer shown as a red error. It’s the game’s server having a moment; the action usually works on the next try
Changed: pressing Start when your attrition is already over your cap now tells you so (with the numbers), instead of just stopping with nothing fought

v2.4.5

Fixed: auto-snipe skipped targets you could afford. The balance the bot kept could only fall — a snipe was taken off it, but the Forge Points a snipe pays back were never added — so it drifted to zero and refused everything. One customer had 1556 FP in the bar and nothing being sniped. The game is now asked for the real figure whenever ours is stale or guessed at
Changed: a snipe goes ahead when the game won't say your balance, instead of being skipped. Packages are still opt-in and diamonds are still unreachable, so the worst case is one refused request
Fixed: Guild Expedition relic collecting no longer needs your city opened first
Fixed: a wave the game never answers is no longer reported as the game refusing it
Changed: warnings about a service the bot can't reach are said once, not every few seconds
Changed: one plan at $10 a month. Remote control is part of it rather than a separate tier — if you're on Pro you keep everything you have
Changed: season cards in #showcase use an alias we assign you, so a Discord handle can't end up in a public channel by accident

v2.4.4

New: Guild Expedition collects the relics on the map as it clears encounters. On by default — there's a switch in the GE popup if you'd rather it didn't
Fixed: a Guild Expedition level you hadn't touched yet wouldn't start. The game doesn't always say which encounter you're on until a battle has happened, so you had to fight one by hand first. It now starts from the first encounter on the map

v2.4.3

Fixed: a Guild Expedition encounter with two waves fought only the first. The game does not always answer an attack with the result — sometimes it answers first and decides after — so the next wave was being started while the previous one was still open. That is why the game asked whether you wanted to continue fighting after a reload
Fixed: a wave the game never decides now stops the run and says so, rather than starting the next one
Fixed: your Forge Point balance is read properly. It now comes from both of the messages the game reports it on, and only from your own stock
Changed: auto-snipe stops when your Forge Points will not cover the next target, instead of working through the rest and failing each one

v2.4.2

Fixed: sniping could spend diamonds. When your Forge Point bar could not cover a contribution, the bot let the game fund it from anywhere — which means packages first, then diamonds. It now reads your bar and will not send a contribution it cannot cover
New: it can open FP packages instead, if you let it. Off by default. Even switched on, it only opens packages when it has counted them recently and they comfortably cover the gap — otherwise it skips the snipe and tells you why. It can never reach your diamonds

v2.4.1

Fixed: after finishing a Guild Expedition level, opening the next one and pressing start did nothing until you reloaded the page. The bot was still going by what the game had said about the level you had just finished

v2.4.0

New: Guild Expedition is automated. It fights the encounters wave by wave and collects the chests between them. A small popup appears when you open GE in the game — pick an army, press start
Your expedition army is separate from your battleground one, so setting it here never changes the army your sectors are fought with. It is re-applied between waves the same way normal mode does it, so units lost in one wave are replaced for the next
New: it can buy more attempts with medals when you run out. Off unless you turn it on, with a limit on how many per run and how much you are willing to pay — the game charges more for each one you buy
New: features can be switched off remotely. If something turns out to be broken we can stop it for everyone within a couple of minutes, instead of waiting for people to download a fresh build

v2.3.0

Normal mode is faster, and nothing about how it fights changed. It used to re-read the whole board and re-send your army before every single attack — three trips to the game server per fight, which is why a 25ms delay still gave about one attack a second. The board is now kept up to date from the updates the game already pushes, and your army is only re-sent when the last fight actually damaged it. Measured at a typical connection: 30–149% more fights per minute, depending on how hard your army is hit
New: the bot now tells you when your tab is the problem. Running it in more than one tab on the same account means they share one army and one board — they overwrite each other’s army and fight each other for sectors. The log now says so
New: it also tells you when the game tab is in the background, where Chrome slows all timers to about a second and your attack delay stops meaning anything. It measures the actual delay in your tab rather than guessing

v2.2.1

Fixed: “stop after losses” did nothing in beast mode. Both stop-on-loss settings were only ever checked by normal mode. Set to 1, a beast run could lose the same sector nineteen times in a row and carry on. They now apply in both modes — note that attacks already fired cannot be recalled, so with a high “max in flight” a few more results still land after the stop

v2.2.0

New: the remote dashboard shows the same board as the panel. Sectors by their map name, a colour per guild, your progress on each one, lock countdowns — and you can click a sector to target it. A second view colours the board by the game’s own attack/defence marking
New: beast mode and your army template can be set remotely, along with max in flight and the re-apply interval — the two settings that decide how fast a burst actually runs
Fixed: “attacks per minute” measured the whole run, including waiting for sectors, reading the map and swapping army. It now measures the time attacks are actually going out, so the number finally matches what you see — expect it to read much higher for the same speed
Fixed: the remote settings form was missing the defence attrition limit, and had a “budget offset” box that never did anything

v2.1.0

Faster beast mode. Changing army used to make the bot stop, ask the game for your unit list, and only then send the new army. It now asks for that list a fight in advance, so the swap is one step shorter — around 50% more fights per minute in testing, and more the shorter your army lasts
Fixed: attacks fired at an army that had already run out. With 20 attacks in flight and an army lasting five fights, fifteen of them reached the game with nothing left to fight with — that is where the “no units selected” popups came from. The bot now keeps attacks in flight within what the army can actually honour
Changed: the army is swapped when a battle leaves none of your units standing, instead of at a health percentage. The old “swap army below this health” setting is gone: unit health in a battle is relative to that battle, so it was swapping armies that were perfectly fine — and each swap costs time
Fixed: a sector your guild flags “ignore” is now left alone only while the flag is up. Clear the flag and the bot fights it again straight away

v2.0.12

Fixed: the bot could keep picking a sector your guild flagged “ignore”, opening on it, stopping a few seconds later, then picking the same one again — which looked like it aiming and never firing. A flagged sector is now left alone while the flag is up (see v2.1.0)
Fixed: the Attacks count looked like it applied under Autopilot. It never did — Autopilot runs until you stop it and uses Attack budget instead. The field is now greyed out with a note, so a fight limit can’t be set where it does nothing
Improved: “no units selected” refusals now say what to change instead of just being retried, and name the popup the game shows you

v2.0.11

Fixed: beast mode ending a run with no explanation. Attacks fired at the instant a sector is captured are never answered by the game at all — the bot waited 8 seconds for them and then stopped the whole run. It now writes those attacks off, says so plainly, and moves to another sector; it only gives up if three bursts in a row go unanswered, and then tells you to reload the game tab

v2.0.10

New: the panel tells you when your attrition resets. The game publishes the time; it now sits next to your attrition, and when a cap is holding the run back the log says how long until you can fight again
New: your army is swapped before it dies, not after. Each battle result carries your units’ health, so beast mode can change army when it’s actually worn down instead of after a fixed number of attacks (Combat → Swap army below this health)
New: attrition cost is worked out from the board. Buildings on your own bordering sectors decide what an attack costs, so sectors the game reports nothing for now show an estimate (marked ~) instead of ? — and a stale figure from the game no longer hides a cheap sector
Fixed: a sector captured a moment before your attack was reported as an empty army, and counted against that sector until the bot gave up on it. It now says the sector closed and simply moves on

v2.0.9

Fixed: the bot could sit “waiting” for hours without attacking anything. If your attrition limit ruled out every sector, it queued for sectors it would then refuse, silently. It now only waits for sectors it will actually fight — and tells you in the log when a limit is what’s stopping it, naming the limit
New: the province map now looks like the real board. Proper hex sectors in their real positions, each guild in its own colour, your progress filling the sector, lock timers, and guild target/ignore marks. A second view colours sectors by the game’s own attack/defence marking
Fixed: sectors the game gives no attrition figure for were treated as 0%, so the bot preferred exactly the sectors whose cost it didn’t know. They now show ? and are tried last

v2.0.8

New: Discord alerts now land when they are useful. Instead of a message the moment any sector locks, you get one shortly before a sector you can actually attack opens — and you choose how many minutes’ warning
New: 0 attacks means unlimited. Beast mode uses the same number as normal mode now, so there is one Attacks setting instead of two
New: the status bar says which sector it is attacking, and names sectors the way the map does instead of by number
Improved: the “attackable” target filter now includes locked sectors you can attack once they open
Fixed: being signed out when the game is open in more than one tab. Two tabs refreshing your login at the same moment could sign the account out everywhere

v2.0.7

Fixed: a run could quietly stop on its own overnight. One slow answer from the game ended the whole run — one customer’s session died at 3am and sat idle for three hours. It now retries and carries on
Fixed: “internal error” popup right after pressing Start. If your army template couldn’t be filled (units wounded or spent), the bot sent units that no longer existed and the game threw an error box. It now attacks with the units you actually have — and if none of them fit, it leaves your current army alone instead
Fixed: other FoE extensions’ errors showed up as ours in your log and bug reports. They are now labelled as theirs

v2.0.6

New: separate attrition limits for attack and defence sectors. The same split your Discord lock alerts show. Hitting one limit no longer ends the run — the bot carries on with sectors of the other kind and stops only when both are reached. Set them to the same number and nothing changes

v2.0.5

New: season recap cards. When a Guild Battlegrounds season ends, your dashboard turns it into a card — fights, your best day, FP sniped and where you rank among SentryFoE players. Download it, or post it to #showcase on Discord if you want to
Fixed: the download button sometimes did nothing, then made you wait 10 minutes. Pressing it now re-downloads the build you already have, straight away, and a download that fails tells you instead of failing silently
Fixed: getting signed out when running the bot on several PCs. One machine refreshing its login could sign out all the others, over and over

v2.0.4

Improved: much less background data. The extension no longer re-sends the same status every few seconds, so it uses a tiny fraction of the data it did while the game is open

v2.0.3

New: update reminder on your dashboard. When a newer build is out than the one you’re running, the dashboard says so, with a one-click download
The extension now reports what auto-build and beast-mode army recovery do, so we can see whether they work and fix them faster

v2.0.2

Fixed: beast mode stopped when your army died. At high attrition the army could run out mid-burst and the run ended. Beast mode now re-applies your army template and keeps attacking. It needs an army template selected
If the army is still empty after 3 re-applies in a row, the burst stops instead of wasting your attacks

v2.0.1

New: a Build tab. Auto-build has its own tab, with every building under its in-game name, sorted by cost
New: drag and drop. Drag buildings to reorder your build order, or straight into a position from the list
New: “attackable” filter in Targets. Shows only sectors you can attack right now
Auto-build is still in beta and not yet tested in a live game — everything stays off by default

v2.0.0.b

Beta — not tested yet. This is a test feature waiting on real results. Everything below is off by default; if you try it, start small and tell us how it went
New: auto-build after capture. When your guild takes a sector, the bot places buildings from a build order you choose, paid from the guild treasury. Capped at 5 buildings per session by default
New: replace leftover buildings. Optionally demolishes buildings the previous owner left on a captured sector and builds from your order instead
New: instant finish. Optionally skips each placed building’s build time, paid from your own diamonds

v2.0.0

New: the bot connects itself. Until now it had to wait for you to open things before parts of it worked — a battle before it could attack, the unit screen before army templates applied, the sniping screens before sniping ran. All of that is gone. Everything connects roughly a second after the game loads, without you opening anything
Fixed: autopilot refused to start when nothing was attackable. That was the exact situation it exists for. Because it could only connect to the game’s battle system by you opening a battle, and you can only open a battle when something is attackable, a quiet board meant it wouldn’t start at all. It now starts, watches the board, and goes the moment a sector opens
Faster, lighter startup. The bot briefly adjusts part of the browser’s internals while it finds the game’s systems. That now finishes in about fifteen seconds instead of two minutes, and a check that ran on every single request — and could never succeed on the current game build — has been removed

v1.9.2

Fixed: the map stopped refreshing. It stayed live for about the first fifteen seconds after you opened Guild Battlegrounds, dropped back to a slow refresh, and eventually stopped updating altogether until you refreshed it by hand. Two separate faults: one path through the refresh logic skipped the staleness check entirely and quietly starved the timer, and a quiet map — nothing happening on the board — was being mistaken for a dead connection
Fixed: autopilot ended the run when nothing was attackable right then. A sector above your attrition cap isn’t locked, it’s simply filtered out, and the bot treated “nothing to attack this second” as “nothing left to do” and stopped. But that filter isn’t permanent: attrition chance drops when your guild builds on a bordering sector. A reported case had a sector fall from 60% to 20% — well inside the cap — with no run left to take it. Autopilot now waits and keeps looking, as it was always documented to
Fixed: waiting on one sector while the rest of the board moved. A real session sat on a single province unlocking in three and a half hours and made zero attacks in that time, because the wait only ever watched that one province’s clock. It now re-checks the board while it waits, and wakes immediately when a building goes up or a sector changes hands — either of which can make something better available
Fixed: beast mode ending a run seconds after a sector opened. When the sector it was waiting on unlocked, it looked once for a target and ended the entire run if that one look found nothing — a log shows exactly that, with 835 attacks of budget still unspent. A sector opening doesn’t guarantee it’s attackable, so one unlucky look no longer ends the run
Fixed: wins on one sector counted as errors. Because of how the game identifies that particular sector, every attack there was recorded as a failure — one run reported “69 fought, 39 errors” when all 39 were wins, alongside a misleading “your army is probably empty”. The same quirk also produced “province #undefined locked” in the log. Both now read correctly

v1.9.1

Hotfix: the rest of the slowdown. v1.9.0 fixed this for the game’s live connection, but the same problem existed on its ordinary requests and had done since the very first release — every reply the game received was being read twice, once by the game and again by the bot, even when the bot had no use for it. The replies that hurt are the big ones: your message list, your inventory, Guild Expedition. They grow as your account does, which is why it got worse the longer a session ran. If you were still seeing lag on v1.9.0, or on any older version, this is the half that was missing
Fixed: a memory leak that lasted the whole session. While identifying the game’s internals at startup, the bot kept hold of everything it inspected — around 17,000 objects — and never let go, so the browser could never reclaim that memory. It now releases them as soon as it is finished

v1.9.0

Fixed: the game getting slower the longer a session ran. The bot was fully parsing every message the game’s live connection sent it — including chat history, which grows all session and reached 28 KB in testing — just to check whether it was interesting. It now checks cheaply first and only reads what it actually uses. If loading messages, Guild Expedition fights or your inventory had started to feel sluggish, this was why
Fixed: beast mode kept attacking a sector after it had been captured. The server refuses those attacks and the game shows an error box for each one — a real log had 23 in a row. The bot now notices the moment a sector is taken, from the game’s own conquest announcement, and moves to the next one
Fixed: “Max in flight” in beast mode never actually did anything. It was counting requests sent rather than results received, so it never limited anything and a whole burst left in one go. It now paces the burst as intended — beast mode will feel steadier, which is the setting finally working
New: auto targeting only picks sectors it can legally attack. Guild Battlegrounds only allows attacking a sector bordering one your guild holds, and the bot had no way to know which those were, so it found out by being refused. It now reads the real map layout. Capturing a sector immediately re-checks what that opens up
New: the map updates live. While you have Guild Battlegrounds open, the bot follows the game’s own realtime feed instead of re-reading the map every few seconds — sector locks, captures and guild ignore/focus flags now register as they happen
New: a Diagnostics button in the Log tab copies everything about your session as one block of text. If you ever report a problem, that is the single most useful thing you can send
Fixed: sector names showed in full (“E3A: Joviolomond”) instead of just the short code on the current map. Sector 0 also had no code at all
Fixed: a run could stop early deciding everything had failed, when it had simply not tried the reachable sectors yet
Fixed: “Re-apply army every N attacks” now defaults to 10 instead of 0. At 0 a long burst outlives its army and every attack after that is fired into nothing — one report spent 89 of 100 attacks that way
Fixed: a rare crash the bot could cause inside the game’s own code while identifying its services, and that identification now stops as soon as it is done rather than staying active for ten minutes

v1.8.0

The Pop Game solver is paused. One of our own test accounts was flagged by the game after very heavy use of it, so the tab no longer appears and the solver will not start. Everything else — Guild Battlegrounds, sniping, the army manager — is unaffected and unchanged. The feature is only switched off, not removed, and will come back once we understand what triggered it
New: a Join Discord button now appears in the Account tab if your account has no Discord linked yet. Update announcements and support land there first

v1.7.0

New: the Guild Battlegrounds map now loads by itself as soon as the bot connects to the game, and keeps itself up to date every few seconds — no more clicking “Load map” and no more acting on a sector list that went stale minutes ago. A tag beside the button shows how old the data on screen is
New: the bot now also reads the game’s own realtime update channel. Forge of Empires pushes changes to the page as they happen — that is how the in-game map updates without you touching anything — and until now the bot ignored that entirely and could only learn things by asking. It now listens, so map changes, battle results and attrition can arrive with no request of its own. Province-lock notifications land closer to the actual moment as a result
Fixed: if a sector your guild has flagged “ignore” gets flagged while you are attacking it, the bot now finishes the attack in progress and moves to another sector. Beast mode was the bad case: it read the map once at the start of a run and never again, so a sector flagged mid-burst kept the entire remaining attack budget
Fixed: a failed map refresh no longer blanks the board — the last good map stays on screen, marked stale, until it recovers

v1.6.3

Fixed: the board played its last move and then tried one more, putting the game’s “you don’t have enough resources” dialog on screen. The game’s out-of-moves signal turns out to mean “no matching group left on the board”, which is not the same as the move counter reaching zero — moves are a resource, so running out comes back as an ordinary refusal instead. v1.6.1 had started trusting that signal alone; both checks now stop the board
With Golden spoon on, a board ending that way now moves to the next board instead of ending the whole run
Reward popups: still investigating. The hide-rewards setting is confirmed to be applying, but the popups are clearly reaching the screen by another route, so this build logs which one — if you run with the setting on, the Log tab will now name it

v1.6.2

Fixed: the Pop Game solver was drastically slower in a real build than in testing — around five minutes a board instead of seconds. The protection applied to shipped builds encrypts text inside the code and pays that cost every time a piece of text is read, which is fine everywhere else but brutal in the solver, which examines roughly a thousand board positions per move. Measured on the real solver: 64s a board before, 2.3s after
The solver itself is also about twice as fast now, independently of the above — the board fingerprinting and group-finding no longer build throwaway text for every square they look at
Fixed: two boards that differed only in a jar’s star rating could share a cached score, so the solver occasionally reused a result worked out for a different board. Only possible since star ratings started counting in v1.6.0

v1.6.1

Fixed: Golden spoon never actually started the next board — it called the wrong internal name and failed with “endGame is not a function” every time a board ran out
Fixed: reward popups kept appearing and the board stopped one move early, both from the same cause. The bot recognised the game’s board view only when a tile was clicked by hand, so during an automated run it was never available — and everything depending on it (hiding rewards, the game’s own out-of-moves signal) quietly did nothing. It now recognises the board from any of the ways the game updates it, and switches over immediately if the board is recognised part-way through a run
Fixed: with the board view missing, the run fell back to counting moves against a counter the game refreshes on its own schedule, which is what left a board stopping with one move unspent

v1.6.0

New: Golden Spoon mode for the Pop Game — when a board finishes it starts the next one on its own, so a five-minute run doesn’t stop dead every time you clear a board
New: hide jar rewards toggle — the reward popup for every jar you collect no longer interrupts the run waiting to be dismissed
New: jar star ratings are now read off the board and factored into which move the solver picks. A 5-star jar is worth more than a 1-star one, and until now the bot couldn’t tell them apart — every jar counted the same, so with two jars falling it had no basis to prefer the better one
Fixed: the Pop Game kept clicking after the board had no moves left. It now uses the game’s own out-of-moves signal instead of counting moves itself, which is what made it stop a move early or a move late
Fixed: the cups and jars tally counted everything twice
Fixed: a build missing its config reported “Cannot read properties of undefined” under the sign-in button instead of saying what was actually wrong

v1.5.9

Security: sign-in sessions now rotate their credentials every time they renew, so a session token that ever leaked stops being usable instead of quietly lasting a month. If a retired token is replayed, every session on that account is signed out immediately
Security: patched all known vulnerabilities in the server's dependencies, including a high-severity one
Security: tightened request size limits on the sign-in and registration endpoints
Note: this update signs you out of the extension once. Just sign in again — your licence, saved armies and settings are untouched

v1.5.8

Fixed: beast mode kept attacking after the army was wiped out. A dead army isn't a failed request — the game answers each attack with a rejection, and beast mode never read those, so it would fire its whole remaining budget into a server saying no every time. It now stops after five server errors and tells you why
Fixed: "re-apply army every N attacks" didn't actually work in beast mode. The swap was fired off without waiting, so dozens more attacks — all still using the old, damaged army — went out before it landed. Beast mode now lets the attacks in flight finish and waits for the new army before continuing, so the next fight really does use it

v1.5.7

Fixed: sniping in "closing only" mode — the default — almost never fired. It priced every snipe as if it still had to defend the slot afterwards, then rejected it for not closing the level. Closing a level is now costed as what it actually is: the FP left to finish it, with nothing to defend afterwards because the level ends. A building 400 FP from done with first place held at 380 and paying 450 is now taken for 400, at 50 profit — before, it was skipped
Fixed: the FP needed to hold a slot was rounded inconsistently — one FP too many against an occupied slot, and one too few against an empty one, where a rival contributing the rest would tie you instead of losing

v1.5.6

Fixed: recording an army could also capture your PvP arena defence line-up, and then quietly rewrite it before every single attack. Saved armies now only ever touch your Guild Battlegrounds army — nothing else
Fixed: that same stray arena line-up was behind the "army may have been rejected by the server" failures — one stale unit in it was enough for the game to reject the whole army change, including the part that mattered. Existing saved armies are cleaned up automatically, no need to re-record them

v1.5.5

Fixed: v1.5.4 could cause serious lag or an unresponsive game tab — a background diagnostic loop that's supposed to stop within moments of loading could keep running for the entire session instead. Sorry about that one — thanks to whoever caught it fast

v1.5.4

New: full automation for the seasonal Pop Game event — the panel already suggested the best tile to pop, now Play can pop it for you too
New: your Account tab now shows the version of the build you're currently running

v1.5.3

Fixed: army templates could intermittently fail to apply mid-run with no visible reason — the bot could hand the game a unit that was already busy elsewhere (mid-attack, or assigned to arena defense) when refreshing a saved army, which the game correctly rejects. Unit selection now skips anything not actually free right now instead of risking a stale pick

v1.5.2

New: the bot now stops itself after losing several attacks in a row on the same province (configurable in Combat tab, default 3) instead of continuing to feed units into a fight it clearly can't win right now

v1.5.1

Fixed: on some downloaded builds, the panel could open in-game but silently fail to prompt for login, leaving the extension unusable — sign-in now works reliably on every build. If this happened to you, grab a fresh build from your dashboard

v1.5.0

New Sniping tab: scans your Friends, Guild, and Neighborhood for other players' open Great Buildings and calculates whether contributing FP right now would win a reward slot — arc coefficient, minimum ROI, per-building and per-scan FP caps, a blacklist, and an instant-snipe mode that acts the moment a scan finds a target

v1.4.1

Fixed: sign-in could silently try to reach localhost instead of the real license server, on some page loads - login now resolves the server address fresh at request time instead of caching it once, too early

v1.4.0

New Pro add-on: start/stop the bot and check live stats from your dashboard, from anywhere — no need to keep the game tab open
Combat tab can now skip provinces your guild flagged "ignore," or restrict to only "focus"-flagged ones — reads your guild's own in-game markers automatically
Fixed: the panel could be dragged off-screen and become unreachable — position is now clamped, and self-heals if it already happened to you

v1.3.0

Fully redesigned control panel — real icons, proper tabs, toggle switches, no more debug-console look
Your attacks/wins now show up on your dashboard
Export log and Report a bug, right from the panel's Log tab
The panel now tells you when a newer build is available

v1.2.0

Customer accounts, single-device licensing, and self-serve builds
New dashboard: check your plan, expiration, and device status any time
This site

v1.1.0

Redesigned control panel - tabs instead of one long scroll
New color scheme across the panel and toolbar popup

v1.0.0

Initial release: targeting engine, timed strike, beast mode
Army recording with full-HP refresh
Discord lock notifications

FAQ

Before you ask on Discord

What is SentryFoE?

SentryFoE is a FoE bot — a Chrome extension for Forge of Empires automation. It concentrates on Guild Battlegrounds (GbG), handling targeting, attacking and keeping your army topped off, and also covers Guild Expedition, production collection and Great Building sniping.

Is using a Forge of Empires bot against the rules?

Yes. Automating gameplay is against Forge of Empires' Terms of Service, and InnoGames can act on your account for it. SentryFoE is provided as-is, entirely at your own risk — see what actually gets accounts caught, or the full Terms & risk disclosure. If you're weighing this against another tool, we also compare honestly to FoE-Extender.

How does the GbG automation decide what to attack?

Auto mode fights your best case first: part-finished conquests, then lowest attrition, then highest VP. Or switch to Manual and pick provinces yourself from a live, sortable board.

Do I need to keep the game tab open while it runs?

Yes — the extension talks to the game's own API from inside your browser tab. Remote control and live stats from your dashboard are included, so you can start, stop, and check on it without the tab open.

Which browsers does the extension support?

It's built for Chrome (Manifest V3) and works the same way on other Chromium-based browsers like Edge or Brave.

How does licensing and getting the extension work?

Sign up, get a license, and build the extension straight from your dashboard — one licensed device per plan, and you can rebuild it fresh any time.

Run GbG on autopilot. Touch grass.