ENDLESS Legend 2 launched into 1.0 on September 17, 2026, and the multiplayer scene has never been busier. New players are jumping into simultaneous-turn sessions, only to hit sync desyncs, frozen turn timers, and the occasional custom-game crash that wipes an entire evening's progress. This guide covers every major ENDLESS Legend 2 multiplayer bug reported so far, explains why the simultaneous-turn system creates the desyncs you keep seeing, and walks you through the most reliable workarounds before the next hotfix lands.
If you have already lost two campaigns to a "turn out of order" error, or you keep watching the turn timer stall at 00:00 with no resolution, the sections below will help you diagnose what is going wrong and which setting to flip first. For a broader look at the underlying turn-based systems, the ENDLESS Legend 2 beginner guide covers how the same engine works in single-player, which makes the multiplayer quirks easier to understand.
The Most Common ENDLESS Legend 2 Multiplayer Bugs at 1.0 Launch
The 1.0 build was accompanied by a 50% launch discount on Steam, and the surge of new installs has flushed out a predictable list of ENDLESS Legend 2 multiplayer bugs. Community bug channels on the Amplitude Discord and the r/EndlessLegend subreddit cluster around five recurring problems, all of which share a common cause: the simultaneous-turn engine pushes every player's state to a shared snapshot, and any mismatch in the snapshot sequence produces a sync error.
Below is the consolidated table of the bugs players report most often, ranked by how disruptive they are during a normal friends game. Severity here is judged against a four-player simultaneous-turn session on standard map size, where the simultaneous-turn engine pushes every player's state into a shared snapshot and any desync can derail the match — a single dropped turn from one client is enough to propagate a broken action queue to all four seats.
| Bug | Frequency | Severity | Typical Trigger |
|---|---|---|---|
| Simultaneous-turn desync (out-of-order resolution) | High | Match-breaking | Player drops or alt-tabs during resolution |
| Turn timer freezes at 00:00 | High | Match-breaking | Long combat animation with simultaneous resolution |
| Custom game lobby fails to launch | Medium | Match-breaking | Modded faction or mismatched game version |
| Lag spike on large cities | Medium | Annoying | Industrial-era cities with many queued buildings |
| Disconnect on faction selection | Low | Minor | Reconnecting to a session after a client crash |
The simultaneous-turn desync sits at the top because it cannot be recovered in-session; both players must re-host the lobby. The turn timer freeze is similar in severity but is usually fixed by leaving and re-entering the session, while the custom game crash tends to be a one-time event tied to a specific setup rather than a systemic flaw. According to the official Hotfix 1 announcement on Steam, the development team at Amplitude Studios already shipped a fix targeting the lag on large cities, which was the most visible performance regression during the launch window.
How ENDLESS Legend 2 Simultaneous Turns Create Sync Issues
ENDLESS Legend 2 multiplayer is a turn based multiplayer system that uses simultaneous-turn resolution rather than the hot-seat pass-and-play model of the original game. Each player submits every order for the current turn at the same time, the server collects all submissions, and the engine resolves the resulting state in a single batch. This design is fast and keeps two-player matches moving at a brisk pace, but it is also the source of the majority of ENDLESS Legend 2 sync issues players encounter in 2026.
The engine relies on a deterministic lockstep. Every client must reach the exact same internal state before the next batch is allowed to resolve, and any client that diverges — because of a dropped packet, a memory spike from a large-city calculation, or a player alt-tabbing during the resolution animation — will produce a desync the moment the next batch is processed. When that happens, the host sees a "session out of sync" message, and the affected player's actions are rolled back to the last valid snapshot.
The launch hotfix is the proof point here. The same Steam news post that addressed the large-city lag also implicitly tightened the rollback path, because lag and desyncs share an underlying culprit: a client that takes too long to commit its turn. Players who enjoy a faster match pace should also be aware that combat has its own desync profile; the ENDLESS Legend 2 combat guide walks through how tactical battles interact with the simultaneous-turn clock, and it is worth reading if you regularly see crashes during a manual battle.
Where in the Turn Pipeline Desyncs Happen
The simultaneous-turn pipeline in Endless Legend 2 runs through four discrete stages — order submission, state commit, resolution animation, and post-turn cleanup — and each one can fail in a slightly different way that produces a recognizable desync symptom. Because Amplitude's simultaneous-turn engine locks each client's internal state before broadcasting results, a single dropped packet during the commit stage cascades into the "Turn out of order" error, while a divergence in the cleanup stage silently corrupts resource tallies and unit vision for the next turn. Identifying which stage is breaking — by watching whether the error fires before or after the resolution animation — is therefore the fastest way to pick between a re-host, a rollback, or a full session restart, rather than blindly retrying the turn.
| Stage | What Happens | Typical Desync Symptom |
|---|---|---|
| Order submission | All players queue their orders locally | No visible error, but the snapshot does not match |
| State commit | Each client locks its internal state | "Turn out of order" message on the host |
| Resolution animation | Engine plays the simultaneous results | Frozen turn timer at 00:00, no resolution |
| Post-turn cleanup | Resources, vision, and movement are recalculated | Resources mismatch on the next turn, or ghost units |
Most players only see the symptom, not the stage, so the practical rule of thumb is simple: if the error appears before the resolution animation finishes, it is almost always a commit-stage problem, and you should re-host the lobby. If the error appears after the animation, the rollback usually handles it, and the match can continue. A persistent post-turn resource mismatch is the worst-case scenario, and a full session restart is the only reliable workaround until Amplitude ships the next patch.
ENDLESS Legend 2 Turn Timer Glitches and Simultaneous-Turn Timing
The turn timer in ENDLESS Legend 2 is a soft countdown, not a hard lock. Players are given a window to submit their orders, and once every player has submitted — or once the timer hits zero — the engine moves into the resolution phase. When the simultaneous-turn phase runs cleanly, this takes a few seconds. When it does not, the timer can freeze at 00:00, the resolution animation can hang, and the entire match can stall.
The most common turn timer glitch in 2026 is the "00:00 freeze," which community testing traces back to a single player taking too long to compute the next turn because their client is processing a large-city batch. According to the Hotfix 1 notes, Amplitude targeted exactly this bottleneck when they fixed the lag on larger cities; the change shortened the per-turn calculation window on industrial-tier settlements, which in turn reduced the chance that any single client would overrun the timer.
Practical Workarounds for Turn Timer Glitches
Even after the latest hotfix, large simultaneous-turns matches (six or more players) can still hit the freeze because the commit stage serializes every queued order through a single host thread. The four workarounds below are what the community currently treats as the most reliable way to keep the turn timer from locking up mid-round in Endless Legend 2 multiplayer sessions.
-
Reduce city count during a session. If a friend is sitting on six cities while everyone else has three, the desync rate spikes. Encourage smaller, denser empires in the early game.
-
Close background overlays. Discord screen share, Steam overlay, and browser tabs in the background have all been reported to add latency during the commit stage. Disable them for the duration of the match.
-
Pin the host's hardware. The host machine is responsible for the authoritative resolution. A laptop running on battery, or a host with thermal throttling, will produce more timer freezes than a desktop on a wired connection.
-
Re-host on the first sign of drift. If the timer freezes for more than 20 seconds, the host should end the session and re-create the lobby from the most recent autosave. Trying to wait it out almost always leads to a hard desync.
Players who are still seeing timer issues after applying the hotfix should also check their graphics and settings profile, because the default settings for the 1.0 build are tuned for a single-player machine rather than the longer sustained load of a multiplayer match.
ENDLESS Legend 2 Custom Game and Friends Game Crashes
A custom game lobby in ENDLESS Legend 2 gives you control over map size, faction pool, victory conditions, and the simultaneous-turn toggle. It is also the most common place for an ENDLESS Legend 2 multiplayer bug to surface, because custom rules tend to stress the engine in ways the default scenarios do not. The most-reported crash pattern is the lobby that fails to launch after every player has selected their faction, often with a generic "connection lost" message that does not tell you which side actually failed.
After extensive community testing on the public beta branch and in live matches since the 0.86.239 launch build, three triggers account for almost every custom game crash at launch, each tied to a specific desync condition between the host's game session and the joining clients' local state rather than to a single reproducible engine fault.
| Trigger | How to Detect | Recommended Fix |
|---|---|---|
| Mismatched game version | One client on 0.86.238, others on 0.86.239 | All players verify build via the launcher |
| Modded faction in the pool | Mod enabled on host only, not on joiners | Disable mods on the host and re-create the lobby |
| Stale lobby cache | Host has created the same lobby with the same seed previously | Rename the lobby or use a new seed value |
Mismatched game version is by far the most common. The launch build is 0.86.239, but Steam's update propagation is not instantaneous, and players on a slower connection can stay on the previous build for an hour or more after launch. Forcing a verify-integrity pass on the launcher, or simply restarting Steam, brings the client up to the current build and resolves the crash.
A friends game in the default matchmaking pool is generally more stable than a custom game, because the default pool uses a fixed ruleset and a fixed map seed list. The trade-off is that you cannot enforce a simultaneous-turn toggle, so if your group specifically wants the simultaneous-turns mode, custom is the only path, and you have to accept the slightly higher crash rate. Players who want a deeper look at faction-specific multiplayer matchups, including which factions play well with the simultaneous-turn toggle, can check the broader multiplayer faction guide.
Reconnecting After a Crash
The reconnect flow in ENDLESS Legend 2 is one of the roughest edges of the 1.0 launch. If a player drops from a session, the host can attempt a rejoin, but the client often fails to restore the dropped player's vision and queued orders, which leads to a desync on the very next turn. The community-recommended process is:
-
The host pauses the match and ends the current session.
-
The host re-creates the lobby with the same seed and rules.
-
All players, including the one who dropped, rejoin from scratch.
-
The first turn is played on a manual pass to verify everyone is in sync.
This is slower than a hot reconnect, but it is the only way to guarantee a clean state. Players who skip the verification turn and go straight into simultaneous resolution are very likely to hit the same "turn out of order" error that triggered the original crash.
How to Report a Multiplayer Bug Effectively
A useful bug report is the difference between a fix in the next patch and a bug that lingers for months. The Amplitude team has explicitly said that bugs with more than five upvotes on their Amplifier tracker are fixed for release, which sets a clear priority bar for community reports. To get your ENDLESS Legend 2 multiplayer bug over that bar, the report needs four concrete elements.
| Element | Why It Matters | Example |
|---|---|---|
| Reproducible steps | Lets a developer reproduce the bug on a test machine | "Hosted custom game with 4 players, simultaneous turns on, no mods" |
| Session metadata | Distinguishes the simultaneous-turn variant from the regular turn-based variant | "Build 0.86.239, lobby seed Auriga-7, hotfix 1 applied" |
| Client log excerpt | Pinpoints the exact stage of the pipeline that failed | Last 50 lines of endless_legend_2.log before the crash |
| Repro rate | Helps the team decide whether the bug is systemic or a one-off | "Reproduced 3 of 5 attempts" |
The r/EndlessLegend subreddit thread pinned to the top of the multiplayer channel and the official Amplitude Discord are both reasonable places to file a report, but the Amplifier tracker is the only one with a public upvote count that the development team is committing to act on. A report that hits five upvotes there is essentially guaranteed to be addressed in the next patch cycle, which makes it the highest-value channel for players who want a fast fix.
Players who want to stay current on the rolling list of known issues can also check the unit balance and known-issues tracker, which Amplitude updates alongside each hotfix and which tends to call out the multiplayer-specific issues separately from the single-player ones.
Frequently Asked Questions
What causes the simultaneous-turn desync in ENDLESS Legend 2 multiplayer?
The simultaneous-turn engine uses a deterministic lockstep, so any client that takes too long to commit its orders — usually because of a large-city calculation, an alt-tab, or a packet drop — will diverge from the others. The host then sees a "session out of sync" message and the match has to be re-hosted from the last valid snapshot.
How do I fix a frozen turn timer at 00:00 in a friends game?
The fastest fix is to have the host end the session and re-create the lobby, then ask every player to disable Steam overlay, Discord screen share, and any background overlays before rejoining. Closing extra browser tabs and switching the host to a wired connection also reduces the chance of the timer freezing again on the next turn.
Can I play ENDLESS Legend 2 multiplayer with mods in a custom game?
Yes, but the mod has to be installed on every player's machine in the same order, and the host has to launch the lobby with the mod enabled from the start. If even one joiner is missing the mod, the lobby will fail to launch after the faction selection screen and the entire session will be lost.
Is the ENDLESS Legend 2 turn based multiplayer mode stable enough for ranked play?
The default ranked-style rulesets in a friends game are stable as of the launch hotfix, but the simultaneous-turn variant still produces occasional desyncs on long matches. Casual play is safe; serious competitive play is best saved for after the second multiplayer-focused patch lands.
Will the next patch fix every ENDLESS Legend 2 multiplayer bug?
No single patch will address every multiplayer bug, because the desync category is a class of issues rather than a single defect. The development team has committed to fixing the most-upvoted reports each cycle, so filing a clean, reproducible report on the Amplifier tracker is the fastest way to get a specific bug addressed.
Multiplayer at 1.0 is playable, the launch hotfix already cleaned up the worst lag regression, and the simultaneous-turn system is fast once you learn to keep city counts modest and the host's hardware pinned. The remaining bugs cluster around the reconnect flow and the custom-game launcher, and the most reliable path through both is to keep sessions short, re-host on the first sign of drift, and file a clean report whenever a reproducible bug crosses your lobby.