No exciting kills in the last few days, although last night I got (well, a bunch of us but I got point on and did top damage) some ******* in a destroyer that likes to fly out to the belts and alpha strike our frigates.
However, elsewhere in EVE, 2 massive fights took place:
First the battle of
eHED-GP. A large fight, involving huge fleets of capital and sueprcapital ships on both sides. This was a very large fight, but not record-breaking by EVE standards.
Its notworthiness comes from technical issues, so those of you in various IT fields might be interested. Many ships in EVE have drone bays. Most ships can deploy up to 5 drones' carriers and supercarriers up to 12 with the right modules. Drones can be assigned to assist another ship too, in much the way a player can use a /assist command in most other MMOs. In addition, carriers are excellent logistical (healer) ships. Therefore, it has become a thing to use huge fleets of carriers all repairing each other, and assigning their drones to one "drone bunny" who uses the massed drone firepower to blap targets off the field. This is a very hard strategy to break without using supercapitals.
There's therefore been arguments over the state of balance, but in this case the real issue was the sheer numbers of drones on the field. With a dozen drones per carrier, a full fleet of 250 carriers would mean 3250 objects on the field being tracked without counting opposing ships, support fleets, or any of the drones of THOSE ships. Needless to say, server load is an issue, and it was here. If you scroll down in the article to 17:55 EVE time you will see where CCP Tweeted that the server node was at 100% CPU load and 10% time dialation (game time passing at 10% of real time).
In the midst of this, one side (the CFC, or Goons) decided to jump in several fleets of dreadnoughts totalling around 700 ships. The server calls for 700 ships simultanouesly trying to load grid apparently caused all kinds of bizarre effects, but amaxingly didn't crash the node. The server screamed in agony, but apparently remained up and the Goons ended up getting massacred as their ships appeared on grid but couldn't load it fast enough to engage before getting destroyed. Moral of the story: When CCP emergency tweets that a node is at maximum capacity, don't throw more capital ships at it.
Next, and more spectacularly, the battle in
B-5R. Like the battle of Asakai a year ago where someone accidentaly jumped a titan into an enemy fleet, this one was due to a cockup somewhere. Evidently PL/N3 either failed to pay a soveriegnty bill or a bug caused it to not auto pay in one of their major staging systems. They tried to re-online their sov structures quietly, but were seen and CFC struck quickly to online their own and destroy the PL/N3 ones.
This turned essentially into the Battle of Jutland, Midway, and Leyte Gulf all rolled into one. Both sides committed cupercarriers and titans in large numbers, although the massive drone-carrier fleets were not used and while the node was heavily loaded it was apparently not in danger of crashing.
PL/N3 got the worst of it. It's looking like at least 60 titans destroyed on both sides, with CFC getting about a 2:1 in their favor. Fighting went on over 14 hours yesterday and ended only for scheduled downtime. PL/N3 was attempting to extract, with what success I'm not sure.
Total losses put every previous EVE battle to shame. Over 5 trillion ISK by estimates I've seen so far. Using the price of PLEX to convert puts the real-world equivalent loss at over $115,000 dollars in internet spaceships blown up. More realistically, it's over 500 years of EVE subscription!
While spectacular to read about, it does make me glad I'm not in a major nullsec sov alliance. I can't really take off work, nor would my wife tolerate, 14+ hour battles.