The usual player logoff mechanics with all associated timers are just not relevant during downtime or live remaps.

Please also note that further information is currently being compiled to give you a more detailed overview.

give us back our 100 carrier kills

Evening capsuleers,


The system of Z9PP-H was brought back online and made accessible as fast as possible, however we realize that the mass disconnect of everyone involved in the fight means that ships are potentially saved by their pilots not logging back in once they have been disconnected, or are lost due to other unforeseen consequences of the disconnect.

What do you guys plan on doing about Aggression/logoff timers on reboot moving forward? I know there are technical limitations, but in a perfect world, what would you like to see happen to combat this error and the resulting cowardice/strategic asset save.

Specifically:

Evening capsuleers,

Many of us here at CCP were watching various player streams of the battle as it unfolded and cannot apologize enough for such a mistake, or for disrupting what was setting out to be an unbelievably epic fleet fight

Evening capsuleers,

This was put into play at 22:14 UTC, however due to an error in communication, all systems including Z9PP-H itself were moved from the node, which caused everyone who was in the system and was involved in the ongoing fleet fight to be disconnected from Tranquility.

Ya think? *facepalm*

You guys are **** at your jobs hope this helps.

You goons need to thank CCP for saving your fleet as it was getting crushed. #nomad

By "communication error" you mean one of your admins fat fingered Q and Z and because your tools were poorly written it just went off and tried to fix a non-existant system.

Why didn't you log back in to continue crushing us?

CCP get your act together. I hope you're considering this summer an embarrassment, because it is.

I'm gonna sperg a little but will you be considering taking action on the carriers that were tackled, trapped, caged or will you be letting them get away and off scot-free?

Better to be lucky than good, right TEST?

CCP, kind of a disgraceful "error in communication". Hard to believe that line.

I'm gonna sperg a little but will you be considering taking action on the carriers that were tackled, trapped, caged or will you be letting them get away and off scot-free?

I'm gonna sperg a little but will you be considering taking action on the carriers that were tackled, trapped, caged or will you be letting them get away and off scot-free?

They're going to do exactly what they did to those CFC dreads we had tackled the other week.

I'm gonna sperg a little but will you be considering taking action on the carriers that were tackled, trapped, caged or will you be letting them get away and off scot-free?

The same thing will happen to them as happened to all the goon dreads that were tackled during previous node crashes that never logged back on: Nothing.

Probably not, but I'm considering taking action on your mom, tackling, trapping, and caging her and not letting her get away without getting some of my scot-free.

You guys keep whining about this kind of stuff.

Thing is...

You are in an alliance that literally nobody has sympathy for anymore. So please, just stop posting and go away.

I especially like the part where you say the fight evolved organically (blame the players) and so you -had- to intervene. Two more hours of 10% tidi and this whole thing would have been a non-event.

Let me run that by you again, you intervened and things went wrong. What have we learned?

once again, this is bullshit CCP. Happens too much.

