The Battle of Z9PP: EVE players vs. Servers

Avatar
nice article to read +1 , but shit happens so GF guys let do it again sometime o/
Avatar
CCP droped the ball gloriously on this one.
Avatar
Yeah no, it's just a few pixels not dying as they should. And it's 100 carriers... Not even a few supers/titans. Not a drop in the world of supercap fleets.The CFC need to win more fights to win anyway, I don't think it will change anything.
Avatar
Shit happens. Fun times were still had.
Avatar
Didn't want that fight anyway.
Avatar
Oh no someone made a mistake! How terrible! Jeez, all these people complaining obviously have no clue how difficult it is to run systems as complicated as EVE. I've worked for a number of hi-tech companies over the last 15 years and I don't think I've worked for anyone with as complex a system as CCP and NONE of them were able to keep their systems running as well as CCP do.From a technical perspective CCP do an amazing job, just because it goes a bit wrong from time to time isn't an excuse for people to behave like spoiled little idiots and throw their toys out of the pram. I wish people would just grow up and understand the reality of the situation.
Avatar
^ Adult :) And the right attitude! It's supposed to be a fun and yep, shit does happen.
Avatar
I can't imagine any fair move to 'make right' the altered outcome. There are no good moves, here. Just very bad luck for CFC, and very, very good luck for Test.Despite the initially fishy look of it, this blunder's timing during such an important event makes sense: The high stakes generates high number of pilot participants, which is what creates the server conditions to call for a technical intervention. And those interventions, as we've seen, carry inherent risk. It's the most likely time that Murphy's Law will pop with a chipper "Hidey Ho, Neighbor!"Conversely: no Asakai/Z9PP/etc, no need for risky intervention.There's a silver lining: Such a high profile, highly visible, rage inducing event absolutely must prompt actions that will be favorable to us Eve players. This is exactly how lingering issues are pulled straight to the front-burner for fixing.
Avatar
http://www.youtube.com/watch?v... <- Vid of the fight
Avatar
Yes and no. You're drastically understating the effect that a handful - let alone dozens - of carrier losses would have. Could they be replaced? Probably. Are there more? Sure.But will there be no change in behavior? Such a loss would've absolutely changed Test's deployment choices and behavior, to the CFC's benefit. And there's other factors too, like finances, morale, opportunities in the immediate aftermath, etc.An immediately war-ending loss it would not have been. But to paint it as no big deal? Nuh uh. That'd be a feat of selective perception.
Avatar
I've been dealing with this system since I got up this morning (the initial oops the ihub just died) until the node crash. I for one, am glad it's over. That was a painful marathon of 0.000005% tidi for 6 hours.
Avatar
what became of the ihub then?
Avatar
I was a bit sad as we were on a killing spree, but sometimes... yeah, shit happens. vOv
Avatar
I weep for your HDD. How big was the file?
Avatar
It onlined somewhere along the way. Might have been put into its shield timer at some point after the remap, not sure.
Avatar
150gb's... took an hour to render after speeding up the footage and reducing down to the 40mins.
Avatar
Up to the point of the incident is was one of those glorious Eve Online moments.
Avatar
As someone who was in one of the bomber fleets, I gotta say, 'I was there for the crash of Z9PP' might be better than the slaughter that was going on.
Avatar
jesus, you're that guy. YOU'RE THAT GUY. You're the fucking guy shooting the secondary, before the first fucking target is dead. giving him plenty of fucking time to broadcast for fucking reps. group your fucking guns and shoot at ONE TARGET at ONE TIME.im mad.
Avatar
yea i actually had to turn your video off. what a fucking joke. it was getting better. when the carriers started dying you ACTUALLY had a SINGLE group of guns. but then the rokhs landed and you SPLIT ALL OF YOUR FUCKING GUNS AND FIRED ONE GUN A TIME AT A DIFFERNETSIRJUHTKIJLSHFDKGJHSDKJLFHSDKJFLHSKJDHFSKJDHFKJSDsdkljfhsdkjfhsd.
Avatar
Tears of joy by CFC... poor dead bodies..
Avatar
CCP needs to consider seamless node migration.
Avatar
Test relies heavily on "slowcats". this would have had a big effect. Not on supers, but on the current way the war is fought.
Avatar
You are an idiot. 7 targets with one gun on each. Holy shit never join a fleet again.
Avatar
The Dev making the mistake get payed plenty of money to double check his shit before pressing buttan.But hey shit happens, devestating blows where given and could be so much more rawr :)Little bee's will be back to sting some more :)
Avatar
I would just like to point a simple Matter: in my Office if anyone dares to make a mistake which affects at least 2000 people as the one that happened yesterday well unfortunately for him this person gets fired and well, he does not even say a word about it.I know it is a game, but we pay for this game so much that if you take the street dollar value of a plex and multiply it for 2000 u get the idea. Therefore what is a game for us players is a job for devs and it should be treated as such.Things like this should not happen anymore.
Avatar
Also news flash, we just killed a goon station anchoringhttp://www.youtube.com/watch?v...o7 to your stations m8s
Avatar
The Goon tears from this "event" are delicious. However, its not a given that they would have actually "won" the capital / super capital engagement. Who knows if PL/NCdot or whomever would have dropped in 200 titans and won the day. All I see is every single crying Goon thinking the outcome would be a sure victory for the CFC... when it was not a sure thing at all.
Avatar
how many times are you guys going to make a whiny artical about bullshit, GET FUCKED GOONS
Avatar
It's a fucking game retard, quit getting mad over it. Ruining somebody's life cause he typo'd? Are you retarded?
Avatar
Goon tears Best tears...
Avatar
That actually is my point. It would be MUCH safer to code the opposite way:'move all processes which are: [insert the list of systems you want moved]'The actual command is basically a kill command, right ? Everything it touches is shut down. My point is that you do not want a kill command that will kill stuff by default even in case of a wrong argument. You want a kill command that will by default DO NOTHING, unless it has a valid argument that it can apply to.Had that been the case, it would have taken more than just one fat finger for the same result to occur.
Avatar
Because the log in servers were all over the place, and having a small percentage of your fleet land on grid with god knows what else from you guys would have ended in disaster.
Avatar
Ive just made a mistake that will probably affect 2000 people because i'm sitting here at my desk reading your shite.If i make that mistake again i will get fired...if they remember.
Avatar
The results of the fight speak for itself. Go get some medicine and therapy for ur butthurt. If u believe that I was the only person doing this, then all I have to say is lololol....u mad bro?
Avatar
Incorrect, TEST was not planning to drop more caps, NC. and PL. were planning to bail test out again with THEIR cap fleets. You know, fleets that don't jump more carriers directly into a slaughter despite being explicitly told "Hey don't do that, they're just going to die horribly." TEST by this point was content to try and shove more rohks into the system while their caps would have desperately clung on to a 200 man slow fleet lead by someone who knows what they're doing.Did you happen to notice that PL extracted 100% uncontested before your own fleet started exploding? Or maybe that the slowcat fleet PL was forming to rescue you was properly composed? For 3+ years TEST has flown under the guidance of a more organized group, and during that time they appear to have learned nothing. From the early days in deklin in the pentagram with Goons doing what they do best with logistics and methodical sov war, teaching TEST what a doctrine was why you should have them. All the way too the HBC where PL tightened up your doctrines and tried to teach FCing and game mechanics. While a little of it has sunk in, hell you actually have a half way decent cloak squad and one good bomber FC, the majority of it has been ignored. Your logistics are a mess, your alliance crashes your comms with frightening ease only to scream "DDOS" when it happens yet does nothing to fix it, and there is actual truth to the claims that your SRP is bankrupt on top of being inept and slow. All you have accomplished from bitterly parting ways with Goons is leaving one nest to crawl into another.Laz and Manny were right, this could have been the fight to end the fountain war if CCP hadn't fatfingered it. Goon's wouldn't have won it so much as TEST's inability to accept responsibility for anything would have lost it.
Avatar
Nomicakes go back to your shit renter alliance and shut the fuck up.
Avatar
m8 stop drinking when you read. won't help your frustration.
Avatar
More vodka is required to process your response.
Avatar
Don't be obtuse. Egg kills are rare, but they happen. How do you think the 1hr pre-downtime tactic was learned in the first place. Titans are more expensive and those don't make news here all the time unless there's a good story associated with it.So yes... take it to EN24 where almost anything, especially if it is anti-goon, will make the front page.

A surprise seven-hour slugfest in the Fountain war was cut short when a CCP typo brought the system down.

The fight started when TEST dropped an ihub in an attempt to save the Z9PP-H system. The CFC started attacking it, and TEST defended. Ships were traded, and PL and TEST both brought in slowcat carriers to attempt to rep the ihub up. At this point, the CFC formed megas to hit the carriers. When the megas came in, the PL carriers got out safely, but the TEST carriers were pinned down, slowly but steadily dying.

The battle was completely unplanned; as such, Z9PP was sitting on an unreinforced node. Tidi hit 10% and stayed there, drawing the engagement out. As with Asakai, this allowed both sides time to call in reinforcements. It also built excitement over time, with plenty of uninvolved people tuning in to Twitch.tv streams of the fighting. 

With the fight going strong and continuing to escalate, CCP decided to do what they could for the poor node to improve performance as much as possible. This meant removing all non-essential stuff (i.e, all other systems) from the node and mapping them on to new nodes. After that was done, the node's full capacity could be used to handle the ongoing battle.

Unfortunately, it never got that far. According to CCP Phantom, the person who initiated the remap typoed, leaving every system on the node, including Z9PP, remapped somewhere else, ending the fighting ahead of its time. When a node is remapped, it works more like downtime than a disconnect. All ships are removed from space completely, so the 15 minute aggression timer doesn't matter. While the system came back up quickly, TEST's carriers were safe. TEST, seizing the opportunity, told everyone not to log on.

In his post explaining what had happened, CCP Falcon indicated that CCP would be reviewing the events leading up to the failed remap and adjusting procedures to prevent it happening again. While this is the largest fight interrupted by a node remap, it's happened before-- a remap in the J5A fight influenced the outcome, and a surprise reboot saved some CFC dreads. Previously, the DDOS and later unrelated network issues have affected fleets as well. Even ending before its time, it was a bloody battle, but one that could have been bloodier.

Ali Aras
CSM8 Vice-Secretary, @ali_of_space, TMC editor. I play EVE, LoL, and miscellaneous other games.