OpenFront Threat Assessment: Choose the Next Target Without Overextending

Direct answer: scan first, then choose a reversible target

After the opening, do not ask only “who has the fewest troops?” Ask which action improves your position while leaving the fewest new ways to lose. The best next target is usually a player whose land touches a route you can defend, whose current army is committed elsewhere, and whose removal shortens your border. A weak player in the wrong direction can be a losing target if the capture exposes your City to a stronger neighbor or leaves your troops trapped behind a new front.

Run the same scan before every meaningful attack. Look at your own troop percentage and cap, the length of the proposed border, the nearest enemy reserve, open water, active alliances, and the notification feed. Then inspect the two players who benefit most if you attack. If one of them can reach your new edge before your troops refill, treat the target as contested even when the attack itself is favorable.

Use a three-state decision. Expand when the claim adds connected land, removes a front, and leaves a reserve. Stabilize when the claim is useful but a building, alliance, or border shortening must happen first. Stop when every available claim lengthens the perimeter, spends the reserve, or creates a profitable invitation for a third party. Stop is a decision, not a failure. A quiet minute that lets troops, Gold, and information accumulate can be stronger than a cheap conquest.

The version boundary matters. This guide describes released v0.33.12 behavior. It assumes normal FFA-style land play unless a mode section says otherwise. The 42% population wave is a growth heuristic from the opening material, not a command to attack. Attack Ratio is a commitment control, not a probability of victory. If the map, lobby timer, or mode removes a system, remove that signal from the scan instead of pretending the same checklist still applies.

Make the scan observable rather than mental. Pause your cursor on the proposed landing tile and trace the shortest route an opponent could use to reach it. Then trace your own retreat route back to a City, Port, or protected interior. If either line is unclear, label the target yellow and spend one short cycle gathering information. Watch whether the suspected beneficiary moves troops, starts a transport, or stops fighting its current opponent. Those changes matter more than a single leaderboard refresh. A useful scan also separates what you know from what you assume: write “visible reserve 180,000” separately from “likely reserve behind the fog.” When the uncertainty is high, choose a claim that can be abandoned without losing the core. This habit keeps a cheap opportunity from becoming a forced all-in and gives you a clear reason to change from expand to stabilize before the map punishes impatience.

Build a five-signal board scan

Your eyes should move in a fixed order so that a flashy low troop count does not hide a strategic threat. First check reachability: can your troops touch the target through connected land, and can the target touch you back after the capture? Next check geometry: how many tiles become border, and can one Defense Post or a natural neck cover the approach? Then check tempo: what will your troop cap and growth factor look like when the attack finishes? Finally check politics and attention: which alliance expires, which player is already attacking, and which notifications would reveal a transport or betrayal?

Signal	Green light	Yellow light	Red light
Route	Connected land and a fallback lane	One narrow lane with a second threat	Capture creates an isolated pocket
Border	Shorter or equally short front	Same length but defensible terrain	Several new exposed edges
Reserve	Troops remain above your chosen floor	Refill depends on a City or quiet ticks	The attack empties the core
Opponents	Neighbors are busy or mutually hostile	One rival can pivot quickly	A third party gains a free flank
Economy	Claim unlocks safe City, Port, or Factory value	Payback needs time and protection	The purchase only increases targets

The table is a thinking aid, not a score that the game displays. Mark one target as primary, one as escape, and one as watch. The primary is the only place receiving most attacks. The escape lane keeps you from being sealed in. The watch player is not necessarily an enemy; it is the player whose movement would invalidate your plan. Recheck those labels after a large border changes, a player dies, an alliance warning appears, or a nuke alters terrain.

Do not let the leaderboard replace the scan. Total land can hide a long perimeter, a depleted army, or a disconnected island. Total Gold can hide a low troop cap or an expensive shared Port/Factory counter. A smaller player with a short front and a ready reserve may be harder to remove than a larger player stretched across three borders. Your target is the position, not the number beside a name.

For a live match, convert each signal into a question you can answer in a few seconds. Reachability is “can I touch it without opening a second route?” Geometry is “which single tile changes the border most?” Reserve is “what attack can I answer before the next growth tick?” Opponents is “who becomes stronger if I succeed?” Economy is “does this claim pay for the protection it demands?” If an answer needs a guess, mark it yellow and avoid stacking another uncertain decision on top. Recheck the same five questions after a player is eliminated because the beneficiary can change instantly when a border disappears. On a crowded map, also note whether two rivals are fighting across the route you want; their conflict can be temporary cover, but it can also produce a veteran army at your doorstep. The table works when it reduces attention load, not when it becomes a rigid score that hides a changing map.

