I have not complained about EP losses/gains, nor have I complained about being credited for time lost, (for the small fee, its not an issue for me). But jarhead, I asked for 'more informative error messages', something we are all taught in 'Good Customer Service'. Advise the customer with the truth, be clear, be interested, give constructive prognostications of when failed services might return, set expectations.

No one knows when it will be back on line and running as needed. but they can materially guess as to when it will not be back. Like, try at hourly intrvals, try tomorrow, try at ten past the hour. There are lots of solutions open to any interested party who wishes to best actualise the dollar in the customers pocket without being rude, overly technical or lame. Berating a fellow customer because they dont do the things you think they should do is neither needed nor requested.

Go climb back into your tree and come down when your momma calls 'Dinner'.

i

sorry, I should stay civil, you are correct, I apologise.

Mutter mutter......   mumble...

You all need to simmer down.   Debugging code to find a logic error is one of the most tedious tasks ever and it takes patience and time.  So less QQ and more just wait till they fix it so we can all pewpew again.

Ironically, I was a Cisco Certified Network Professional (CCNP) for years. By the end of my career I was manager for a network that spanned three countries (one across the Pacific Ocean). I was younger than most of my employees and had already been recognised by peers for some work that I had done.

I quit, gave up the good salary, and swore never to do IT again except for some few contracts for people I knew well. For the simple reason that those without any technical knowledge have no understanding of what's involved, appreciation for, or reasonable expectations of the work in IT.

It doesn't matter how well the system is setup, how well things are prepared, how many backups there are, or contingency plans, something will fail or something unpredictable will happen. People will always demand timelines when there's no means to predict one. Trying to explain that, or detail the problem, makes their eyes glaze over, or angry because it goes over their head and they assume you're lying/making excuses to cover yourself. Even when you manage to produce a miracle and have service restored quickly, all they will say is "this better not happen again" or similar.

E.g. A company I worked for had an employee infect some servers (he did things we'd specifically told him not to). He'd done it, just before leaving work... Meaning my automated notifications alerted me, just as I walked through the door of my home. I immediately went back and cleared everything, created new passwords for all employees, etc, including having to rebuild some servers from near scratch to be sure we were clear. I then sent an e-mail out at around 5 am explaining the events of the night. I got home again at 6:30 am in the morning. The CEO called me at 7:00 am because he couldn't read his new password, I changed it remotely to something easier for him. After that, he asked me if I was coming in that day... and was angry when I said, "no". The company didn't experience any downtime, lose any money, lose any information/have it stolen, or have any liability to clients for any of those events... Yet the response the next day was blame from the guy who'd caused the issue (you IT guys didn't explain it well enough) and annoyance from the CEO ("you weren't here for the day").

My point, I guess, is that these Devs have my greatest respect for actually daring to make do something where they will have those/these sorts of situations constantly. They've already done/do more than most companies do. Patience, is a virtue, and something that should be fairly applied to their efforts.

Simply insolence ! To sell access to the game and then I must look at it."Temporary user limits are in effect until we resolve server issues. Sorry for the inconvenience. "  Impudent swindlers !!!!!!!!!!!!!!!!!!!!!

Noob Rules for SQL tuning: put the most restrictive filter query first, i.e., the query that results in the fewest returned records, then repeat with that strategy for all query parameters.  Sometimes doing that is difficult without creating problems based upon dependencies, meaning you have to get the selection criteria in order of hierarchically dependent relationships in the context of relational (and possibly compound) record keys. And doing this on gigabyte sized query results is tougher still.  And I read somewhere in these forums the term "SQL Server" <-- that would be the first problem ...

Glad I don't have to fix it...  Keep up the good work Devs!  As it is, I can sip barley wine, make random forum posts, and procrastinate on my school work ... while you guys do the real work of fixing the systems problem.  Life is such fun !

Databases are evil.

Here, play this:

http://games.adultswim.com/robot-unicor … -game.html

That'll pass your time.

while this is all going on I dont see there to be much point in any serious pvp campaigns or activities.

The only thing us older players can do to help is log off, or at least dont log in all your accounts.

We've had many months of enjoyment before and we arnt going to miss anything if we just leave it alone for a few days and let the newer players explore.

Okay - now I am experiencing severe lag in terms of clicking the "OK" button.  Many attempts to log in result in a greyed out "OK" button for 20 full secs.

Can you fix this degradation in performance please?  (j/k of course, but the problem does exist.  Just more fuel for the "build a queue" concept.) <has other things to do, but instead continues to sip barley wine and spam "OK">

Gamer base more than doubled in a few days.

All I can say is that i totally understand the situation, and wait for the server to be up to the task again, knowing that the devs are working on it. Hell ! They probably want this to work far more than any of us.

Patience fellows.

It's akin to me opening a restaurant and then being surprised when people show up for dinner, knowing I don't have enough food, but seating them anyway.

Perhaps the number of subs should be limited to a number the servers and code can handle and expanded as performance is improved and demand increases? I don't know maybe there isn't simulations that can be run and we are really in the technical equivalent of sticking your finger in the air, or driving till the wheels fall off.

I guess it's more about getting people through the door, hooked and invested, much like the relationship between peddler and fiend.