Community
July 11, 2026 · 2 min readDrafted with AI tooling.REDDIT

Marathon Update 1.1.0.5: Solo Queue Fix and What Players Are Saying

solorankedprogressionbeginner

THE FIX THAT MATTERS

Bungie dropped Update 1.1.0.5 today, and the headline change is a targeted solo queue fix. The patch addresses an issue where selecting Solo Queue could fail to update your matchmaking state — leaving players locked into another queue or unexpectedly shunted into a crew-based lobby. If you've been hitting a wall trying to queue solo and ending up somewhere you didn't ask to be, this is the patch you were waiting for.

It's a small note in the official patch text, but the problem it describes was anything but small in practice. Solo queueing is foundational to how a meaningful portion of players experience this game, and a matchmaking bug that silently routes you somewhere wrong is the kind of friction that turns a frustrating session into a "I'm done for tonight."

WHAT THE COMMUNITY WAS SAYING BEFORE THIS LANDED

The timing is worth noting. In community threads this cycle, u/tee-jade posted about solo queue still not showing up — describing the issue as intermittent and persistent: it had worked once, then stopped, and the question was whether a hotfix was coming. That thread is a direct line to what 1.1.0.5 addresses.

It's a narrow slice of the community conversation, not a full revolt — but it's the right slice. Solo queue failures are the kind of bug that disproportionately hits players without a regular squad: new players feeling out the game, returning players who haven't rebuilt their crew yet, and the significant chunk of the playerbase that simply prefers to run alone. Those are exactly the players Marathon needs to retain.

REACTION: NOT YET IN

Here's the honest read: this patch just landed, and real player reaction to 1.1.0.5 specifically is not yet in the sources available this cycle. The Reddit threads captured here predate the fix. The Steam reviews don't reference it. The Twitch clip titles — "lobby wipe in 60s," "greenhouse key manifest," a few vague reactions from streamers like Diffizzle and pyroxna — don't tell us anything about matchmaking sentiment post-patch.

What those Steam reviews *do* tell us, taken as a baseline, is that the broader paying playerbase is in a surprisingly positive place. Multiple reviewers with real time in the game are logging genuine enthusiasm — one with 356 hours calling it good, another with 38 hours describing it as a game that won them over despite usually hating the genre. That underlying goodwill matters here: it means the solo queue bug was irritating an otherwise engaged player base, not a community already looking for the exit.

THE BOTTOM LINE

1.1.0.5 is a surgical patch — one fix, no frills. Whether it fully resolves what u/tee-jade and others were experiencing is the question the next 24-48 hours will answer. The lobby will tell us what the patch notes can't. Check back when the threads catch up to the fix.

SHARE
POST TO XREDDIT
← MORE FROM Community
Related Intel
Community
Marathon S2 Gear Gap and Server Woes: What Players Are Grinding Through
87d ago
Community
Marathon Update 1.1.0.5: Solo Queue Fix Lands, Reaction Pending
91d ago
Community
Marathon Steam Reviews vs. Reddit: Two Very Different Games
92d ago
Meta & News
Marathon D54 Battle Pistol: The Secondary That Deserves a First Look
97d ago
Meta & News
Marathon Volt Battery Weapons: The Trickle Charge Meta Shift
58d ago
Meta & News
Marathon Solo Vault Breaker: What the 1.1.5.1 Changes Mean
73d ago
LIVE
STEAM3.7KRUNNERS ONLINE
TWITCH658WATCHING · 12 LIVE