Turn the scan into an attack or a stop line

Write a one-sentence hypothesis before clicking: “This claim shortens my east border, leaves 180,000 troops, and denies the only route to my City.” If you cannot name the benefit and the reserve, you are still scouting. The hypothesis creates a falsifiable check. After the attack, ask whether the border shortened, whether the target was actually reachable, and whether a new neighbor gained a better attack than you did. If the answer is no, cancel the next commit even if the first claim succeeded.

Use a reserve floor that fits the position. In an open interior, the floor can be lower because a new border takes time to reach. On a peninsula, island, or narrow corridor, the floor must be higher because one transport or land cut can create an immediate second front. The floor is not a universal percentage. It is the amount needed to answer the fastest credible attack while your economy continues to work.

The attack ratio should express the job. A small tap can test whether a lane is open, finish an isolated neutral tile, or keep troops below cap. A larger send is justified when it removes a border, captures a strategic building, or lands before a rival can reinforce. Repeated taps are dangerous when they prevent the first attack from resolving and leave your force in transit. Let the route and the next check determine the ratio, not a remembered streamer build.

The stop line becomes explicit when any two of these conditions are true: the new border is longer than the old one; the reserve falls below the response floor; the target is not connected to a safe core; the strongest outside neighbor is free to pivot; or the next building would be exposed. At that point, spend on the bottleneck, request a purposeful alliance, or wait for a rival fight. You are not waiting for a perfect board. You are buying time for the board to become legible.

Use the stop line as a commitment gate, not as a post-match explanation. Before sending, state the expected reserve after the move and the first event that would cancel the next send. For example, “I will test the neck, keep 300,000, and stop if the northern army turns south.” That sentence gives you a pre-agreed exit when adrenaline makes a successful first tile feel larger than it is. A stabilizing action should solve one bottleneck at a time: close a corner, protect a City, replace a broken alliance, or let troops refill. Do not combine all four with a single risky claim. When the gate remains closed for several checks, redirect the army to a safer border or use Gold to increase resilience. The point is to preserve options until the outside threat is committed elsewhere. Expansion becomes attractive again only when the original hypothesis still holds and the reserve floor survives the updated travel-time estimate.

Scenario one: a weak neighbor that opens a dangerous flank

Assume you hold 600,000 maximum troops, 420,000 current troops, and 350,000 Gold. Your western neighbor has 180,000 troops and a thin strip of land. The northern player has 700,000 troops, a short border with you, and no active attack. Capturing west looks free because your current force is more than double the target. The map test says otherwise: the western strip adds two exposed corners and gives the northern player a direct path to your level-2 City.

Your first action is not a full send. Claim the tile that closes the western corner, then inspect whether the northern player turns toward the new edge. If the border becomes shorter and the route to the City remains behind one connected block, the attack has a strategic payoff. If the corner opens a second line, stop after the test claim and use Gold for a Defense Post or City placement behind the safe side. The target may remain alive while you improve the shape.

Suppose the first test leaves 360,000 troops and the northern player starts expanding south. Your response floor is 300,000 because the strongest neighbor can reach the corner quickly. A second 150,000 commit would leave only 210,000, below the floor, even though it might finish the weak neighbor. The correct decision is stabilize: hold the captured corner, shorten the border, and wait for the northern player to commit elsewhere. If they attack west, the weak neighbor becomes a buffer rather than a prize.

The numbers are assumptions, not a promise about a specific match. They illustrate why a 240,000-troop advantage does not equal permission to spend 150,000. Check actual travel distance, terrain, notifications, and enemy movement. When the target is finally removed, the best outcome is not merely more land. It is a connected core, a reserve above the response floor, and fewer ways for the northern player to become the next attacker.

This scenario also shows why a test claim should have a measurable purpose. Pick a tile that answers one question, such as whether the northern route is open or whether the western strip is actually connected. Count the troops before and after the test, note the border length, and watch the event feed for the next few moments. If the test creates a second exposed corner, the information is still valuable because it prevents a larger commitment. If it closes the corner and the northern player keeps fighting elsewhere, the same test has converted a weak neighbor into a safe buffer. Avoid chasing the clean elimination while the geometry is unresolved. A player who survives behind your new edge may be useful for one more cycle, giving you time to build, refill, or negotiate. Only finish the target when the finishing move improves the shape and leaves enough force to answer the strongest credible pivot.

