Quote Originally Posted by LittleImp View Post
It's an extremely basic expectation to create systems of redundancy around networked features in modern software, all the more if you are trying to market your service in an area that may have imperfect networks. There is absolutely no valid excuse whatsoever for this game closing itself and frequently removing you from the queue when it drops a singular packet at the wrong time (It's also been widely demonstrated that it does this when no packets are dropped at all). Even if the developers feel it's necessary, it would only be necessary due to constraints created by incompetence somewhere in the long development of this game and its backend.

This isn't the 1980's. There is no reason for a program to terminate itself over such a basic and commonplace error.
You seem to make it sound as though the issue is very simple to solve through the writing and changing some code. I'm not going to disagree with you because I have no clue about what goes into coding a game but I'll just ask this; if it's honestly such a simple thing to do for the devs, just a bit of code to write so that you keep your place in the queue, why do you think they wouldn't do that? Do you honestly believe the developers are just lazy/don't care about profit or public appearances?

And if you're saying; "Oh well they're incompetent and can't do this thing I am saying because they are bad at creating/improving a game" then again, where is the solution exactly? Should they hire new developers right now? Ask them to quickly tackle writing/changing code for a game they've never worked on? Is it an apology you'd want? Money back?

I mean surely you have to agree that they too -want- you to play their game, right?