Tag Archives: M2-XFE

CCP Offers Up Broken Monthly Economic Report for December

We got the EVE Online Monthly Economic Report for December last week and I waited a while to write about it because what they put out was simply and obviously wrong in places.  At least more so than usual, so I thought they might go back and fix the most egregious bit.  I am ever the optimist.

EVE Online nerds harder

But, since no update appears to be forthcoming, lets look at what they gave us and hope for better next time.

Destruction

The flaw in the December MER is the destruction numbers.  If you pull out the regional data for destruction, the top ten regions are:

  1. Delve – 3.23 trillion
  2. The Forge – 2.1 trillion
  3. The Citadel – 1.77 trillion
  4. Lonetrek – 1.68 trillion
  5. Catch – 1.47 trillion
  6. Metropolis – 1.38 trillion
  7. Sinq Laison – 1.26 trillion
  8. Domain – 1.04 trillion
  9. Genesis – 832 billion
  10. Black Rise – 753 billion

The total destruction according to the regional data was 35 trillion ISK.  That put Delve down by more than a trillion from November, with overall destruction down by trillion.

The problem is that the number for Delve… and thus the total number for all regions… was very far from the actual mark.

With the war on and the huge battle at M2-XFE that started on December 30th and ran until downtime at 11:00 UTC on December 31st, many of us were expecting to see a huge jump in the destruction numbers for the Delve regional data.  The battle report showed more than 20 trillion ISK destroyed in that first fight.

Battle Report Header

That seems like a big miss.

I sometimes get a bit pissy about CCP and the MER because the numbers from one chart and data set do not line up with numbers from another chart and data set.  It seems like a summer intern project to write a little unit test to validate the data being pulled.  And this month is no different, but at least this time around another data set shows that the regional data is bad, at least for Delve.  So I will bring up the Produced, Destroyed, Mined chart.

Dec 2020 – Produced vs Destroyed vs Mined

This tracks the daily data game wide, with the thick line being the 30 day moving average and the light lines being the actual daily totals.  You can see there, at the end of December, the daily number jumps up off the chart, which has a top range of 6 trillion ISK.  Likewise, the 30 day average for destruction is pulled up, exceeding production.

CCP provides the raw data for that chart in a .csv file, so anybody can see what the actual amounts are.  The total destruction in the data for December is 74.83 trillion ISK, and the value for just December 31st, which covers the primary portion of the battle before downtime, is 23.26 trillion ISK.  (The second battle is in the data already, as it leaks out into the current date when they pull the report, and that totals up to 15, 4 trillion ISK destroyed on January 3rd.)

Of course, the data for that chart isn’t wholly accurate as well as there are three days missing, December 3, 4, and 26.  Still, they reflect the reality of the situation more than the alternative.

So the regional stats are off by a good 40 trillion ISK total, and at least the amount of that battle report for just Delve.  So a more likely ranking is:

  1. Delve – 26 trillion (estimated)
  2. The Forge – 2.1 trillion
  3. The Citadel – 1.77 trillion
  4. Lonetrek – 1.68 trillion
  5. Catch – 1.47 trillion
  6. Metropolis – 1.38 trillion
  7. Sinq Laison – 1.26 trillion
  8. Domain – 1.04 trillion
  9. Genesis – 832 billion
  10. Black Rise – 753 billion

Anyway, here is to hoping they’ll set things right next month.

NPC Bounties

Moving on to NPC bounties, which were the big story last month, we see they are still way down.

Dec – and Faucets Over Time

The numbers began to crash when the ESS and the Dynamic Bounty System were introduced to the game in November.

Total bounties collect in November were 39.3 trillion, which was down from 55.9 trillion in October, the last full month without the new systems.  December, the first full month with the ESS and DBS changes saw that number tumble to 22.8 trillion ISK.

Even with the ESS payments, which amounted to 6.5 trillion ISK, that leaves the total at a little more than half of the value paid out in October.  This is a big hit to income.  The top regions for December were:

  1. Oasa – 1.62 trillion (PandaFam)
  2. Vale of the Silent – 1.19 trillion (mixed small groups)
  3. The Kalevala Expanse – 1.02 trillion (PandaFam)
  4. Perrigen Falls – 996 billion (PandaFam)
  5. Insmother – 918 billion (Legacy)
  6. Cobalt Edge – 753 billion (PandaFam)
  7. Tenal – 739 billion (PandaFam)
  8. Metropolis – 737 billion (High Sec)
  9. Branch – 711 billion (PandaFam)
  10. Fountain – 699 billion (Imperium)

Of note is that a high sec region has entered the top ten, meaning that NPC bounties collected by mission runners are now likely a significant portion of the remaining bounty total.  There are no Forsaken Hubs in Metropolis.

Outside of NPC bounties, the sinks and faucets for December looked like this:

Dec 2020 – Sinks and Faucets

Commodities, which are drops from NPCs in wormhole space, Abyssal Deadspace, and the December holiday event (and maybe the bonds from robbing an ESS in null sec) and sold back to NPCs, continue be the largest ISK faucet into the game, ringing in at 40.59 trillion ISK.

After that there is NPC bounties, which are now in close competition with incursion payouts.  And then there is insurance, which if you look at the first sinks and faucets chart, saw a spike at the end of December, no doubt related to the battle at M2-XFE.

Production

Turning to production, the regional data shows the following regions as the top of the list:

  1. The Forge – 21 trillion (High Sec)
  2. Delve – 7 trillion (Imperium)
  3. Lonetrek – 6.94 trillion (High Sec)
  4. Sinq Laison – 6.25 trillion (High Sec)
  5. The Citadel – 5.73 trillion (High Sec)
  6. Domain – 4.51 trillion (High Sec)
  7. Tribute – 4.22 trillion (mixed small groups)
  8. Esoteria – 3.73 trillion (Legacy)
  9. Vale of the Silent – 3.64 trillion (mixed small groups)
  10. Heimatar – 3.07 trillion (High Sec)

The Forge, and the high sec regions around it, which support the Jita market, remain strong.  Delve, home of the Imperium, led the production outside of high sec.  The war has kept production going.  Legacy production remained ongoing in Esoteria despite claims that they were set to abandon the region.  Oddly, two regions of small holders, Tribute and Vale of the Silent, made the top ten, but PandaFam in Oasa fell to 11th and off the list.

The total for production in the regional data was 107.84 trillion ISK, though since I’m double checking things this month, the production/destruction data only shows it at 74.83 trillion ISK.  However, that is missing three days.  I am not sure those three days would make up the gap, so it shows once again that the data can be questioned.

Trade

