This is why i hate CCP and his BoB friends. (N3.)
This is not the first time when this happend. I remember CCP cheat when they give to Bob, T2 BPO-s.
I remember when we catched/trapped 7 southern titan in low sec when they tried to invasion north. The node crashed same like now and the successfully ambush went to garbage. 2 days later the nodes broke again when we catched Sir Molle's titan + 4 other one.
I remember when we tried to attack north and when we jumped to enemy system all ammos missing from loaded guns of whole fleet and we missed our ammos from our cargoholds too.
I remember when we trapped in south 12 super carrier + 40 carrier the node crashed again in delve.
I remember when we trapped 70 of Atlas dreads we got black screens and the server crashed again instantly.
Always this save operations happend accidently isn't ? The engineers jus accidently push the buttons isn't ?
GTFO and dont affect the 0,0 fights and gameplaying u tard CCP.

I'd pin a medal on the guy who reset the servers. But that's just my burning envy of Goons and all the super fun super cool super bad stuff they do. They're all like Shaft. In fact, I think it might have been the Goons who arranged for the crash themselves, those crazy crazy guys. To give us all that good content they're always taking credit for.

Best day in Eve in months, actually.

Wait CFC leadership are seriously telling you this was going to be the death blow to the defense of fountain? Or is this something you've theorised yourself?

I suspect they aren't stupid enough to believe it themselves and I hope they don't consider their line members stupid enough to believe it.

Wait CFC leadership are seriously telling you this was going to be the death blow to the defence of fountain? Or is this something you've theorised yourself?

Listen to yourselves. :cripes:

2. Z9PP-H, E-IO0O, and 4-EP12 are constantly getting hit with timers and big giant alliance crushing fights are going to happen there for the foreseeable future. Place all 3 of these systems on their own reinforced nodes. If you don't have that many spare nodes, have the reinforcement follow the iHUB and Station timers. You have 20,000 players watching those timers and responding to them, please give them some attention to guide your server balance decisions.....

So you are comparing a video game losing service for a few minutes to a real life job where I assume you would be fired because the action would have caused financial harm to whoever was involved?

Again I request anyone who actually (Not just raging on the forums like in idiot) feels that a CCP employee ought to lose his or her job or punished for a simple mistake that was likely due to the excitement over the battle happening in a game they maintain. I personally request anyone that feels that way biomass their character and leave EVE for good. In my opinion the game will be better without them.

Do you know how on average how difficult it is to land a similar job if you have been terminated from your existing one? Many jobs won't even bother looking at the application (Some even admit this) if the person applying is not currently working.

A perfect example of a comment by someone who really has no clue.

to summarize this debacle up by a fanfest 2009 quote from Darius Johnson (ex-CEO Goonswarm, Ex-CCP)

"We're not here to ruin THE game. We're here to ruin YOUR game."

This is why i hate CCP and his BoB friends. (N3.)
This is not the first time when this happend. I remember CCP cheat when they give to Bob, T2 BPO-s.
I remember when we catched/trapped 7 southern titan in low sec when they tried to invasion north. The node crashed same like now and the successfully ambush went to garbage. 2 days later the nodes broke again when we catched Sir Molle's titan + 4 other one.
I remember when we tried to attack north and when we jumped to enemy system all ammos missing from loaded guns of whole fleet and we missed our ammos from our cargoholds too.
I remember when we trapped in south 12 super carrier + 40 carrier the node crashed again in delve.
I remember when we trapped 70 of Atlas dreads we got black screens and the server crashed again instantly.
Always this save operations happend accidently isn't ? The engineers jus accidently push the buttons isn't ?
GTFO and dont affect the 0,0 fights and gameplaying u tard CCP.

LOL, Isn't karma a *****.

It would be karma if players ruined the goons game, not CCP. Logic, it's half the battle, try it sometime.

Campaigns are decided by a few big fights for which you break and cripple opposition. This would have been one of those.

To imply that isn't possible, or wasn't going to happen, shows me how little you know.

I can tell from an IT Leadership perspective this looks like the failure in change control process or a lack of will to enforce the process that is there. In other words when a node is down you have a couple really smart guys going cowboy on it fixing it by hacking away at various control points in the system. That gives you the fastest and best result in most cases but then you will have outliers like this that are devastating to your reputation. What we don't see is how many times and how much engineers 'going cowboy' to make the game better real time has actually made the game better--I bet they are unsung heroes in this regard.

It is a fairly simple matter to establish a process that will prevent this kind of mistake, but I can tell you that CCP's technical staff will despise and ridicule being constrained in this way. You also have to put teeth behind process compliance even if it means letting someone go that does not get it. In the end, you will probably end up exchanging a fast response for stability but change control mistakes are too much of a liability when they are so public and significantly affect so many players. This is a PR disaster for CCP, and I expect it will be reported in the broader gaming press soon.

How you say? Rather then genius cowboys hacking away at the CLI until you get the result needed, change commands have to be explicitly written and approved by multiple senior technical leaders and a t least one senior manager/VP who's involvement insures that everyone is taking it seriously enough. The exact players in this reflect the risk involved in a change.

The 'soft' remapping of a node is a common affair so a template procedure and set of commands should be put in place that is adapted to each situation. Upon full approval, the commands are executed with a script (or cut and paste). If there are significant errors the change is failed, queued for later review by a Problem Management process and if the change is still needed, the writing and approval process must start over. Yes it sucks but this is how companies that wear big boy pants do it

So if I get it right, the summation of CFC demands thus far in the thread have been:

Every server gets its own node so that they never miss out on cap kills because they are the only ones who have had this happen to them.
The person responsible should be fired.
Game code should be entirely rewritten from the ground up to satisfy their butthurt.
All TEST ships should be destroyed and kills granted to every CFC ship in system, but the CFC dreads that were saved by server outage should remain (since there are no demands to remove them).

Listen to yourselves. :cripes:

**** YOU CCP **** YOU

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

Their complaint was don't have bad algorithms and poor management design that encourages human mistakes.

Anyone who is a programmer or admin in a real enterprise would know that this kind of human mistake is entire unacceptable and would normally result in a firing. These kinds of problems are easily avoidable.

How does a tool that handles system moves, offer nary a complaint when someone tries to erroneously shutdown and transfer a critical system?

Here's an analogy. Say you're in the medical field and on your chart that you're supposed inject embalming fluid into your live patient? Would that send up a red flag and be like... hmm.. that might kill someone. Or do you just blindly keep on trucking and be like... ooops, human error.

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.