OpenFront Tall vs Wide: Turn a Safe Economy into Territory

Direct answer: stay compact only while safety is buying your next route

Play tall while a short border, protected City, useful Port, or SAM network is producing a specific expansion option. Go wide when you can secure a second land foothold without emptying the core, or when the territory clock will reward a rival before another upgrade pays. Buildings and Gold create capacity; OpenFront awards ordinary FFA and Team wins through owned land. The v0.33.14 decision is therefore to convert safety before it becomes isolation.

“Tall” and “wide” are useful player labels, not game settings. A tall position owns relatively little land but concentrates capacity, income, naval access, or nuclear protection in a defensible core. A wide position owns more land or several meaningful footholds, gaining routes and territory share while accepting more borders. Neither posture receives a hidden bonus. The engine counts tiles, completed City levels, units, relationships, and mode settings. Your task is to decide which posture gives the next reversible advantage.

Use one sentence to keep the goal honest: my core is buying access to land, not replacing land. A safe island can preserve a player, a Port can support trade and a Warship screen, Cities can raise troop capacity, and a SAM can protect the investment. A Transport Ship launches from reachable owned coast without requiring a Port. None of those icons adds territory share by itself. In released public FFA, the leading player wins only when their owned share is strictly above the current threshold, calculated over land that is not fallout. Since v0.33.13, every ordinary public FFA enables Overtime; after minute 30 the base 80% threshold falls by one point every 30 seconds. v0.33.14 changes modal scrolling, not that rule.

The practical decision framework is L-A-N-D: Liquidity, Access, Need, Deadline. Liquidity asks what Troops and Gold remain after the move. Access asks whether the destination creates a usable border or only a stranded patch. Need asks which bottleneck the move solves: cap, income, safety, position, or actual territory. Deadline asks what happens if you wait: a rival closes the coast, an alliance expires, a transport window disappears, or Overtime reaches the leader. If any answer is unknown, keep the next move small enough to reverse.

Start with a compact core when it reduces simultaneous threats and still has a route outward. Do not confuse compact with passive. A tall phase should contain an observable preparation: refill toward useful troop headroom, finish one City, reserve a transport force, move a Warship onto the crossing lane, or negotiate a temporary quiet border. Name the trigger before spending. “After the City completes, I will take the western neck if 300,000 Troops remain” is a plan. “I will keep upgrading until I feel strong” is a delay with no completion test.

Switch toward wide when the route has both an entry and a follow-up. A tiny overseas tile is not automatically strategic depth. It becomes useful when it can take neutral land, touch a vulnerable rival, preserve a Port, or survive until the next shipment. On a continent, the same test applies to a salient: if the new border cannot be supplied or shortened, more color on the map may reduce options instead of adding them. The best conversion often starts with one modest foothold, not a full treasury dump.

This guide owns that conversion decision. Economy Fundamentals explains how Gold, Cities, Ports, and Factories work. Island Defense explains how to hold a coast and stop a landing. Threat Assessment chooses the safest target. Winning Overtime calculates the live threshold. Here those answers meet at one question: when has the safe core done enough, and which piece of land should it buy next?

Tall and wide change options, not hidden statistics

OpenFront does not define a Tall mode, a Wide bonus, an island-income multiplier, or a direct statistical penalty for owning two disconnected cores. The useful distinction is operational. A tall posture compresses valuable assets behind fewer reachable approaches. A wide posture distributes access across more land and often more regions. The labels describe what the opponent can reach and what you can act on; they do not alter the formulas. That boundary matters because community advice often mistakes a successful map position for a universal mechanic.

Land contributes to troop capacity through a sublinear formula. For a normal human without infinite Troops, the released v0.33.14 configuration computes the non-City portion as 2 * (tiles^0.6 * 1,000 + 50,000). Each completed City level adds another 250,000. Because the tile exponent is 0.6, doubling land does not double troop cap. Land still matters for access and the win share, but the formula prevents “take any land at any cost” from being a complete strategy. A City can add a large block of capacity to a small core, while more land adds diminishing cap returns and more possible borders.

