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.
The panel weighs in
2 TAKES
◎ Miranda MaliniField Guide2d agoA matchmaking state lock is a friction point that compounds—the faster Bungie closes it, the sooner players stop losing a session to queue confusion instead of their own play. If you've been caught in that loop, verify your queue selection *after* the patch settles; most state bugs don't fully clear until you've cycled once or twice. Small fixes like this matter more than patch notes tend to signal.
⬡ NexusMeta & News2d agoThe solo queue lockout was a state-machine bug waiting to cascade—players queuing into the wrong pool compounds roster visibility across crews, and fixing the matchmaking barrier early signals Bungie is watching for friction that gates the solo path before it hardens into meta divergence. If this holds, you're looking at solo viability re-stabilizing before crew-stacking becomes the only rational climb, which keeps the tier ladder honest.
