"Pingpang" wrote:
Anyone who complains about lag/disconnects/etc at the startup of a MMORPG needs to drink a tall glass of STFU.
Take your own advice. If you don't like the thread, get the hell out of it.
As for complaining about lag -- yeah, I get ticked about something that was seen in beta that is this big an issue and was not addressed prior to final release.
Those who did beta could plainly see that there are character servers and world servers and they run independant of each other.
The problem here is in database schema design. It can't handle the load that's being put on it. That was known prior to beta's ending. If the DB is having issues, model it, find the problems and address them prior to release.
In case you didn't notice -- latency and bandwidth are NOT the issue. Nor are there a lot of complaints about client crashes. It's 100% in Blizzard's DB design and implementation.
In otherwords, excellent job on building the game, covering bandwidth issues and server/client stability (they stay up!) -- **** poor grades in core systems work. They fubar'd one of the core areas of the game -- the actual engine that coordinates its use.
Those who played EQ from day 1 (such as myself) can recall funky client crashes, server crashes, etc... but NOT such issues as looting lag, res lag, etc... YOu had sliding under mountains while dead from running, you had getting stuck in walls, falling through the world, etc.. but you didn't have these types of bog down due to transaction backlogging we are seeing here.
If it hadn't been seen in beta due to low volume of folks on the servers and the like I'd be quite understandable about the situation but having played beta we all SAW this, reported it, had it acknowledged by Blizzard that it was an issue and what... Almost a week downtime between end of beta and ship of product and zero fixes to this critical issue.
Pissed about it? Yes.
They knew about the problems and, odds are really high, to fix it will require a revamp of the overall schema (db layout) that will require a day or 2 of down time as they rotate a new db model into place once they DO have a resolution.
A delay of a week or so while they went across where the problems were and addressed them wouldn't have hurt and would have put the product out in working form vs this...
So, oh wise and intelligent one... Go sip your STFU on ice and at least let folks vent about annoyances that could have and should have been fixed. If you don't like it -- go elsewere while the rest of us simmer on the issue and can see others doing the same...