Mark Roberts says Path of Exile 2 temple exploits “ruined Christmas” after emergency patches

Path of Exile 2 co-director Mark Roberts says Grinding Gear Games had to interrupt its holiday break because temple exploits effectively let players print loot and “become in-game millionaires in a few days.” Roberts called it “ruined Christmas for me” after learning the strategy was being repeated again in the middle of an interview, and then added that he’s “lost all sympathy for that bloody temple and everyone running it.”

Here is the core issue, straight from the developer description. The “temple” system was introduced in the most recent season as a way to fight a new boss and access temple-exclusive loot. But players quickly turned it into the most lucrative loot engine in the game by building their temple connections to maximize valuable drops far beyond what they were intended to get anywhere else. According to Roberts, this severity was bad enough that the studio deployed emergency fixes, including a moment where he reacted in real time as another developer showed him what players were doing.

To understand why this matters so much, it helps to zoom out on how Path of Exile-style economies work. In PoE 2, making as much in-game wealth as possible tends to become the primary goal for players who want to upgrade their builds with the most powerful items. That creates a strong pull toward strategies that convert time into loot efficiency. When one system becomes disproportionately rewarding, it doesn’t just benefit a few players. It reshapes what most players feel is “necessary,” because high earners set the pace for the market. The source describes the outcome bluntly: the trading economy “crumpled” in the last season the moment word got out about the technique.

The exploit mechanics, as Roberts explained through the described player approach, were less about cheating and more about exploitation of intended flexibility. Part of the strategy involved “locking a character in the campaign” and repeatedly resetting a level to “gradually grow your temple into a money-making machine.” Then players linked specific synergistic rooms together in an “endless snake.” That design choice mattered because it helped them avoid certain deletion behavior after running the dungeon, while also “guarantee[ing] heaps of valuable loot” versus other avenues in the game. The result was an economy shock: too much loot coming from one optimized loop, too quickly.

Roberts also described how the studio’s ability to detect and respond changed. He said that because of this “bloody temple,” Grinding Gear Games “now-because of this bloody temple-have way more active stats for checking how many items are dropping in certain instances.” That is a classic live-service pattern: you ship a system, players find the edge, and the developer retrofits measurement and control because the first-round visibility wasn’t enough.

Then, because players moved fast, the studio’s response had to move faster. The source says Roberts was told the exploit was being run again, and he noted what he saw on-screen: “It says, 'TEMPLE SHENANIGANS T1 ISSUE AFTER INTERVIEW' in capital letters,” he said while looking off-screen. Within hours after the interview, a patch went out to address the temple strategy. Roberts framed it as a mid-league intervention because the first case and subsequent threat were severe enough to justify breaking the usual cadence: “Typically, the developers try not to touch anything major a few weeks into a league, but the temple exploits were too severe to ignore.”

There is also a perception and expectation risk here, especially for early access. PoE 2 is technically early access, but most players treat it like PoE 1 and expect Grinding Gear Games to be on top of balancing so it doesn’t sour the experience. The source emphasizes that when the economy breaks, it doesn’t just create unfairness. It changes the emotional contract between players and the studio. Roberts’ “lost all sympathy” line is about more than one patch. It’s the frustration that players kept turning the same system into a market-distorting machine even after the first emergency response.

For executives and boards thinking in operational terms, the second-order implication is simple: live-service security is not just about fraud or hacks. It is also about gameplay systems with emergent behavior. If a mechanic can be looped, optimized, and repeated, it can force engineering and product teams into emergency mode. That can disrupt roadmaps, consume staffing, and push studios toward permanent on-call readiness, especially around seasonal releases.

And for peers who are planning launches around major holidays, there is a strategic stake. The source ends by pointing out the uncomfortable reality: players “aren’t going to respect that you're on vacation,” so someone has to be “on-call to stop whatever absurdly powerful exploit they inevitably find.” Roberts’ “trauma” metaphor is colorful, but the operational lesson is real. When the economy is part of the product, exploit-driven shocks become business continuity problems, not just gameplay balance tasks.