2011-11-03, 10:22 AM
While I like Nexon's somewhat new stance on directly trying to punish hackers by flat-out deleting characters, the way this has been handled is just as amazingly un-professional as I'm sure most of us expected it to be. What they should've done imo (semi-pseudo-SQL-code):
UPDATE character_table
SET end_date = today, main_account_perm_banned = YES
WHERE (hair_id IN (list of hair ids not yet available) OR face_id IN (list of face ids not yet available))
AND character_created after date hack was first believed to be used
AND character_type = UA
YES, a paragraph or two of code code is ALL IT TAKES! But alas, a company that can't even put correct dates on their notices and doesn't proofread can't be expected to have any sort of competence.
I can also go on and on about how easily fixable the duped and/or enhance-hacked and/or elemental-glitched weapon situation is but that's for another topic.
UPDATE character_table
SET end_date = today, main_account_perm_banned = YES
WHERE (hair_id IN (list of hair ids not yet available) OR face_id IN (list of face ids not yet available))
AND character_created after date hack was first believed to be used
AND character_type = UA
YES, a paragraph or two of code code is ALL IT TAKES! But alas, a company that can't even put correct dates on their notices and doesn't proofread can't be expected to have any sort of competence.
I can also go on and on about how easily fixable the duped and/or enhance-hacked and/or elemental-glitched weapon situation is but that's for another topic.