2012-03-07, 01:05 AM
Some comments:
Those of you who are assuming the reason for these attacks is the removal of hacked gear, are forgetting we had the same thing happen long before Nexon touched that gear. Back then there was speculation it was because Nexon sued some people associated with a certain hacking site and tool.
These attacks are also not made for the purpose of duping. As several posters said above, DDoS is a very crude method of crashing a channel - if it even works at all. Dupers are usually able to find bugs in Nexon's server software, which cause an instant channel crash upon receiving a certain packet (or sequence of packets). They use these to time their duping crashes precisely and to crash one channel at a time. What we are seeing now just doesn't fit.
Eos is, of course, correct about preventing duping. It's a relatively simple matter of actually using the features the database product offers, instead of treating it as nothing but a glorified flat file. I'd also like to point out that the "item ID" method, besides being inefficient, does nothing against the duping of stacks and stacks of "rare" scrolls, recipes, or crafting materials.
Those of you who are assuming the reason for these attacks is the removal of hacked gear, are forgetting we had the same thing happen long before Nexon touched that gear. Back then there was speculation it was because Nexon sued some people associated with a certain hacking site and tool.
These attacks are also not made for the purpose of duping. As several posters said above, DDoS is a very crude method of crashing a channel - if it even works at all. Dupers are usually able to find bugs in Nexon's server software, which cause an instant channel crash upon receiving a certain packet (or sequence of packets). They use these to time their duping crashes precisely and to crash one channel at a time. What we are seeing now just doesn't fit.
Eos is, of course, correct about preventing duping. It's a relatively simple matter of actually using the features the database product offers, instead of treating it as nothing but a glorified flat file. I'd also like to point out that the "item ID" method, besides being inefficient, does nothing against the duping of stacks and stacks of "rare" scrolls, recipes, or crafting materials.