Arguably a new public dupe.
You should have an idea of where to look for specifics if you care about them, but here's the part relevant to us:
1) It's an old dupe that has reportedly been used by most major item suppliers for some time
2) Although the details behind the dupe have been made public, some of the actual programs required have not been, so there shouldn't be any huge duping sprees for quite some time still.
3) The method involves causing server wide crashes/lag. Even though the dupe itself relies on a bit more than that (d2hackit trigger crap doesn't give people precise enough timing) kids with d2hackit are still trying to make it work, resulting in the fun of server wide crashes/lag
4) Due to the above, blizzard will likely end up banning many accounts because they really don't like attacks on their servers
5) Unfortunately however it's supposedly not something that blizzard is supposed to be able to fix using a reasonable amount of resources.
6) It essentially works like:
Any player leaves game, all players are saved.
All players are not saved at the exact same time, they are saved in order.
So the 8th player in the game drops items, first player picks them up and leaves, as players are being saved in order server is crashed, and thusly 8th player is not saved.
I'm not so much worried about the possibility of a duping spree with this one so much as I don't care for the idea of mass server crashes/lag. It also involves coordinating having multiple games on one server (since the server is being crashed the more games you have the dupe coordinated on on that server the more efficiently you can dupe), so there's a chance of the fun of even longer lines >_<
You should have an idea of where to look for specifics if you care about them, but here's the part relevant to us:
1) It's an old dupe that has reportedly been used by most major item suppliers for some time
2) Although the details behind the dupe have been made public, some of the actual programs required have not been, so there shouldn't be any huge duping sprees for quite some time still.
3) The method involves causing server wide crashes/lag. Even though the dupe itself relies on a bit more than that (d2hackit trigger crap doesn't give people precise enough timing) kids with d2hackit are still trying to make it work, resulting in the fun of server wide crashes/lag
4) Due to the above, blizzard will likely end up banning many accounts because they really don't like attacks on their servers
5) Unfortunately however it's supposedly not something that blizzard is supposed to be able to fix using a reasonable amount of resources.
6) It essentially works like:
Any player leaves game, all players are saved.
All players are not saved at the exact same time, they are saved in order.
So the 8th player in the game drops items, first player picks them up and leaves, as players are being saved in order server is crashed, and thusly 8th player is not saved.
I'm not so much worried about the possibility of a duping spree with this one so much as I don't care for the idea of mass server crashes/lag. It also involves coordinating having multiple games on one server (since the server is being crashed the more games you have the dupe coordinated on on that server the more efficiently you can dupe), so there's a chance of the fun of even longer lines >_<