First all those goon dreads get away 4 times, now this. :(

If they were tackled and dying when the server went down, like yours were, then you should be gifted the kills IMO!

In my company when we f*ck up in epic magnitude like this we normally kiss our costumers ass a lot and them make a lessons learn and write a document that we deliver to our costumer explaining in details what we did wrong and what we will do to prevent the mistake from happening again, ever.

For the kissing ass part, CCP can put a special edition ship in my hangar, thanks in advance. Something new and rare thanks.

For the document part I will wait for a dev blog.

"The Legionnaires send their regards" - CCP "Roose Bolton" Dolan, shortly before pulling the servers down and stabbing the Kings of the North through the heart with his developer dagger.

Cool then lets talk about the 10+ CFC supercarriers that were saved from the server crashing. Also the multiple fleets of subs and caps CFC-side. Not to mention, that SBU we were going to kill but server crashed and it went through and reinforced a key system.

Kinda sucks when it happens to ya doesn't it?

Well I lost an Incursus because I went for a roam when the system was taken offline. Do I get to whine now?

But seriously guys, we all make mistakes. Luckily most of us don't get angry Internet space ship mobs when we do. I'm sure you will find another occasion for an epic fight soon and I'm also sure that next time CCP is going to be *WAY* more careful.

They're going to do exactly what they did to those CFC dreads we had tackled the other week.

again if that's for real then you should have the kills!

the goon tears are worth 10x what we lost

No, it doesn't.

This thread helps gather all the stuff in one place so it can be conveniently brushed aside with a few random posts that will be requoted to no effect.

wasn't it ccp policy never to intervene in cap fights for fear of not being neutral

well I think that policy went out the window tonight

again if that's for real then you should have the kills!

At least our tears are reimbursed.

If CFC had the same amount of participation in the actual game as they do in this thread; they would have won the Fountain war by now.

You are completely wrong here though. In regards to the "other week". CCP had an emergency shutdown due to something going on in eve away from the fight. They gave everyone 10 minutes to get safe and took the servers down. If the servers had come back online in 2 or 3 minutes, our dreads would have still be aggressed and would have been killed.

In this case the server shut down like a downtime. All aggression clear, bubbles clear, everyone vanished from local unless they login. Big difference.

Let it go, man.

wasn't it ccp policy never to intervene in cap fights for fear of not being neutral

well I think that policy went out the window tonight

This was put into play at 22:14 UTC, however due to an error in communication, all systems including Z9PP-H itself were moved from the node, which caused everyone who was in the system and was involved in the ongoing fleet fight to be disconnected from Tranquility.

As has already been said, Mad AniGÇÖs Twitch stream had over 5000 people watching including a number of CCP staff. The popularity of the steam got it onto the front page of Twitch and there were lots of people saying they would re-sub or sign up because they were really impressed by the scale of the fight.

I suspect it was the attention this was getting out of game that prompted CCP to try to improve performance. They should have just left it alone and made more effort to re-enforce nodes as these fights start to escalate in the future.

At the time the node went down, the Test Rohk fleets were dying like flies and server performance was picking up. With the TEST battleships out of the way all those carrier and dreads would have been next. CFC fleets were being constantly re-enforced so make no mistake, those caps were dead.

In my view CCP meddled with things to improve the spectacle for the twitch viewers and as a result prevented a truly great battle from playing out. ItGÇÖs now going down in Eve history for the wrong reasons. Such a shame :-)

Just my opnion of course.

How do multiple people combine to make that mistake? If it was the mistake of just one person, what are his prior connections to corporations/alliances ingame? Why was this change not double checked before the node was remapped?

How can this mistake be made? Why should we trust you -- AT ALL -- that this will not happen again?

Will there be compensation or penalties ingame for the parties involved?

If it really was an intentionally incorrect entry -- er, I mean typo -- of the system name, how do you not have autocompletion or input correctness checking, like say a popular mapping tool that is in my signature?

Will internal affairs be involved in investigating this incident?

what im trying to say is that no matter how you paint this my friends you're still losing fountain haha

All pilots involved have our sincerest apologies for this error...

Only according to the goon forums and infrequent mittens updates on TMC. In the real world that is not the case.

I could understand a situation where this randomly happens. But this is the second event during a major fight where the node just happened to be reset.

CCP said before that nodes of fights would not be brought offline and that nodes not related to the fights would be. In the case of the first major fight ccp took down the node on J5A system and left B-D system fully untouched. This allowed test to rep the ihub with 0 tidi and bring in reinforcements, while b-db was in full lockdown.

That was I guess part of the deal or at least okay. This happening with regards to the server in the middle of a fight is pretty poor. I was streaming the fight for the mittani dot com and I had several ccp people on the stream watching but the way its handled is bad. If say they had froze the system at 100% tidi and made everyone show up in local once the server was up, that would have been different.

Only according to the goon forums and infrequent mittens updates on TMC. In the real world that is not the case.

Everyone makes mistakes. Forget about it and move on.

Apologies accepted.

ok mate