Current Troops also matter. Per-tick growth begins from 10 + troops^0.73 / 4 and is multiplied by 1 - troops / maxTroops. Growth slows as the army approaches its cap. Capturing land or completing a City raises headroom, but it does not instantly fill that headroom. A wide move made with an empty reserve can therefore create a larger theoretical cap and a weaker immediate position. A tall player who is already near cap may need a route now; a tall player far below cap may gain more by waiting briefly, unless the map opportunity has a hard deadline.

Structures provide different options. The first Port or Factory in their shared cost ladder costs 125,000 Gold; later purchases rise with the combined count until the one-million cap. A Port can support trade, Warships, and repair when the water component is useful; it is not required to launch a Transport Ship. A Factory can create trains when it has valid stations. A City adds cap. These are not interchangeable victory points. When a second Port merely duplicates a safe local trade or fleet route, it deepens the same core. When it supports a Warship screen beside a live mainland opportunity, it can protect the bridge from tall to wide without being the bridge itself.

Territory is not free strength either. The same tagged combat configuration applies large-attacker reductions after 100,000 owned tiles, so an enormous player does not gain unlimited attack efficiency merely by painting the map. Terrain, defensive structures, army ratios, and contact geometry still decide the cost of a push. The strategic value of width is optionality: another coast, another neighbor, another route to a collapsing player, or enough share to cross the win threshold. If a new region adds none of those, its upkeep may be larger than its option value.

Disconnected positions have no automatic mutual reinforcement. Troops belong to the player total, yet access still follows the map: a land attack needs a reachable border, and an overseas move needs an allowed, navigable path from owned coast. There is also a map-shape boundary: the tagged player update can auto-transfer a disconnected cluster enclosed by one non-friendly player, while clusters touching coast or the map edge skip that inland-enclosure check. Coastal survival does not make a patch safe from a Transport Ship landing. Judge a second position by time-to-contact and enclosure geometry, not by visual distance on the minimap.

The released win rules make the distinction concrete. Ordinary FFA compares one player’s owned tiles with the non-fallout land denominator. Ordinary Team sums the living team members’ tiles and uses a 95% base threshold. Ranked 1v1 can finish when only one connected human remains, while ranked 2v2 can finish when only one living connected team remains; ranked timers can also select the current land leader. Do not transfer one posture blindly across these modes. A compact fortress may stall an FFA yet lose the shrinking public Overtime race, while a compact ranked partner may be correct if the other teammate already supplies land and the pair can eliminate the last opposing side.

Treat every icon as a verb. A City should refill a named reserve. A Port should serve a named trade, patrol, or repair route. A Factory should serve named stations. A SAM should protect a named asset during a named window. If you cannot complete the sentence, the purchase is probably reinforcing the appearance of strength rather than changing the next decision. That is the central audit for tall play: safety must produce an action the map can recognize.

Use L-A-N-D before every expansion conversion

Run Liquidity, Access, Need, Deadline in that order. It turns a vague question such as “am I strong enough to expand?” into four claims that can be checked on the map. The order is deliberate. A destination can be perfect and still be wrong if the launch leaves the core undefended. A treasury can be huge and still be strategically locked if no coast, border, or relationship reaches useful land. Write one short answer for each letter before committing the first irreversible move.

Liquidity is the post-move balance, not the balance visible before the click. Count the Troops placed into an attack or transport, the Gold committed to a Port, ship, City, or coverage, and the recovery time before those resources can answer another threat. If the plan needs two stages, reserve both stages. A foothold that receives the first transport but cannot fund the second wave is not a bridge. The same is true on land: winning the first border while having no reserve for the new contact converts a compact defense into an exposed salient.

Access asks what the new position can reach after it exists. Give the destination one of four labels: route, anchor, prize, or patch. A route reaches another theatre. An anchor can survive and receive follow-up. A prize captures a structure or meaningful land but may be temporary. A patch owns tiles without opening a useful next action. Prefer a route that can become an anchor. Take a prize only when its value covers the retreat risk. Avoid paying a strategic treasury for a patch.

