For some reason blizzard couldn't fix this behavior, instead they kept adding layers of protection that would prevent you from dropping items. So if you can find a way to drop items while trading, you end up duplicating them. Most 'real' dupe methods revolved around trade window, which rolls back both players' inventories if trade is canceled. The games were built to work on dial up (56K and slower) internet speeds for multiplayer, something that they don't have to do now.Ĭrash/rollback dupes are the simplest (have one player save and exit game with items, then crash the game before the other player's empty inventory is saved), but not reliable and attracts attention, so I don't think they were used for mass/'commercial' duping.

Hell, in Diablo 1 you could dupe by throwing an item on the ground, having a pile of 1 gold in your inventory, clicking on the item on the ground from afar, and clicking on your gold pile in your inventory - I might have that backwards, but either way - duping in Diablo (1/2) has always been about abusing the way the game processes data naturally.

That particular bug has been fixed, but it was one of many ways to cause a conflict with the server and multiple clients to force dupes. So if you drop an item, other play picks it up and leaves naturally, and you force the server to crash - you've generated a rollback for the entire server. If I'm not mistaken, saving happen(s/ed) in batches, or by saving and exiting. Last updated at 14:00:17 UTC Weekly Help Desk RAGE Loot Thread Trade Threadīasically it comes down to (at least one previous method) exploiting the 'save and exit' and savestate intervals of the server.

Diablo 2 remastered duped runes