Then there is trade value, where the top regions were:

  1. The Forge – 429 trillion (Jita)
  2. Domain – 51 trillion (Amarr)
  3. Sinq Laison – 20.6 trillion (Dodixie)
  4. Lonetrek – 16.25 trillion (Caldari High Sec)
  5. Delve – 16.21 trillion (War Zone)
  6. Metropolis – 10.9 trillion (Hek)
  7. Heimatar – 10.1 trillion (Rens)
  8. Essence – 5.55 trillion (Gallente High Sec))
  9. The Citadel – 5.34 trillion (Caldari High Sec)
  10. Tash-Murkon – 3.65 trillion (Amarr High Sec)

Everything was about in the same zone as November, save for Delve, which was down about 6 trillion ISK.  That is odd because with both sides now based in Delve there ought to be more buying rather than less.

Mining

Finally, there is mining.  After seeming to plateau in November, mineral prices continued their climb skyward as CCP’s keeps the starvation economy plan in place.

Dec 2020 – Economic Indices

The October peak was an all time high point for mineral prices and now the spike continues.

Mining remained largely a high sec occupation, though Oasa in PandaFam territory climbed to the top of the list in December.

  1. Oasa – 1.27 trillion
  2. The Forge – 1.17 trillion
  3. Metropolis – 1.04 trillion
  4. Domain – 990 billion
  5. Sinq Laison – 824 billion
  6. Lonetrek – 751 billion
  7. The Citadel – 617 billion
  8. Tash-Murkon – 575 billion
  9. Perrigen Falls – 568 billion
  10. Everyshore – 559 billion

Aside from Oasa, which is up slightly, numbers are down in every region on that list.  Since the value of ore mined depends on the price, that appears to mean that a lot less mining went on in December, even in Oasa.  The total mined from the region data was 19.9 trillion in value, down from 23.7 trillion in November.

Since we’re skeptical of the regional data this month, I double checked it against the Produced/Destroyed/Mined data which, despite missing the three days indicated above, shows 19.8 trillion ISK value mined, down from 24.9 in November.  That is within the usual margin of error between the different data collection methods.

So it goes.

As always, you can find all the standard charts and the raw data used to create them… such that it is… in the MER dev blog.

Related:

28 Weeks of World War Bee

It was a week of continuing to come to grips with the post-M2-XFE situation for Legacy, as other alliances in the coalition had meetings, including Brave and Warped Intentions.  The Brave meeting was notable for Dunk Dinkle, whose usual mellow countenance was replaced by an angrier, expletive spouting Dunk.  Since he is one of the titan pilots still logged out in M2-XFE (I saw his Leviathan during the fight) he has some reason to be on edge.  And then there is the situation in Catch and Brave’s need to neglect Delve and any break out attempt in order to defend their own space from “knuckleheads.”

We also might be coming up on an infrastructure hub crisis.  The war has seen ihubs destroyed in unprecedented numbers.  Every time a system swaps hands, a new ihub had to be hauled out and deployed.  We’ve already seen in some less hotly contested areas like Querious a lack of desire by both sides to expend ihubs on systems not deemed strategic.  But it sounds like stocks of Planetary Interaction materials, from which ihubs are built, might be running low.  It might be a good time to start on PI.

The Delve Front

The situation in Delve has largely revolved around PAPI trying to come to grips with their situation and regain momentum in the war.  They need to keep pressure on us in Delve and, of course, they need to do something about their trapped titans, supers, and other capital ships.

On the former, the week did heat up some as PAPI tried to re-assert control over ihubs in the region after we used the post-M2 calm to snatch many key systems back.  That has led to a bunch of fights over timers, though the number of systems actually changing hands has not been that big.

Delve – Jan. 17, 2021

The hell camp in M2-XFE continues, to the exclusion of other strategic camps for the Imperium.  The Helms Deep camp has been abandoned for now, so I have removed it from the map for now.  Those systems do not seem to be in play at the moment however.

PAPI has pressed on the M2-XFE camp several times in attempts to clear bubbles.  They have also been trying to drop Azbel’s in the system to get themselves a defensible foothold from which to work.  But so far, after two weeks, the camp is holding fairly strong.

Meanwhile, the situation in M2-XFE looks like this.

The M2-XFE Keepstar grid

The hostiles have been logging in some ships every day just before downtime (11:00 UTC) in order to try and cap them up so that, when the breakout comes, they will be able to jump out.  However, Imperium forces have been countering that for neuts and focused void bombs and the like every day so this could be a long process.  We shall see who has the patience to sit this out the longest.

The Catch Front

Catch picked up in activity over the last week as The Initiative found some more friends to come in and help assail Brave and Warped Intentions.  Brave has held onto their territory so far, but has had to clash repeatedly to do so, often coming up on the short side of the fight when the numbers are counted.  This has kept Brave focused on Catch rather than Delve.

Meanwhile, space that once belonged to The Watchmen has started to get picked up by Dreadbomb, expanding out of Providence.

Catch – Jan. 17, 2021

While Catch has shed one metaliminal storm, which moved on into Querious as expected, the other one is hanging out in the middle of Brave space.  It might move on towards Querious and Delve as well.

Other Theaters

In Queirous the Imperium has popped Legacy Coalition ihubs in a dozen systems, the bulk of them having been held by Brave.  Neither side has been keen to drop a fresh ihub in many systems in the region though, so that made for a fresh batch of unclaimed locations.  Meanwhile, that metaliminal storm that looked to be heading out of Catch made its way into Querious and might keep moving into Delve.

Querious – Jan. 17, 2021

Over in Esoteria The Bastion and its Stain Russian allies haven’t expanded their ihub holdings this week, so I can re-run last week’s map.

Northwest Esoteria – Jan. 17, 2021

They have, however, been shooting structures, including planetary customs offices and the like in order to be a nuisance and prevent TEST members from picking up their PI materials. (Which, as noted above, can be used to make ihubs… or structure fuel blocks… or a number of other essential items.)

A fruitful evening of POCO kills

The Bation’s main FC Qicia was on The Meta Show this past weekend to talk about what has been going on in the region, which included TEST flying a Munnin fleet out from Delve to defend structures in Esoteria.

My Participation

I have been on the M2-XFE hell camp for a while every day, helping out to cover the USTZ hours.  As I have said before, PAPI keeps logging in just enough targets to keep everybody happy and hopeful.  I have also made it out on a few for some of the ihub skirmishes.

Out in Eagles with Mister Vee

