EVE General Discussion

We will just have to wait and see how it goes down next time. Hopefully there will be plenty more goon tears to collect

Wonder if this one will make it into the EvE true stories collection

So funny, all these Testes coming out commenting about goon tears. It was TEST tears that were flowing in that fight. Of course, that may be the reason the server went down... If enough TEST people /petitioned that they were going to unsub in a fit of nerd rage, then CCP may have to act for no other reason than to maintain revenue.

Let's face it, they need profit to run the game.

They had us right where they wanted us.

It's a poor analogy - what you're describing is an active agent reviewing erroneous instructions and not questioning them. What happened here was a passive agent received erroneous instructions, and didn't have the capacity to question them.

The miskeyed command is more analagous to the harried nurse making a checkmark on the chart and having it be long enough to appear to give incorrect instructions... which a lazily coded automated system then processes without asking for clarification.

The actual miskeyed command entry is an extremely minor mistake - and frankly, one that 'anyone who is a programmer or admin in a real enterprise' should be anticipating and creating failsafes to and confirmation checks to filter out. As you say:



That's the 'unacceptable' mistake here.

"Our infrastructure isn't fail because we didn't get a 'Fleet flight notification' beforehand" Yeah, its the players fault. Seriously?

Ultimately TiDi and continued fail at manually re-enforcing nodes when big fights go down IS epic fail, 10 years in for a company that espouses 'single shard' 'one sandbox'...

CCP has serious architecture scalability issues and unfortunately it appears they have decided to wait until they hit a brick wall, painting around the edges with vaporware like TiDi, rather than biting the bullet and doing a re-write on a kernal that doesn't scale, to one that better does dynamic server resource allocation.

It shouldn't be 'single shard' in the marketing literature anymore...It should be 'single shard*' with a big fat asterisk...

"*So long as more than 2,000 players don't enter a single system"

And re: "All pilots involved have our sincerest apologies for this error, and we are currently looking to review our policy of action in these types of situation to ensure that this is not repeated."

Policy of action?

Isn't the real answer to march ass up to the guys holding the budget dollars and telling them you are going to keep hitting this brick wall until a rewrite around a dynamic resource allocating architecture is done? THAT's being honest, to yourself, your executive and your players...

Looking forward to your next 'fix' for this situation, 'TiDi Plus+' perhaps? Where we see dancing (care)bears go across our screens, while waiting for actions to register and come back from the servers.

Look, look! I can contribute with emoticons too!!

Doubt they would do that much more. It only affects a small portion of players a small portion of the time.

Better to work on something else. Like a new-and-improved launcher.

I suggest you retool your software so that moves like this in the future cannot be done without first specifying an exception (Z9 in this case)

CCP ruins gameplay again, this is not news.

Any other company that screwed it's customers repeatedly like this soon went out of business.

Start firing some of these fat fingered "DEVS", maybe the others will actually check what they're typing.

Any employee that screwed up this bad, or this many times needs to be fired.