{"id":20002,"date":"2026-03-07T11:04:52","date_gmt":"2026-03-07T11:04:52","guid":{"rendered":"https:\/\/magicstark.cz\/?post_type=herni-recenze&p=20002"},"modified":"2026-03-07T11:04:53","modified_gmt":"2026-03-07T11:04:53","slug":"marathon-review-pc","status":"publish","type":"herni-recenze","link":"https:\/\/magicstark.cz\/en\/game-reviews\/marathon-review-pc\/","title":{"rendered":"Marathon Review \u2013 A Technical Nightmare in Cyberpunk Colors"},"content":{"rendered":"\n
\n

What is Marathon exactly?<\/h2>\n\n\n\n

Marathon<\/a><\/strong> was supposed to be the grand return of a legendary IP and Bungie’<\/a>s answer to the rising popularity of extraction shooters like Arc Raiders<\/a><\/em>. The studio that gave us Halo<\/em> and Destiny<\/em> attempted to graft its world-class action onto hardcore looting and survival mechanics. However, the result in its current state is a cautionary tale of how an ambitious project can fail when technical polish and basic world readability are neglected.<\/p>\n\n\n\n

While the game tries to lure players with high stakes and adrenaline-fueled loot runs, the reality of 17 hours played is one of pure frustration. The “high-stakes looting deathmatch” concept only works if the game doesn’t trip the player up with its own broken architecture. While Bungie<\/strong> can still craft a great shooting feel, in Marathon<\/strong>, this element is wrapped in so many layers of problems that it is difficult to actually enjoy.<\/p>\n\n\n\n

\n