The week saw no ship losses for me, so my count for the war stands as follows:

  • Ares interceptor – 15
  • Crusader interceptor – 5
  • Atron entosis frigate – 6
  • Rokh battleship – 5
  • Drake battle cruiser – 4
  • Malediction interceptor – 4
  • Scimitar logi – 3
  • Ferox battle cruiser – 3
  • Purifier stealth bomber – 2
  • Guardian logi – 2
  • Scalpel logi frigate – 2
  • Raven battleship – 1
  • Crucifier ECM frigate – 1
  • Gnosis battlecruiser – 1
  • Bifrost command destroyer – 1
  • Cormorant destroyer – 1
  • Hurricane battle cruiser – 1
  • Sigil entosis industrial – 1
  • Mobile Small Warp Disruptor I – 1

Other Items

As I mentioned over the course of the week, we hit the date where structures need Quantum Cores in order to provide station services like repairs and tethering.  Also, new structures that are deployed now need a core to come online, otherwise they will never enter that state and will remain immediately killable.

This is the big money moment for many alliances.  As I mentioned previously, TEST was pulling down structures in their space, likely to avoid having to core them.  The Imperium started issuing war bonds in order to cover that bill.  While I have yet to receive my shares in the corporation that is being used for the war bonds, they did boost up the number of shares available from the default 1,000 to 21,000.  At a price of 1 billion ISK per share, that is potentially a lot of liquid cash.

Share count

That does not necessarily mean that they raised 21 trillion ISK from the offer, but they did get enough to drop cores into our critical structures.

And the peak concurrent users for the week remained about on par with the previous week:

  • Day 1 – 38,838
  • Week 1 – 37,034
  • Week 2 – 34,799
  • Week 3 – 34,692
  • Week 4 – 35,583
  • Week 5 – 35,479
  • Week 6 – 34,974
  • Week 7 – 38,299
  • Week 8 – 35,650
  • Week 9 – 35,075
  • Week 10 – 35,812
  • Week 11 – 35,165
  • Week 12 – 36,671
  • Week 13 – 35,618
  • Week 14 – 39,681
  • Week 15 – 40,359
  • Week 16 – 36,642
  • Week 17 – 37,695
  • Week 18 – 36,632
  • Week 19 – 35,816 (Saturday)
  • Week 20 – 37,628 (Saturday)
  • Week 21 – 34,888
  • Week 22 – 33,264
  • Week 23 – 33,149
  • Week 24 – 32,807 (Saturday)
  • Week 25 – 31,611
  • Week 26 – 39,667 (Saturday)
  • Week 27 – 34,989 (Saturday)
  • Week 28 – 34,713

Related

Life on the M2 Hell Camp

Feed us PAPs and hostile caps and we’ll keep logging in!

-Motto of the M2 hell camp

I’ve spent quite a bit of time of late in the hell camp in M2-XFE, sitting in my Rokh, waiting for a target to appear.

My Permaband Rokh on tether in the bubbles

“Camping” is a pretty common term in MMORPGs.  I was camping spawns back in TorilMUD before EverQuest was even a twinkle in John Smedley’s eye.  You sit and you wait for a mob to spawn or otherwise show up, and then you kill it.  And then you do it again… and again.. and again… until you get your fill or your rare drop or whatever.  It has its variations.  In PvP you can camp the respawn point in a battleground or the objective the enemy is trying to reach.

A “Hell Camp” on the other hand might be a special EVE Online term.  I haven’t run into it anywhere else.

A “Hell Camp” is an operation when you have an enemy or a hostile fleet or the like trapped, in a station or logged out in space, in a known location and you set up to camp them from down time to down time, every day, for as long as it takes, until they either try to break out or they offer terms you can accept to let them go.

Many a hell camp has been called, but sustaining them is difficult.  You really have to have the hostiles pinned down for it to be effective and you must field a force capable of sustaining the camp.  Attempts to hell camp the Imperium into the Quafe Factory Warehouse station in Saranen during the Casino War were largely ineffective.  We had enough people that we came and went when we wanted.  And, in the end, packed up and left for Delve without much hindrance.

Likewise, at one point Guardians of the Galaxy declared they were going to hell camp Reavers into a station in ROIR-Y during a deployment.  That lasted less than a week before they wandered off and let us be.  Such a camp isn’t a lot of fun over an extended period of time.

Which leads us to the camp in M2-XFE, where 337 334 titans sit trapped, along with scores of smaller capital ships, the remains for the fights over the Keepstar armor and hull timers.

That is a lot of titans.  Progodlegend said that PAPI was bringing one thousand titans to attack Delve, so that is about a third of what they promised.  Add in about 200 more destroyed in both battles and afterwards and we’ve trimmed their titan fleet by half… if we can keep a hold on the 334 that are logged out.

The Mittani has said that this camp is the most important thing for us in the war right now.  We’ve given up the Helm’s Deep camp and moved carriers and supercarriers to the M2-XFE Keepstar to sit with fighters out, ready to grab anybody who logs in.  We also cleared out hostile structures and deployed multiple additional Fortizars around the camp grid.

Bubbles on the M2 Keepstar Grid – Now featuring more Fortizars

How long will this last?

We’ve been at it for two weeks now and the camp shows no sign of slackening.  There is always a full fleet worth of ships on when I join, and an overflow fleet with 50-150 more hanging about, putting a sizable force on call around the clock.

It is helpful that being on the camp doesn’t demand much attention.  On my big monitor I have EVE Online open, full screen, in the background and then something else I am working on… like this blog post… in the foreground with just the overview and fleet history from the game displayed on the right side of the monitor.

That is enough.

My overview tab is set to show nothing save hostiles, so somebody logging in or showing up attracts the eye immediately.  I haven’t missed anything that has shown up in range of my guns, save for the interceptors that occasionally show up to try and pop bubbles.

A Nagalfar provides a momentary target for us

You can sit on coms and chat.  There is a channel just for the camp.  I prefer to do other things and wait for the overview to alert me to action.

It is nice that we get PAP links, marking our participation.  (I covered PAP links in another post a while back.)  But even those reach a level of absurdity when you get one every three hours for being logged on in the camp.

The fact that PAPI forces keep logging on trapped ships is probably the biggest thing keeping people active in the camp.  At this point I am sure PAPI knows the situation and has communicated it as far and wide as they are able, but people make mistakes.  Somebody logged their titan in too soon before downtime… they have been logging in just before downtime to recharge capacitor… and ended up getting blow up.  And there have been a few where I suspect that they clicked on the wrong character by mistake at the login screen… I’ve done that a few times… and then their stuck riding the warp back into the bubbles and sure destruction.

Every kill revitalizes those in the camp.

But there is also, as part of the Goon identity, the idea that we’ll do something like this for as long as it take, far longer than any other group in the game would, just out of sheer stubbornness and desire to prove that we can.  So the camp goes on.

