Bungie's pre-launch playtest for Marathon has closed, and the developer is now sorting through a substantial pile of community feedback before the extraction shooter's full release on 5 March. In a weekend feedback recap published to the Marathon Development Team's social channels, the studio acknowledged several recurring complaints and outlined which concerns have been formally logged with the development team.
The most talked-about gap in the game's current queue system is the absence of dedicated duo lobbies. Bungie confirmed it has heard the request, stating the feedback has been "logged and shared with the team," as PC Gamer reports. At present, players can only matchmake as a solo or as part of a full three-person crew. Two friends who want to play together must either accept a randomly assigned third squad member or risk being outnumbered in every engagement. The studio gave no firm commitment on whether a dedicated duos playlist would arrive at launch or be added later.
Player-versus-player pacing generated divided opinions. Time-to-kill, or TTK, is the central battleground: some players want engagements that last longer and allow for more tactical duelling, while others are comfortable with the current speed. According to Game Informer, Bungie is reviewing runner density on non-beginner maps as part of this assessment, with Perimeter already receiving a temporary increase in squad numbers during the playtest to test higher PvP contact rates.
The game's user interface drew some of the loudest criticism across the weekend. Reports described cluttered menus, inconsistent icon design, and difficulty reading key information during live combat. Bungie says it plans to "continue iterating post-launch" on the UI, telling players it wants to ensure they can "read what's happening mid-fight, manage your equipment effectively, and see your pings without any noise around them," as reported by GameSpot. Players have been directed to the official Marathon Discord to continue submitting interface feedback.
PC performance also emerged as a concern, with Dot Esports noting that players reported high CPU usage, low GPU utilisation, and frame-rate ceilings in the 80 to 100 FPS range during intense combat. Bungie has asked affected players to submit hardware specifications and video clips through its help forums. The developer did fix several issues in real time during the playtest, including a voice chat bug, mouse input lag affecting users with streaming or capture software, and an overzealous chat filter that was blocking innocuous terms.
Movement also drew scrutiny. As The Escapist reports, players requested smoother slide transitions, better momentum preservation on downhill terrain, and reduced heat generation on core movement abilities to improve chase and disengage scenarios. Bungie acknowledged the discussion around slide feel and heat mechanics is significant enough to warrant review.
Marathon on Steam recorded 143,000 concurrent players during the Server Slam, according to GameSpot, a figure that reflects genuine market interest even as some observers noted the game is entering a crowded extraction shooter space alongside a resurgent competitor in ARC Raiders. Bungie noted that players who progressed deeper into the game's faction and progression systems reported increasing enjoyment, which may suggest the game's friction points are concentrated in its early experience.
With only days remaining before launch, not every piece of feedback can realistically be addressed. The studio's willingness to publish daily recaps and respond to specific requests during the Server Slam is an encouraging sign of its feedback culture, though critics have pointed out that issues as fundamental as UI readability should ideally have been resolved before a public playtest concluded. How Bungie manages its post-launch update cadence will ultimately determine whether Marathon builds on its early player numbers or cedes ground to its competitors.