Scenario two: a rich route that should be paused

Assume you have 1,200,000 current troops, a 1,500,000 cap, two safe Cities, and 900,000 Gold. A coastal rival owns 450,000 troops and a Port that would improve your trade if captured. Their border touches a long peninsula. A third player is fighting your rival from the other side, so the Port appears available. The tempting plan is to attack now, take the Port, and spend the income on more expansion.

The scan finds three yellow signals. The peninsula creates a longer border than your current core. The third player is not an ally, so their attack can stop at your new edge and turn you into the next profitable target. Your 300,000 troop headroom is useful, but it does not guarantee that the captured Port will produce a safe ship or that the route will stay open. A Port is an economic node and a capture target at the same time.

Choose stabilize. Send a measured force only if it removes the peninsula neck or forces the rival to defend the Port. Keep enough Gold to add the building that solves the immediate bottleneck and enough troops to answer a pivot. Watch the rival’s remaining army and the third player’s direction. If the third player takes the outer peninsula, the rival becomes weaker but your attack becomes less attractive because the new border would face a fresh army.

If the third player exhausts the rival and their own force falls below your response floor, the stop line can move. Capture the Port only when its surrounding land is connected to your core, a fallback City remains safe, and the new border is shorter or protected. Otherwise keep the Gold liquid and use land growth. The right result is not always the richest route; it is the route that still pays after the next diplomatic or military event.

Treat the Port as a conditional investment rather than a prize. Before capture, identify the land tile that protects it, the City that can absorb a retreat, and the player who can reach the coast first. If any of those three answers is missing, keep the Gold liquid and pressure the neck with a smaller force. You can also let the two existing rivals trade troops while you improve the interior, because their next exchange may change both the response floor and the safe direction of attack. When the outer peninsula changes hands, recalculate from the new army positions instead of reusing the old plan. A route that was yellow can become green after the third party is exhausted, or red if the third party emerges with a fresh reserve. The correct pause is active: patrol the approach, watch the Port’s owner, and set a time or event for the next scan so that waiting does not become unexamined drift.

Failure modes and opponent counterplay

The most common failure is ranking-only targeting. A player sees the smallest number and sends troops without checking who can reach the landing tile. Counter this by naming the strongest outside beneficiary before every attack. If that player gains a shorter path or a captured building, the target is not safe. A second failure is perimeter greed: every successful claim feels good, but a chain of claims can create three borders that one reserve cannot cover. Stop when the shape worsens even if the target is weak.

Another failure is notification blindness. Alliance breaks, transport launches, and border attacks may appear in the event feed before the map looks different. Read it during each scan. A fourth is alliance comfort. Normal alliances last 3,000 ticks and warn 300 ticks before expiry, but the icon is not a guarantee of renewal. Treat the warning as a scheduled rescan. Decide whether to renew, reposition, or let the pact expire naturally before your main army is committed.

Opponents can manipulate your scan. A player may tap your border to pull troops away, send a transport as a distraction, or offer an alliance that freezes your only growth lane. They can also wait until you empty your reserve and then attack the captured edge. Your response is to separate contact from commitment. A small test or a visible patrol can gather information. A full attack happens only after the target, outside beneficiary, and reserve floor still pass.

If a rival builds a Defense Post, do not treat its radius as a challenge to your pride. Move around the 30-tile zone when the map allows it, pressure a different edge, or wait for the builder to spend elsewhere. If the rival prepares a Silo or SAM, the signal is economic and temporal: you may need Gold and a protected core before another tile. Read land combat for resolution math, and nuclear deterrence for weapon-specific preparation. This page decides whether to create the contact at all.

Counterplay is strongest when it makes you spend attention before it spends troops. A rival can flash a small attack, offer a tempting pact, or move a transport where you can see it while the real army takes a longer route. Respond by assigning one watcher to the suspected beneficiary and keeping the main reserve behind a connected core. If the opponent builds a Defense Post, compare the cost of walking around its 30-tile zone with the cost of feeding attacks into it. If the opponent retreats, do not assume weakness; the retreat may be a bait that lengthens your border. If an alliance warning appears, make the expiry part of the stop-line sentence and rescan before committing. Your goal is to force the other player to reveal a route or spend a resource before you reveal your own reserve. That discipline turns notifications and small contacts into information instead of invitations to panic.

Mode and map adjustments

