Diablo 4 Trading Suspended Again After Item Exploit Discovered

Blizzard Entertainment has pulled the plug on Diablo 4 trading yet again following the emergence of a new duplication exploit.

Community manager Rich Bantegui updated fans on the feature’s sudden removal in a post on the official Diablo 4 forums. Trading will remain offline until Blizzard has found an optimal fix for the glitch that some players have been taking advantage of.

“We’ve suspended player trading in Diablo 4 until further notice due to a duplication exploit,” Bantegui wrote. “We are working on a fix to amend this issue and will update you once we’ve reinstated the ability to trade. We will continue to monitor this activity to ensure a healthy playing experience for all.”

Bantegui continued: “Any account that engages in gold and item duplication exploits will be actioned in accordance with our End User License Agreement. We thank you for reporting this exploit to us and your patience.”

Related: Error-Filled Diablo 4: Season of Blood Video Pulled by Blizzard

Blizzard did not immediately detail the specific exploit some players are using to cheat their way through Diablo 4 this time around. However, as spotted by VGC, a few forum users have recently mentioned a new dupe exploit that revolves around season 2 boss Echo of Duriel. The boss, which has the ability to drop Uber unique items, is supposed to be difficult to summon. Where the problem lies, according to forum user Gorz, is that some are navigating around the requirements needed to access the boss by duplicating certain items. Again, Blizzard hasn’t confirmed if this is the reason for the pause on trading, but it certainly sounds like an egregious exploit nonetheless.

This is only the latest occurrence of pulled features in Diablo 4. In August, another dupe exploit resulted in Blizzard’s decision to temporarily stop trading. It took the developers mere days to reinstate trading during that first hiccup, so let’s hope it won’t be long before the feature comes back again. When the studio has found a fix for the issue, you can be sure to read about it here.