Which doesn’t mean the war has stopped elsewhere.  The week has seen a bunch of subcap battles over ihubs and timers both in Delve and in Catch.  The fighting surges back and forth and billions in ships are still being blown up.  I’ve been on some of those this week.

But the camp remains, uninterrupted, waiting for the hostiles to attempt a break out.

27 Weeks of World War Bee

The past week saw both sides adjusting to the new reality after the battles over the Keepstar in M2-XFE.  The Imperium has used their momentary advantage in morale to take back ihubs.

On the PAPI side, Progodlegend issued what has been called the “Dunkirk” update in which includes a mea culpa about knowing that jumping into the second fight at M2-XFE was a bad idea but that nobody wanted to be the person who called it off.  Also in the update:

  • Shifting to a “much simpler and much more fun game plan”
  • Breakout plan for trapped capitals under way
  • Titans lost at the fight will be reimbursed; may need to go to third parties for hulls
  • May issue war bonds to cover mounting costs

It has been reported that TEST is unanchoring some structures to avoid having to pay for quantum cores, the theory being that they can pay for SRP or pay for cores, but not both.  Critiques of the prosecution of the war have been rife, with Vily even being compare to George McClellan.  Certainly this past week did give PAPI a taste of the Seven Days Battles of the Peninsula campaign.

On the Imperium side, the M2-XFE system has been camped from downtime to downtime since the first fight and there are usually two fleets running because one is inevitably full.  Camping that space has become a priority as there are said to be 337 titans logged off in the bubbles under the Imperium Keepstar.  Some Imperium members have been offering to buy trapped ships, which led to at least one Wyvern logging and getting blown up.

On the weekly fireside chat Saturday The Mittani urged us all to man the M2-XFE camp as it is our key threat to PAPI assets at the moment.  When asked about negotiations, he did say that he would offer a golden ticket out of the trap to any single alliance that offered the best terms.  While he did not expect anybody would take the offer, he did explicitly exclude TEST from it as they are the ones who sowed the seeds of war and who thus must reap the whirlwind.  TEST is estimated to have more than 90 titans trapped in M2-XFE.

And then, on the finance front, the first series of Imperium war bonds has been sold out.

Delve Front

While Delve has been the primary focus of the war for week, these past ten days have pulled most everybody away from the secondary fronts.  The Imperium has setup a downtime to downtime camp, complete with bubbles, around the M2-XFE Keepstar.

In furtherance of this, the Imperium blew up the Fortizar PAPI had setup on the Keepstar grid to act as a staging point for attacks.

The PAPI Keepstar begins to explode

In its place the Imperium dropped its own Fortizar just in case any supers or titans managed to log off on tether.  PAPI defense of the Fortizar was limited to a small group of interceptors there to harass the attackers.

Bubbles on the M2 Keepstar Grid

Those bubbles groups are:

Bubbles on the M2 Keepstar Grid – Annotated

The primary trap is where the titans from the first battle have (mostly) remained logged off since downtime on Dec. 31, 2020.  The secondary trap is the point where PAPI titans, supers, and other capitals jumped in for the second battle, the location of some “ghost” titans.

Maintaining that camp has been declared the coalition’s highest priority due to the estimated 337 titans trapped in the system.  Jay Amazingness has been named the Bubble Czar to make sure that we have correct coverage of the areas where hostile ships are logged off.

The camp itself continues to feed people kills, which helps keep it going.  I have been on enough to have caught a titan and a few faxes.  Every so often somebody will log on… either by accident or in futile hope… and they get blown up.  There have even been some ghost titan kills, which means that not all the empty fit titans that were blown up during the second fight were moved back to their starting point.

You only die twice

PAPI sends interceptors and other small ships out to attack the anchored bubbles now and then, which also feeds the camp and keeps it engaged.  Give us PAPs and some kills and apparently we’ll sit logged in all day every day.

PAPI was in a funk early in the week and the Imperium used that time to work on some of its own problems in Delve.

Delve – Jan. 10, 2021

The Imperium started by taking back all of the ihubs in the NJU-QV constellation, which includes M2-XFE and is the route into the Fountain region.  The ihub blitz carried on and flipped more than a dozen ihubs, about half of which were systems containing Keepstars.  The systems hit were:

  • KEE-N6
  • M2-XFE
  • 5-CQDA
  • I-E3TG
  • ZXB-VC
  • S-6HHN
  • 4X0-8B
  • 23G-XC
  • D-W7F0
  • SVM-3K
  • 6Q-R50
  • UEXO-Z
  • 9O-8W1
  • 1-2J4P

Towards the end of the week PAPI started putting up a stiff resistance, and the struggle over the D-W7F0 ihub was a long fight. By the weekend the invaders were able to field enough pilots to keep the Imperium from flipping the 1-SMEB and M5-CGW ihubs.

Catch Front

The aftermath of the fights in Delve relegated the Catch front to a distant second over the last week, which was probably fine with Brave.

Catch – Jan. 10, 2021

The Watchmen space continues to remain empty and the two metaliminal storms in the region both seem to be making their way towards Delve as if they want to join up with the storm already there.

The one bit of influence the region has was when The Initiative reinforced a TEST Keepstar down to the final timer, which required Legacy to show up and make sure it did not get blown up, something that coincided with an ihub contest in Delve.  There was also a fight over the ihub in FAT-6P, a system on the Legacy Ansiblex jump gate network that went to the Imperium, disrupting their travel infrastructure, though Legacy regained the ihub to restart the time until they can use the system again.

Other Theaters

Even more so that Catch, Querious was very much a backwater after the events of the last week or so.  Some small changes, but not a hot spot.

Querious – Jan. 10, 2021

While the Imperium has been focused on Delve, northwest Esoteria remains a camp in the middle of Legacy space and a spot from which to launch attacks.

Northwest Esoteria – Jan. 10, 2021

And over in Fountain The French ConneXion has picked up a couple of ihubs that were sitting empty.  I do not know if this is the start of something, but the two systems the grabbed would make for a nice Ansiblex jump gate conneXion.

My Participation

While the ihub struggles tend to be in EUTZ I managed to get into fleets that help turn the NJU-QV constellation and was there for the see-saw struggle over the D-W7F0 ihub.  I was also around for the destruction of the PAPI Fortizar in M2-XFE.  And then there has been the camp in M2-XFE, which is something I can log into and put in the background so that just my overview and the fleet window are poking out behind whatever I am working on.  If a target pops up I can click over and shoot.