In FFA, the outside beneficiary is often the real threat. A conquest that makes you the largest connected block can invite several players even when the local target was weak. Use the FFA opening guide for spawn and first-wave questions, then switch to this whole-board scan once several human borders exist. In Team, replace “who benefits?” with “which teammate can use the opening?” A target is safer when the team can cover the new edge and communicate a reserve floor.

On compact maps, travel times are short and a single new tile can connect two fronts. Rescan after every claim. On large continental maps, the same attack may be safer because a distant neighbor cannot pivot immediately, but long borders can still drain attention. On straits, count the neck rather than the land area. One captured tile can decide whether a route is a buffer or a doorway. On islands, a Port can be both income and the only repair or transport anchor, so the stop line must include water access and a ground fallback.

If Ports or transports are disabled, remove naval reachability from the scan and give more weight to land corridors, Cities, and Defense Posts. If alliances are disabled, every border must stand on its own; raise the response floor where a pact would otherwise buy time. If Peace Time is active, use it to improve geometry and infrastructure, not to assume that a bad border will become safe. If Water Nukes can change coastlines, treat each blast as a topology event and run a fresh scan before spending.

Doomsday and Overtime also change what “safe” means. Doomsday rewards survival and usable territory rather than an endless perimeter. Overtime can make a stable lead more valuable than a risky conquest, while a challenger may need a timed opening. The current guide does not replace those mode rules. Read winning Overtime, Doomsday Clock, and map strategy when the lobby changes the win condition or map topology.

Mode changes should alter the priority of the five signals, not erase the framework. In a team lobby, write the teammate who can reinforce the threatened tile and the delay before that help arrives. In a no-alliance lobby, assume every warning is real until the border itself proves safe. On an island, a Port route may be the only way to answer a transport, so a modest land advantage cannot compensate for losing water access. On a strait, count how many defenders can stand behind the neck and whether a single cut disconnects the core. On a large map, add travel time to the reserve floor rather than lowering it automatically; a distant enemy is slower, but a long border can still hide a second attack. After a Water Nuke changes the coastline, discard old route labels and run the scan from the new graph. The framework remains useful because it asks what changed and who benefits before it asks for another claim.

Next reading and a repeatable log

End every scan with four fields: state, threatened tile, reserve floor, and next check. Example: “stabilize; north neck; 300,000 troops; check the alliance warning in 300 ticks.” If the next check shows the route is safe and the outside beneficiary is committed elsewhere, change to expand. If it shows a new border, a transport, or a reserve below the floor, change to stop. This log is short enough to use during a live match and specific enough to review afterward.

Use economy fundamentals when the scan says Gold or troop cap is the bottleneck. Use alliances and betrayal when an agreement changes your border timing. Use recovery playbook once a core is already lost and the question is how to survive the damage. Use island defense when the threat is a transport or disconnected coast. These pages are adjacent answers, not substitutes for deciding whether the next expansion is worth creating.

The official v0.33.12 boundary behind this guide is the released OpenFrontIO Release and tagged Config.ts, AttackExecution.ts, AttackImpl.ts, AllianceImpl.ts, and WinCheckExecution.ts. If a later release changes a clock, multiplier, or win condition, update the scan table, scenarios, and stop sentences together.

The practical rule is simple: expand to improve shape, stabilize to protect options, and stop before a weak target turns your position into someone else’s best move. The player who sees the next border before clicking it controls more of the match than the player who merely owns more tiles.

When the scan identifies a pocket worth closing, continue with Annexation and enclosure to test shoreline contact, owner credit, and the reserve needed for the final edge.

Keep the log short enough to survive combat pressure. Four fields are sufficient when each has a concrete value: state, threatened tile, reserve floor, and next check. Add one optional “unknown” note if a fogged reserve or hidden route drives the decision. At the next check, change only one field at a time so you can tell why the state moved from stabilize to expand or stop. After the match, compare the written hypothesis with the actual result: did the border shorten, did the outside beneficiary pivot, and did the reserve floor protect the core? That review improves your thresholds without turning them into universal numbers. Pair this page with the adjacent guides according to the bottleneck: economy for cap and Gold, alliances for timing, land combat for contact resolution, recovery for a lost core, and island defense for transport threats. The repeatable loop is scan, state the hypothesis, test one tile, recheck the beneficiary, then commit only when the shape and reserve still agree.

When that scan ends at a Hard or Impossible border, continue with Nation Pressure to evaluate v34’s valuable-target branch, name a stop line, and time one bounded counterattack.