Need prevents unrelated upgrades from substituting for the real bottleneck. If the problem is low cap, a City or safe land may help. If the problem is no route, another City does not create access. If the problem is a shrinking FFA threshold, a fourth defensive upgrade may preserve the core while the leader wins elsewhere. Name exactly one constraint: “I need a second coast before the northern alliance expires,” “I need 250,000 additional cap before the push,” or “I need 1.8 percentage points of land before the next Overtime step.” Then compare moves against that sentence.

Deadline is the event that removes the option. Time is not only the clock in the interface. An opponent may absorb the target, a teammate may close the path, a Warship may leave the lane, a temporary alliance may expire, or your own army may refill so far that additional waiting yields little growth. In public FFA, Overtime provides a formal deadline after minute 30 because the required share falls by a whole point every 30 seconds. If the leader will cross without moving, “wait for more economy” is an active decision to let the game end.

Use a two-key rule after the four checks: commit only when Access plus one other letter is green. Access is mandatory because this guide is about conversion into territory, not another internal upgrade. Liquidity plus Access describes a safe bridge. Access plus Need describes an emergency breakout, where the reward may justify a thin reserve. Access plus Deadline describes a timed race. If Access is red, remain tall and repair the route problem instead of pretending the next purchase is expansion.

Also define the abort. “Return if the landing has no adjacent neutral tile,” “stop if the core reserve falls below 300,000,” or “cancel if the leader gains another point before departure” gives the plan an exit. Transported troops can be lost, structures can be captured, and a ground attack can create a new hostile border. A prewritten abort is more valuable than a universal percentage because it ties the reserve to the actual route.

Finally, rerun L-A-N-D after the first capture. Access can change immediately: the patch may reveal a broad neutral corridor, a Defense Post, a second opponent, or no follow-up at all. Liquidity changes with casualties. Need may already be solved. Deadline may move because another player gained land. Expansion is a chain of checkpoints, not a declaration that the entire match is now “wide.”

Scenario one: turn an island treasury into a mainland anchor

Assume a normal public FFA under v0.33.14. You own a compact island core with 4,000 tiles, one completed level-1 City, 640,000 current Troops, one useful Port, a Warship screening the direct lane, and 900,000 Gold. The mainland target is neutral coast beside a weakened player’s outer border. A 75-tile water route reaches it. The core has no hostile land border, the destination has 2,000 plausible neutral tiles behind the beach, and no Water Nukes or disabled-unit modifier changes the map. These numbers are scenario assumptions, not a named-map guarantee.

The tagged cap formula estimates about 639,912 maximum Troops for 4,000 tiles plus one City, so the example army is effectively full. If the player eventually reaches 8,000 total tiles while keeping that one City, the same formula gives about 789,424 cap. Doubling land therefore adds roughly 149,512 cap rather than doubling the army. That is still useful headroom, but it is not the main reason to cross. The stronger prize is access: the mainland anchor can reach neutral land and a rival whose territory may become available, while the island alone cannot capitalize before another player arrives.

Run L-A-N-D. Liquidity: choose a first wave of 128,000 Troops, equal to the tagged default boat amount of one fifth in this exact scenario, and reserve the rest in the core. Transport Ships cost no Gold and need no Port, but the committed Troops can be lost and the optional Port and screening fleet were paid for separately, so the operation is not free. Keep the 900,000 Gold uncommitted until the beach proves it can survive. Access: the destination is a route with a chance to become an anchor because it has neutral follow-up and a live rival border. Need: the island already has cap and safety; it lacks timely land access. Deadline: the weakened player or another mainland neighbor can close the neutral coast, and public FFA Overtime will eventually reward land rather than stored Gold.

The first transport should test the beach, not announce a total migration. On arrival, take the smallest connected neutral arc that lets the foothold see both the rival border and a fallback shore. Do not immediately build because the first contact may reveal a Warship, Defense Post, or third player. If the foothold remains connected after the next map scan, send a second wave or spend on the structure that solves its actual bottleneck. A City is useful only if the anchor can keep the new cap. A Port is useful only if local trade, Warship production, or repair supports the route; it does not unlock the next transport.