That was all fairly low key and I did not end up losing any ships over the course of the week, so my loss count remains:

  • Ares interceptor – 15
  • Crusader interceptor – 5
  • Atron entosis frigate – 6
  • Rokh battleship – 5
  • Drake battle cruiser – 4
  • Malediction interceptor – 4
  • Scimitar logi – 3
  • Ferox battle cruiser – 3
  • Purifier stealth bomber – 2
  • Guardian logi – 2
  • Scalpel logi frigate – 2
  • Raven battleship – 1
  • Crucifier ECM frigate – 1
  • Gnosis battlecruiser – 1
  • Bifrost command destroyer – 1
  • Cormorant destroyer – 1
  • Hurricane battle cruiser – 1
  • Sigil entosis industrial – 1
  • Mobile Small Warp Disruptor I – 1

Other Items

Just a bit of New Eden war trivia, but I was out on an op and saw a vaguely familiar name pop up in fleet chat.

Haargoth Agamar returns to the game

Haargoth Agamar was the player who, close to 12 years ago now, disbanded Band of Brothers back during the Great War, one of the great moments in EVE Online.  World War Bee has brought back a lot of old names and we can add one more to the list.

Meanwhile, CCP has been doing their usual bang up job when it comes to presenting a coherent message to the user base.  While they’ve spent the last year nerfing the ability to earn ISK in game, they still want to push wealth as an objective in the New Eden.

Get Wealthy!

As you can imagine, this has irked a few people.

  • Day 1 – 38,838
  • Week 1 – 37,034
  • Week 2 – 34,799
  • Week 3 – 34,692
  • Week 4 – 35,583
  • Week 5 – 35,479
  • Week 6 – 34,974
  • Week 7 – 38,299
  • Week 8 – 35,650
  • Week 9 – 35,075
  • Week 10 – 35,812
  • Week 11 – 35,165
  • Week 12 – 36,671
  • Week 13 – 35,618
  • Week 14 – 39,681
  • Week 15 – 40,359
  • Week 16 – 36,642
  • Week 17 – 37,695
  • Week 18 – 36,632
  • Week 19 – 35,816 (Saturday)
  • Week 20 – 37,628 (Saturday)
  • Week 21 – 34,888
  • Week 22 – 33,264
  • Week 23 – 33,149
  • Week 24 – 32,807 (Saturday)
  • Week 25 – 31,611
  • Week 26 – 39,667 (Saturday)
  • Week 27 – 34,989 (Saturday)

And, finally, the requirement to have quantum cores in all structures hits this coming week.  Quantum cores were introduced with the September update and, since October, new structures have required them.  January 12th is the date that all structures will need them or ship fitting, tethering, and ship/module repair services will be disabled.  Without a core structures will also be vulnerable to immediate destruction.  No timers or return trips will be required.  I expect this will be another “happy time” for Upwell destruction.

Related

The Imperium Retakes the NJU-QV Constellation in Delve

The likelihood of a another fight soon over the Keepstar in M2-XFE diminished greatly last night when the Imperium flipped the ihubs in the entire NJU-QV constellation which includes that system.  Shortly after the second fight that saw PAPI forces face a lopsided loss when the server was unable to handle their forces attempting to jump in after the Imperium had setup more than 4,000 ships on Keepstar to defend it, Imperium pilots went out and reinforced the ihubs in the constellation.  The timers came up last night.

The Delve NJU-QV constellation in green

The Imperium, motivated by PAPI’s misfortune, formed up four fleets and a large number of entosis ships to contest the timers.  PAPI was reported to have assembled a force capable of contesting the timers, but stood down rather than do so.  As the evening progressed, one ihub after another fell until the constellation was back in Imperium hands.

The Delve NJU-QV constellation restored to Imperium control

Much was made of the taking of the NJU-QV constellation previously, as it cut the Imperium off from the Fountain region and was to serve as the springboard of PandaFam’s re-invasion of that region.  The latter petered out, but there were still multiple Imperium Keepstars in the constellation that faced the threat of destruction once PAPI waited out the 35 timer and was able to deploy cyno jammers to keep the Imperium from jumping in when the Keepstars were contested.  However, that went astray when a newbie Imperium pilot reportedly kept shooting the cyno jammer.  Per Asher Elias:

You may not know this but the M2 ihub jammer was stopped by a couple month old :shobon: newbee shooting the jammer to pause it. This new player is directly responsible for nearly 300 dead enemy titans. Every ship counts.

That led to a bit of classic Goonswarm propaganda being updated yet again.

Every Ship Counts

That opened a hole that allowed the Imperium to kill their cyno jammers and deploy three of their own.  While the Imperium could not jam the system, the cyno jammer mechanic only allows three to be deployed in a single system, so we had a flash of the old “defensive SBU” tactic of the Dominion sovereignty days, which helped the Imperium to get setup on the Keepstar for the second fight.

Meanwhile, the Keepstar grid in M2-XFE remains bubbled and camped by Imperium forces eager to get in on another super or titan kill.  I lucked in on an Avatar kill when a FinFleet pilot decided to risk it and log in.  Chance was not with them.

The Keepstar camp gets another kill

Despite a persistent PAPI claim that all the supers and titans from the second fight either died or where ghost kills and restored to the T5ZI-S Keepstar, bubbles and dictors have been deployed above the Keepstar as well as below it.  And the upper bubbles have yielded some kills.  I watched a Nyx that managed to log out during the second fight get warped right back to its logout spot in the midst of all those bubbles, where it too was blown up.

The Nyx in its final moments

Some half-hearted attempts have been made to try and free the trapped capital ships left behind after both fights, but the promise of more kills has kept the camp strong so far and any form up by the hostiles has been met by a counter-form by the Imperium.

For the moment the Imperium has been able to check PAPI’s momentum in Delve.  But that does not preclude them being able to get their act together again and continue their onslaught.  The war isn’t over yet.

26 Weeks of World War Bee

Here we are on the first Monday of the new year.  A lot of us are back at work.

And the war?

The war is now at about the six month mark.  That is a long time for continuous operations.  The great war lasted for three years, but was a series of intense periods of fighting broken up by quiet periods where both sides rebuilt.  We’re still fighting and have reached levels of destruction never before seen in New Eden.

I was worried that the week between Christmas and New Years would be quiet, so had a couple of small items to hand to fill out this opening section of the weekly post, like the fact that Asher Elias, 23rd best FC in the Imperium, is now at the top of the kill mail list for Goonswarm Federation Alliance.

Asher in first position

He passed Bratok Srayona, a pilot nobody could really recall, and who was active between February 2012 and August 2017.  They apparently went on a lot of fleets and got on a lot of kill mails.  He was the epic line member of the alliance in his time.   I must have flown with him, looking at some of his kills, but never knew him.

