Reading the Board: What OpenFront Actually Shows You About Every Opponent

Direct answer: read the board before you commit

Before you send a single troop, you can already see almost everything you need about every opponent on the map. OpenFront removes the fog on the numbers: each player’s exact gold, their troop bar (green total, orange committed, right-aligned cap), their building count, their player type, and their alliance and traitor states are all visible to you, not to them only. The skill this guide builds is not collecting that data — it is decoding it, because the same green bar that looks “full” to a new player is actually a player sitting near the top of their growth curve, growing slowly, and easy to hit on the next tick. The decision it changes is the timing and target of every attack, every expansion, and every defensive build.

Read the board in a fixed order so a flashy number does not hide a strategic one. First, hover the opponent: note the gold box and its rate, the troop bar’s three values, and the building count. Second, read their position on the growth curve from the gain color and the gap between the green total and the right-hand cap. Third, check the Attacking Troops Overlay on any shared frontline to see the live attacker-versus-defender number and whether you clear the 2x push threshold. Fourth, open the Game Info modal and sort by StolenGold or ConqueredGold to surface who has been raided or is quietly trading. Only after those four reads should you ask “is this a good target or a good moment?” The version boundary is explicit: everything below describes the released v0.35.4 behavior; the fields, the overlay default, and the leaderboard columns are confirmed in the v0.35.4 tag source, so they hold for the build you are playing today.

Make the read observable rather than a hunch. Write down “green 410,000 of 600,000 cap, gold rate falling, building count flat” instead of “they look weak.” That sentence is falsifiable: if their green bar is climbing, they are not committed and you should probably wait; if the orange committed slice is large and the green total is low, they have spent their army and are regenerating slowly, which is your window. Keep the read short enough to survive combat pressure. The goal is not to know everything — it is to know which numbers are visible versus assumed, and to commit only when the visible numbers still agree with your hypothesis. That discipline turns the fogless board from a wall of numbers into a set of timed, reversible decisions, and it is the single biggest separator between players who see the board and players who merely own tiles.

What the info panel actually shows you

Hover any player’s entity and the info panel renders a fixed set of fields, and none of them is hidden behind a fog. The gold box shows the opponent’s exact gold and, in the control-panel treatment, the rate at which they are gaining it. A flat or falling rate with a high absolute number usually means they are about to spend — on a City, a Warship, or a nuke — so the number is a countdown to a big build you may want to interrupt. The troop bar is the richest single element: the green fill is their total troops, an orange overlay marks the troops currently committed to an active push, and a right-aligned label gives the maximum cap they can grow toward. The building count tells you whether they are investing in infrastructure (Cities, Defenses) or staying lean and mobile. The player type (Human, Nation, or Tribe) and, for a Nation, its attitude toward you (Hostile to Friendly) tell you whether you are dealing with a reactive AI or a deliberate player, and how warm the current relationship is.

The same panel, field by field, is a fixed set of signals you can read the same way every time. Keep this as the checklist you run on hover:

Field	What it shows you	What it implies
Gold box + rate	Exact gold and the gain rate	A falling rate with a high number is a countdown to a big build (City, Warship, nuke) you may want to interrupt
Troop bar green	Total troops currently held	The absolute size of their reserve, not their strength right now
Troop bar orange	Troops committed to an active push	How much of the army is already spent and where the contact is
Troop bar right label	Maximum cap they can grow toward	Headroom to grow; the gap from green to this cap is the number that matters
Building count	Cities, Defenses, and other structures	Whether they are investing (slower, sturdier) or staying lean (faster to commit)
Player type / attitude	Human, Nation, Tribe; Nation attitude toward you	Reactive AI versus deliberate player, and how warm the current posture is
Alliance icon + timer	Current pacts and the time to the next rescan	A scheduled rescan, not a guarantee of renewal
Trait (broken shield) + timer	The defense debuff and how long it lasts	The cheapest attack window on the board, visible to every rival

The alliance and traitor states carry countdowns, and those timers are the most underused numbers on the board. An alliance icon is not a guarantee of renewal — the official help text and the timer both say it is a scheduled rescan, so a warning is a prompt to decide whether to renew, reposition, or let the pact expire before your main army is committed. A traitor (the broken-shield state) applies a large, time-boxed defense debuff, which is the cheapest attack window in the game and one that the panel makes visible to everyone, including the victim’s rivals. Finally, the panel’s values refresh every tick, so the read is a sample, not a photograph: a bar that is green-and-full this frame can be orange-and-committed the next.