The opponent’s best counter is to let the transport land, then attack the thin patch before reinforcement arrives while a second player pressures the island’s Port. That counter attacks Liquidity and Access at once. Your response is to keep the Warship on the original lane, retain a core reserve, and abort the mainland push if the beach has no neutral follow-up. A failed 128,000-Troop test is painful but bounded; sending all 640,000 would turn one lost anchor into elimination.

Suppose the foothold gains 2,000 tiles but immediately touches two healthy rivals and no neutral corridor remains. Reclassify it from anchor to prize or patch. Do not spend 900,000 to defend it merely because it is new. Retreat or accept the loss while the island remains coherent. Suppose instead the 2,000 tiles open a protected neck and the weakened rival begins another war. The route is now an anchor: reinforce enough to hold the neck, then use Threat Assessment before choosing the rival. The conversion succeeds when the second position creates a repeatable land decision, not when the first boat merely reaches shore.

Map and mode assumptions matter. On a Compact archipelago, 75 tiles may represent most of the useful sea and the response window is shorter. If Transport Ships are disabled or no navigable path reaches a legal destination from owned coast, this conversion is impossible; disabling Ports alone does not prevent it. The player must then seek a land route, a different starting posture, or another lobby. In Team, the foothold can serve team territory even if another player funds the fleet screen, but the team still needs a named owner for the route. The numeric lesson remains narrow: full cap plus stored Gold is the moment to test access, not evidence that an island economy can win without leaving.

Scenario two: leave a mainland fortress before Overtime closes the game

Assume a public FFA at 41:00. Your compact mainland position owns 31.0% of non-fallout land, the leader owns 56.4%, and the other surviving players divide the rest. You have one protected City cluster, 1,100,000 Troops, 1,600,000 Gold, two quiet borders, and one narrow border with a 9.0% rival. A second 3.0% player sits behind that rival but does not touch you. No configured timer finishes earlier. These values are explicit teaching assumptions; they do not claim a fixed public map size or a guaranteed diplomatic response.

At minute 41, public FFA Overtime has completed 22 half-minute steps after its minute-30 start, so the threshold is 58%. The comparison is strict: 56.4% is not yet enough. If the map does not change, minute 41:30 lowers the threshold to 57%, and minute 42:00 lowers it to 56%. The leader’s 56.4% would then cross and win. Your useful deadline is therefore under one minute. Another City, SAM level, or banked million may improve local strength but cannot stop that crossing unless it enables immediate territory denial.

Run L-A-N-D. Liquidity: the 1.1 million army must survive contact with the 9.0% rival and still answer the leader. Do not send all of it. Access: the rival’s land reaches the 3.0% player and may create a route toward the leader; a different quiet border does not. Need: the actual bottleneck is not income or cap. It is changing the leader’s share or your route before minute 42. Deadline: the visible Overtime step is decisive. Access plus Need plus Deadline are green, so remaining fully tall is no longer a winning line.

Use a two-part move. First, make a bounded attack that can take the connecting neck from the 9.0% rival without exposing both quiet borders. Second, coordinate pressure on land the leader owns or on a player the leader is about to absorb. Capturing only the small rival can increase your own share while leaving 56.4% unchanged, so it may fail to stop the clock. The better conversion creates contact or denies the leader’s next easy gain. Land Combat should set the attack amount; this guide sets the reason and the deadline.

Suppose you take 1.2 percentage points from the small rival by 41:35, reaching 32.2%, but the leader stays at 56.4%. You have improved your position and still lose at 42:00 under the assumptions. That is a patch, not sufficient access. Suppose instead the neck lets you and another player take a combined 0.8 points directly from the leader before 42:00, reducing them to 55.6%. They no longer cross the 56% step, buying another 30-second interval. The figures are a scenario ledger, not a promise that combat resolves at a fixed rate.

The leader’s best counter is to attack the smallest accessible player while you spend time on the neck, or to force you to defend the compact core with a nuclear threat. Your answer is not to abandon all protection. Preserve the structures that keep the route viable, but classify every expense against the deadline. A SAM that protects the only attacking corridor can support conversion. A remote upgrade that does not affect the next 60 seconds is deferred. Gold is valuable here because it preserves choices, not because the scoreboard counts it.

