EVE General Discussion

As an engineer whose mistakes have caused brief outages before, I certainly can sympathize with what this engineer is going through right now. I can assure you he won't be sleeping tonight, and will be beating himself up for weeks if not months to come.

That being said, when you are dealing with the very core of your product, you must be extraordinarily diligent in your work to ensure you don't break anything. This level of mistake is completely unacceptable, and there is no real way to make it right.

Free tank of honor to all those involved.

I do not subscribe to the conspiracy theories.

CCP's actions, however, were exceedingly stupid:

1. The fight had been running for several hours and numbers had actually DROPPED at the time CCP introduced its 'cretin' plan. Why watch a massive fleet fight for hours and then decide to take action near the last section?
2. Obviously the action itself was incredibly badly planned, communicated and executed. Playing about with processes on an active system is a very delicate operation and needs people who take care and know what they are doing - not a CCP strong point it would seem!

The calls for people to be sacked over this are extreme but somebody (especially the individual who made the decision to move things) should be reprimanded and apologise personally.

It's ok guys it was his first day.

"keyboard error" - i think the keyboard was working as intended
"error in communication" - well the real problem is that it is impossible to convey tone in written language. Now if the instructions had used the font Sarcastica 12 he would have known it was a joke. Instead it was in Good Times New Roman.

pfft ******* fonts

TEST finally did it.

They got a spai into CCP.

You sirs are awesome.

So annoyed that you might forget about the new launcher for a whole day?

A blessing in disguise

I don't use the launcher to do anything but patch. i log in via the exe. so its mostly forgotten about anyhow.

You know, I'm not gonna call for the guy's head - it was a typo. Who among us hasn't had one? As someone who's recently lost my job, I'm very, very wary of calling for someone's family to suffer because of a typo. Instead, I'm hoping the process will be changed - that safeguards like a simple 'hey, that system doesn't exist' error message will be put into place, as well as 'Are you SURE? Y/N' confirmations. More importantly, I'm hoping the code will be changed so that if* something like this does happen again, basic IT practices like archival data imaging and restoration rollbacks will be implemented so that whoever the guys on the field are, they're not denied the fight they worked hard to get.



* - if? Who am I kidding? when.

This is really unfortunate considering that major battles seem to have the most mistakes on CCPs side. This is quickly turning into another Uemon!

Instead of always cleaning up PR messes perhaps you should be more proactive on the successes you have. When this happens to one of the biggest and now most publicized fights in EVE history it just bring a ton of bad press and allegations that CCP is "in" with TEST. Instead you need to start publicly addressing the successes as well. In my memory, you've made one such attempt when TiDi was released and since been silenced.

I would instead bring forward the successes and comparisons to the rest of the game industry. Not as justifications for a very sloppy key press, but to show the players the amount of things that go RIGHT instead of waiting for another disaster.


P.S. As for the sloppy key press... I still don't understand why you wouldn't have some sort of confirmation message and actually reviewing it. You can ill afford to mess with 2000+ active pilots and more thousands watching the live streams. Pretend like your game depending on it, because I am sure to some... it does.