Treat the panel as the difference between what you know and what you assume. “Visible reserve 180,000” is a fact you read; “likely reserve behind their City” is an inference you must label as such. When the two disagree, choose the action that can be abandoned if the inference is wrong. This is the meta-skill behind every other guide on this site: threat assessment decides whether to create contact, and this page decides what you can already see that makes that contact cheap or expensive right now. Read in-game Gold rates to turn the gold box into a real income estimate instead of a raw number.

The troop bar and the 41 percent growth line

The troop bar is not a health bar; it is a growth-curve indicator. Your (and every opponent’s) troop cap grows with territory and with City levels — the v0.35.4 engine computes the cap from owned tiles and city troops, which is why expanding your border and upgrading a City both raise the right-hand number. More importantly, the rate at which troops refill depends on where the current total sits relative to that cap. The growth rate peaks around 41 percent of the population and falls off on both sides: below that line you are climbing steeply, above it you are near the top and each new tick adds less. The gain indicator is the on-screen tell — the (+troops) number changes color and size as you move along the curve, going green at the fast part and turning orange as you flatten out.

This is why a full-looking bar is not a safe-to-attack bar. An opponent sitting at 90 percent of their cap looks massive, but they are past the peak and regenerating slowly, so a 2x push now removes a large fraction of what they can cheaply replace. An opponent at 35 percent looks small, but they are at the steepest part of the curve and will be a different number in ten seconds. The two numbers you must extract from the bar are therefore not the total and the cap alone but the gap between them and the color of the gain. The gap tells you headroom; the color tells you slope. Community playbooks and the v31/v35 tutorials all teach the same move: watch a rival hover, see that their max troops is high while their actual total is low, conclude they have committed most of their army into an attack and their growth is temporarily depressed, and time the counter-push into that exact window.

Do not turn the 41 percent line into a rigid order to attack at a threshold. It is a reading aid for the slope, not a trigger. A player at 41 percent who is also traitored or whose border is overextended is a far better target than a player at 41 percent who is freshly allied and behind a Defense Post. The line answers “how fast are they refilling?” and the rest of the board answers “is that refill going to matter before I hit them?” When the map or a mode removes a system — no Cities on some maps, no troops in a lobby — remove that signal from the read instead of pretending the same checklist still applies, and fall back to the gold box and the building count.

The Attacking Troops Overlay and the 2x push threshold

The Attacking Troops Overlay is a real setting, on by default, that draws the attacker-versus-defender troop counts on every active frontline. It removes the need to estimate: instead of guessing whether a border is holding, you read the live number on each shared edge. That turns a whole-front scan into a list of explicit margins, and the margin is exactly the number that decides whether a push is worth committing. In the engine, a push succeeds most cheaply when the attacker reaches roughly twice the defender at the contact point, which is why the overlay’s ratio is the cleanest single number for “can I take this tile now without bleeding troops.”

Read the overlay in three states. When the defender is clearly above the 2x line, the contact is not free — hold, defend, or pick a different edge. When the attacker (you) is near the line, a measured send is justified because you are removing a front at an acceptable cost. When the defender is far below the line but the overlay also shows a second enemy reserve nearby, the apparent margin is a trap: the first contact resolves in your favor and the second contact arrives after you have spent the margin. The overlay does not show you the second reserve, so the read must pair the local ratio with the global scan.

Use the overlay to set a commit gate, not a score. Before pushing, state the ratio on the tile you intend to take and the fastest reserve that could reach it. If the ratio holds and the reserve is committed elsewhere (which you confirm from that rival’s own troop bar), push. If either fails, stabilize: let your bar refill toward the growth peak, spend gold on the building that removes the bottleneck, or pressure a different edge. Because the overlay is on by default, most players are already seeing it without thinking about it; the improvement is stopping and reading it deliberately. This is the same discipline as the attack-ratio decision, applied to the information the game already draws on the screen rather than to a remembered percentage. A useful habit is to keep one number in your head at all times — the ratio on the edge you most want to take — and let the overlay confirm it for you every frame, so the commit decision is a flip of a number you are already tracking instead of a fresh estimate made under pressure.

The Game Info modal and leaderboard signals

