OpenFront Near-Parity Combat: Why Their Push Wins When Your Bars Look Equal

Direct answer: read the other side’s total army, not your bar

Your push is not fighting the troops the neighbor holds on the border you are facing. It is fighting the whole army they have anywhere on the map, because the loss and the speed of your push are both set by one number: the ratio of their total troops to the size of your committed stack. When two troop bars look the same, the fight is almost never a coin flip. The player with the larger total army pushes faster and cheaper every time, and that single gap is the whole reason the “equal bars, they still win” feel happens. So the in-the-moment call is simple. If their total army is meaningfully larger than yours, do not answer a full push with your own full push. Whittle the incoming push with small clicks, re-route your push to a front where your own ratio is better, or hold and bank growth until your ratio flips in your favor. If you are the bigger side, the same math is a green light: your push sits at the fast, cheap end of the curve, so commit and take the land.

Everything below is the mechanism behind that one decision, and the part of it most players miss. You already know the ratio ladder from the attack-ratio guide, but that page is written for the player choosing what to send. This page is written for the player on the receiving end of a push from someone whose bar looks like theirs, and it answers the specific question “why does their push beat mine when we look the same.” It walks through exactly how the denominator is chosen, why the bigger neighbor’s push is structurally faster and cheaper rather than merely a little better, where the 0.82 speed floor leaves you when your bars are near parity, how the large-territory bonus compounds the gap on top of the raw ratio, and a decision table you can run in under two seconds before you click. If you only take one sentence away, take this one: at near-parity the fight is decided by whose total army is bigger, not by whose front looks denser, so the winning move is to find the front where your total army is the bigger one and only push there. The rest of the page is just the arithmetic that makes that sentence true, and it is written so you can read the numbers and run them against your own screen in a match, not so you can file it away as theory.

The trap: the ratio reads the defender’s whole army

The v0.34.21 combat formula keys both your loss and your speed to one number, the troop ratio, and that number is the defender’s total army divided by the troops in your push. The crucial detail is what “defender’s total army” means. It is not the troops the defender has parked on the tiles of the front you are about to push. It is every troop the defender controls anywhere in their territory, their entire population bar, the number in the bottom-left of their screen. When you commit a stack to a border, the game does not look at how thick that particular border is in troops; it looks at how much bigger the defender’s whole army is than your stack, and it prices your push from that comparison. Your per-tile attacker loss is the terrain magnitude times the clamped ratio times a base plus a density term, and your push speed is the clamped ratio in its own speed band. Both inherit the same denominator, so a single change in the defender’s total army moves both your cost and your speed in the same direction at once.

This is the trap, and it is why the bar you are watching is the wrong bar. In the bottom-left of your own screen you see your total troops and you compare it to the number you think the neighbor has, but the fight does not run on that comparison. It runs on the neighbor’s total army compared to the size of the stack you actually commit, in both directions. Two players with equal-looking bars do not produce a symmetric fight, because when the neighbor with the bigger total army pushes at you, the ratio that prices your defense is your smaller total divided by their big stack, and when you push back the ratio that prices your push is their bigger total divided by your smaller stack. The fight has a built-in direction to it, and the direction always favors the side with more total troops. Recognizing that the denominator is a total rather than a front count is the entire reframe; once you start reading the neighbor’s population bar instead of their border density, the “we look equal” fights stop being mysterious and start being one-sided in a predictable way. The threat-assessment page owns the first step of that reframe, deciding which neighbor is the bigger total, and this page owns what to do once you know which side of the line you are on.

Why the bigger neighbor’s push is faster and cheaper

Now put a number on the direction. Take a midgame where you have 110,000 total troops and your neighbor has 140,000, a gap of about 27 percent, the kind of gap that looks “close enough to be a fair fight” on the screen. When you commit your full 110,000 to a push at their border, the ratio the game reads is their 140,000 divided by your 110,000, which is 1.27. Your per-tile loss multiplies by 1.27, so you pay 27 percent more per tile than a parity push would, and your push speed cost is 1.27, so you advance 27 percent slower than a parity push. Now run it the other way. When the neighbor commits their 140,000 at your border, the ratio is your 110,000 divided by their 140,000, which is 0.79. Their loss multiplies by 0.79, about 21 percent cheaper than parity. Their speed cost, though, is the 0.79 clamped against the 0.82 floor, so it lands at 0.82 rather than 0.79, which means their push runs at one over 0.82 of a parity push, about 22 percent faster than parity. The same fight, the same two bars, two completely different price tags, and the side that is 27 percent bigger wins on cost at the same time as it wins on speed, and the speed win is real even though the gap is small.

