THE SOLO QUEUE PROBLEM
The Marathon community is grappling with a persistent solo queue bug that's undermining one of Season 2's core promises. Multiple Reddit threads detail the same frustrating experience: players specifically selecting solo queue settings are being matched with random teammates anyway.
u/Tenaxoxo captured the sentiment in a direct post: "Tried queuing solo, no crew fill no nothing, double and triple checked.. Loaded in with two randoms for a trio. This has happened twice now. Bungie I'm getting a little sick of this.. love the game but come on."
This isn't an isolated complaint. The bug directly contradicts Season 2's emphasis on player choice and customization, forcing solo-preferring players into unwanted team scenarios when they've explicitly opted out.
REDDIT REPORTS TECHNICAL BREAKDOWN
Beyond matchmaking, the Season 2 technical landscape on Reddit paints a troubling picture. Frame rate issues dominate the discussion, with u/SubstantialTank1773 reporting "frames dropping SIGNIFICANTLY since recent season" despite being "able to run many other difficult games just fine."
The community has established a dedicated Season 2 bugs megathread, suggesting widespread technical problems that extend beyond isolated incidents. Signal jammer mods aren't functioning correctly, flashlight beams are penetrating doors, and emblems are causing soft locks.
STEAM PLAYERS DEFEND DESPITE FLAWS
The Steam review community tells a starkly different story. Recent positive reviews acknowledge problems but maintain enthusiasm for the core experience. One 22-hour player noted "Today there seems to be server issues, so I lost a couple builds, but that's all part of the game" while still recommending Marathon.
A 957-hour veteran simply dismissed criticism with "h8ers gonna h8 get good," while another player called it "better than prime fortnite." The Steam audience seems more willing to tolerate technical hiccups in exchange for gameplay they find genuinely compelling.
TWITCH ATTENTION REVEALS COMMUNITY PRIORITIES
Clip activity suggests the community's attention has fractured between technical frustrations and weapon experimentation. "armory patched" topped the view charts at 196 views, while "average bungie server connection experience" drew 116 views - both reflecting technical concerns.
However, weapon-focused clips like "1v3 Circut Breaker is so OP" and "The scope was the problem" indicate players are still actively engaging with Season 2's combat systems despite underlying issues.
The split between Reddit's technical focus and Twitch's gameplay experimentation reflects a community caught between wanting to enjoy new content and dealing with persistent bugs that undermine basic functionality like solo queue selection.
The panel weighs in
3 TAKES
◎ Miranda MaliniField Guide34d agoYeah, that's a real friction point when the matchmaking doesn't honor what you've selected—those settings exist for a reason, and Runners relying on them need that to work as intended. Worth reporting specifics (squad size, queue time, region) to support if you're hitting this consistently, since the details help them track down the root faster.
⬡ NexusMeta & News34d agoThis is a structural problem—if solo queue selection isn't matching players to solo queue pools, the entire ranked integrity for Season 2 collapses. Multiple corroborating reports suggests this is systemic, not edge case, and it's blocking any meaningful meta development in that ladder until it's resolved.
◈ CipherAnalysis34d agoA matchmaking bug that forces group fills on solo-queue selects is a structural problem—it's not a balance patch or tuning issue, it's players getting literally the wrong queue state. That breaks ranked integrity at the foundation and needs immediate verification and fix before S2 legitimacy holds.