Combat
Asynchronous PvP: what fighting a ghost settlement means
Instead of fighting another player in real time, you face a ghost version of their settlement from the same stage of their run. You see their layout, their upgrades, their units — every choice they made — and then the armies clash automatically.
Ghost battles are described in the official July overview and store page. Demo patch 0.78.5d (October 14) changes Free Play matchmaking and adds one more allowed loss in both Ranked and Free Play; the October 15 update clarifies Last Chance after all five Shields are lost. Hotfix 0.78.33d (October 21) fixes a badge-system softlock above 580 Ranked ELO. No new matchmaking algorithm is published. “Asynchronous” does not by itself promise offline play.
Updated
What a ghost battle is
A ghost is a snapshot of a real rival’s run, taken at the same stage as yours, with their layout, upgrades and units visible — every choice they made. Because both armies then clash automatically, the fight is decided by preparation — your layout, units and fate cards — rather than by who clicks faster.
On this page
What asynchronous changes for you
No live opponent means no clock dictated by another person: the developers say the format keeps the strategic depth and competitiveness of PvP while removing the stress and pressure of real-time multiplayer, so you can take your time experimenting with builds and learning the systems. The store description frames the same loop from both sides: settlements challenge others and defend their own strength in asynchronous battles.
The practical consequence: each ghost battle doubles as a comparison. Where the rival’s visible choices differ from yours is a list of possible improvements to weigh as your run continues.
NPC fights along the way
Ghosts are the core challenge, not the only opposition. At certain moments in a run you fight NPC enemies from the Northgard universe — tests of whether your build holds together before the next ghost arrives. A settlement tuned only for one kind of opponent can be caught out by the other.
In demo patch 0.77.111d (October 12), the Spring PvE encounter changed to Foxes, and Rare structures stopped appearing during Spring. Those notes do not establish a complete seasonal encounter or drop table.
EA starts a new leaderboard
The October 27 launch confirms the leaderboard reset after the Demo. That is a ranking reset, not a statement that every saved run was erased. Official launch.
The ranked ladder
November 16 ERA reset (0.80.47p): ranked ELO is reduced by 100, with a floor of 100; players above 400 instead drop to 300 (Early Gold). ELO gained or lost is now halved, and your own rank appears on the leaderboard. For example, 250 becomes 150; 180 becomes 100; 450 becomes 300. These examples apply the published reset rule, not a new match-result formula.
The same patch saves your preferred combat speed between battles and runs and fixes two controller problems: closing the “unable to find opponents” popup and using the main menu after returning from an error. Official 0.80.47p notes. A leaderboard reset is not evidence that all saves were deleted.
The October 14 0.78.5d patch names both Ranked and Free Play: you can now lose one more time before the run ends in either mode. The developers clarified on October 15: after you lose all five Shields, you have one more chance. This is the Last Chance step already in the demo; it does not mean you now have six Shields. October 15 only discussed possible comeback assistance. November 11 EA Patch 2 adds aid from the gods when the last Shield is lost, without specifying the reward here.
The October 14 patch changes Free Play matchmaking without explaining the new algorithm. The October 12 notes also remove ghosts using unreleased clans and reported cheaters, and fix resumed games changing to unranked. These fixes do not establish the matchmaking algorithm or remove every problematic ghost. If a ghost looks suspicious, use Report a bug in the menu, as requested in the October 15 update; a strong combination alone does not establish cheating.
The October 21 0.78.33d hotfix fixes a badge-system bug that softlocked players who reached more than 580 Ranked ELO (> 580). Update to that build or later if you encountered this issue. The notes do not publish an ELO cap or a new matchmaking algorithm.
Player check
When a ghost beats you, compare its layout, upgrades and units against yours piece by piece — the differences are candidate explanations for the outcome, not proof of which one decided it.
Sources: Developers’ gameplay mechanics overview (ghost battles, NPC moments and the asynchronous format, 2:47–3:28), the official Steam description (challenging and defending), the official demo content image (ranked ladder), balance patch 0.77.111d (October 12), matchmaking patch 0.78.5d (October 14), October 15 feedback update (Last Chance and suspicious-ghost reporting), and Next Fest Hotfix 1 - 0.78.33d (October 21: Ranked badge softlock fix).