Then there was the fact that the Imperium began issuing war bonds to support the fight.  This has been viewed by PAPI as a sign of weakness, a last desperate attempt to stay in the fight, a sign that we were on the brink.  But it raised more than a trillion ISK in the first hours of issue, so it will sustain us for a bit.  One billion ISK will buy you one bond with a return rate of 10% per year, with payments due on the first of the month.  That one bond will earn you about 8.33 million ISK every time the first rolls around. [edit: changed from 8.4 to 8.33 million ISK]

But all of that was eclipsed by the battles over the Keepstar in M2-XFE where, during the armor and hull timer fights, the two sides may have destroyed more than 300 titans. (~250 for the first fight and maybe as few as 50 or as many as 170 for the second.)  CCP is going to have to do a dev blog to give us an official count because, unlike the presidential election, there are actually some irregularities in play here.

No matter what though, trillions of ISK went up in flames as the Imperium and PAPI clashed in the battles that so many were hoping for.  It was an epic week in New Eden.  The Monthly Economic Reports for December and January are going to be interesting.

There was also a monthly loss report put together for December.

Most expensive losses

This includes the titans from the first M2-XFE fight, but not the second.  The balance of loss remains fairly close, with the Imperium losing 16.5 trillion ISK to PAPI’s 15.9 trillion.  For January though, PAPI might already be close to 10 trillion ISK in the hole.  And there are, as of this writing, still a significant number of PAPI capital ships logged off on the Keepstar grid in M2-XFE that are being camped around the clock by Imperium forces, so there may be some more losses when PAPI makes a serious break out attempt.

Delve Front

Titans exploded in huge numbers in M2-XFE, a system previously of no particular consequence that has now entered the realm of legends.  There are a number of articles specifically about that event and, rather than retelling the tale here, I will link to them specifically at the end of this post.

With much of the week spent focused on the Keepstar in M2-XFE, the map did not change dramatically.

Delve – Jan. 3, 2021

A few ihubs changed hands, the most important likely being the one in PUIG-F, where an Imperium Keepstar is anchored.  Taking that ihub back reset the 35 day clock on PAPI being able to install cyno jammers and reduce the structure without the Imperium being able to drop supers and titans to defend it.

And then there is the metaliminal storm, which has wandered into the Helms Deep defended systems.  This is actually a bonus for the Imperium as the storm disables the ability to cloak, so there won’t be any sneaking up on an anomaly to light a covert ops cyno for a hot drop.

Catch Front

At the beginning of last week I was pretty sure this was where the action would be.  The Initiative and Reavers and other Imperium groups were out and setting fire to the place.  The Watchmen Alliance was falling apart and its sovereignty was collapsing.  We were reinforcing the ihub in Brave’s capital system and getting fights over it.  Good times were being had.

Catch – Jan. 3, 2021

Even the two metaliminal storms seemed to be on the move in the region… and an incursion popped up in The Watchmen space, like they needed something else on their plate.  And then on Wednesday all eyes turned to Delve and M2-XFE and operations went mostly quiet in the region.

One interesting item did come up later in the week.  With all the focus on M2-XFE, The Initiative put the TEST Keepstar in 0SHT-A into the hull timer.  We could have another Keepstar fight this week… just in Catch.  We’ll see if anybody shows up for it tomorrow.

Other Theaters

Querious remained a secondary point of conflict, as ihubs were reinforced and occasionally changed hands.

Querious – Jan. 3, 2021

The biggest win for the Imperium was the GOP-GE ihub, as that system hosts another Keepstar of ours.

Over in Esoteria the insurgent forces continue their work against TEST, expanding their reach a bit further while eyes were on the big titan fights.

Northwest Esoteria – Jan. 3, 2021

My Participation

I somehow managed to stumble into the right place at the right time all week.  I was in the fights in Catch early in the week and then managed to show up just at the right moment in M2-XFE for the first fight, witnessing the opening titan salvo as I tethered up at the Keepstar.

Titans open fire with Doomsdays

And then I was back again for the second fight, where we were able to pick off PAPI titans as they loaded into system, leading to a lopsided slaughter.

The PAPI titan blob with faxes being whittled down

So I had a few more “I was there,” or at least “I can say I was there,” experiences in New Eden.

I also lost a few more ships, including two more Ares interceptors moving around Delve and a Scimitar at one of the fights in GE-8JV, which brings my total war losses so far to:

  • Ares interceptor – 15
  • Crusader interceptor – 5
  • Atron entosis frigate – 6
  • Rokh battleship – 5
  • Drake battle cruiser – 4
  • Malediction interceptor – 4
  • Scimitar logi – 3
  • Ferox battle cruiser – 3
  • Purifier stealth bomber – 2
  • Guardian logi – 2
  • Scalpel logi frigate – 2
  • Raven battleship – 1
  • Crucifier ECM frigate – 1
  • Gnosis battlecruiser – 1
  • Bifrost command destroyer – 1
  • Cormorant destroyer – 1
  • Hurricane battle cruiser – 1
  • Sigil entosis industrial – 1
  • Mobile Small Warp Disruptor I – 1

Other Items

CCP gave us the option to make My Year in EVE Online videos, which had the option to include the most valuable kill mail you were on.  And then, two days later, M2-XFE happened and a lot of us had an even more valuable kill mail for the year that wasn’t in the clip.  Oh well.

That battle though, it managed to pop up the peak concurrent user number for the week, getting it close to the 40K mark.  CCP Explorer put the count across the three key systems as well past 13K, giving Delve 37% of all pilots logged in at the peak.

If the servers could have handled it, we would have almost doubled the world record set at FWST-8.  However, the servers were not up to that task, not by a long shot.

Remember that when somebody says null sec is a tiny fraction of the game that nobody cares about.  The fight itself made for the third highest concurrent peak of the war, reversing the downward trend we had been seeing over the last few weeks.

  • Day 1 – 38,838
  • Week 1 – 37,034
  • Week 2 – 34,799
  • Week 3 – 34,692
  • Week 4 – 35,583
  • Week 5 – 35,479
  • Week 6 – 34,974
  • Week 7 – 38,299
  • Week 8 – 35,650
  • Week 9 – 35,075
  • Week 10 – 35,812
  • Week 11 – 35,165
  • Week 12 – 36,671
  • Week 13 – 35,618
  • Week 14 – 39,681
  • Week 15 – 40,359
  • Week 16 – 36,642
  • Week 17 – 37,695
  • Week 18 – 36,632
  • Week 19 – 35,816 (Saturday)
  • Week 20 – 37,628 (Saturday)
  • Week 21 – 34,888
  • Week 22 – 33,264
  • Week 23 – 33,149
  • Week 24 – 32,807 (Saturday)
  • Week 25 – 31,611
  • Week 26 – 39,667 (Saturday)