Only according to the goon forums and infrequent mittens updates on TMC. In the real world that is not the case.

Cognitive Dissonance, thy name is TEST

Conquering a fountain in the real world isn't that hard, harder than in EVE Online though.

At least our tears are reimbursed.

Didn't have any spin in your back pocket for that one? Swing and a miss I guess.

the decision was made to remap all other systems away from the node on which Z9PP-H was located in order to improve responsiveness and playability. [...]

This was put into play at 22:14 UTC, however due to an error in communication, all systems including Z9PP-H itself were moved from the node, which caused everyone who was in the system and was involved in the ongoing fleet fight to be disconnected from Tranquility.

Given that this was done via an engineer/admin-executed command - ie: Z9PP-H was not remapped because of an error in the running code, but was remapped as part of a process specifically initiated in order to remap systems - my question is this:

Why are system states, including ship position, aggression and criminal timers, and other critical information relevant to the state of gameplay in that system, not immediately backed up as part of the remap process? Presumably, if other players had been in a small gang fight in the other systems on the same node, remapping those systems under the current system would drop their aggression timers as well.

If this had been a crash, then the failure to log an archive image of the state of the database might be understandable, but as this was a deliberately initiated process, why does that process not include an automated archiving of the state of the node for potential rollback if necessary?

Given that this was done via an engineer/admin-executed command - ie: Z9PP-H was not remapped because of an error in the running code, but was remapped as part of a process specifically initiated in order to remap systems - my question is this:

Why are system states, including ship position, aggression and criminal timers, and other critical information relevant to the state of gameplay in that system, not immediately backed up as part of the remap process? Presumably, if other players had been in a small gang fight in the other systems on the same node, remapping those systems under the current system would drop their aggression timers as well.

If this had been a crash, then the failure to log an archive image of the state of the database might be understandable, but as this was a deliberately initiated process, why does that process not include an automated archiving of the state of the node for potential rollback if necessary?

CCP TEST: Before I press ENTER please confirm I have everything correct.

CCP PL: Looks good.

CCP NULLI: I don't see any problems here.

CCP TRIBE: Let me see, yes, that will do.

CCP PIZZA: I wanna see, can I see?

CCP 401K: Push the friggin button already!

Look. Im new to eve, about 5 months old. I support CCP for creating an amazing universe for me to dive into, but F nullsec alliances having pull on server status. None of the test/goon war applies to me and my friends, and denying us the time to play on our day off is ****.

You wouldnt pull the plug on the servers if I was about to lose my Myrm in a combat site.. If your friends alliance is about to lose a fleet, let it happen. Whats the point of warfare if you cheat your way through it.

why you posting this again man ???

None of the test/goon war applies to me and my friends, and denying us the time to play on our day off is ****.

Hey look, two party system politics.

I thought it was test carriers, and PL had already left?

I cannot post from my main -- but I believe I speak for all goons.

What worries me isn't the capitals getting out, or us losing the strategic objective in this system. What really gets under my skin is that my killboard will not reflect my pvp prowess.

I want CCP to manually adjust my killboard so that it reflects what should have happened, roughly 200-300 test carriers dying.

CCP stated 'this will never happen again.' CCP also said 'we don't stop the best content our game can deliver, giant fights that matter.' I know CCP Phantom is the mouthpiece I can read, I'm just acknowledging that the problem and onus is larger than him.

Please, detail for us exactly what steps you will take to avoid this from happening again in the future. I understand you'll probably need a meeting or two to talk about policy changes or even code changes, but we need to know. This could have just as easily gone our way for some bull **** in Tenal or 4-EP12. Neither side wants this to happen again.


Here are my humble suggestions:

1. The guy who did this, actually entered the command, gets a 2 day paid vacation. I know his job is full of stress and fuckery and this has got to keep him up at night for the next several days. I know I couldn't sleep after this.

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. Though an easy counter to this suggestion is if 20k players are watching you'd think 1 of them would fill out the damn 'please reinforce this system' request form.

