Deleted Characters Being Reviewed

Wasn't CrazyNomad of Broa deleted, then Nexon recovered the character? Or am I remembering wrong?

no. my char got xfered to bera and name changed. Nexon transfered my char back to broa, changed my ign back to crazynomad, and they had track of EVERY item I had on my char, and mule accounts, since Gm Tiara dropped everything for me (even my 5000 power elixir I had on my mule account).

I know that belisema and tuffgai, both had their char deleted, and nexon had to remake it, power lvl it (I remember tracking tuffgai, and it would be on a secret map).

Lovely.

So they are going to attempt something that's never been done before, on thousands of characters at once, in the live server.
Well, with their track record, I'm sure everything will work out perfectly.

Server Check was an unmitigated failure.
GM Board's still showing random messages, character's still missing.

Or is it scheduled for tomorrow night? It's hard to tell when they say it's on Thursday morning EST, Friday morning PST.

edit: nevermind, I can't understand times either at 8am. Patience young padowan.

That was sad.

>The maintenance will last approximately four hours.
>Eastern: 2:00 AM - 6:00 PM Thursday, November 3, 2011

So glad I've learned nexonspeak.

>The maintenance will last approximately four hours.
>Eastern: 2:00 AM - 6:00 PM Thursday, November 3, 2011

So glad I've learned nexonspeak.

this is why i use PST, nexon doesn't know how to add.

this is why i use PST, nexon doesn't know how to add.

Clearly they don't know how to subtract either based on the number of extra deletions

Clearly they don't know how to subtract either based on the number of extra deletions

i wouldn't call that substracting, but more of differentiating balls and cubes.

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.

They actually don't have a creation date in the character database unless they've added one.
Just the logout date.

Not sure how they're doing the UA link either but I doubt it's in the character table, more likely a separate table like spouses.
Banning of course isn't in the character DB at all, that's done in the account DB.

They actually don't have a creation date in the character database unless they've added one.
Just the logout date.

Which is probably why they used the date the Cygnus skill was acquired (this would be in the Quest table). But does not explain why they used April 7th, give or take a day.

Not sure how they're doing the UA link either but I doubt it's in the character table, more likely a separate table like spouses.

...and performing a Join is way beyond their abilities.
Although, as has been pointed out elsewhere, a normal adventurer does not need a KoC on the account in order to get the skill. They can just do the Lunar Dew quest at level 70. So perhaps the test for a KoC is unnecessary.

If I were Nexon, with their renowned delicacy, I'd just go ahead and ban any account that got the skill within the past 2-3 weeks or however long it was, and tell the users to submit a ticket with a preset title if they think they were banned wrongfully. Then set up an automated filter to handle those tickets, and a procedure to check, for example, if the character has any quests completed significantly earlier (indicating it's an old normal adventurer), or still has its KoC link, or the user can provide screenshot proof of having had a KoC at the time the UA was created. Obviously if the char is a Cannoneer or has unreleased hair or eyes, the appeal would be rejected out of hand.

They actually don't have a creation date in the character database unless they've added one.
Just the logout date.

Not sure how they're doing the UA link either but I doubt it's in the character table, more likely a separate table like spouses.
Banning of course isn't in the character DB at all, that's done in the account DB.

LOL, the fact that there's no creation date unless they've created one is fail within itself (not like I know the exact columns/table names which are there anyway). Even without the line of code relating to the creation date, that algorithm would work based on the fact that characters with unreleased hair/face ids are released. Same thing with character type id. Revised:

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))

^still works and is full-proof.

As for hacked UA chars without the new hair/face, there's gotta be other simple ways.

If I were Nexon, with their renowned delicacy, I'd just go ahead and ban any account that got the skill within the past 2-3 weeks or however long it was, and tell the users to submit a ticket with a preset title if they think they were banned wrongfully. Then set up an automated filter to handle those tickets, and a procedure to check, for example, if the character has any quests completed significantly earlier (indicating it's an old normal adventurer), or still has its KoC link, or the user can provide screenshot proof of having had a KoC at the time the UA was created. Obviously if the char is a Cannoneer or has unreleased hair or eyes, the appeal would be rejected out of hand.

that's just as bad.

^still works and is full-proof.

As for hacked UA chars without the new hair/face, there's gotta be other simple ways.

These two statements contradict one another, since it's not full proof if it misses anyone who looks natural

And both of you left out an important qualifier ;

OR b_job in ( illegal jobids )

that's just as bad.

Actually far more recoverable since any tardmonkey of a GM can unban someone. Undeleting takes significantly more skills.

These two statements contradict one another, since it's not full proof if it misses anyone who looks natural

And both of you left out an important qualifier ;

OR b_job in ( illegal jobids )



Actually far more recoverable since any tardmonkey of a GM can unban someone. Undeleting takes significantly more skills.

you are still taking away from people who did nothing, which imo, is just as bad. sure, easier to fix, but what we have right now is also better than "ban everyone with UA skills" see what i mean?

you are still taking away from people who did nothing, which imo, is just as bad. sure, easier to fix, but what we have right now is also better than "ban everyone with UA skills" see what i mean?

No, it's not just as bad.
Permanent Irrecoverable damage is orders of magnitude more severe than the temporary inconvenience of blocking them for a while.

These two statements contradict one another, since it's not full proof if it misses anyone who looks natural

And both of you left out an important qualifier ;

OR b_job in ( illegal jobids )



Actually far more recoverable since any tardmonkey of a GM can unban someone. Undeleting takes significantly more skills.

Jeez, I meant full-proof for those with illegal hair/face. It works perfectly at least in that regard.

As for the create_date of the character. It HAS to be somewhere in the maple schema (i.e. an inner join/subselect may just do the trick here). Thanks for the illegal jobids thing (though I'm not sure if cannoneers were made -can someone confirm?).

They actually don't have a creation date in the character database unless they've added one.
Just the logout date.

Use the earliest completed date in the quest table. Dunno if UAs have a quest auto-completed on creation though. Wouldn't it be when they get their clothes?

As for the create_date of the character. It HAS to be somewhere in the maple schema (i.e. an inner join/subselect may just do the trick here).

You are severely over-estimating their design. It's been leaked more than once, go look at it, or at the queries that were dumped from the client.

No, it's not just as bad.
Permanent Irrecoverable damage is orders of magnitude more severe than the temporary inconvenience of blocking them for a while.

hence the IMO, however, IN A NORMAL COMPANY, a delete doesn't mean the data's lost, it's still recoverable i'm sure, which is from what i was basing on, you are taking into account how much nexon lolprogramming sucks, and in such case, yes, i agree, they should have taken the road that after messing up, would be easier to fix.

however, that's not how nexon works <.< if they drop the eggs, they're going to clean the mess with acid.