The Game Info modal (the ranking view) is the board’s summary layer, and it sorts by the same fields the engine tracks: TotalGold, StolenGold, NavalTrade, ConqueredGold, and Lifetime. Each column is a different question, and reading the right one changes the target. TotalGold ranks who is richest right now, which is useful for predicting the next big build. StolenGold surfaces who has been raided most — a high value flags a player who has lost income and may be forced into a risky push to recover it, which is either a target or a future aggressor you must prepare for. ConqueredGold and NavalTrade separate players who grow by land from players who grow by trade and Port lines, and those are different threats: a land grower can be cut off, a trader can be starved of a Port. Lifetime is the slowest-moving number and is best as a tie-breaker for who has been accumulating all match.

The modal’s main failure is the same as any leaderboard: it replaces the scan with a ranking. A player high on TotalGold may be about to spend it all on a nuke you can interrupt; a player low on ConqueredGold may be the safest, most predictable opponent to finish. The correct move is to sort by the column that answers the specific question you are facing, then return to the per-player panel to confirm. Do not attack the top of the TotalGold list because it is the top; attack the player whose visible numbers make the next action cheap.

Pair the modal with the panel in a fixed loop: the modal narrows the field from all players to the two or three whose situation changed most since your last read, and the panel confirms the exact gold rate, bar color, and committed slice for each. If a player’s StolenGold jumped in one tick, their gold box is now lower and their posture is now more aggressive — that is a concrete, timestamped change, not a vibe. This is the read behind economy fundamentals: the modal tells you whose economy is the interesting one, and the fundamentals guide tells you what the number means for the next build. Keep the loop short so it survives a live match: one modal sort, two panel hovers, one decision. The habit that separates this from a glance is the timestamp: note when the StolenGold or TotalGold column last moved, because a change in the last two ticks is actionable now and a change from early in the match is background. Treat the modal as a change detector, not a scoreboard, and you will stop reacting to players who are merely large and start reacting to players whose situation just shifted.

Scenario one: a committed opponent you can hit now

Assume the board is legible enough to write down. You hold a troop cap of 600,000 and a green total of 410,000, your gain color is green (you are below the 41 percent peak, so you are refilling fast), and your gold rate is steady. Your eastern neighbor has a cap of 265,000 but a green total of only 33,000, an orange committed slice of about 200,000 pushed into a fight with a third player, and a falling gold rate. Their building count is flat. The read is unambiguous: they have committed most of their army, they are past their growth peak on whatever they have left, and they are not investing in defenses right now. That is the cheapest attack window available.

Your action is not a full send. Send a measured force that clears the 2x push threshold on the shared edge and takes the single tile that shortens your border and denies them a retreat lane. Because their orange slice is committed to the third player, the contact resolves in your favor and the third player’s war is what keeps them from pivoting back. Before you commit, name the beneficiary: if a fourth player could reach the new edge after you capture it, the margin is a trap even though the local ratio is good. With the neighbor’s army committed and their reserve low, the window is the few seconds before their push resolves and their green total climbs back.

Suppose the capture leaves you at 360,000 green and the third player finishes the neighbor. Their troops return, but they are now at a lower cap and a longer border, and you have a shorter front and a reserve above your response floor. That is the correct outcome: not a larger land count, but a better shape and a rival who spent their army on a war that bought you time. The numbers above are assumptions that illustrate the read, not a promise about a specific match; verify the actual travel distance, the neighbor’s committed slice, and the beneficiary’s reserve before you click. The lesson generalizes: a high max cap with a low actual total is not “they are weak,” it is “they are committed and regenerating slowly, and the next tick is the window.” If the window closes before you arrive, do not chase the contact into an unfavorable ratio — the correct fallback is the same claim without the finishing push, which still shortens your front and denies the lane. The whole sequence should take one or two seconds of reading plus one click, which is what makes it usable under fire instead of a slow back-table analysis you only run between fights.

Scenario two: a full bar that is actually slow to grow

Assume you are choosing between two targets that both look beatable. The northern target shows a green total of 520,000 against a 600,000 cap, an orange committed slice of only 20,000, a rising gold rate, and a building count that just increased — they are investing. The southern target shows a green total of 300,000 against a 500,000 cap, an orange slice of 150,000 committed to a border fight, a flat gold rate, and a flat building count. The northern target looks bigger, the southern looks smaller, but the read is the opposite.

The northern target is at 87 percent of their cap, which is far past the 41 percent growth peak: they are near full and refilling slowly, but they have almost nothing committed, they are rising in gold, and they are spending it on defenses. Attacking now spends your troops against a position that is about to get stronger, and the rising gold rate means a Defense Post or a City is one tick away. The correct read is hold and prepare: keep your bar near the peak, spend gold on the building that solves your own bottleneck, and wait for their committed slice to grow or their defenses to be placed and exposed. The southern target, despite the smaller total, has committed a third of their army, is at 60 percent of cap with a slow slope, and is not building. That is the target.