That asymmetry is the whole of the “their push is just faster” complaint, and it scales in a way that matters. The loss clamp runs from 0.6 to 2, so below ratio 1.0 the bigger player’s push gets strictly cheaper the bigger the gap, and above 1.0 your push gets strictly more expensive, until it caps out at double a parity push. The speed band runs from 0.82 upward, so once your ratio is below 0.82 your push is at full speed and no more speed can be bought, and the speed penalty only grows as you approach and pass parity. The practical read is that a near-parity gap of even 20 to 30 percent is not a near-parity fight at all: it is a fight where the bigger player is already at the cheap, fast end of the curve and the smaller player is already paying the slow, expensive end, and the “fair” feeling the screen gives you is the one place in the whole game where the visual is the least like the actual arithmetic. The gap you need to worry about is not the gap between the two bars; it is the gap between each side’s total army and the size of the stack they commit, because that is the gap the formula actually prices.

The speed floor: 0.82 is where equal bars stop working

There is a hard line in the speed formula and it is the number that decides whether a near-parity push can win at all. The per-tile speed cost is the troop ratio clamped between 0.82 and 7.5, divided by 8.55. The clamp floor at 0.82 means a push whose ratio is below 0.82, in other words a push that carries at least 1.22 times the defender’s total army, moves at full speed no matter how much bigger you make it. The extra troops past that point buy no speed, only cheaper losses, which is the whole “size the push past the defender” rule of thumb, and because the denominator is a total army the real statement is “carry 1.22 times their entire army, not just their border.” When your bars are near parity, your full push sits at or just above that 0.82 line, so it is crawling through the slow zone by a wide margin, and the only ways out are to make your committed stack bigger relative to their total, or to move to a front where the defending total behind it is smaller than their headline number.

This is why “just push harder” does not fix a near-parity fight. Pushing harder means sending a bigger fraction of your own total, which lowers your ratio toward 0.82, but you are spending troops you need to keep behind the line, and if your total army is already smaller than theirs, no fraction of it gets you comfortably under 0.82 against their total. You can get under the speed floor only by attacking a front where the defender’s relevant total is smaller than their headline number, which is what the density and re-routing moves in the later sections do. The 0.82 line is the difference between a push that wins on speed and a push that wins on attrition, and a near-parity player who understands it stops treating the fight as a test of who pushes first. Instead they treat it as a test of which front puts them under 0.82, and if no front does, the correct play is not to push at all. It is to hold, keep your army behind a wall where their ratio against it stays high, and let the growth curve bring your total up to the point where your push finally lands in the fast zone, which is exactly the hold move the population-growth page quantifies.

The large-territory bonus compounds the raw ratio

The raw ratio is not the whole asymmetry, because there is a second system stacked on top of it that makes the bigger neighbor’s push even faster and cheaper than the ratio alone predicts. It is the large-territory bonus, a smooth curve centered on 300,000 tiles that subsidizes the player who owns more land. On the attacker side the bonus works in the bigger player’s favor: pushing from a larger territory lowers your per-tile loss and raises your push speed, and the discount it can create against a small player caps at roughly three and a third times their rate at the floor. On the defender side there is a mirror bonus that raises the loss floor of a large territory, which is why the giant endgame empire is a wall, but the attacker-side bonus is the one that matters in a near-parity midgame, because it quietly hands the bigger of two “equal” neighbors an extra speed and loss discount that the ratio calculation does not show you.

In a real midgame the tile gap between two near-parity neighbors is modest, so the bonus is a 5 to 15 percent nudge rather than a decisive multiplier, and the honest read is that it tilts an already-uneven fight a little further rather than deciding it on its own. But it points the same way as the ratio, so the full picture of a near-parity fight is the raw ratio times the large-territory bonus, and both multipliers favor the bigger player at once. This is why the “equal bars” fight feels unfair rather than merely close: the screen is showing you one number, the troop bar, while the fight is running on two, the ratio and the territory discount, and both of them are stacked against the smaller player. The practical consequence is that you should not treat a near-parity fight as breakable by raw troop commitment at all. You break it by changing one of the two multipliers, either by shrinking the defender’s relevant total on the front you push, a density or re-routing move, or by growing your own total and your own tile count until the bonus stops favoring them. Until one of those two numbers moves, pushing at near parity is pushing into a compounding disadvantage, and the only near-parity push that is usually worth it is the kill push in the endgame, where the land is worth more than the army you will spend.

The hold-or-counter call, in the moment

The mechanism above earns its keep only if it changes what you click, and the decision you are actually making when a near-parity push is coming at you is a three-way fork, not a fight. The fork is: whittle, re-route, or hold, and you pick it by reading the ratio the incoming push represents rather than by reacting to how far it has crossed. Whittle is the answer when the incoming push is large but its owner is not committing their whole army, so the stack crossing the border is bigger than the ratio you would pay to fight the rest of their army. You answer with small five to fifteen percent clicks as the push crosses, trading a thin strip of your front for a proportional drop in the effective size of the incoming stack before it lands, and then a small follow-up once the push commits and its troops spread over new tiles. Re-route is the answer when the front the push is coming through is the worst front for your ratio and another front is better; you do not meet their push on its terms, you move your own push to the front where your total army is the bigger one and force them to split their attention to stop it. Hold is the answer when neither of the other two is fundable, your ratio on every front is at or above 1.3, and the right play is to keep your army behind a wall, bank the growth, and let your curve close the gap until one of your fronts finally lands under the 0.82 speed line.

The mistake that turns all three into a loss is answering a near-parity push with your own full push while it is still crossing, and it fails for exactly the reason the mechanism describes. A defender at full strength is a defender whose army is packed, so your full counter walks into the highest ratio and density you can get, while the incoming push is priced at the cheap, fast end of the curve because its owner sized it for exactly that. Your counter and their push meet, and the side whose push is cheaper and faster simply wins the merge, so the counter is nullified and you have spent your entire army to cancel a push you could have whittled with a fifth of it. The counter that actually works is the delayed counter, the one you run after the push commits and its density breaks, when the front it crossed is thin and your ratio against the remainder is finally fundable. Timing the counter to the commitment rather than to the arrival is the entire difference between the counter that wins and the counter that “should have won,” and it is the single highest-leverage habit on this page because it is the one a near-parity player can start applying on the very next push they receive.

Numbers on the table: four situations

The table runs the v0.34.21 formula on four near-parity situations players actually meet, on plains with magnitude 80, no defense posts, and no fallout. “Their total” and “your total” are the two population bars, “your push” is the stack you commit, and “your push” and “their push” each show the ratio that prices that side’s advance plus the clamped multiplier the game actually applies. “Loss” is the clamped ratio driving that side’s per-tile loss, and “speed” is how that side’s advance rate compares to a full-speed parity push. Reading the two columns side by side is the whole point: the same two armies produce two different price tags, and the fork is just a lookup into which side of the table you are on. The four rows are the four postures you can be in when a push is coming, and they are worth holding in your head.

Situation	Their total	Your total	Your push ratio	Their push ratio	Your loss	Their loss	Your speed	Their speed	Read
You are bigger	100,000	140,000	0.71	1.40	0.71	1.40	1.22x	0.71x	commit, take the land
Near-parity, close	140,000	110,000	1.27	0.79	1.27	0.79	0.79x	1.22x	whittle or re-route
Near-parity, wide	160,000	110,000	1.45	0.82	1.45	0.82	0.69x	1.22x	hold, bank, grow
Outnumbered	220,000	110,000	2.00	0.55	2.00	0.60	0.50x	1.22x	probe only, or kill

The first row is the green light and it is the only row where the full push is the obvious answer, because your total army is the bigger one, your push ratio of 0.71 sits under the 0.82 floor, and you run at 1.22 times parity speed on a cheap loss while their counter-push at you is slow and expensive. The second row is the default near-parity fight this whole page is about: you are 27 percent smaller, your push ratio is 1.27 and you pay 27 percent more per tile, while their push ratio is 0.79 and they get the 0.82 speed floor, so neither a full counter nor a full push is the right answer and only whittle or re-route are. The third row is the wide gap where holding is correct, because your ratio is high enough on every front that the right play is to keep your army packed behind a wall and let growth close the gap rather than spend it. The fourth row is the trap the table exists to prevent: your push ratio is 2.00 and the loss clamps at double a parity push while your speed is a slow 0.50, so a full commit there buys nothing; the only versions of that row worth running are a small probe to read their density and a full kill push you only take when the land is worth the army. Add one adjustment for every real fight: if the front holds a defense post, multiply the loss and the tile cost heavily, which moves the near-parity rows into the “do not push this front” zone entirely, and if the defender is a bot, their own losses are reduced by 30 percent, which is why the bot neighbor is the front you re-route to rather than the front you hold against.

When this flips: breaking the front and re-routing

The hold-or-counter fork assumes the ratio on every front is stuck at or above 1.3, and the whole point of re-routing is that it usually is not. A player who looks “27 percent bigger” on the headline number is usually 27 percent bigger in total but not 27 percent bigger on every front, because their army is spread across the borders of every neighbor they touch, and the front they are pushing you from is only one of several. The move is to find the front where your total army is the bigger one and push there, which forces them to either send troops to that front, which drops their density and their total behind the front you were holding, or ignore it, in which case you take land and grow the gap the other direction. This is the same routing logic the endgame giants fight with, but in reverse and at midgame scale, and it is the single most underused tool a near-parity player has, because it changes the two multipliers the fight is running on instead of trying to win the fight at its current setting.

Map and mode shift the numbers, and the shifts are where the specific knowledge lives. On coastal maps the front you defend is shorter than the front you attack, so your density on the front is higher than your average, which means holding the coast with a packed wall is the strongest version of the “hold” move and the front you re-route to is the open land side where your ratio is better. On mountain and highland terrain the magnitude term rises from 80 on plains to 100 on highland and 120 on mountain, a 25 to 50 percent increase in every loss number on this page, and a defense post on a mountain tile multiplies that further, which is why the posted mountain front is the one front you never meet a push on directly; you break its adjacent open front first and let the defender move off the posted tile before you push it. In overtime the two ratios flip toward you if you have been winning, because your own total is the bigger one and the large-territory attacker bonus is strongest for the biggest territory on the map, so the overtime push is the parity push into the lowest-density front your opponent holds, and the full kill push is the one moment on this page where the slider goes to maximum. Run the fork on the overtime push exactly as you run it on any push, and the endgame stops being a wall you push through and starts being the arithmetic it always was.

Where to go next

The page you read next depends on which side of the near-parity line you are on and which of the two multipliers you now own, and the order matters less than making sure each question this page defers gets answered by the page that owns it. If your question is the percentage itself, what army to commit and when to click it, the attack-ratio guide is the attacker’s version of the ratio ladder this page prices, and it is the page to open when you want the exact slider settings and the double-click pattern that exploits the density drop between pushes. If your question is the terrain and density under the numbers, the land-combat guide is the per-tile loss reference that this page quotes from, and it is where the terrain magnitudes and the defense post multipliers come from; open it when the two-second ratio read ever disagrees with what you see on the map, because the mismatch is almost always a terrain or defense-post term this page only references but does not derive. If your question is which neighbor is the one your ratio is computed against, the threat-assessment guide is the target-selection page that decides which of your neighbors is the bigger one, and this page is the combat answer to the army answer that page gives.

If your position is that all of your neighbors are about your size rather than one being bigger, the ffa-trapped-middle guide is the positional page for exactly that, and it pairs with the winning-overtime guide for the endgame where the near-parity fight becomes the kill race. If your question is the growth side of “when does my total finally get bigger,” the population-growth guide is the growth-curve page that the hold move runs against, and it is where the peak growth rate comes from, the number that tells you how fast the hold move closes the gap and when it is faster to hold than to fight. The defensive pair matters most in the last two minutes of a match, when the question flips from which front can I win to which front can I survive, and the winning-overtime guide is the one that owns that flipped question. Read these pages as a cluster rather than one at a time, because the near-parity fight is decided by the ratio, the bonus, the terrain, the growth curve, and the position all at once, and no single page owns all five; this one owns the ratio and the bonus, and the others own the rest.