GUIDES
OpenFront Player Levels, XP & Prestige: How to Climb v0.35
A v0.35.0-beta1 decision framework for the new player-level system: how the end-of-game XP reveal is built source by source, what the ten prestige ranks unlock, when the opt-in level-100 prestige reset is worth it, and which daily caps and trusted-account gates quietly decide how fast you actually climb.
Direct answer: what do levels, XP and prestige actually do?
Player levels, XP and prestige are the new long-horizon layer that v0.35.0-beta1 puts on top of everything you already know about OpenFront. They do not change how a single match plays — your spawn, your attacks, your infrastructure and your growth curve are exactly the same as the stable v0.34.25 you may be playing right now. What changes is what you keep between matches. Every qualifying game now awards XP, and that XP stacks across games into a persistent 100-level track that is tied to your account, not to any single lobby or server session. Your current level and your prestige rank are shown by a level badge everywhere you can be seen: the lobby player list, the in-game player panel, the ranked leaderboard and clan lists.
The three terms answer three different questions, and the guide is organized around that split. XP is the fuel: it is earned every game, revealed to you source by source at the end of the match (with a provisional figure shown the moment you die so you are not left guessing), and it is what pushes your level bar forward. Levels are the meter: a fixed 100-level track where reaching the higher levels needs noticeably more XP, and where the specific XP-to-level curve is set on the server rather than hard-coded in the client, so the bar at level 40 and the bar at level 89 can move at very different paces. Prestige is the opt-in reset: once you reach level 100 you may reset your level track to start again at level 1 but at a higher prestige rank, and you can do that up to ten times (P1 through P10), after which you are a Legend rather than a ranked prestige. The whole point of prestige is that the reset is never forced on you — a game never changes your prestige by itself, so the reset is a deliberate choice you make from your profile when you decide the climb from zero is worth it again.
Why any of this matters to your decisions: progression is where OpenFront starts rewarding how you choose to spend your games, not just whether you win one. A player who plays big FFA maps to the end, finishes rather than leaves early, and reaches high placements earns XP from several of the breakdown sources at once, while a player who hops into small private lobbies with custom settings can earn almost none and hit the daily caps faster. And because level Plutonium is held until your account is trusted — the same trusted state that the new ranked queues require — the path to claiming your progression rewards is partly a path to earning the account’s trust. The rest of this guide turns all of that into a decision framework: how to read the end-of-game reveal, what each prestige rank and milestone is worth, when the level-100 reset pays off, and which caps and gates decide how fast you can realistically climb. For the competitive side of the same update, the ranked 1v1 guide and the caps vs plutonium guide cover the ELO and currency halves that levels now sit alongside.
Read the end-of-game XP reveal like a decision table
The single most important new habit v0.35.0-beta1 gives you is learning to read the end-of-game XP panel, because it is the only place the game tells you exactly why you got the number you got. At the end of a qualifying game the panel lists your XP source by source, and each line maps to one of the breakdown keys the client knows: the base played XP, time XP, placement XP, a win bonus, a firstGame bonus, and feats (the in-game achievements the update ships, like winning a ranked game). The listed lines are only the non-zero ones, in a fixed order, followed by an “other” line that absorbs anything the client does not recognize so the lines always add up to the subtotal. When you die you see a provisional figure, so the number is not a mystery while the match is still resolving around you; the final reveal is what counts.
The subtotal is then multiplied by up to two multipliers before it becomes your total, and the panel shows only the multipliers that are not 1x. The game multiplier (gamePermille) is the rate the game type pays at — the release notes state that singleplayer games score at a lower rate and under their own private daily cap, which is why the schema carries a separate singleplayerPermille and a separate privateGames/singleplayerGames per-day allowance. The subscriber multiplier (subscriberPermille) is the boost your subscription tier adds, and the client recognizes three by their exact permille value: Sovereign at 200% (2000‰), Warlord at 150% (1500‰) and Vanguard at 125% (1250‰); a multiplier the client does not recognize still shows up as a plain subscriber bonus rather than disappearing. Both multipliers are applied in one step with a single rounding, so total = round(subtotal × game × subscriber). One subtlety the panel is honest about: when only one multiplier is in play, the amount it added is exactly total − subtotal, but when both are in play the panel does not split the difference between them, because the order of application makes that split ambiguous — so neither line gets an amount that might be wrong. Reading this correctly means you always know whether your number was lifted by playing a high-rate game type or by a subscription, and how much of it was each.
Treat the reveal as a table you check after every serious game. If your placement and feats lines are missing or tiny, the question is not “why is my XP low” but “did I actually finish a competitive game and reach a good placement, or did I leave early or play a custom-lobby game that the system refuses to score?” That distinction is the difference between a session that moved you up the track and one that burned a game against the daily allowance without moving you at all. Build the habit of glancing at the four lines that should be non-zero in a normal FFA game — played, time, placement and at least one feats — and if any of them is absent, you have found the reason to fix. The provisional-at-death figure exists precisely so you can make that judgment mid-match instead of after it.
The level track: 100 levels, server-set curve, no published table
Your level is a whole number from 1 to MAX_LEVEL, which the client fixes at 100. Inside the current level the client only stores two numbers: xpInLevel, how much XP you have already banked toward the next level, and xpForNext, how much XP the next level costs. The fill fraction of the bar is simply xpInLevel / xpForNext, clamped to the 0..1 range, and a level that has nothing left to earn — level 100, where xpForNext is 0 — reads as full. Here is the part most players mis-read: the per-level XP curve is not a client constant and is not published as a fixed table. xpForNext is a value the server sets, which is exactly why the client can compute a bar without knowing the curve itself. The consequence for you is that the climb is back-loaded by design — the release notes say reaching the higher levels needs “noticeably more XP” — but the exact cost of level 30 versus level 70 is something the server decides, so no guide (including this one) can promise you a specific number of games per level at the top of the track without inventing data the game has not published.
What you can rely on from the source is the shape and the caps. The track has exactly 100 levels and the badge art is cut to match that, so raising the ceiling would require new art, not just a new number — which is a strong signal that 100 is the intended long-horizon target, not a placeholder. The client also fixes the milestone levels at 10, 25, 50, 75, 100: these are the levels the end-of-game panel calls out with their own “new milestone” card (level 100 being the Legend card at the last prestige), and the server dates each milestone on your profile. So even though the bar between milestones moves at a server-set pace, the milestones themselves are the stable checkpoints the whole progression UI is organized around, and they are where the reward track pays out. Plan your climb in milestone blocks rather than in individual levels: the decision of “how many games do I need to the next milestone” is meaningful, while the decision of “exactly how much XP is level 43” is not answerable from anything the game publishes.
The practical read: early levels (1 through 10) come quickly because xpInLevel builds against a small xpForNext, and that is where a new account sees the system working. By the time you are between 50 and 75 the same amount of XP per game moves the bar far less, and that is the stretch where session discipline (finishing maps, reaching placements, stacking feats) starts to matter more than raw time. You do not need the exact curve to manage that stretch — you need the habit of checking the reveal and knowing that the bar is moving slower than your early levels did, which is the intended shape of the track, not a bug.
Prestige ranks: iron to champion, then Legend — and what the reset does
Prestige is the opt-in reset that turns your 100-level track into a long career rather than a one-shot climb. The client fixes MAX_PRESTIGE at 10, and each prestige rank has its own tier name and its own badge colour, in this exact order: P1 iron, P2 bronze, P3 silver, P4 gold, P5 platinum, P6 emerald, P7 diamond, P8 master, P9 grandmaster, and P10 champion. Before your first prestige you are on a “none” tier with a slate badge; after you have prestiged ten times you are a Legend, drawn in a distinct gold rather than in any tier colour, and a rank beyond P10 still keeps the Champion art rather than inventing a new one. The badge lights one segment of its rim gauge per rank, so you can read someone’s prestige by position even when you cannot tell the colours apart — that is the design intent, and it is what makes the ten ranks legible in a busy lobby.
The reset itself is deliberately simple and deliberate: when you hit level 100 you may reset your level track back to level 1, and in exchange your prestige rank goes up by one. A single game never changes your prestige by itself — the client drops any “level reached” entry that belongs to a different prestige rather than celebrating it as a level-up, because the only thing that moves prestige is the opt-in reset done from the profile. That is the whole design: prestige is a decision, not an automatic consequence of a big game. The release notes make the same point that the reset is yours to choose, and they pair it with the reward track so that the prestige moment is also a reward moment — you do not just get a new rank, you get the prestige reward the track has staged for it.
What to decide before you reset: whether you are at the top of your current interest in the current track or just at level 100 because you played a lot. Prestige is the right move when you want the next milestone block (the next ten tiers, the next set of milestone rewards, the next prestige reward) and you are willing to re-climb from level 1 against a server curve you know is back-loaded. It is the wrong move if you are at level 100 by accident, because you will immediately feel the bar slow down again and you will have traded a high level number for a higher rank that you may not yet care about. The prestige count is the long-horizon flex — a P5 or P6 badge is a statement about how many full 100-level climbs you have completed — so spend it only when the climb is something you are choosing to do again, not when you have simply accumulated games. For what prestige does and does not do to your competitive standing, see the ranked 1v1 guide, because the ELO and the prestige rank are separate tracks that the badge now shows you together.
Milestones and the reward track: where Plutonium actually pays out
The reward track is the part of progression that turns your levels into currency, and it is organized around the milestone levels rather than around every single level. The client fixes the milestone checkpoints at 10, 25, 50, 75, 100, and those are the levels where the track stages its bigger rewards and where the end-of-game panel gives the reached level its own “new milestone” card. Within the track the reward the client explicitly names for a level up is a Caps award (the level-up reward reason is a distinct one, level_up, separate from level_milestone and prestige), and the reward list formats them in a pattern the client documents — for example a line reading “+300 Caps (3 × 100)” for a multi-tier level-up and a line reading “Level 50 rewards +100 Caps +25 Plutonium” for a milestone. The headline number for your long-horizon planning is the cadence the release notes state: Plutonium is awarded every 25 levels, which lines up exactly with the milestone checkpoints at 25, 50, 75 and 100. So your Plutonium income from progression is a staircase at the quarter points of the track, not a steady drip every level.
There is one rule in the reward track that more players will hit than any curve, and it is the one the release notes call out by name: level Plutonium is held until your account is trusted, and the rewards list says so. This means the moment a milestone would normally pay you Plutonium, that Plutonium can sit unclaimed in a “held” state until your account crosses into trusted status. The client models this explicitly — the reward state tracks whether any reward is “held” (neither claimed nor released) and the held rewards are shown one line per currency. For you the practical effect is that an untrusted account can climb all the way through milestone 25 or 50 and see the Plutonium reward appear, but not be able to bank it, until the account is trusted. That ties progression rewards to the same trusted-account state that the new ranked queues require, and it is the single biggest “why didn’t my reward show up” answer in the entire system. The trust requirement is itself earned by playing — the community’s own summary is that the free route is “just playing, enough games played,” with a subscription or a purchase as a faster alternative.
Plan your currency strategy around this staircase-and-hold interaction. If you are chasing Plutonium specifically, your goal is to clear the 25-level milestones after you are trusted, because every milestone you pass while untrusted stages a Plutonium award you cannot bank yet. If you are chasing Caps for in-game play, the level-up and milestone Caps are claimable and are the part of the track that works immediately. And because the held-Plutonium rule is stated on the rewards list itself, you are not guessing at it — the client shows you the held line, so the moment your Plutonium is stuck you will see why. For the broader Caps-versus-Plutonium economy this track feeds into, the caps vs plutonium guide is the companion read.
The caps and gates that decide how fast you can climb
Progression has a second set of rules that sit below the curve and decide whether a game earns XP at all, and these are the ones that cap your real climb faster than the back-loaded curve ever could. The client names the per-game ineligibility reasons a game can be rejected for: not_spawned (you did not actually spawn), too_short (the game was too short to count), no_action (you took no meaningful action), custom_settings (the game ran under custom lobby settings the system refuses to score), too_few_humans (not enough human players to count as competitive), daily_cap (you have already used up today’s XP allowance for this game type), unverified (the game’s final stats were not agreed by the players’ end-of-game vote), and before_progression (a game played before player levels existed, which is never scored). Each of these has its own player-facing line in the reveal, so when your XP is zero or low you are told the reason rather than left to infer it. Singleplayer games get their own unverified line because they never carry the end-of-game vote, and they score at the lower singleplayer rate under their own daily cap.
On top of the per-game reasons there are the per-day allowances, which the schema models as separate numbers for private games and singleplayer games (privateGamesPerDay, singleplayerGamesPerDay) in addition to the normal competitive allowance. This is the structural reason hopping between small private lobbies burns your day faster than it climbs your track: private and singleplayer games draw from their own daily budgets at their own (lower) rates, so a day spent in custom lobbies can end with your competitive allowance intact but your private allowance exhausted, and the next competitive game you play is the one that actually moves the bar. The daily_cap ineligibility reason is what you see when you have already spent today’s allotment for a given type and the game will not award more. Read the caps as three separate budgets — competitive, private, singleplayer — each with its own per-day ceiling and its own rate, rather than one shared pool.
The third gate is the trusted-account requirement, which is not a cap on XP but a gate on what the XP and rewards are for. The release notes state that the two new ranked queues (ranked FFA for 4–10 players and ranked clan wars for 8–16, both ELO-matched) now require a trusted account, and that the level Plutonium is held until trusted. So the same trusted state that the community is talking about when it complains about locked lobbies is also the state that releases your progression Plutonium and unlocks the competitive queues where the feats XP (like winning a ranked game) is on the table. You can level without being trusted — trusted status does not block the level bar itself — but the rewards and the competitive XP sources are where trust pays off. The practical sequence for a new account is therefore: play normal competitive games to both earn XP and earn the account’s trust, let the held Plutonium release once trusted, and only then treat ranked queues as part of your XP plan. The caps tell you how much a day can earn; the trusted gate tells you what that earning is allowed to unlock.
Decision framework: who should prestige now, and who should bank
The decision this guide is really about is the level-100 one: at the top of the track, do you prestige now, or do you stay at level 100 and keep banking? Everything else in the system — the curve, the milestones, the held Plutonium, the trusted gate — feeds into that choice, so here is the framework that turns your actual situation into the answer. The core trade is always the same: prestige trades a high level number in the current rank for a higher prestige rank and a fresh 100-level climb, and the value of that trade depends on three things you can read straight from your own account. First, your trust status — if you are not trusted yet, prestige now would stage another round of Plutonium you cannot bank, so bank toward trusted first. Second, what you want next — if you are chasing a prestige badge and a new milestone block, prestige is the move; if you are chasing Plutonium or Caps, the milestones you have not yet cleared are worth more than the reset. Third, your session quality — if your recent games have been finishing big FFA maps with good placements, the climb is cheap for you and prestige is worth taking; if you have been leaving early or sitting in custom lobbies, a fresh climb will feel slow, so fix the session first.
The archetype table below is the framework applied to the four situations players actually report. A new untrusted account at level 100 should not prestige yet, because the held-Plutonium rule means the prestige reward and the next milestone Plutonium would both stage as held; the right move is to bank toward trusted and let the held Plutonium release. A trusted grinder who plays competitive FFA to the end should prestige on hitting 100, because their high session quality means the re-climb is fast and the new prestige rank is the flex they are building. A subscription player (Vanguard 125% up to Sovereign 200%) should prestige when the new milestone block is what they want, because the subscriber multiplier makes the re-climb materially faster than the base rate and the prestige reward is the same for everyone. And a competitive player focused on ranked ELO should treat prestige as a background decision, because the ELO track and the prestige track are separate — the badge shows both, but resetting your level does not move your ELO, so they should prestige only when they are genuinely at the top of the level track and want the rank.
| Situation | Trust status | Right move at level 100 | Why |
|---|---|---|---|
| New account that hit 100 fast | Not trusted | Bank toward trusted first, prestige later | Held-Plutonium rule stages the prestige and next-milestone Plutonium you cannot bank yet |
| Trusted competitive grinder | Trusted | Prestige now | High session quality makes the re-climb fast; the new rank is the long-horizon flex |
| Subscription player (125–200% XP) | Usually trusted | Prestige for the new milestone block | Subscriber multiplier makes the re-climb faster; prestige reward is the same for all |
| Ranked ELO-focused player | Trusted | Prestige only if genuinely at the top | ELO and prestige are separate tracks; a reset does not move ELO |
The meta-rule that ties it together: prestige is a career decision, not a match decision. It is the one action in the whole progression system that is deliberately irreversible-in-practice (you do not lose the rank, but you do hand back the level number and re-climb), and it is the one the client refuses to do for you automatically. Make it from your profile, at a moment when the new block is something you are choosing, and only when your session quality says the climb back up is worth your time.
Two worked scenarios: a Sovereign grinder and a stuck daily cap
The framework becomes concrete once you put numbers on it. Scenario one is a trusted Sovereign subscriber (the top tier, 200% XP) grinding competitive FFA. Their game multiplier for a normal competitive FFA is the standard 1x (gamePermille 1000) and their subscriber multiplier is 200% (subscriberPermille 2000), so every qualifying game’s subtotal is doubled before it hits the bar — the reveal will show the subscriber multiplier line because it is not 1x, and it will attribute the added XP exactly, since with only one multiplier in play the added amount is simply total − subtotal. Concretely, if a well-finished FFA game earns a subtotal of 5,000 XP from played, time, placement and a feats line, the Sovereign rate turns that into 10,000 before the bar moves, while a non-subscriber gets the 5,000 and a Vanguard (125%) gets 6,250. The decision this changes: a Sovereign player who is between 75 and 100 should almost always prestige promptly, because the doubled rate means the back-loaded stretch that slows everyone else down is roughly halved for them, and the new prestige rank plus the next 25-level Plutonium milestone is on the way in fewer games. The counter-check is the daily cap: even at 2x, the competitive daily allowance is a fixed number of games, so the Sovereign rate makes each game worth more but does not let them exceed the per-day competitive budget — a full day still ends when the competitive allowance is spent, it just ends with the bar much further along.
Scenario two is a non-subscriber who keeps hitting the daily cap without climbing, the pattern that matches the “why didn’t my XP show up” threads. Their games are small and private: they hop into custom lobbies where the settings mean the game is rejected with custom_settings, or they play short games that get rejected with too_short, or they fill their privateGamesPerDay budget at the lower private rate and then their competitive games for the day award nothing because the competitive allowance was already spent on private play. The reveal in this scenario is the diagnostic: the ineligibility line will name the exact reason — custom_settings, too_short, or daily_cap — and the multiplier lines will show 1x for both, so there is no subscription or rate masking the problem. The fix is structural, not effort-based: stop running the custom-settings lobbies if they are being rejected, stop treating private games as the main XP source (they draw from a separate, lower-rate, separately-capped budget), and finish at least one competitive FFA map to the end so the placement and feats lines are non-zero. A single clean competitive game that earns played + time + placement + a feats line, scored at the standard rate under a fresh competitive allowance, will move the bar more than five rejected private games combined. The decision here is to optimize for eligibility, not for volume: the cap does not punish you for playing a lot, it punishes you for playing games the system refuses to count, and the reveal is the tool that tells you which of those is happening.
Failure modes, counters, and how mode and map change the climb
The progression system has a short, well-defined list of ways a game fails to move you up, and each one has a counter you can read straight off the reveal. The first is the daily cap (daily_cap): you have already spent today’s allowance for that game type. The counter is to plan the day rather than grind it — front-load your competitive games when the competitive allowance is fresh, and treat private and singleplayer games as drawing from their own separate per-day budgets at their own lower rates, so a day of private play does not quietly starve your competitive climbing. The second is unverified stats (unverified): the end-of-game vote did not agree on the game’s final statistics, so the game does not score. Singleplayer games are always in this state by design (they never carry the vote) and get their own line; the counter is to play the normal competitive types where the vote exists rather than relying on singleplayer XP. The third is the early exit the client tracks with the leftEarly flag: leaving before the game resolves costs you the placement and feats lines that a finished game would have earned, so the counter is simply to finish the maps you are in when a placement is reachable.
The fourth failure mode is the one that is not a game at all: the held-Plutonium wall (...held until trusted). This is not an ineligibility reason and it does not block your level bar, but it does block your currency, and its counter is to bank toward trusted status by playing normal competitive games (the community’s own read is that the free route is enough games played, with a subscription or purchase as a faster path). The fifth is the pre-launch blind spot (before_progression): any game played before player levels launched is never scored, so if you are comparing your total against what you feel you have played, the pre-v35 history is simply not on the track — the counter is to plan your climb from today forward, because the track starts where the feature starts, not where your account does. The sixth is the custom-lobby trap (custom_settings and too_few_humans): games run under custom settings or with too few humans are rejected, so a “practice” session in a two-person custom lobby can be a session that earns nothing; the counter is to check the reveal for these lines and, if your practice lobbies keep getting rejected, move the practice to normal lobbies or accept that they are XP-neutral.
How mode and map change the climb is where the placement source does most of its work. In ranked FFA (4–10 players, ELO-matched) and ranked clan wars (8–16, ELO-matched) a high placement is both a better placement line and a feats line (winning a ranked game is one of the feats), so the competitive queues are where the breakdown sources stack — but they require the trusted account, so they are the late-stage XP source, not the starter one. In normal FFA the map size matters: the client shows each spawn’s map size relative to the average (a “larger than average” marker when you are on a big map), and a bigger map is more time and more room to reach a top placement, so finishing a large FFA map is the single best XP-per-game the base system offers. The counter-move for map selection is to prefer the larger maps when you are going to commit to finishing, and to avoid the small maps when you only have time for a short session, because the short ones risk the too_short rejection. The meta is that XP is a session-quality currency: the same wall-clock time earns far more when it is spent finishing a competitive map with a reachable placement than when it is scattered across short or custom games the system refuses to count.
How to level faster: a concrete session plan
The whole system collapses into one practical question — how do I actually move the bar faster — and the answer is a session plan that optimizes the three levers the reveal exposes: eligibility, rate, and volume. Eligibility is the first lever and the one most players ignore. Every game you play should be one the system will count: spawn (not_spawned), last long enough (too_short), take real action (no_action), play a type with enough humans (too_few_humans), and play a normal (non-custom) lobby (custom_settings). A game that fails any of those is a game that burns a slot in your daily budget without moving the bar, so the first optimization is to stop scheduling games you will be rejected for. Check the reveal after your first few games and if you are seeing any ineligibility line, that is your session leaking — fix the lobby choice, the game length, or the commitment to the map. Rate is the second lever: the game multiplier is mostly fixed by the type you choose (competitive types pay the standard rate, singleplayer pays the lower singleplayerPermille rate), but the subscriber multiplier is a multiplier you can actually buy — Vanguard at 125%, Warlord at 150%, Sovereign at 200% — and it is applied to every qualifying game’s subtotal, so it is the cleanest single rate boost available. If you are a serious grinder, the subscription is not a cosmetic, it is the XP engine. Volume is the third lever and it is bounded by the caps: you cannot exceed the competitive daily allowance, so the question is not “how many games can I play” but “how many counting games can I play before the competitive allowance is spent,” and the answer is to make every one of them count.
The plan that ties the levers together is a repeating loop. First, pick a competitive game you are going to finish — a normal FFA on a larger-than-average map when you have the time, because that maximizes the time line and leaves the placement line reachable. Second, play it to a placement you are proud of, because the placement line and any feats you stack (a clean win, the ranked win once you are trusted) are the lines that separate a high-XP game from a low-XP one. Third, read the reveal and confirm the four lines you expected — played, time, placement, and at least one feats — are all non-zero; if one is missing you have found the leak for next session. Fourth, respect the daily budget by stopping when the competitive allowance is spent rather than grinding into daily_cap rejections, and by keeping private and singleplayer games within their own separate budgets so they do not starve the competitive climb. Repeat that loop and the bar moves at the maximum rate the system allows for your trust status and subscription tier.
The one decision to keep in front of you while you run the loop is the level-100 choice. As the bar approaches 100, stop and run the framework from the decision section: are you trusted, is the new milestone block what you actually want, and is your session quality good enough that the re-climb is worth it? If the answer to all three is yes, prestige from your profile and start the next block; if any of them is no, bank at 100 and keep the level number while you fix the one that said no. That is the entire game: play counting games, buy the rate you can afford, respect the caps, and make the one irreversible decision — the prestige — only when the three checks line up. The rest is repetition, and the end-of-game reveal is the dashboard that tells you, game by game, whether you are climbing or just burning the day. For the competitive queues the loop feeds into, the ranked 1v1 guide covers the ELO side of the same trusted-account gate.
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 AFK Teammate Takeover: Absorb a Disconnected Ally for Zero Troop Loss
A Team-mode decision guide for what a teammate's disconnect does to your win/loss position, when absorbing their land is free, when it is a trap, and what the 30-second mark and the ranked 2v2 rules actually change.
Sep 23, 2026
- How Nations Aim Their Nukes: Smarter Targeting, No Wasted Blasts
A strategy guide for the upcoming AI Nation nuke targeting change: Nations now compute how much of a blast hits enemy land before firing (atom 25%, hydrogen 40% minimums), they skip a spot where another player's nuke is already landing, and they never nuke a target that would hit friendly land. What changes in your decision, the coverage gate, the anti-double-nuke rule, the failure mode and the mode/map adjustments.
Oct 8, 2026
- Alliance-Break Timing: When 30 Seconds Is Worth the Trade
Decide whether to break a live alliance now, wait for it to expire, or renew it, using the 30-second traitor window, the 0.5 defense and 0.8 speed debuffs, and the -100/-40 relation drops in OpenFront v0.34.
Sep 30, 2026