Related

 

PAPI Thwarted at Final M2-XFE Keepstar Timer by the Early Bird Imperium

After the mighty massacre of titans at the Keepstar armor timer in M2-XFE on Wednesday night/Thursday morning, all eyes in the war were on the system for the battle over the final timer.  Expectations were high on both sides for a repeat of the earlier blood letting.

That PAPI plan, after getting logged out at downtime after the first fight, was to stay logged out there until the final timer was up, bringing up some reinforcements to jump in to support the forces already there.  Or so their actions indicate to me.

The Imperium plan involved a tactic as old as war itself: Get there first in great numbers.

PAPI had some early move ops to get reinforcements in position, which led to a few losses along the way.

An early start on titan losses

Rorgan Darator is said to be a Progodlegend alt, which makes those kills extra special.

The Imperium had a State of the Goonion at 20:00 UTC, five hours before the Keepstar timer.  The SOTG had to be move to Twitch as the Mumble server was struggling to handle all the players attempting to log in.  While a Fireside on a Saturday can run out to 45 minutes, SOTGs tend to be short and to the point.  The Mittani got on with us, told us the plan, then sent us off to do it.  We started jumping capital ships into M2-XFE right away… some had jumped before the SOTG… deploying them below the Keepstar, close by where the PAPI fleet logged out.

The mass of supers and titans below the Keepstar

That huge formation of capitals was on grid for hours.  There were more than 4K people in system at that point, way before the fight began.  This is the oldest play in the book in New Eden, getting into a system early and being ready before the enemy.  Tales of this tactic go back to the Great War and before.

We were there… my alt in his Ninazu in the fax fleet… when PAPI finally started to jump in their fleet from T5ZI-S.  Their choice was to go in way above the Keepstar, away from our titans.  That put them out of range of our titans (and our titans out of range of theirs), but the supercarriers sent their fighters up after them.

PAPI titans up high in the bubbles

They had 6K people in their staging system and we had 4K in the system already (amounting to more than 25% of the nearly 40K people online in the game at that point) when they started jumping in and… the math just didn’t work out.  The server, already in heavy tidi when we were just sitting around doing nothing, began to chug and grind and commands began taking minutes to complete, so that the hostile titans were landing on grid and were not able to load fully or react before the fighters were on them.  Titans began blowing up in ones and twos and threes.  It turned into a one-sided fight very quickly.  The count of dead PAPI titans kept growing.

But the server was still an issue in other ways.  Some of the kill mails in the long list on zKillboard show the titans to be unfit, which explains how they died to the fighters so quickly at times.  The fighters were on them before the server could pull up and load their fit.  There were also reports that some titans, on being blown up, loading back up in the station from which they had undocked undamaged.  Over at Talking in Stations they began counting both kill mail losses and wrecks on the field, and the wrecks were showing up at about half the rate.

When this started going very wrong for PAPI they tried to put the brakes on things, but too many were already on the way.

So the actual number of dead titans may remain unknown unless CCP comes out with a dev blog, but the battle reports last night were crazy lopsided in favor of the Imperium, with about 100 billion ISK lost on the Imperium side compared to more than ten trillion ISK lost to PAPI.

Battle Report Header – Probably a Worst Case Scenario

The armor timer fight was a massacre of titans, but the final timer ended up being a massacre of PAPI.  The final accounting will come at some point.  Over at zKillboard the loss list looks to be ~170 titans, plus the five killed before the fight.  If even a majority of those are legit, PAPI could be looking at 100 titans destroyed for no titan kills.  This was B-R5RB in an evening.

And then there was the Keepstar, which repaired successfully, so we won the objective.  They need to start over again in order to destroy it.

My main, once again in a boosting ship, ended up having to wait until things were well under way before he was able to bridge in.

Flown out on titan wings

By the time he got there the call went out to pull down boosts and other things that might be contributing to server lag.  So there I was, in the system… well, I got kicked out, logged back in, waited for 40 minutes at the login screen and then a long stretch with just a black screen, but eventually I was through again… with no real role.  So I went motoring up the Keepstar to see if I could take a few pot shots at hostile titans to get on a kill mail or two of my own.   I managed to get on two, both of which had clearly loaded into the system.  They were not ghost targets.

Our titans did the same, warping up to the top of the model, to start picking off the remainder of the PAPI fleet.

Imperium titans now in range

Now that the fight is over, the post-game analysis will start.  That is already well under way on Reddit, with memes proliferating.  Some will seek to blame the servers for the loss, and certainly server performance played a role.  But the servers favor nobody specifically, and allowing the Imperium to setup on the Keepstar with thousands of pilots, to the point that tidi and lag was constant, and thinking they could jump a fleet in on grid and engage without issues was a serious mistake. (Grath Telken puts it more directly in this Twitch clip, though his full statement is even more brutal.)  People will be playing out how it should have been done all week or trying to justify the plan as a good one.  But none of that will change what actually happened.

Certainly pleas to CCP to undo losses will go unfulfilled.  There is a long history of such requests being denied, so starting now would be a very bad look, and all the more so since they have been going on and on about the problem of super and titan proliferation.  Give back dead titans people jumped into a fight?  Not going to happen.

Then there is PAPI going forward.  The first fight only whetted people’s appetites for more slaughter, but this fight was a serious setback for PAPI, a major loss.  They are not defeated in their conquest, but they will have to asses their strategy.  They successfully killed the NOL-M9 Keepstar in Delve by putting up a cyno jammer and keeping us out of the system so they could blow it up unimpeded.  The system’s location helped with that.  If they want to kill more Keepstars they will have do it the safe way, with no slip ups.

But first they have to get out the capital fleet that logged off in the system after the first fight.  They didn’t log on and are still in the bubbles the Imperium laid out for them.

Finally, there is the war itself.  Leaving aside Vily’s extermination policy, even evicting the Imperium from Delve seems problematic now.  Locking us out of a system with cyno jammers and gate camps is one thing, but how do you get in and fight us in 1DQ1-A, our home system, where all our ships, big and small, are waiting to greet any invader, where we can be formed up on grid before an attacker can start finish jumping in?  And if you can’t kick us out of our home system can we be defeated directly?  Does PAPI have the wherewithal to lay siege to Delve for months more to wear us down to the point such an attack is possible?

For now the war goes on, but everybody will be watching for PAPI’s next move.

Related:

Titan Massacre at M2-XFE