Look. Im new to eve, about 5 months old. I support CCP for creating an amazing universe for me to dive into, but F nullsec alliances having pull on server status. None of the test/goon war applies to me and my friends, and denying us the time to play on our day off is ****.

You wouldnt pull the plug on the servers if I was about to lose my Myrm in a combat site.. If your friends alliance is about to lose a fleet, let it happen. Whats the point of warfare if you cheat your way through it.

again if that's for real then you should have the kills!

The next time something expensive gets tackled and TQ gets DDOS'ed to save it, You will only have yourselves selves to blame CCP...

Lets be honest CCP, what an absolute JOKE, I wasn't even involved and I'm enraged...

first DDOS and Now this, this games been around for 10 years now and as much as i love it, im surprised!

The amount of constant f**k ups you make are unbelievable (BOOT.ini). for example,
you need to start rewarding your players more for playing a game that's constantly unhinged by disappointment,
and quit boosting balancing then changing it back because it became unbalanced!
surely tonight's experience goes to show, LEAVE THE DAMN GAME ALONE...
I hope you're firing that fat fingered moron that ruined such an amazing spectacle.. just saying

Welcome to EVE Online where ccp shape the outcome of events. Where 50k people are playing on the same server but if 10% of these go to the same place the server crashes. Oh... and dont forget that ccp takes your money to improve a product that nobody wants - dust.

Haha, you think something is actually going to come out of hilariousposting in EVEO general discussion.

You want a sarcastic or serious response to that Goonie?

It's not that CCP shoots itself in the foot when it has the largest possible stage for their game that bothers me... it's how often and eager they seem to be to reload the gun.

The buttmad is strong in these goonies.

A question then: what (if any) is the process for/evaluation for the need of the kind of action that took the node down earlier? Is there a true metric by which server/node performance is graded that initiates or flags the need for the initiation of this process? Was there a real, measurable threat of a node crash if intervention did not occur?

Anyone, anyone at all?

If CFC had the same amount of participation in the actual game as they do in this thread; they would have won the Fountain war by now.

A threatening post has been deleted.

Well it's amusing at least if you're not involved. Another case of player driven content

A question then: what (if any) is the process for/evaluation for the need of the kind of action that took the node down earlier?

According to the metrics that you played by in the war for Tribute, they have won this war.
They've fought every fight outnumbered, and they've killed far more of you than they've lost.
What's good for the goose is good for the gander.

The players are the content, it was driven by CCP's use of server mechanics, so it would be CCP-driven content.

again if that's for real then you should have the kills!

It requires players in some form or another. Hence "player driven"

Force all ships that were in the fight before the issue happened, on an agreed time, to spawn back in and fight it out in the same conditions and let history remake itself.

I got bat-phoned, and was on my way home from the Holiday to join in on the action. (I skipped out on family to join this battle)

This is a major mess-up by CCP. Don't fix it if it isn't broken.

However, with that said, the benefit of doubt must be given.
I forgive you.

I do wish CCP could compensate in some way.


Learn from your mistakes. NEVER AGAIN.

Not to sound mean but CCP did say when theres a big fight involved, you have to communicate that event to them in advance so they can prepare it.

If you tell CCP (anyone or any other corporation on the planet that is) at the last second they have to divert all resources to a node, then yes they are bound to be mistakes... like this one. personally, I don't blame CCP for this. It was told numerous times and from a long time ago to tell CCP about those events which was not done.

(I skipped out on family to join this battle)

Learn from your mistakes. NEVER AGAIN.

Because CCP can force players to log online when they don't want to, it's part of the EULA.

You're an idiot.

What part of "organic" didn't you understand?

You mean to say we have over 1000 goons posting now?

That seems interesting.

It requires players in some form or another. Hence "player driven"

Because CCP can force players to log online when they don't want to, it's part of the EULA.

CPP could just rename their Engineers to Wizards. then they could quite seriously say "A Wizard did it"

They shouldn't kick them offline then without aggro timers and wipe the ships from space. If those players decided to log off on their own their ships would still remain in space and in those bubbles.

Instead they were completely wiped, both fleets kicked from space, thus giving the losing side advantage and saving their ships in the process. They can't force anyone to log in, true, but they shouldn't cause anyone to cleanly log off in the middle of a fight.

Who is to say what would have been outcome of that? Maybe it would have escalated further, or one side could have completely gotten wiped out and war in Fountain would have been changed. This way, those ships saved by the derp live to see another day and SRP people let off sigh of relief.

See, what's really getting to us is that we know TEST is low on cash and desperately behind on reimbursements, and are hemorrhaging R64 moons at an impressive rate. They don't have the means to replace what they lost tonight, and what they were about to lose would have been crippling, and probably would have saved us at least a month of structure grinding. This wasn't like Asaki, there wasn't near as much at stake for either side as there was in Z9 today.

Those supers and dreads and carriers that the CFC would have lost had those nodes not gone down? ******* take 'em! We have the luxury of being able to absorb that and keep going, TEST doesn't, and that's why this sucks so much.

I don't know if CCP realizes how hard they ****** us.

Yeah we're so poor right now that they're telling the dudes that lost caps today to hold off filing reimbursements.

NEED ANOTHER LOAN FROM N3 PLS.

2200 - wow. Just wow.



Is that a new record?

Troll = I know 2200+ people who didn't pay that micro-transaction!
Non Troll = Hey, mistakes happen! Granted it was a large capital fight. There isn't much that can be done now that won't **** off even more people!

I cannot post from my main -- but I believe I speak for all goons.

What worries me isn't the capitals getting out, or us losing the strategic objective in this system. What really gets under my skin is that my killboard will not reflect my pvp prowess.

I want CCP to manually adjust my killboard so that it reflects what should have happened, roughly 200-300 test carriers dying.

See, what's really getting to us is that we know TEST is low on cash and desperately behind on reimbursements, and are hemorrhaging R64 moons at an impressive rate.

They don't have the means to replace what they lost tonight, and what they were about to lose would have been crippling, and probably would have saved us at least a month of structure grinding.

Those supers and dreads and carriers that the CFC would have lost had those nodes not gone down? ******* take 'em! We have the luxury of being able to absorb that and keep going, TEST doesn't, and that's why this sucks so much.

I don't know if CCP realizes how hard they ****** us.

The way I see it... Both fleets where kicked? Correct? Therefore, they haven't saved any specific amount of just TEST ships. CFC would have also lost ships in the battle, so your ships where also saved.
Both sides are stating they were winning, as per the norm in war. Both sides lost ships, both sides had ships saved.

This is a sodding game, so what if you couldn't flip the station, or whatever was going down, just do it again tomorrow or whenever...

Troll = I know 2200+ people who didn't pay that micro-transaction!
Non Troll = Hey, mistakes happen! Granted it was a large capital fight. There isn't much that can be done now that won't **** off even more people!

CCP Falcon:

I have a few questions that I would like to hopefully have answered, if you would be so kind.

1) Understanding the purpose of the system remap, and the desire to have it increase response of the server (node) when pushed past its peak, What is the average increase in ability of the server (node) handling the fight itself, when a remap (when performed properly) occurs? Is this increase in processing ability significant enough to warrant a hot-swap?

2) What safeguards are there in place (or I assume planned) to prevent something such as this occurring?

3) This isn't the first recorded instance of a server swap such as this occurring (and causing one side that believed they had the upper hand to potentially lose out). Is the staff member responsible for today's remap responsible for others as well?

4) Why, is this treated like a standard downtime (where everyone gets out freely), Instead of the server recording ALL combat timers in place in the affected systems, and treating the ships that have these flags accordingly. The example here being that when the server comes back to operation, the timers resume?

I understand that these questions may have already been asked, but left unanswered, and I feel it best to reiterate them.

The first part is right, but the second part is wrong. CFC has lost more moons than us. Look north on the third timer my son.

The first part is right, but the second part is wrong. CFC has lost more moons than us. Look north on the third timer my son.


You do realize that N3 has a 200 or 300 man slowcat fleet deployed to Fountain?


I don't understand how you guys think you were going to kill ships you didn't kill, when we hadn't even called in half of our reinforcements yet and we had you almost at a standstill.

Do you think it is just a coincidence that CFC progress in fountain has been going backwards for 2 weeks?

Don't count kills until they are on your killboard.

And exactly how do you think the mechanics of this will work? Who will get the killmails for the kills? Do some of the Goon ships get randomly killed too or do all the Goon ships survive? Does CCP just randomly assign the kill shots? The damage scores? Sometimes you just get the shaft and you have to accept it. That's been something Goons have preached to others ad nauseum over and over forever on these forums. This time the tables are turned and the ones impaled on the shaft are you guys. Ho hum. You'll get over it.

See, what's really getting to us is that we know TEST is low on cash and desperately behind on reimbursements, and are hemorrhaging R64 moons at an impressive rate. They don't have the means to replace what they lost tonight, and what they were about to lose would have been crippling, and probably would have saved us at least a month of structure grinding. This wasn't like Asaki, there wasn't near as much at stake for either side as there was in Z9 today.

Those supers and dreads and carriers that the CFC would have lost had those nodes not gone down? ******* take 'em! We have the luxury of being able to absorb that and keep going, TEST doesn't, and that's why this sucks so much.

I don't know if CCP realizes how hard they ****** us.

No, you don't!!! How do you think the world works? There are ALWAYS other avenues to recoup losses. Most are not in the sense that the average person could comprehend, much less prefer, but there are ways (Legal of course). This is how businesses exist today & continue to profit. If you think any business that's been around for 10 years takes a hit & doesn't do something about it then I fear you have more to learn about IRL, not to mention your power as a customer of ANY business.

After 5 hours why did ccp even bother to transfer the node, the main peak of the battle was over, the cleanup of the enemy fleets was happening and next would've been beating down that carrier blob.

Ccp shouldn't even of risked trying to transfer it to a supernode

Really dude? You haven't called in not even half of your reinforcements but let some 30+ caps get killed? Let me guess: you had us where you wanted us.

If you had those reinforcements, you would have called them and pinged jabber like madmen. Only reinforcements you had were those that died on the field and reshipped and were waiting to bridge via titan only to get roflstomped again.

Maybe you had N3 and PL supers waiting to jump in, maybe that's your support, but even the "we've got supers" card has been played too many times and one day the bluff will be called.

What you have to realize - and btw, I have no stakes in this - is that it was unintentional and I bet you that they are right now kicking themselves.

You don't need to convince them that it was an awful mistake, THEY KNOW.

If CFC had the same amount of participation in the actual game as they do in this thread; they would have won the Fountain war by now.

CCP Falcon:

I have a few questions that I would like to hopefully have answered, if you would be so kind.

1) Understanding the purpose of the system remap, and the desire to have it increase response of the server (node) when pushed past its peak, What is the average increase in ability of the server (node) handling the fight itself, when a remap (when performed properly) occurs? Is this increase in processing ability significant enough to warrant a hot-swap?

2) What safeguards are there in place (or I assume planned) to prevent something such as this occurring?

3) This isn't the first recorded instance of a server swap such as this occurring (and causing one side that believed they had the upper hand to potentially lose out). Is the staff member responsible for today's remap responsible for others as well?

4) Why, is this treated like a standard downtime (where everyone gets out freely), Instead of the server recording ALL combat timers in place in the affected systems, and treating the ships that have these flags accordingly. The example here being that when the server comes back to operation, the timers resume?

I understand that these questions may have already been asked, but left unanswered, and I feel it best to reiterate them.

Actually, they had themselves where they wanted themselves.

No longer in space

I apologize, I missed one more question I had

5) How is there NOT a safeguard at the very least in the system transfer protocols to come up with an error, when a non-existent system is entered? (attempting to move everything but Q9PP-H instead of Z9PP-H, should have failed, as there IS no system called Q9PP-H)

Touch+¬

CCP, killing EVE since 2003.

Evening capsuleers,

WeGÇÖd like to ask that you keep discussions and questions relating to tonightGÇÖs fleet fight in Z9PP-H to this thread so as to keep CCP responses centralized, and to make this the go to place for questions and answers.

WeGÇÖd first like to explain the situation, and what exactly has happened so far.

Owing to the heavy load in Z9PP-H, caused by a fleet flight involving 2200+ pilots deeply embroiled in the Fountain War, the decision was made to remap all other systems away from the node on which Z9PP-H was located in order to improve responsiveness and playability. We were later than we wanted to be to try to reinforce the node (obviously) since it was a more organic-type battle without a fleet fight notification. Once we fully assessed the situation and what was at play, we figured it was time to go for it and the remap in preparation of what was set to be "Asakai 2.0".

This was put into play at 22:14 UTC, however due to an error in communication, all systems including Z9PP-H itself were moved from the node, which caused everyone who was in the system and was involved in the ongoing fleet fight to be disconnected from Tranquility.

The system of Z9PP-H was brought back online and made accessible as fast as possible, however we realize that the mass disconnect of everyone involved in the fight means that ships are potentially saved by their pilots not logging back in once they have been disconnected, or are lost due to other unforeseen consequences of the disconnect.

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.

Many of us here at CCP were watching various player streams of the battle as it unfolded and cannot apologize enough for such a mistake, or for disrupting what was setting out to be an unbelievably epic fleet fight

If you have any questions or comments, please keep them to this thread as a centralized point of contact, and weGÇÖll see about answering them.

Thank you for the explanation. I'm willing to accept that it was an honest mistake and y'all at CCP were genuinely trying to take steps to make the battle better, not worse.

This is an epic "Oops!" but it is no more than that. Forum warriors on both sides of the Fountain War will do their utmost to spin this in favor of their side; others with rage and sputter and whine and unsub. Those people are idiots. This was an honest mistake, and honest mistakes are always forgivable.

Just a heads up CCP, the ihub in 4-EP comes out around 1700 tomorrow. So. Yeah.

That's where you're wrong. Sry to point it out, but there is a lot that could be done. For example, take the most recent snapshot of server data that includes aggression timers. From that data, determine the exact number of people that were "engaged" at the time. Then, remove the ships of all who were engaged, on BOTH sides. It's not an exact, but it is the best way to level the outcome of what would have been.

Thank you for the explanation. I'm willing to accept that it was an honest mistake and y'all at CCP were genuinely trying to take steps to make the battle better, not worse.

This is an epic "Oops!" but it is no more than that. Forum warriors on both sides of the Fountain War will do their utmost to spin this in favor of their side; others with rage and sputter and whine and unsub. Those people are idiots. This was an honest mistake, and honest mistakes are always forgivable.

Really dude? You haven't called in not even half of your reinforcements but let some 30+ caps get killed?

Let me guess: you had us where you wanted us.

Maybe you had N3 and PL supers waiting to jump in, maybe that's your support, but even the "we've got supers" card has been played too many times and one day the bluff will be called.

Does disconnecting when you're agressed require you to be online for your ship to be in space?

Something about a log off timer.... but logs show nothing

Everyone f*cks up once and a while, it's apart of being human!

To say otherwise is to admit you're a ******* ******.

The first part is right, but the second part is wrong. CFC has lost more moons than us. Look north on the third timer my son.

You do realize that N3 has a 200 or 300 man slowcat fleet deployed to Fountain?

I don't understand how you guys think you were going to kill ships you didn't kill, when we hadn't even called in half of our reinforcements yet and we had you almost at a standstill.

Do you think it is just a coincidence that CFC progress in fountain has been going backwards for 2 weeks?

You goons need to thank CCP for saving your fleet as it was getting crushed. #nomad