GUIDES
OpenFront No Alliances Mode: FFA Borders, Targets, and Survival
Play an OpenFront lobby with alliances disabled: read every border, avoid becoming the easy dogpile, preserve trade, and convert a lead without a ceasefire button.
Direct answer: replace ceasefires with strength, distance, and a second route
In a No Alliances lobby, plan as if every non-teammate border can become hostile on the next tick. Keep enough troops to make attacking you more expensive than attacking somebody else, expand through targets that shorten rather than multiply your exposed borders, and never spend your whole reserve on a war whose winner becomes the next easy target. You cannot negotiate safety with the alliance button, so you must manufacture it through position.
That does not mean hiding until everyone else is large. A player who waits with 50,000 troops while neighbors clear Bots, take Cities, and widen their income often looks safer for only one minute; afterward that player is the cheapest land on the board. The correct opening is active but bounded. Take nearby neutral and Bot land while the exchange is favorable, build population before the cap stalls growth, and leave a visible reserve after every click. Your displayed troop count is a deterrence signal as well as a resource. When two neighbors compare targets, the one that just emptied itself usually loses the comparison even if its first war was efficient.
Use three layers of safety. The first is balance: do not let any one neighbor hold an obvious local advantage without a response. The second is geometry: prefer one broad, defensible contact and an independent exit over three thin fingers touching three opponents. The third is option value: keep Gold and troops that can become a City, Defense Post, counterattack, Boat, or route change after another player commits. No Alliances removes the formal ceasefire, but it does not remove third-party incentives. A neighbor may still ignore you because another target is weaker, farther overextended, or blocking a better route.
| Board signal | What it means without alliances | Immediate decision |
|---|---|---|
| Your troop display falls below two bordering players | You are a cheap shared target | Stop the side war, rebuild, and narrow the border |
| One neighbor begins a deep attack elsewhere | Their home reserve and density may fall | Prepare a bounded counter, but wait for commitment |
| A Port or Train partner stays trade-eligible | Economic contact can continue without an alliance | Protect the route; do not confuse trade with safety |
| An embargo appears | That specific trade link is unavailable | Recalculate payback and use a second station or land income |
| You lead in territory near the win line | Every remaining player benefits from stopping you | Convert Gold into defense and close the shortest route |
The practical test is simple: after each expansion, identify who can attack you, how much you would still hold after your next click, and where you go if that route closes. If you cannot answer all three, do not add another frontier. The threat assessment guide helps scan the whole map, while land combat handles a border already fighting. This page owns the missing decision between them: how to remain unattractive, flexible, and capable of winning when no temporary alliance can turn a dangerous edge friendly.
Know exactly what the zero-minute setting removes and what remains
In v0.34.12, the host’s Custom Alliances control accepts one to fifteen minutes, and a value of zero is labeled as disabling alliances. The configuration treats customAllianceDuration === 0 as disableAlliances() === true; it also honors the older disableAlliances boolean for legacy configurations. Player logic then rejects every alliance request. There is no pending request, acceptance, extension, natural expiry, manual break, or alliance-created friendly border to manage. The game configuration and player implementation establish that boundary.
The setting does not turn every other system off. Fixed teammates remain teammates because team membership and timed alliances are separate. The game treats players on the same fixed team as friendly even when alliance requests are disabled. A Team lobby with a zero-minute alliance duration is therefore not a pure everyone-versus-everyone contest: your assigned teammate can remain non-attackable under ordinary friendly checks, while every player outside that team lacks a temporary treaty path. Before spawn, read both the game mode and team count. The phrase “No Alliances” alone does not tell you whether fixed teams exist.
Trade is separate too. A player can trade with another living player when neither side has embargoed the other; an active alliance is not a prerequisite. Ports and Train stops can therefore keep paying across a politically dangerous border. That income is useful, but it is not protection. The same player whose Port receives your Trade Ship may attack your coast, embargo you, or lose the station to somebody else. Build the route only if its return survives those possibilities. Trade versus piracy owns the trade-mode switch; this guide treats trade as one input in border risk.
Host switches for donating Gold or troops are also independent. If donation is enabled, the recipient still has to satisfy the game’s friendly check, which normally means a fixed teammate or an active ally. With alliances disabled in FFA, there are no new allied recipients, so do not budget around strangers donating. In a fixed-team lobby, teammates may remain eligible. Embargo controls remain relevant because they govern trade rather than friendliness. Nuclear weapons, Boats, Warships, Cities, Factories, Ports, Defense Posts, Overtime, and Doomsday likewise keep their normal rules unless the host separately changes or disables them.
No Alliances also removes a defensive trick: accepting an alliance cannot recall attacks or cancel relevant in-flight nuclear weapons because no acceptance can occur. Treat every launch and land commitment as something position must answer. An emoji, target marker, shared enemy, or parallel attack may reveal another player’s incentive, but none creates engine-enforced safety. Use those signals to predict, never to subtract a border from your threat count. The reliable ledger is mechanical: fixed teammate, current embargo and trade eligibility, actual attacks, actual units, and the live victory state.
This distinction prevents the two most expensive mistakes. One is assuming “alliances disabled” means trade disabled and abandoning profitable neutral routes. The other is assuming a trading neighbor is effectively friendly and emptying that coast. Read the lobby settings once, then classify every relationship by what the engine actually protects. No button means no treaty; it does not mean no economics, no teams, and no temporary alignment of interests.
Run the BORDER check before every expansion
Use BORDER as the repeatable decision frame: Balance visible armies, Observe commitments, Reduce contacts, Diversify routes, Exit losing exchanges, and Recalculate the win line. The order matters. Players often begin with a desired target and search for reasons to attack it. BORDER starts with the board that exists, then asks whether the attack leaves a better board after the first capture. It is meant to run in fifteen seconds while troops regenerate, not to predict the entire match.
Balance visible armies. Compare your current troops with every player that can reach you, not only the player you want to fight. Include the reserve that each opponent will retain after their visible attacks. You do not need to be largest, but you should avoid being simultaneously cheaper than two adjacent alternatives. If a 900,000-troop neighbor and a 750,000-troop neighbor border your 620,000, sending 250,000 elsewhere broadcasts a 370,000 target. A City or short neutral capture that raises future capacity can be worth more than starting that war.
Observe commitments. A displayed number is not the whole threat. Watch active attacks, Boats already launched, Warships moved away from home, construction, and border density. The best No Alliances window is not “my neighbor is smaller”; it is “my neighbor has committed enough elsewhere that the route can be taken and held before a third party benefits.” Let the first attacker pay to lower density. Enter only when you can define your stopping tile and still defend the new edge.
Reduce contacts. Count distinct hostile players after the move. Capturing a compact pocket can remove one enemy and shorten a frontier. Capturing a long coastal ribbon may add two players and a vulnerable shore. Territory is valuable only with a sustainable perimeter. The annexation and enclosure guide explains how to close pockets; here the reason is diplomatic absence. Every extra contact is a treaty you cannot request.
Diversify routes. Keep two independent ways to create value: for example, a land expansion plus a protected Port, or a safe City cluster plus a Boat exit. They must fail for different reasons. Two land routes through the same narrow border are one route. Two Ports exposed to the same Warship are one route. Diversification lets you stop a bad fight without stopping your entire economy.
Exit losing exchanges. Define the stop before the attack: a reserve floor, a time window, a captured structure, or the arrival of a third player. If the trigger occurs, stop adding troops. Sunk cost is especially dangerous here because nobody can grant a ceasefire after both armies are drained. A controlled retreat with 55% of your force intact can preserve deterrence; a heroic finish that leaves 12% invites the rest of the lobby.
Recalculate the win line. Normal FFA and Team victory use the current mode rules; disabling alliances does not create a separate territory threshold. Check the live share, Overtime state, map timer, and Doomsday condition rather than assuming the match will wait for total conquest. As the leader approaches a win, “do not look weak” changes into “deny the shortest interruption.” As a chaser, it changes into “attack the route that reduces the leader’s share fastest.” BORDER therefore begins with survival but ends with conversion, which keeps it from becoming passive turtling advice.
Open fast enough to avoid weakness, but do not collect every border
The first minutes decide whether the lobby reads you as a participant or inventory. Without alliance requests, you cannot turn an awkward neighbor into a five-minute buffer while you fix a slow start. You need early growth, yet every opening capture changes who can reach you. Start by mapping three rings: immediate neutral or Bot land, the first human contacts behind it, and one independent fallback route. Take the cheap ring quickly, then pause long enough to see which human is expanding toward the same junction.
Neutral and Bot targets are attractive because they add land, Gold opportunities, and sometimes structures without requiring the same fight as a prepared player. They are not automatically free. A long attack can drain the reserve while a neighbor takes the other half, and a thin finger through neutral land can touch multiple players. Prefer a target that gives one of four concrete improvements: a City that expands troop capacity, a Port with a defensible terminal, a Factory connected to valid stations, or a compact closure that removes an exposed edge. “More tiles” without one of those outcomes is a weak reason to advertise lower troops.
Use a reserve floor rather than a favorite attack percentage. Suppose you open with 180,000 troops, two neighbors show 150,000 and 210,000, and a Bot pocket contains one City. If you require 125,000 at home, the maximum first commitment is 55,000, about 31%. That is a planning assumption, not a universal combat formula. If the Bot needs more, wait for growth or choose a smaller route; do not change the reserve floor merely because the target looks valuable. After the City falls, reassess because your border may now touch the 210,000 player directly.
Shape matters before buildings. A compact core lets the same reserve answer several edges and makes Defense Posts cover useful approaches. A radial star forces troops and attention across narrow fingers. On open continental maps, stop the first expansion at a choke or at a line where only one major player can reach you. On archipelagos, a coastal core needs an inland fallback and an observation plan for Boats; simply having water between players does not make them harmless. Coastal boat defense covers the defender’s response once a Transport is inbound.
Do not interpret “no alliances” as “attack immediately.” The strongest opening can be a credible armed border that both sides postpone while clearing easier land. That is not a treaty; it is a shared calculation that neither side has formal protection from the eventual winner. Keep it stable by matching, not provoking. Avoid unnecessary small attacks that lower your display and reveal intent. If you need to test a route, send a bounded probe whose failure leaves the reserve unchanged enough to deter the other neighbors.
The opening ends when cheap land is gone, not at a fixed clock time. Before starting the first human war, answer four questions: Will the capture remove a hostile player or add new ones? Which third party gains while we fight? What structure or route makes the cost worthwhile? At what troop floor do I stop? If one answer is missing, spend the next growth cycle improving capacity or watching commitments. Patience is useful only after you have earned enough size that patience does not look like weakness.
Let third-party incentives choose the midgame fight
The central No Alliances skill is reading the beneficiary of a fight. Two players can exchange efficiently and still both lose because a third player absorbs neutral land, builds Cities, or enters after their densities collapse. Before clicking, name the player who benefits most if your target and you each lose half your troops. If that beneficiary can reach either border, the fight needs a shorter objective or a later start. This single question catches more traps than comparing the two visible troop totals.
Prefer wars with an asymmetry you can finish. Good asymmetries include a target already committed elsewhere, a pocket whose closure removes them from your perimeter, a structure that immediately pays, or terrain that lets you stop at a defensible line. Bad asymmetries include anger, an old emoji, equal armies across a wide border, or a target whose land opens directly onto the lobby leader. A rival with 800,000 troops fighting another 800,000 is not automatically your opportunity. If you enter too soon with 600,000, both may turn toward the smaller unprotected stack.
Use active attacks as clocks. When a neighbor launches 40% of 1,000,000 troops away from you, the visible 600,000 reserve creates a window, but travel time and growth matter. Do not attack only because the number dipped. Wait until their army is committed far enough that recall or reversal cannot instantly restore the edge, then set a limited objective: one City, one enclave, or a frontier correction. Stop when the original defender disengages or a new player approaches. The goal is to purchase position from commitment, not to volunteer for a three-way elimination.
Dogpiles usually form around weakness and convenience rather than a secret pact. No treaty is needed for three players to attack the same exposed empire; each independently sees land with low density and a defender already occupied. Counter that incentive in four ways. Keep the home number credible, shorten the border, let invaders overlap each other’s routes, and counter the smallest commitment rather than chasing the largest flag. If one attacker is taking a thin finger, conceding a few low-value tiles can make their border meet another attacker. Spending everything to preserve every tile can keep all enemies separated and focused on you.
Target signals and emojis may coordinate attention, but treat them as nonbinding information. A player who attacks the same leader is a temporary co-beneficiary, not a protected partner. Do not align both armies so completely that they can take your exposed side after the shared target falls. Maintain a separate approach and a reserve that still makes betrayal costly, even though the game does not classify the action as betrayal when no alliance exists. Parallel pressure works because incentives overlap; it ends the moment those incentives change.
Leaders need the reverse calculation. Approaching the victory threshold makes you the universal beneficiary to stop. Side wars become distractions unless they directly raise your share or remove the fastest interrupter. Convert Gold into the Defense Post, City capacity, SAM coverage, Warship position, or reserve that protects the shortest losing route. Chasers should avoid draining each other when one leader is close: attack the leader’s cheapest share and preserve enough force to survive after the threshold drops. No Alliances removes promises, not arithmetic. Everyone can independently arrive at the same urgent target.
Keep economic links, military safety, and team status in separate ledgers
Economy is where players most often invent a relationship the engine does not provide. A foreign Trade Ship or Train can pay without an alliance because trade eligibility depends on embargoes, not treaties. The correct ledger has three columns: expected income, route survivability, and military exposure. A route passes only when all three are acceptable. High theoretical Gold cannot compensate for a terminal that invites a landing or for a partner whose capture would delete the only useful station.
For Ports, measure distance, active Trade Ship cadence, hostile Warships, and whether the far terminal remains eligible. The v0.34.12 Release increases early-to-middle-game Trade Ship and Train spawning, but does not guarantee a fixed extra payout or repair a bad route. Observe completed trips under the current lobby rather than importing an old waiting time. If ships appear more often, the exposed Port may become more valuable and more visible at the same time. Keep a land-income fallback before adding the next Port level.
For rail, a moving Train is still not proof of settlement. Verify reachable Cities and Ports, legal track, ownership, and actual Gold. A neutral trading relationship can disappear through embargo or capture while the railway remains drawn. Build a redundant self or teammate station so the network has value after the foreign endpoint fails. The Train network guide covers range and stop economics; the No Alliances adjustment is to price political failure into every branch.
Embargoes remain deliberate tools. If a neighbor funds a stronger economy through your station while preparing an attack, stopping trade can be rational even when it costs your own income. Calculate both sides rather than treating embargo as punishment. Suppose a route gives you 35,000 per valuable ally-style stop under its actual relation but helps the other player finance the Warship covering your coast. In No Alliances, the absence of a treaty does not automatically block the trade, and the trade does not block the Warship. Close it only when the avoided military risk exceeds the lost cadence.
Fixed teams require a separate read. A zero-minute alliance setting can coexist with assigned teams. Teammates remain friendly through team membership, and host-enabled donations may still work between eligible friendly players. Coordinate roles normally inside that team, but assume no temporary treaties with outsiders. The best team shape often gives each member an independent economy and a shared reinforcement line, so one outsider cannot cut both. Team economy space explains ownership and payer decisions.
In pure FFA, donations to strangers cannot be a plan because alliances cannot make them friendly. Keep emergency Gold yourself. A trading partner can remain economically useful, but do not place irreplaceable defense behind their goodwill. On small compact maps, one safe self City may outperform a richer foreign branch because travel time is short and every contact can attack. On large maps, a long route may earn before the partner can project land force, but Boats and Warships collapse that distance. Economic cooperation survives No Alliances only as long as both routes and incentives survive; your reserve must assume neither is permanent.
Work the numbers in two explicit board states
Scenario A: four-border continental FFA. Assume you have 720,000 troops, 1.8 million Gold, 9.5% territory, and four contacts. West has 520,000 and is attacking a Nation; north has 910,000 with a compact border; east has 1.1 million but only a narrow contact; south has 640,000 and is already fighting east. Overtime is not active. These values define this scenario rather than promising live results. Your first idea is a 35% westward attack, committing 252,000 and leaving 468,000.
Run BORDER. Balance fails after the click because both north and south can compare 468,000 with easier alternatives, and west may recall. Observation says south and east are already paying for a fight, while west’s Nation attack has not yet crossed a decisive line. Reducing contacts favors a small western enclosure only if it removes the western player; the proposed push does not. Diversification exists through an unused coastal Port site, but 1.8 million Gold can also fund capacity and defense. The correct choice is to wait for west’s commitment, use part of the Gold on the structure that raises the reserve or secures the northern line, and cap the eventual push at a reserve floor such as 600,000. If growth reaches 900,000, a 300,000 bounded objective leaves that floor. Stop after the City or pocket; do not chase to the next human border.
Notice why this is not “never attack the weak player.” West can remain the best target, but timing converts the same route from a signal of weakness into a compact gain. South and east are the unspoken third-party clock. If one stops fighting, rerun the decision before your click. No alliance request will buy thirty seconds while you finish.
Scenario B: fixed 2v2v2 team lobby with alliances disabled. Assume your team controls 22% territory. You have 1.2 million troops and a level-2 Factory; your teammate has 800,000 troops and two coastal Ports. A rival team has 25% territory, with one 1.4 million front player and a 500,000 economic player. A third team holds 18% and is pressuring the rival. Custom alliance duration is zero, but fixed teams remain friendly. Your Train can reach your teammate’s City, and trade with outsiders remains possible unless embargoed.
The bad plan is to donate or commit everything to kill the 500,000 economic player simply because they look weak. A 600,000 attack would leave you at 600,000 while the 1.4 million front player can switch edges. Instead, divide the task by team status. Your teammate’s Ports and your Factory create independent incomes; preserve both. Commit perhaps 300,000 to close one compact objective while retaining 900,000, and ask the teammate to cover the coast with their own force rather than assuming an outsider stays neutral. If the third team pushes the rival below your share, stop the attack before you become the new leader with an empty reserve.
The completion test is not whether the target dies. It is whether your team exits with a shorter border, two functioning incomes, and enough combined force to face whichever team benefited. If the rival’s strong player turns, abandon the deep capture and defend the junction. If the third team approaches the victory line, redirect to territory that changes the live share. No Alliances simplifies the formal relationship list, but it makes the beneficiary calculation more important after every 5% change in territory.
Anticipate failures, counters, map changes, and the winning conversion
The first failure is passive deterrence: you keep a large number but take no capacity, structures, or routes, so neighbors grow past you. Fix it by spending from a reserve floor, not by refusing all spending. The second is victory through exhaustion: you eliminate one player and emerge with the lowest force. Fix it by defining the post-capture border and stop trigger before attacking. The third is trade-as-truce: you empty a Port coast because ships are moving. Fix it by keeping economic and military ledgers separate. The fourth is every-tile defense: you burn troops to preserve fingers that increase your perimeter. Fix it by retreating to a compact line and making attackers meet each other.
Opponents counter strong No Alliances play by hiding commitment, opening a second route, embargoing profitable endpoints, or waiting until you near the win line. Answer hidden commitment with observation rather than prediction: watch active attacks and unit movement. Answer the second route with a true independent reserve, not two Defense Posts on one frontier. Answer embargo with a self or teammate station and land income. Answer the leader dogpile by converting early: protect the fastest interruption route and stop side projects that do not change territory, survival, or the clock.
Map topology changes which part of BORDER dominates. Compact maps reward balance and contact reduction because everyone projects force quickly. Continental maps reward geometry: rivers, impassable terrain, and enclosure can turn a long frontier into one approach. Archipelagos reward route diversity and coastal observation; a player without a land border can still send up to the current Transport limit and use Warships to control the crossing. On maze maps, distance can function like temporary safety, but a new capture may suddenly connect corridors. Read the actual map rather than carrying one reserve percentage between layouts.
Mode changes matter too. In pure FFA, every other human is mechanically nonfriendly when alliances are disabled. In fixed Team games, teammates remain friendly and the normal team threshold applies. Overtime changes the value of waiting because the live threshold can fall; Doomsday changes the value of compact survival; a configured timer can end the match before a long economic route pays. No Alliances does not override any of those win conditions. Use the winning Overtime guide for the threshold and recovery playbook after multiple fronts have already broken your core.
The final counter is social inference. Players may still move in parallel, mark targets, or avoid each other. Do not accuse the board of breaking the setting: synchronized incentives require no alliance object. The engine promises only that alliance requests cannot create a timed friendly relationship. It does not promise isolated one-on-one wars. Your response is to alter incentives: look expensive, offer a worse route, let attackers collide, and threaten the leader’s share so attention moves.
You are ready to queue when you can state four things without an alliance plan: your reserve floor, the maximum hostile contacts after the next capture, the independent fallback route, and the stop condition for the first human war. During the match, rerun those four after every elimination, embargo, major launch, or territory swing. The winning conversion is not permanent peace. It is reaching the moment when the remaining players cannot take enough of your share before the current victory rule resolves, because you preserved position while everyone else spent theirs.
Related content
Use OpenFront v34.3 costs, troop growth, route payback, and stop signals to choose City, Port, Factory, defense, or a liquid reserve without copying a fixed script.
- OpenFront Annexation and Enclosure: Close Pockets Without Overextending
Learn how to take small footholds, close an enemy pocket, and keep a second route after the capture instead of turning a lead into a fragile border.
Sep 4, 2026
- OpenFront Attack Ratio: What Percentage to Send, and When to Click
A v0.34 decision framework for the bottom-left send slider: how the troop-ratio clamp and defender density turn your chosen percentage into losses and speed, why one bigger push beats several small ones, the 2x max-speed rule, full-send timing, and when to whittle instead of counter.
Sep 21, 2026
- OpenFront Building Timing: When to Build City, Factory, or Port
Decide when to build a City, Factory, Port, Defense Post, Silo, or SAM; this page owns timing, while Port vs Factory owns payback.
Aug 23, 2026