Another Nexon Mistake

Hey things happen. Their is so much a company can do towards hackers attacking them. Look at sony and others companies that have felt the wrath of hackers.

It's rather ironic that you try to use Sony as an example. See, the only reason Sony "felt the wrath of hackers" is because their security was out-dated and weak:
"Being susceptible to SQL injection is embarrassing enough—techniques to prevent it are well-known, and easy to apply to any database-driven website—but what makes this hack even worse is the data that has been compromised."

Weak, you know, like Nexon's is now.

So your analogy was quite fitting, but your conclusion was flawed.
The fault still very much lies with the company itself.

Also dont give me the bs that the login id packet shouldn't have been in the code, because all the original code comes from kms. So give gms a break on an issue they could not control. I dont know how packet editing works, but i doubt to get rid of a packet is as easy as pressing backspace.

Two things:
1 - The GMS team certainly could control it, much like they've adapted to other holes in the original code.
2 - Most people are complaining about Nexon as a whole!

I find it strange that you're so eager to protect the GMS team from ridicule.