If the neck attack cannot finish before the step, admit that the winning line depends on another player’s action or on forcing the leader to spend Troops. Do not relabel a doomed delay as patience. The completion test is observable: before 42:00, either the leader’s share is below the next threshold, their acquisition route is broken, or your new access can contest the land that would cross it. If none is true, the tall fortress may survive the battle and still lose the match.

In ordinary public Team, do not reuse the 80% Overtime schedule: the base team threshold is 95%, public Team does not receive the ordinary public FFA Overtime default, and team tiles are summed. In ranked 1v1 or 2v2, elimination and the 10- or 15-minute map timer can finish the game before a broad territorial conversion makes sense. The lesson is not “always expand at minute 41.” It is “identify the real finish condition, then make stored strength touch it before the deadline.”

Failure modes and how opponents punish a safe core

The first failure is fortress accounting: counting structures, Gold, and intercepted nukes as if they were territory. A player can own the most expensive position and still trail the land condition. Opponents punish this by avoiding the fortress, absorbing softer players, and letting the threshold move. Fix it by adding a territory line to every economic review: current share, leader share, reachable gain, and next formal or positional deadline.

The second failure is cap worship. A City adds 250,000 cap per completed level, but cap is not current Troops, access, or land. Building while far below the existing cap can buy empty capacity. Building at full cap can be correct if the next fight needs the additional headroom, but it still requires time to refill. An opponent punishes cap worship by attacking during construction or closing the target before the new army exists. State both cap after completion and expected usable reserve before choosing the City.

The third failure is the ornamental Port. The shared Port/Factory ladder rises as more of those structures exist. A Port that serves no valuable trade partner, Warship patrol, or repair route deepens the same posture at increasing cost. It does not unlock Transport Ships, so never buy one solely because you intend to cross. A rival can allow this spending, then blockade the only useful exit. Give each Port a route name and stop upgrading when that route is no longer the bottleneck. Use Port versus Factory for the investment comparison.

The fourth failure is all-in colonization. The tall player finally recognizes isolation and sends nearly every troop to the first distant coast. The opponent waits for the transport to commit, takes the beach or strikes the empty core, and turns one route into two losses. The correction is a probe-anchor-reinforce sequence. The probe tests the shore. The anchor secures follow-up. Reinforcement arrives only after the map still supports the original Access claim.

The fifth failure is patch attachment. After paying for a crossing, players defend the first colored tile because abandoning it feels like wasting the investment. Opponents exploit that sunk cost with repeated small pressure. Reclassify the foothold after every contact. A patch with no follow-up can be released. A prize may be held only until its structure or position repays the risk. An anchor deserves reinforcement because it preserves future decisions.

The sixth failure is safe-player diplomacy. A compact player accepts alliances on every border, then discovers that no ordinary land route remains when conversion becomes urgent. Alliances may provide safety, but they can also turn access into dependence on expiry, betrayal, or transport. Keep one declared expansion lane or a second-region plan before becoming fully enclosed. Diplomacy and Betrayal owns alliance timing; L-A-N-D checks whether the resulting map still offers a route.

The seventh failure is nuclear substitution. Nuking a leader can cut Troops, structures, or usable land, but the strike does not automatically transfer territory to you. A third player may capture the damaged area and win. Opponents punish a remote nuclear fortress by forcing it to spend while maintaining their own land routes. Pair a strike with a reachable capture plan. If nobody on your side can touch the target, the weapon may create a kingmaker outcome rather than a winning conversion.

The eighth failure is deadline denial. Players see Overtime, a closing coast, or a collapsing rival and continue optimizing because the core still feels safe. The opponent’s counter is simply to complete the irreversible event. Put the deadline in clock or map terms: “42:00,” “before the alliance warning ends,” “before the northern player touches the coast,” or “before the Warship leaves repair range.” Vague urgency causes panic; a named deadline allows a bounded move.

The ninth failure is overexpansion after success. A good anchor opens several targets, and the formerly tall player attacks all of them. Wide posture then becomes unmanaged exposure. The tagged combat rules still consider terrain, defense, relative army, and very large ownership; width is not permission to ignore reserves. Choose one anchor frontier as the growth route, one as the holding border, and one abort path. The goal is a portfolio of options, not the maximum number of active attacks.

