Ooo yay, a kinda decent rant. Okies, let's see here.
Is there a reason that Aeria is deliberately moving or deleting threads?
yesterday a thread started by Sighborg addressing the connection issue during GRB was completely deleted. No information about why it was deleted or any comment.
In that thread, sighborg stated that there was a coding issue that caused people to disconnect.
I asked a clear question. What kind of code only kicks groups of people out of the GMO during heavy load on the server? I never got or saw a reply. 2 pages later, that thread got removed.
This is a problem with Aeria that I will agree with you on. I can not agree with you on the specific topic you speak of simply because I never read it, and while a lot of deleted/locked threads should very much have that action taken upon them, there is also a lot that shouldn't. I personally had this issue happen to me only a few months ago regarding a thread I posted, but I won't get into that.
However, even with that said, I do feel Aeria has recently gotten quite better about being delete/lock button happy. I've been seeing quite a few threads I would generally expect to be locked or deleted left open (this one for example).
Now, the rest of your rant is just... bad. You think you know what you're talking about, but you don't.
I stated that it's time that Aeria stop pinning the blame on the developer and start taking responsiblity. I understand coding quite well.
There is not a code that only kicks certain people out of GRB but allows others, unless written that way. There are no codes that lags players out when the server is under a heavy load, unless its to prevent crashing. There are no codes that only goof during GRB that enable a few selected people to play.
Does Aeria really think people are that gullible? All I request is an honest answer, nothing extereme, a simply, answer like the server is overburden we're working on it. Instead, Aeria blames the problem on Nexon. Nexon didn't do the merger, Nexon don't control the SQL database. Nexon certainly didn't kick player out of the game during GRB.
All this started to happen when the servers got merged. Trolls like me already advised that the merger will cause problem with lag and disconnect. Many of the trolls knew that the lag would happen when too many people are in the same area. Leo blamed the player's for having bad computers. I sort of agree with him to an extend. The problem really manifested itself during GRB and in the AH. Not everyone has a slow computer and poor internet connection.
I myself have a very high end pc with a 30Mb/s connection, this is more than for any MMO. I have never maxed out the limits of my pc with any game on the market. I tried logging into GRB just for the fun of it and it was closed to me. I did try when the server were heavy. I connected but never even made it to the character screen. I did get a time out issue. I did ping aeria and got 0% loss reply.
All this support my statement, that the problem lies in the hardware. Hardware is not under the control of Nexon. Saturation of the server is not under the control of Nexon either.
So next time you try to blame Nexon, have something to back that up. Not all of us are that stupid to believe such a blant lie.
You may understand coding well, but obviously not that well.
I don't really have anything to say on this matter that hasn't already been stated by Merlin.
What he states also negates all your statements regarding hardware so I won't get into that.
I know I'm going to get slammed for toeing the party line here, but I'm going to have to disagree with a few things (not everything, but a few things).
Firstly, Nexon did the merge, not AGE. Someone from AGE may have kicked the process off, but the process was designed and built by Nexon. The decision for the merge will have been made jointly by Nexon and AGE and probably based on Nexon's recommendations.
Also, while AGE nominally controls the database, Nexon have full administration access to it.
While you are correct that there won't be code that kicks people out of GRB and allows others, it is completely feasible that portions of the code do not handle stress well and cause timeouts and disconnections for some people and not others. It could even cause server crashes.
Optimising those portions of the code that are causing problems certainly is the job of Nexon.
Also, don't assume the thread got deleted because of your question (at least that's what you seem to imply, I could be incorrect though). There's also a good chance your question didn't get answered due to security reasons... or the simple fact it's a pointless question.