HHG1

I had this same issue a while back.

Your character's skin color data has been corrupted. Contact support and ask them to send you a skin color coupon to fix the issue.

Don't be ableist. Not everyone has 10 fingers. Also, married people only get 9 slots, and people with fat fingers get no slots.

JushiroNet wrote: »

On the topic of forum rules I do think it's funny that so many people want old maple that it had to be banned as a topic here.

Well, no. It was banned because one guy kept bringing it up, constantly, with an increasingly entitled tone. Even after the ban he kept making threads either to dispute this "totally unfair rule" or make thinly veiled "old maple" threads under the guise of nostalgia, then quickly move to discuss his real motive. I bet he still doesn't understand that he (and others like him) is the main reason the rule is in place.

It's much better to keep that circlejerk on Facebook where it belongs.

NicholasB wrote: »

i have to disagree with you, other classes are fine, including jett, etc, because they're not that good for hackers and yet kanna are very good for hackers
i really don't know why you're trying so hard to protect this class called kanna, they say those who protect kanna are usually hackers themselves, which is make sense.

Did you even bother reading my post? Because if you did, I have to say that reading comprehension is not your strong suit.
I'm making the point that it's stupid to make the argument that just because a class is popular among hackers for any period of time warrants it getting removed. I illustrated this by pointing out other classes that have dominated as the hacking class for longer periods of time as well. (And responding to the person saying that kanna should be removed just for being a non-KMS class, which is equally dumb.)

Again, hackers have used a large variety of classes for hacking over the years, and removing kanna as a class would not slow them down at all.
Arguing for removing kanna is the same as arguing for the removal of every other class that has ever been used for hacking, which, again, is stupid.

If you can't see why removing a whole class solely based on the reasoning that hackers have used, are using, or will use it on a larger scale, then you must be stupid too. If you see no other merit in keeping kanna as a class then you have clearly never played one.

There is a case to be made against kishin and the unhealthy meta surrounding it, but going "kanna hackers bad, all kanna are hackers, remove the class" is so far detached from any type of logic I'm not even sure if I should have dignified it with a response, or several.

It's a good suggestion. I guess my main concern with it would be how Nexon formulates the survey, what options are available. Essentially; how introspective are they able to be in order to create a survey that asks the right questions and draws in valuable feedback. They have to understand how the community thinks and what we may feel is important.

I could use the familiar FAQ as an example. The initial information we got for that was very lacking. Nexon had to ask us what questions we had about it, like they couldn't already have provided at least half of those answers in the initial post just by understanding what's important for the community to know about upcoming changes, in general.
It's great that we eventually did get answers and I think some would say that it's better that they included us in the process.
But I still feel that game developers and producers should have some intuition when it comes to what's important information to include in FAQs and patch/update notes, and that wasn't the case.
So my question then becomes; Would they know what type of feedback they should be looking for, or what type of feedback we'd be likely to want to give?