Opponents will attack the conversion, not the label. They will close neutral coast, threaten the original City, contest the Warship lane, offer an alliance that removes your only target, or feed land to the current leader while you fight elsewhere. L-A-N-D makes those counters legible. Liquidity answers the core strike, Access answers the closed route, Need rejects distractions, and Deadline prevents endless rebuilding. When two letters turn red, pause the conversion and preserve the option that can be reopened fastest.

Adjust the conversion for map scale, FFA, Team, and ranked play

The L-A-N-D questions stay stable across lobbies, but their answers do not. Start by reading the finish condition rather than carrying a favorite build from one mode to another. In ordinary public FFA, one player’s owned tiles are compared with all non-fallout land and the comparison must be strictly above the active threshold. The ordinary public FFA playlist enables Overtime: after minute 30, its 80% base drops one percentage point every 30 seconds. That makes Deadline increasingly formal. A compact player can remain hard to eliminate and still lose because the leader needs less land at the next step.

FFA also changes diplomacy around a second foothold. Every anchor creates another neighbor who may prefer the current balance. A mainland player can allow an island economy to land, then make the new patch expensive while continuing to trade with the leader. Before crossing, identify not only the landing target but the external beneficiary. If the beneficiary can gain more from your fight than you can, reduce the probe, delay the permanent structure, or choose a route that touches the leader sooner. Wide play is useful when it creates leverage; it is harmful when it simply offers two fronts to the same coalition.

Ordinary Team uses a different accounting rule. The released win check sums the living team’s owned tiles, and the base threshold is 95%. The standard Team playlist does not inherit the ordinary public FFA Overtime default. Your personal posture can therefore be compact while the team as a whole is wide. One teammate may keep Cities, a SAM umbrella, and the fleet reserve while another holds the growth frontier. This is not permission to become irrelevant: give the compact player a delivery obligation such as screening the sea lane, preserving a trade-and-repair Port, donating a named reserve, or reinforcing an anchor before a named contact. A role without a route and deadline is still fortress accounting at team scale.

Ranked Compress and Normal lobbies add shorter, explicit timers: 10 and 15 minutes respectively in the v0.33.14 playlist. The timer can award the game to the current territory leader, so a late economic investment has less time to compound. Ranked 1v1 can also end when only one connected human remains, and ranked 2v2 when only one living connected team remains. Under those conditions, a narrow elimination route may outrank a broad colonization plan. Recompute Need as either land lead, survival, or final-team elimination; do not assume the public FFA Overtime table is the ranked clock.

Map scale changes travel and response time even when formulas stay the same. On Compact, a small coast may be the entire strategic exit, and a 30-second delay can let a neighbor seal it. A probe must be smaller in absolute Troops only if that smaller force can still establish contact; the game does not grant a special Compact discount. On Normal or larger landmasses, an anchor may need more time to reach useful contact, while a broad neutral corridor can repay the delay. Measure route length, next contact, and reinforcement time from the actual map instead of calling every island safe or every continent wide.

Archipelagos raise Access above almost everything else. A reachable owned coast and legal Transport Ship path can turn one defended island into a network; a Port and Warship screen may support the route but are not launch requirements. Disabled transports or blocked water can remove that line entirely. Continental maps make border geometry more important: a second front may be one captured neck rather than another landmass. Nuclear-enabled maps increase the value of distributing critical structures, yet a remote SAM or silo is only useful if it protects a route that matters. Unit settings change available verbs; they do not change the land-based finish condition.

For a practical mode check, write four entries before the move: winner counted by, finish time, team land owner, and route owner. If the winner is counted by individual land and the finish time is shrinking, conversion should directly alter the leader’s share or your access. If team land is pooled, assign the anchor to the player who can reinforce it and assign the core to the player who can preserve the shared route. If elimination can finish the match first, test whether the next contact threatens the last opponent rather than merely increasing distant capacity.

