Bungie’s extraction shooter Marathon has faced significant player feedback following the release of its first major post-launch patch, update 1.0.0.4. The patch, which went live on March 11, 2026, included several improvements intended to enhance gameplay, but one change in particular—louder gunshot and explosion audio—altered the game’s dynamics for many players.
The patch notes detailed multiple adjustments, such as additional ammo in free loadout kits, improved objective markers, and a fix for a map bug affecting the character Rook. While these changes were generally well-received, the increase in the distance at which gunfire could be heard led to a noticeably more aggressive in-game environment. Players reported feeling constantly under threat, with encounters becoming more frequent and challenging, creating frustration across online discussions and the Marathon subreddit.
Bungie Responds to Community Concerns
The reaction from the community prompted Bungie to address the issue publicly. Marathon audio director Chase Combs acknowledged player feedback on Twitter, signaling that the team had heard the concerns. Game director Joe Ziegler later provided a more detailed explanation through the Marathon development team’s BlueSky account.
Ziegler stated that the original intent of the audio change was to give players more information about their surroundings, helping them make tactical decisions regarding danger and movement. However, he admitted the adjustment overextended the audio range and negatively impacted gameplay.
In a follow-up statement, Bungie confirmed it would partially roll back the audio changes in an upcoming patch. The goal is to retain the benefits of enhanced map awareness without creating an overly aggressive environment that players found overwhelming. The studio emphasized that it is actively monitoring the effects of the louder gunshots and will continue refining the system based on community feedback.
Impact on Gameplay and Player Experience
The update illustrates the challenges developers face when balancing real-time changes in online multiplayer games. While the intention was to provide players with better situational awareness, the increased audio range unintentionally made combat encounters more frequent and intense. Many players have noted that returning to a slightly reduced audio range should restore the intended gameplay balance without removing the informational benefits of the update.
Looking Ahead for Marathon Updates
Bungie’s handling of update 1.0.0.4 highlights the studio’s commitment to responding to player feedback. While the partially rolled-back audio adjustment may address the immediate concerns, the team continues to evaluate the broader effects of gameplay changes and is expected to implement further refinements in future updates. Marathon players can anticipate additional patches that aim to maintain the balance between strategic awareness and fair combat encounters.
Source: Kotaku
Make sure to check out our articles on gaming gadgets:
Best Apple Products for Gaming
Best Nintendo Switch Accessories
Best Gaming Androids (phones)
Frequently Asked Questions (FAQs)
What changed in Marathon update 1.0.0.4?
The patch increased the range at which gunfire and explosions could be heard, added more ammo to free loadout kits, improved objective markers, and fixed a bug on Rook’s map.
Why are players upset about the update?
The increased gunshot audio range made combat feel more intense and frequent, creating frustration for players who felt constantly under attack.
How is Bungie addressing the feedback?
Bungie has acknowledged the issue and announced it will partially roll back the audio changes in a future patch to restore balanced gameplay.
Will the louder gunshots be completely removed?
No, Bungie plans to retain some of the audio improvements to maintain situational awareness while reducing the distance that made encounters overly aggressive.
When can players expect the rollback?
Bungie has not provided an exact release date for the rollback but confirmed it will be included in an upcoming patch following further testing and monitoring.