Send the measured push to the southern edge, take the tile that shortens your border, and stop after the test claim. Do not chase the finishing kill while the geometry is unresolved and while the northern target’s gold rate says a defense is coming. If the southern fight resolves and their army returns, re-read the gap and the color before the second send; if the window is closed, the first claim has already shortened your front and denied them a lane, which is the payoff. The numbers are assumptions, not a guarantee, but they show the failure this guide is meant to prevent: a bigger-looking bar that is actually slow to grow is the target you should avoid in this moment, and a smaller-looking bar that is committed is the target you should hit. The board is fogless; the skill is reading which number is doing the work. If you must choose only one signal when two targets look close, it is the gap and the gain color, because that is the number the game already draws for you and the one that survives a fast fight.

Failure modes and how opponents abuse the same information

The most common failure is trusting the total and ignoring the slope. A player sees a high green total and reads it as “they are strong, I am safe to attack later,” when the high total is actually a slow-growth position they should hit now, or a player sees a low total and attacks into a bar that is at the steepest part of the curve and will be a different number in ten seconds. Counter this by always reading the gap and the gain color, not just the fill. A second failure is overlay blindness: the Attacking Troops Overlay is on by default, but players watch the number without asking what reserve is behind it, so a favorable local ratio hides a second contact that arrives after the margin is spent. A third is leaderboard ranking as strategy: attacking the top of TotalGold because it is the top, instead of the player whose visible numbers make the next action cheap.

Opponents can abuse the same fogless board against you. A rival can flash a small attack to pull your troops away from the edge you actually need, send a transport as a visible distraction while the real army takes the longer route, or offer an alliance that freezes your only growth lane while they commit elsewhere. Because the panel shows everyone the same numbers, a rival who is committed has told you exactly when they are vulnerable and exactly when they are not — the manipulation is not hiding information but making you act on the wrong reading of it. Your response is to separate contact from commitment: a small test or a visible patrol gathers information and forces them to spend attention, while a full attack happens only after the target, the beneficiary, and your own response floor all still pass the read.

Treat the traitor and alliance timers as scheduled rescans rather than guarantees. A broken shield is a visible, time-boxed defense debuff that makes the next attack cheaper for everyone watching, so a player who just betrayed is a priority target for the whole board, and the countdown tells you how long that window lasts. An alliance warning is not a promise of renewal, so the warning is the moment to decide whether to renew, reposition, or let it expire before your main army is committed. The practical rule: the board is fogless, which means every number is a fact and every inference is yours to own; read the fact, label the inference, and commit only when the visible numbers still agree with the hypothesis.

Mode and map adjustments, then the next guides to read

In FFA, the beneficiary is usually the real threat, and the read must include who gains from your contact, not only whether the local ratio is good. A conquest that makes you the largest connected block can invite several players even when the target was weak, so the Game Info StolenGold and ConqueredGold columns matter more here: they show who has been bled and who will be the next aggressor. In Team, replace “who benefits?” with “which teammate can use the opening?” and the read of a rival’s committed slice doubles as a cue for where your team should commit, because a teammate can cover the new edge while you hold the reserve.

On compact maps, travel times are short and a single captured tile can connect two fronts, so re-read the overlay after every claim and keep the second reserve in the read. On large continental maps, a distant neighbor cannot pivot immediately, but a long border still drains attention and hides a second contact, so the local ratio is necessary but not sufficient. On islands and straits, a Port can be both income and the only transport anchor, so the read must include water access and a ground fallback, and NavalTrade in the modal tells you which rival is built on that Port. If a lobby disables Ports, transports, alliances, or Peace Time, remove that signal from the read and weight the remaining ones — the building count and the gold rate — accordingly.

This page decides what is visible and what it implies; it does not replace the decision guides that act on it. Read threat assessment to turn the read into whether to create contact at all, in-game Gold rates to turn the gold box into income, and attack ratio to turn the overlay margin into a send size. The facts here are verified against the openfrontio/OpenFrontIO v0.35.4 tag — the info panel fields in PlayerInfoOverlay.ts, the troop-cap formula in Config.ts, and the Game Info sort list in the ranking components — and against the official openfront.io help text describing the panel, the default-on overlay, and the retreat mechanic. If a later release changes a field, a timer, or a multiplier, update the scenario numbers and the mode notes together so the read stays legible. The player who sees the next border before clicking it controls more of the match than the player who merely owns more tiles.