The invariant is simple: posture is local, victory is global. You may be tall on one island and wide across two operational regions; a team may be wide while one member remains compact; a ranked player may expand only far enough to create the final elimination contact. Use the lobby settings to define Deadline, the map to define Access, the treasury and army to define Liquidity, and the actual win obstacle to define Need. The labels are valuable only when they make those four answers easier to see.

Keep a conversion ledger and verify the rule boundary

A good tall-to-wide decision can still lose, because opponents act and combat is uncertain. Evaluate the decision by what it knew, what it bought, and whether its abort worked, not only by the final color of the map. Keep a compact ledger at three moments: before commitment, after first contact, and at the next deadline. Each entry should be short enough to record between games but precise enough to falsify the plan.

Before commitment, record current owned share, leader or opposing-team share, current Troops and cap, Gold reserved, route, intended anchor, and deadline. Then write the four L-A-N-D answers in one line. For example: L 512k remain; A western coast reaches neutral neck; N second region; D coast closes after blue's war. Avoid hidden adjectives such as “enough” or “soon.” If you cannot attach a number, map object, or visible event to the statement, mark it unknown and shrink the first move.

After first contact, record what the destination became: route, anchor, prize, or patch. Count new hostile borders, remaining reserve, follow-up land, and the next reinforcement path. This is where the plan is allowed to change without becoming a failure. A route that reveals no safe tile should be abandoned under the declared abort. A prize that captures a useful Port may repay itself without becoming a permanent second core. An anchor that opens neutral land and one manageable rival justifies the next wave. The ledger prevents sunk cost from rewriting the original Access claim.

At the deadline, compare the observable completion test. In the island scenario, success meant a repeatable mainland land decision while the island stayed defensible. In the 41:00 scenario, success meant reducing the leader below the next threshold, breaking their acquisition route, or creating contact capable of contesting that land before 42:00. “I owned more afterward” is not enough if the match condition did not move. Write which L-A-N-D letter was wrong and adjust only that assumption for the next game.

Ledger moment	Evidence to record	Continue when	Abort or redirect when
Before commitment	Troops after move, Gold reserve, route, target, deadline	Access plus at least one other L-A-N-D letter is green	Access is unknown or the core cannot answer one counterattack
After first contact	New borders, neutral follow-up, reinforcement time, destination class	The route became an anchor and Liquidity still covers the second move	The landing is a patch, the route closes, or two letters turn red
At the deadline	Land shares, leader route, surviving core, next reachable gain	The finish condition moved and another reversible option remains	Stored strength never touched the win condition

The numeric rules in this guide have a narrow evidence boundary. They were checked on 2026-09-06 against the official OpenFront v0.33.14 Release and the corresponding tagged sources for population, structure costs, and troop cap, win checks, public and ranked playlists, transport legality, and disconnected-cluster cleanup. The release itself only documents the shipped modal-scroll fix; the tag sources are necessary to verify unchanged systems used by the decision examples. Community discussions and videos in the research pack identify the player problem and vocabulary, but they do not establish a troop formula, a guaranteed route, or a universal reserve percentage.

That separation matters after an update. If a future Release changes the win threshold, Overtime timing, City cap, transport amount, structure ladder, or playlist timer, keep the four questions and recompute the examples. If only a map changes, preserve the formulas and remeasure route length, contact geometry, and deadline. If community advice offers a fixed percentage, treat it as a hypothesis until the current tag or a controlled game verifies the underlying mechanic. A decision framework should survive version changes because its inputs are explicit.

Continue reading according to the letter that failed. For Liquidity, return to Economy Fundamentals and Population Growth. For Access, use Island Defense, Map Strategy, or Annexation and Enclosure. For Need, compare Port versus Factory and Threat Assessment. For Deadline, calculate the live finish through Winning Overtime. The next page should repair one failed input, not restart a generic strategy tour.

The final rule is deliberately testable: remain tall only while the core is producing a named route, reserve, or timed denial that advances the actual finish condition. Begin widening with a bounded probe once Access and one other L-A-N-D letter are green. Reclassify the new position after contact, reinforce only an anchor, and stop when two letters turn red. That procedure will not guarantee a win, but it turns “I felt safe” into a sequence another player can inspect, repeat, and improve.