AKradian

DarkPassenger wrote: »

Arwoo even said not to ask about bans, ban appeals and stuff like that

my question is whats up with the Nexon Launcher, any news on it yet in regards to the issues that arose in conjunction to the Nexon Launcher update

He said not to ask about individual bans. As in, "Please unban me!" or "Why is X still not banned despite me reporting them every day for a month?"

Customer Support and the Investigations Team do not fix bugs, prioritize bugs to be fixed, or test the software, so there's no point asking them about game (or launcher) issues.

DarkPassenger wrote: »

It's not a job interview. The random factor would entail different feedback from the gameplay. I dont think spending money on the game will have anything to do with being chosen. most likely it is a random number generator thats picks the players. Imagine how many people would write the same thing, what they think Nexon would want to hear to be chosen. Wouldnt you rather not be chosen because it was random than because you didnt say what they wanted to hear, or think you didnt say what you think they wanted to hear?

The question isn't how I would feel about not being chosen. The question is what's better for the game. And I think choosing testers at random would be a mistake.

Last time we had Tespia, years ago, the testers were chosen at random. As a result, the vast majority were not interested in testing, but just in fooling around with the auto-leveling and free gear offered by the server. Another group were there to scope out exploits (and not report them to Nexon). And only a few were actually testing.
The result was a complete failure and Tespia being closed off for years.

We do not want a repeat of that. So I hope Nexon does do some kind of "interview" before accepting people, to make sure that they know what they're signing up for. The fact that there's an NDA involved this time - a legally binding contract you have to sign with your real ID - gives me hope that Nexon is a lot more serious about player testing, this time.

TBH I don't know why everybody is so eager to get into Tespia. Well, actually, I do know. "Get to see the new content before everybody else." But that's not what Tespia needs. That's not what the game needs. And if you think about it, it's of little use to you (generic you) too. So you get to see the new content first, so what? You're not allowed to tell anybody about it. Playing it doesn't give you anything for your real account - you're going to have to play it all over again on the live servers when it's released. And meanwhile, for "testing", you might need to run through it over and over while it crashes or glitches or behaves oddly, try to figure out whether it's a bug or intended, and write out detailed bug reports galore, with screenshots and videos and stuff. Does that sound like fun? It's an actual job that people get paid to do, because a lot of it is very tedious and frustrating.

Some people want to do this job, voluntarily, for the satisfaction of knowing they've helped make the next patch not be a nightmare of bugs and unscheduled maintenances. These are the people who Nexon needs to find. Not random players who may well be useless or even malicious.

On the one hand, I see why you'd want to remove threads you made by accident.
On the other hand, if you wrote something, and a discussion ensued, and you don't like the way it was going, you should not be allowed to just make it all like it never happened.

What you can do is flag your own posts and ask the moderators to "delete this duplicate thread" (I think they're supposed to do it anyway, but sometimes they're too busy to notice it immediately).

Edit: or... you should be able to do it. I thought I saw the ability to flag my post, but then it went away?

There were reports that if you take your 5th job advancement before doing the quest for Call of Cygnus, you won't get the skill.
http://forums.maplestory.nexon.net/discussion/9899/skill-call-of-cygnus-missing
http://forums.maplestory.nexon.net/discussion/10750/call-of-cygnus-bug

I haven't heard of this being fixed, even though these bug report threads are six months old.

No, it's a bug in Reboot.