Marathon Technical Problems: Players Love the Game, Hate the Stability

There is a specific kind of frustration that only hits when you actually care about something. That is what the Marathon community is living right now — and the Steam/Reddit divide lays it bare more cleanly than usual.

Steam reviewers, playing across 40 to 200 hours, are largely landing positive. One reviewer at 154 hours calls it outright: "This game rules. I have never really been into extraction shooters but the combat and movement mechanics make this so much fun to play." Another at 195 hours describes it as "an amazing game" with "a rich world." Even a two-hour reviewer gushes about the immersive experience and sound design. These are real, paying players sticking around for serious time — and their verdict on the core game is warm.

Reddit tells a different story at the surface level, but dig past the post titles and you find the same people. They are not here because the game is bad. They are here because it is breaking on them.

The bugs-and-tech-support megathread from u/Shabolt_ is open for Season 2, and it is filling up. u/goblinskirmisher put it plainly: "This game has become unplayable the last week for me. Every other game I get in I am DCing. Once it starts it happens repeatedly like every 2 minutes until the game is over." u/PringlesPun1sh3r1980 is hitting Weasel error codes on PS5 — hardwired ethernet, full restart, still locked out.

Then there is u/SuperV1234, who threads the needle that defines this whole cycle: "I love the game and enjoy playing it, despite how poorly made it is." That sentence is doing a lot of work. It is not a troll or a quitter. It is someone who has absorbed every bug, every disconnect, every stuttered frame — and still shows up — but is done pretending the technical foundation matches the quality of the design underneath it.

On Steam, a 61-hour reviewer cuts to it without ceremony: game gets a CPU-usage patch, runs worse afterward. The update made things heavier.

This is not outrage. It is exhaustion. And exhaustion from players with real hours is the kind of signal worth tracking.

To be fair to the data: the noise here is coming from a vocal subset, and the broader Steam picture is "Very Positive." The 200-hour negative reviewer even leads with "I like this game." A 27-hour reviewer swings harder — "Another generic extraction shooter" — but at 27 hours they have barely touched the endgame content the longer-time players are calling excellent.

Twitch attention this week is scattered rather than spiking around any single crisis: clip titles on BogOnMyDog's stream reference weapon loadouts, another from l3vski's stream flags what sounds like an inventory glitch ("game makes me sell my dna key"), and wallah's stream produced a "Ganglion glitch explanation" clip drawing 62 views. The pattern across these titles is consistent with what Reddit is reporting — people finding and flagging bugs — but view counts are modest, which suggests this is friction, not catastrophe.

The double XP weekend noted by u/Ke7een (up to 1,400 Cyberacme - Faction XP from the Shell Games contract chain) and active squad-finder posts from new S2 arrivals like u/anypastaisfine show the social engine is still running. The game is not emptying out. But the gap between "this movement and gunplay are exceptional" and "I disconnected twice this match" is real — and it is the thing the community most needs addressed before that goodwill clock runs out.