We had been warned to be on hand for possible fleets yesterday.  The armor timers for three Imperium Keepstars under PAPI cyno jammers were set to come out and we were going to try to make them pay for the effort this time around.

I was busy during much of the day, but I could see the pings coming up announcing fleets.  It looked like the enemy was going to try for the Keepstar in M2-XFE.  The other two Keepstars were ignored and repaired while both sides focused on the remaining one.

When I finally had a chance to log in I flew out in an ECM burst Malediction just to take a look.  Both sides were grouped up, two masses of titans and supers facing each other, the Imperium fleet on the Keepstar and the PAPI fleet below it, shooting the structure.  The timer had been paused at just about the 10 minute mark.

My arrival

As I was scooting around, tethering up, and looking for some way to be annoying, the Imperium titans, which had been tethered, opened up with a doomsday barrage on the PAPI fleet.

Titans open fire with Doomsdays

That was the point that the battle became real.  There were over 5,000 names in local, a number that grew past the 5,500 mark as the battle carried on.

Exchange of fire

At that point I flew my Malediction into the midst of the hostiles and set off the ECM burst.  I wasn’t sure if I was going to be able to commit to the fight.  But then my wife and daughter went out together and I decided to join one of the subcap fleets.  I parked my interceptor in one of our structures, destroyed my pod to revive back in 1DQ1-A, where I grabbed a Rokh to join Mister Vee’s fleet.

While M2-XFE had cyno jammers setup by the hostiles, they were bringing them down now and then to jump in reinforcements, which allowed us to jump in our own reinforcements.  Since the system was running at 10% tidi, the five minute up/down cycle of the cyno jammer lasted almost an hour for those of us jumping in from normal speed space.

I got in and joined the fun, shooting fighters and subcaps of opportunity.  Tidi worked in my favor as my ECM burst hit a titan that was blown up after I returned in the Rokh, so the game counted me on the kill mail.  It shows my ship as a Rokh, but my weapon as an ECM burst.  I fulfilled my goal of getting on at least one titan kill. (I also got on the 10 billion ISK MTU kill mail.)

But then there was a call for boosters for the titan and super fleets.  Asher pinged out to Reavers to get some boosters, so I went to answer the call, which took me out of the fight for almost two hours.  I went to dock up and leave my ship so as to self-destruct again to get back to 1DQ again.  However, by that point the server was under a lot more pressure, and docking took a long time and left me with a black screen that took a long time to clear.  The client went unresponsive and I have to exit and try to log back in.  That took ages, but eventually I was back in and in my pod.  Then it was time to self destruct.  That took a while as well.

I may have pressed the button a few times

Eventually though I ended up back in 1DQ where I had a Damnation command ship ready to go.  The cyno jammers were down again, so I was able to take the slow bridge back to M2-XFE, where I got in one of the capital fleets and started boosting.

My Damnation in the orange of another explosion

With that setup, I felt ambitious and got out my main alt and flew him over in another interceptor.  As he flew over I contracted the Rokh to him, and he was able to dock up, collect the Rokh, board it, join Mister Vee’s fleet.  That took about an hour to accomplish, but I managed it, after which I set him up on my little second monitor in UI-only mode and shot targets of opportunity as I heard them called.   Along the way I tagged some hostile titans with him, and now he his on more titan kill mails than my main.

The command ship had a target painter, so I was able to get on a few kills with my main, but all the big toys were out of range of that.

The hostiles won the objective, reinforcing the armor timer and setting the structure up for the final timer.  That will come out in about two days.  But the fight kept on going.

The exchange of kills was fairly even, favoring PAPI by a few kills for much of the fight, but as the evening drew on past midnight Pacific time and towards downtime, which hits at 3am where I live, the exchange of titans began to favor the Imperium, though ships from both sides kept blowing up until the server shut down.

Ships still exploding around the Keepstar

The tally for this fight will be huge.  I am writing this as the battle is winding down, so the final numbers have not settled, but for titan kills I last saw 10 Leviathan, 18 Avatar, 87 Ragnorak, and 126 Erebus titans destroyed.  That is almost 250 titans down and there will no doubt be more on the list once things settle down.

But this battle far exceeded B-R5RB back in 2014, the previous high water mark for the Tranquility server, when 75 titans were destroyed.  This fight went well beyond that, though the destruction was much less lopsided than the earlier battle.

Expect follow up posts about this fight.  Not only were many titans destroyed, but the total cost of the fight will easily exceed 20 trillion ISK according to early battle reports. (Edit: Now that things have settled down, adding the report header.)

Battle Report Header – Updated as new kills have shown up

To put that in perspective, the total destruction in Delve in October, which saw five huge fights in NPC Delve, only amounted to about 11 trillion ISK according to the October MER.  (11 trillion ISK was also the amount of destruction wrought at B-R5RB, so this fight eclipsed that in ISK as well as losses.)

And there will be some clean up to do after downtime, as many people just went to bed after that and they will need to have their capitals, supers, and titans extracted.

Another historic day in New Eden.  We shall see what the post battle repercussions lead to.  This should certainly inflate the December MER.

Addendum:  Now that I have had a bit of sleep and zKillboard has caught up, the titan loss totals look like this:

Imperium Titan Losses:

  • Erebus – 66
  • Ragnarok – 42
  • Leviathan – 10
  • Avatar – 5
  • Vanquisher – 1

PAPI Titan Losses:

  • Erebus – 63
  • Ragnarok – 50
  • Avatar – 14
  • Leviathan – 1

Total Imperium: 124
Total PAPI: 129
Total Titans Destroyed: 252

[Edit: This is getting updated as kill mails show up. ]

You can tell which titans are considered the least tanky.  Both sides shot the Erebus and Ragnaroks first.  The first titan to die belonged to the appropriately named Titanic Death, while the last was Sandrin Stone, who blew up just before downtime kicked everybody out.

To expand on titan numbers, the count of them on the battlefield was:

Imperium:

  • Avatar – 317
  • Erebus – 137
  • Ragnarok – 135
  • Leviathan – 82
  • Vanquisher – 2
  • Molok – 2

Total 675

PAPI

  • Avatar – 248
  • Ragnarok – 193
  • Erebus – 111
  • Leviathan – 90
  • Molok – 2
  • Vanquisher – 1
  • Komodo – 1

Total 646

Combined Titan total: 1,321

That is a lot of very expensive ships thrown in on a Keepstar armor timer.

For the battle report, the difference in the ISK totals pretty much comes down to that Vanquisher faction titan loss on the Imperium side.  Otherwise it was a pretty even exchange on the titan front.  Now we will no doubt see both sides going on about how the other cannot afford to replace their losses.

Related: