Tag Archives: 3-DMQT

48 Weeks of World War Bee

War drama spilled over into EVE Online Twitch more so than usual this week as Matterall, who runs the steadfastly pro-PAPI Talking in Stations, lashed out at The Mittani this past week.  When CCP was doing candidate interviews on May 29th, Vily’s interview rather suspiciously landed in the same time slot as The Meta Show.  The Mittani pinged out to the Imperium that The Meta Show would be delayed until after the interview so he could pick it apart during the show.

The Mittani pings

This saw the viewership surge on CCP’s channel and probably made Vily’s the most watched interview in the series.  He was razzed in chat by Imperium members, but his interview was not visibly affected even a tiny bit by what was said in chat.  I suspect he wasn’t even watching the chat scroll by, which was probably the smart thing to do.  Otherwise it was a fairly bland presentation, which is all that somebody who is guaranteed a seat due to his coalition is obligated to give.

But Matterall took grave offense at The Mittani’s ping, comparing it to the January 6th assault on the US capitol.  He made it clear that he felt INN should no longer be allowed to be part of the EVE Online partnership program and vowed to take action.  Of course, this set the TIS Discord server on fire and made it to Reddit when the TIS Director of Programming quit over the Matterall’s statements which in turn dug up how Matterall had purged people who had any association with INN.  It was all quite a distraction from the state of the war for a few hours and should probably blow over if Matterall and his staff can stop digging the hole deeper for themselves.

We’re a long ways from Matterall’s “I know The Mittani” days.

As for the state of the war, the stalemate in Delve continues and PAPI in general, and Legacy in particular, has started to try another narrative shift.  The new line… well, really a revived old line… from Vily on Trash Talk Tuesday was that the Imperium is losing because they are not attacking PAPI… in Delve.  The Legacy backfield we’ve destroyed doesn’t count.  Continuing the make them jump clone for fights in other regions doesn’t count.

The questions about who blued 100+ alliances and out numbers whom by 3:1 aside, the PAPI war aim remained, as of last week’s Legacy Town Hall, to destroy the Imperium and drive us all from the game.  I don’t think that has actually changed, though Vily seems to be trying to unsay his past statements, as he does whenever they stall only to reiterate them again when they get make some progress, so we win by surviving to fight the blue donut and the Council of Wardens, which has been capitalized as “COuncil of WARDenS” to indicate the Imperium response to that idea.

Of course, there is a probably reason for this latest narrative swap and it may involve what happened in Delve during week 48.

Delve Front

After a low population weekend PAPI failed on Monday to contest the two Azbels they dropped in the AU/CN TZ attack the previous week.

Or maybe later

PAPI decided to roll with the same time zone surprise attack again.  I woke up Tuesday morning to find pings going out calling everybody into fleets to defend the Imperium capitol constellation.

PAPI was trying to force their way in and drop more two more Azbels, though they were shooting for systems besides 3-DMQT this time.  One of them was blown up in N-8YET before it could get past its 15 minute initial vulnerability, while the one in MO-GZ5 managed to get past that and is now on the list as a target once the six day deployment time runs down.

In the mean time The Initiative had been baiting PandaFam to jump back to their space in the Dronelands to hit an Azbel they dropped in the Pandemic Horde capitol system of R10.  That was destroyed, but it opened a window for them to drop a Keepstar on the E-VKJV gate grid in 3-DMQT.

The Initiative eye now watches the gate

The following day when the Keepstar was set to anchor the Imperium showed up in force, with supers and titans on grid.  PAPI chose to pass on contesting the structure.  They remain unwilling to commit supers and titans to anything beyond uncontested structure kills.

There is now a Keepstar doomsday weapon that can reach out and smite hostiles on their way into the constellation, making PAPI’s job just that much harder.  The Ansiblex in 3-DMQT was moved over to the E-VKJV gate grid as well, so now we can gate straight into action when it comes.

The new Keepstar

With that in place PAPI ran another AU/CN TZ op later in the week in order to try and plant more Azbels and shoot cyno jammers elsewhere in the constellation, which ended up with about the same results as previously.

As such, I can once again re-use my map of the siege of 1DQ for the fifth week running, as the status quo remained.

O-EIMK Constellation – June 7, 2021

The campaign report for Delve shows that total ship losses and loss value were down again.  Week 46 saw nearly 15K ships explode, week 47 was 11.5K ships, and week 48 saw that number drop to about 9K ships.

Week 48 Losses in Delve

Other Theaters

Out in Esoteria Army of Mango Alliance kept pushing on the space hel by The Bastion and its allies, taking one more ihub since week 47.

Esoteria – June 6, 2021

Likewise, out in Feythabolis, The Bastion lost one of its ihubs and a couple others traded hands among the groups vying for the region.

Feythabolis – June 6, 2021

Meanwhile, The Initiative’s campaign in Etherium Reach appears to have gone on a break for a bit, as no ihubs are currently reinforced.  They are probably still celebrating their ruse to get another Keepstar planted in the Imperium capitol constellation.

My Participation

I woke up Tuesday morning to find pings going out to repel invaders and managed to log in just in time to get in on the tail end of the AU/CN TZ PAPI incursion into our space.  I undocked in time to help pick off a few PAPI members as they ran for the T5ZI gate in 1DQ.

After that, the week was fairly quiet.  PAPI stood down several times after we counter-formed them and I mostly shot bubbles in their space for the rest of the week.  They did try to drop one of our ADM fleets in 3-DMQT, so I joined in on that, but not much happened.

I hung around for a bit as the Jackdaw cover fleet ran some Blood Raider sanctums to help keep the ADMs for the system up.

Jackdaws in a sanctum

I had no ship losses for the week, leaving my total for the war at:

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

Other Items

A lot of the week away from the war was focused on the CSM16 elections, which kick off tomorrow, June 8th, after downtime.

Dunk Dinkle did another informal survey of capital ship builders to see if anybody had resumed production since the industry changes.  The general response was that pre-change hulls are still available for well below what it costs to build hulls now, so there isn’t much point.

Meanwhile, the daily user numbers remain down.  Only Monday, Memorial Day in the US and UK, saw the peak user count pass 30K.  Sunday is generally the peak day in any week, though some weeks Saturday is at the top.  For this week, because I go from Monday to Sunday in my reporting, Monday takes the crown.

  • 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
  • Week 29 – 35,996
  • Week 30 – 38,323
  • Week 31 – 38,167
  • Week 32 – 37,259
  • Week 33 – 35,886 (Saturday)
  • Week 34 – 35,626
  • Week 35 – 35,379
  • Week 36 – 35,085
  • Week 37 – 34,394
  • Week 38 – 36,319
  • Week 39 – 35,597 (Saturday)
  • Week 40 – 35,384 (Saturday)
  • Week 41 – 33,708
  • Week 42 – 33,521
  • Week 43 – 33,731
  • Week 44 – 33,742 (Saturday)
  • Week 45 – 33,758
  • Week 46 – 31,768
  • Week 47 – 29,898
  • Week 48 – 31,462 (Monday)

Related

47 Weeks of World War Bee

This post is coming out later than usual due to the end of the month and Memorial Day coinciding, along with my firm belief that nobody needs three blog posts from me in quick succession.  But I couldn’t just push it 24 hours out because Burning Crusade Classic is coming as well.  So here it is something of the dead zone between days.

Week 47 started off with PAPI feeling pretty good about itself.  Progodlegend led a Legacy Town Hall meeting (which you can listen to here in its entirety) where he repeatedly denigrated the Imperium’s fighting and theory crafting abilities (we also only have two bloc level FCs, Asher and Mister Vee, and maybe Elo Knight if he shows up) while talking up Legacy’s strengths in that regard.

He also reiterated that the PAPI blue donut would remain so long as Goons are any sort of power in the game, with a council of wardens (made up of basically everybody but the Imperium) allied so long as we still exist.  If we go to WH space or Pochven or where ever, they will follow and remain united until we have been purged.  He was careful to repeat that PanFam was totally committed to this plan.

The town hall also continued the ongoing strong support by PAPI for Vily’s “Imperium Delenda Est” war aims that I recorded back in week eleven of the war.   We’re bad people, bad for the game, bad at the game, must be driven out, yadda yadda yadda.  They would destroy the game rather than leave us be.

On that theme, Monday started off strong for PAPI, with a surprise AU/CN TZ flash form that managed to drop two Azbels in 3-DMQT as well as reinforcing a couple of Imperium towers in the system.  The ISK war was a draw, but they won the objective.

High on this, PAPI returned on Monday night in US prime time to defend an Azbel that was coming out to anchor… and got wrecked.

Their new Abaddon battleship doctrine was pretty much wiped out on the gate, the space superiority fighters, which Progodlegend had mocked as a tactic in the town hall, ate up their blaster Harpy fleet exactly as they were supposed to, and their Azbel was destroyed, bringing the Azbel death total up to 14 at that point.  They lost the objectives, never getting off the gate in 3-DMQT, and the ISK was was so tilted against them that even Progodlegend had to allow that the Imperium had won this one battle in the war.  It must have stuck in his throat to even say that much.

And then they stopped hitting 3-DMQT in any serious way for the rest of the week, with no more Azbels dropped. They went back to running ops into Curse to shoot an INIT structurem though they subsequently forget to scoop the core when they were done, allowing INIT to recover it.  The rumor is that PAPI is giving up on trying to assault the Imperium capital and will, instead, attempt to starve us out in some sort of cold war approach that, so far, seems to mostly involve complaining about the Imperium posting too much on r/eve.

Delve

The stalemate continues.  PAPI has the numbers to keep the Imperium from pushing back in the region, but cannot bring itself to commit to taking the losses that would be needed to actually break into the 1-DQ1A and the rest of the O-EIMK, the Imperium’s capitol.  In the town hall Progodlegend blamed the advantages of defenders and suggested that CCP needed to fix that.  Then there is the cold war rumor.  As such, I can re-use my map of the Imperium capitol constellation for the fifth post in a row.

O-EIMK Constellation – May 30, 2021

The assault on the Imperium capitol began back at the end of April and looks to have petered out for the moment.  Skirmishes continue, but if you look at the campaign report for Delve, the week, action was down considerably.

However, there is still a possible fleet action approaching.  I am writing this on Sunday to correspond with the end of the week, but this won’t post until Tuesady, and on Monday morning the two Azbels that were dropped last week will come out of their deployment timer and be ready to anchor, again in late AU/CN time and right about the middle of the day EUTZ.  And, since Monday is a holiday in the US and UK, there might have been a titanic battle… or PAPI might have passed.  But that will get reported as part of week 48.

[addendum: in case I forget, they passed.]

The campaign report for the week shows that overall destruction was down for the region.

Delve Campaign – Losses for Week 47

While not as lopsided overall as the Abaddon massacre, things still tilted in favor of the Imperium for the week.

Other Theaters

In Esoteria The Bastion and its allies appear to have stopped the mark of Army of Mango Alliance, which had been retaking their gains.

Esoteria – May 30, 2021

Whether that was because of action elsewhere or the incursion in the region I am not sure, but The Bastion continues to hold on.

Likewise, The Bastion and Red Alliance are still holding on to a corner of Feythabolis.

Feythabolis – May 30, 2021

A few ihubs in the center of the region changed hands, but there was no dramatic change in the situation.

And in the Dronelands The Initiative has kept up its activity in Etherium Reach, reinforcing systems and forcing PanFam to jump clone back home to defend timers.

Etherium Reach – May 30, 2021

The Initiative has yet to destroy an ihub, but they would like to remind everybody that they took a side trip over to The Kalevala Expanse and reinforced the ihub in R10-GN, which happens to be Pandemic Horde’s capitol system.

Pandemic Horde’s main system in TKE

I am going to guess that PH will feel the need to jump clone home to deal with that.

My Participation

I was in the thick of things Monday night for the fight on the gate in 3-DMQT and managed to survive, though many of my fellow Eagle fleet pilots were blown up in the brawl.

Eagles helping bump a fax out of the bubbles after the fight

After that though, there wasn’t much going on.  The nightly stand to for the vulnerability window saw no attacks.

I did end up losing two Jackdaws in skirmishes towards the end of the week, though for that to happen John Hartley had to bring us into E-VKJV to hang around, shoot their Ansiblex, hang around some more, eventually they formed Caracals, which we traded well with for a while, then they finally formed Munnins, after which we took off.  That brings my loss total for the war up to:

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

Other items

CCP launched its Stargate Trailblazers event which encourages players to get out and support the four main empires in their efforts to construct new stargates by getting involved in resource harvesting, which allowed CCP to recycle its old resource wars content.  TNG has a couple of posts about the event.  I did find it interesting that, after pitching this as a bit of a competition between empires, CCP Fozzie had to confirm that all the planned stargates will get built now matter what players do, so it isn’t like the Triglavian invasion where players has some small influence on the outcome.

From the forums

So if you’re in it, it is for the rewards.

I forgot to mention this last week, but the candidate application and review process for the CSM16 election was wrapped up and CCP announced all of the candidates that qualified, though there process left us wondering about happened with the candidates who did not make the cut.  60 people posted threads in the forum, as required by CCP, but there were only 47 on the final list.

Voting for CSM16 starts next week, on June 8th after downtime, and continues on until downtime his on June 15th, per the dev blog.

CCP also published their video of user submissions for the 18th anniversary celebration.

On the player count front, it is starting to feel like the easing of the pandemic, warm weather, and a war in stalemate is leading more players to go outside.  The daily peak concurrent number did not rise above 30K on Monday through Friday, a trend that carried through the weekend, with Sunday peak falling just short of the 30K mark for the first time since the war began:

  • 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
  • Week 29 – 35,996
  • Week 30 – 38,323
  • Week 31 – 38,167
  • Week 32 – 37,259
  • Week 33 – 35,886 (Saturday)
  • Week 34 – 35,626
  • Week 35 – 35,379
  • Week 36 – 35,085
  • Week 37 – 34,394
  • Week 38 – 36,319
  • Week 39 – 35,597 (Saturday)
  • Week 40 – 35,384 (Saturday)
  • Week 41 – 33,708
  • Week 42 – 33,521
  • Week 43 – 33,731
  • Week 44 – 33,742 (Saturday)
  • Week 45 – 33,758
  • Week 46 – 31,768
  • Week 47 – 29,898

Related

PAPI Battleship Failure in 3-DMQT

The pattern of operations has hit something of a predictable routine.  With the vulnerability windows of the O-EIMK constellation set to USTZ and the ADMs at or close to maximum, both sides start to ping for people around 00:00 UTC and, if a battle is going to happen, it happens in the next couple of hours.  There has been, for several nights running, an Azbel coming out of deployment to fight over, and last night was no exception.

Yesterday PAPI did a surprise change and formed up in China/AU time to drop another pair of Azbesl, one with a name about the “3-D invasion starts now” but trading about even with our defense even though they had almost double the numbers according to the battle report.

As a follow up they came back again last night to defend and older Azbel that was set to try and anchor.  The ping for an Eagle fleet went up first at our end and I once again joined in an Eagle and a Scythe logi on my alt.  We got into 3-DMQT and, as PAPI assembled, got ourselves positioned around the gate.  A second fleet of Munnins was called up, and carriers were arrayed on the Fortizar near the gate, their fighters off a ways from us.

Then the word came that PAPI was undocking.  Abaddons would be coming our way, a new doctrine for them, along with Munnins of their own, as well as Harpies, their doctrine for taking our our carrier fighters.

We sat on the gate and waited, then there was a gate flash and local started rising and it was clear they were coming through.  Some unfortunate Abaddon pilot decloaked from the gate jump early and was promptly devoured by our Eagles.

Then they started all decloaking and things settled into a brawl on the gate, with the Eagles shooting Abaddons and their logi while PAPI focused largely on our own logi.  I have few decent screen shots from the fight because I had turned down my graphic settings and, with that change, the mass of bubbles around the gate became largely opaque.  I mostly stayed zoomed out to avoid the bright screen white-out of being in the bubbles.

My view of most of the battle

We lost a lot of our logi, though the Eagles run with cheap T1 cruiser logi, so they were easily replaced.  My own Scythe managed to survive largely because I got focused on my Eagle and keeping an Abaddon scrammed, so when our logi anchor went down my alt flew off in a straight line away from the fight.

There he got ECM’d by a couple of PAPI Kitsunes, which meant he couldn’t lock up and rep anybody anyway.  But, with the ECM nerf from a couple of years back you can always lock the ship hitting you with ECM, so I dropped the combat drones I had brought along and put them on one Kitsune, then another.  Somebody else came along and finished them off, but my alt got on both the kill mails.  His fighters, left on their own, also found a PAPI Eagle to attack later on.

In the brawl I managed to avoid being the primary and kept on locking and firing.  Then the word came that things were going so badly for PAPI that they were attempting to de-aggress and get back through the gate, the fight never having really moved off to the Azbel, the ostensible reason for the fight.

With that word coming down, the focus at our end was to blow as many ships up as we could before we they got away.  HAW dreads were jumped into the melee on the gate, adding to the faxes we already had with us for support.

Final frenzy at the gate

And then the last few targets were gone and we had the field to ourselves.  The battle report showed that their plan with the Abaddons did not turn out the way that they had hoped.

As we waited for the vulnerability timers to run down for the system, the point at which operations generally each evening, we helped the faxes and dreads out of the gate bubbles by bumping them to speed them up.

Things went very much our way.

Battle Report Header

150 billion ISK isn’t a very large battle for this war, though at any other time it might have been noteworthy.

According to the details at the EVE Fleet Manager battle report, PAPI lost 98 of the 119 battleships that were engaged, all of which are more expensive to manufacture now due to the industry changes, along with 307 assault frigates, their anti-fighter Harpy fleet, and a good 30 heavy assault cruisers and 42 logi.  My killboard has three expensive Bhaalgorns on the list of hostiles I hit.

Our biggest loss was 70 heavy assault cruisers, largely from the Eagle fleet I was in, and 57 light fighters.  Oddly, none of the anchored bubbles on the gate died.

And so another day defending our last constellation passes by with us winning the objective, killing the Azbel and keeping PAPI from any other mischief, as well as with us winning the ISK war.  A good day for us.

Related:

46 Weeks of World War Bee

Week 46 kicked off with a big brawl in 3-DMQT, a system that saw almost nightly clashes as the “Siege of 1DQ” finished up its fourth week in stalemate.

Meanwhile, CCP announced some new changes and pushed some recently announced plans to Tranquility (TQ), the live server, much more quickly than people seemed to expect.  Even the main EVE Online Twitter account didn’t seem to get the memo as it was boosting a story from the 13th about trying out changes on the test server that had already been pushed to TQ on the 18th.

Maybe they just hadn’t had their coffee yet

Overall it was kind of a busy week, so I guess even they had trouble keeping up.

Delve Front

Once more I can recycle my map of the conflict area in the Delve front, originally created to show the situation at the end of Week 43.

O-EIMK Constellation – May 23, 2021

The war in Delve entered a new pattern with the Monday fast form by PAPI to try and reinforce the infrastructure hub in 3-DMQT.  That routine continued through the week, with the Imperium quickly noticing PAPI’s flash form routine just before the vulnerability window started.  That led to a series of nightly clashes where PAPI often won the ISK war and was able to drop another Azbel in the system, but in which they also failed to gain any sort of foothold, losing every Azbel at the end of its deployment cycle, or reinforce the ihub.

The battle plan for this was leaked (high quality meme) so the Imperium was informed.  And, if you want to experience how this all works yourself, somebody made a browser version of the game called Delve Defense.

Looking at the weekly campaign report, ship losses went up by ~600.

Week 46 Campaign in Delve

However, some variable exceeded its max value and somehow GSF lost 6,861 ships that added up to zero ISK.  I would guess that the actual losses exceeded one trillion ISK in the region.

Other Theaters

Over in Esoteria the Army of Mango Alliance continued to push back on The Bastion and its allied and their long held foothold in the northwest of the region.  The Imperium allied forces have been reduced to just six systems now, half of what they held at the end of Week 45.

Esoteria – May 23, 2021

In Feythabolis a couple of systems traded hands, but neither side is pushing the other completely out of the region so far.

Feythabolis – May 23, 2021

And The Initiative appears to be still plugging away in the PandaFam backfield, reinforcing ihubs in Etherium Reach again.

Etherium Reach – May 23, 2021

Whether or not they can win an entosis contest and take an ihub remains to be seen.

My Participation

With a nice, predictable cadence of operations happening I was able to jump into a number of fleets.  The big brawl in 3-DMQT opened up the week, during which I lost three Drakes and a Scythe.  But it was announced one pilot cycled through seven Drakes during the fight, so my losses were not extraordinary.

Another Drake about to explode

I also lost two Jackdaws and a Cormorant in further skirmishes over the week, leaving my loss totals for the war as:

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

Other Items

CCP, in a rush to do… something I guess… pushed out the changes for warp core stabilizers and interdiction nullification less than a week from when they began to solicit feedback.  The rushed nature was apparent in the details that they appear to have overlooked.

CCP also announced the plan for combating AFK cloaky camping via mobile observatories.  We’ll see if their in a rush to get that out the door tomorrow I guess.  As with the warp core stabilizers and nullification changes, reactions for this change were all over the board.  Those against AFK cloaking felt the change would not go far enough as the mobile observatories would not be exactly tough to kill.  Those defending the cloaking playstyle felt that these things would be spammed everywhere and, in conjunction with the stabs and nullification changes, make null sec much safer than it should be, with bubbles on every gate, faction scrams at every gate camp, and mobile observatories in every system.

In brighter news, CCP won the Webby Award for Games in the “Public Service, Activism, and Social Impact” category for its work with Project Discovery.

And the April Monthly Economic Report was posted… and then fixed… and then fixed again.  But it is looking okay now.  Or no worse than usual.  I should have the usual post about that tomorrow.

Perhaps in response to these changes, or boredom with the war, or sunshine and a receding pandemic, peak concurrent numbers were down noticeably over the course of the week, with the peak day of week 46 dropping a couple thousand players when compared to week 45.

  • 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
  • Week 29 – 35,996
  • Week 30 – 38,323
  • Week 31 – 38,167
  • Week 32 – 37,259
  • Week 33 – 35,886 (Saturday)
  • Week 34 – 35,626
  • Week 35 – 35,379
  • Week 36 – 35,085
  • Week 37 – 34,394
  • Week 38 – 36,319
  • Week 39 – 35,597 (Saturday)
  • Week 40 – 35,384 (Saturday)
  • Week 41 – 33,708
  • Week 42 – 33,521
  • Week 43 – 33,731
  • Week 44 – 33,742 (Saturday)
  • Week 45 – 33,758
  • Week 46 – 31,768

Related

Slugfest in 3-DMQT over iHub and Azbel

After spending much of the weekend shooting targets on secondary fronts after the pasting they received at the hands of Imperium bombers in two consecutive fights, PAPI decided to make an aggressive attack on the ihub in 3-DMQT just before 00:00 UTC yesterday.

As I have mentioned in the last few weekly updates, the system of 3-DMQT is the focus point for PAPI in their attempt to break into the O-EIMK Constellation which is the capitol of the Imperium and the last bastion of our defenses in Delve.  As such, both sides have Ansiblex jump gates setup to facilitate piling forces into that system

O-EIMK Constellation – May 17, 2021

As the fight started several fleets were called for on the Imperium side, including one for carriers and supers.  As we had done previously, the carriers sat on the Fortizar nearby the ihub on tether and sent their fighters in to clear enemies from the ihub.  The subcap fleets went in to keep the hostiles from being able to simply shoot fighters.  We have a fighter shooting doctrine we have used to great effect previously, and PAPI sent in a Harpy fleet to do that.

Battle around the ihub

I went in with the Drake fleet under Kretin Valefor, in part because it was the first fleet called, but also because I am happy to see the return of the Drake to a fleet doctrine.  It isn’t quite 2012 again with clouds of perma-MWD Drakes prowling the spaceways, but the hull is back and spewing heavy missiles.

Yes, I can bring my Drake

For whatever reason… I guess I thought this would be a short and/or easy fight, I decided to dual box and got my main alt in a Scythe to play logi.  What could possibly go wrong?

The ihub grid was crowded when we got there, with bubbles up and the usual mess of clashing fleets.  There were around 2,000 people in the system and, while tidi was clearly in effect, it managed to hover between 13 and 20% for much of the fight, meaning the server had slowed us down, but was still able to keep up and process commands.  Things still took seemingly forever to accomplish… nothing like the FC having you change ammo and then, just as that starts to cycle, seeing a different fleet on grid, tells you to change back… but nothing was backlogged.

This was the costly part of the battle for me, as I managed to lose three Drakes during the skirmish over the ihub.

Seeing your ship brew up from your pod

The finance team was on the job though.  I applied for SRP for my losses and was paid before I was back in the fight with a fresh Drake… expect for the second one, when I was in a hurry and forgot to check if the rigs were in the cargo hold before I undocked.  SRP Denied.  Oh well, I guess Progodlegend and I have something in common now, though I only did it once in a single fight.  But getting back into the fight was speedy and I was on a couple of the better kills, those being the two Minokawas that PAPI dropped in to rep their subcaps.

Minokawa brews up on the ihub

I did considerably better with my alt in the Scythe on the second screen.  I couldn’t be bothered to save my own Drake it seems, but I managed to get reps on a few others and, with my armor and hull drones, managed to haul one Drake pilot back from the brink.

Back from the brink

One more volley would have done in that Drake, but the enemy saw he was getting reps and switched targets.  Oddly, the hostiles left my Scythe alone for the most part during the ihub fight and I was able to amble about the field repairing as I went.  We were intermixed with a fleet of hostile Harpies, but aside from the occasional potshot, they focused on fighters and ignored me.

The ihub battle went on until the vulnerability window closed, after which both sides pulled back a bit and we safed up on the Keepstar in system.

The doomsday reaches out to hit some PAPI pilots who strayed too close

We were waiting for the next round, which was one of the PAPI Azbels that was set to come out of its six day timer and anchor.  As the time ran down we got on an Astrahus that was 1,051km from the Azbel.  Because we own the system, it only takes us a day to anchor a structure, so we can always plant one near any of the ones they are trying to drop.

Azbel with 2 minutes left

They deployed bubbles and ships between the two structures, but there are enough bounces in the system that when the time came we were able to warp in right on top of it.

They got the core in and the 15 minute repair timer started counting down, but we stopped it before it hit 10 minutes and it never moved after that.  It seemed to be a foregone conclusion that the Azbel was going to die.

Instead both sides brawled in an attempt to destroy as many opposition ships as they possibly could as drones and some Bigbillthaboss specials chewed away at the structure.

BBtB Myrmidons from his personal fleet

In this fight the Drakes were mostly ignored by the enemy, who sought out more valuable targets.  The only exception was my Scythe, which got blapped at one point.  But I was able to reship with my alt and rejoin the fight.

We shot the Azbel ourselves from time to time, then get stuck into whichever hostile fleet we could find.  Slowly but surely the health on the Azbel ticked down until it exploded.

Azbel blows

The quantum core dropped… because cores have a 100% drop rate per that update… and a TEST Mammoth scooped it, only to be destroyed.  But the core dropped again… because cores have a 100% drop rate… but I don’t know who ended up with it.  It is 50K m^3 in size, so you can’t just grab it with an interceptor and run.

After that there was a bit of a frenzy to get in some final kills and then we settled down back on the Keepstar.  The fight was over but we needed to wait for PAPI to extract in order to ensure they were not up to any more mischief.

That took a while because PAPI, having learned its lesson, didn’t try to squeeze through the out gate in one giant, server melting mass this time.  Instead they went out by small groups, which took them a good while.  Eventually they cleared off and we were able to take the Ansiblex back to 1DQ1-A and log out ourselves.  I was tired at the end of that, being a long battle that started just as I was done with work… and since I work from home, meant sitting in my desk chair for another five hours.  But that wasn’t as bad as our FC, who said at the end he had been up for 25 hours straight.  He must be young though, I saw him in a ping leading a fleet the next morning.

It was a long fight.  The battle report showed quite a bit of destruction.

Battle Report Header

PAPI soundly won the ISK war, with the Imperium losing more than double their number.  This was helped along by a Nyx super carrier that got itself blown up and some dreads and faxes of ours that were on grid for the Azbel part of the fight.  I am pretty sure part of the reason the Drakes were left alone is that they were going for big targets.  And as well they might.  We would have done the same.

Progodlegend posted a brag on Reddit about PAPI winning the ISK war while being outnumbered.  That is certainly true, though it also raises an eyebrow when the side that has three times the total pilots of its foe can’t out number them in a big fight.  What good is blueing up over a hundred alliances if they won’t blob for you?

The Imperium, however, can claim to have won all of the objectives.  The ihub did not get reinforces and PAPI once again failed to anchor a structure in 3-DMQT.  Having made no progress for all the effort, PAPI has to do it all over again.

So the “Siege of 1DQ” carries on.

43 Weeks of World War Bee

The week saw an uptick in clashes in Delve as PAPI, after having announced last week that anybody waiting for a huge capital fight over the O-EIMK constellation was going to be disappointed, kept to their word about assailing the systems with subcaps.  With no Keepstars left to shoot, they launched their subcaps at the Imperium.  I put together a campaign report to try and capture a general sense of how much destruction went on over the course of the week.

Delve Campaign in Week 43

The PAPI side is an incomplete list because I haven’t the energy to add all 100+ alliances in the coalition, but I put in the major players that were active. (Also, I missed Siberian Squads on the Imperium side, but they add just 13 ships to the total.  Next time.)  The Imperium losses are padded out a bit by a few final structure losses, but is mostly ships.

If you change the campaign dates to the week before, the ISK value is a little more, largely due to the final two Keepstars, but the total ships destroyed is about half.  That feels like a serious boost in activity in Delve to me.

Delve

I think I can forego the full Delve map for now as the sovereignty situation outside of the O-EIMK constellation seems unlikely to change so long as the PAPI assault continues. (And the metaliminal storm has moved off into Querious.)  Instead, I’ll put up a map focusing on the primary PAPI objective.

O-EIMK Constellation – May 2, 2021

While the bulk of both forces sit facing each other in the adjacent systems of 1DQ1-A and T5ZI-S, most of the fighting has been taking place in 3-DMQT.  1DQ1-A is a tough nut to crack and the easiest for the Imperium to defend, as we can just undock and join the fight.  The other systems in the constellation are cyno jammed and have no connection to systems held by PAPI.  That has left 3-DMQT as the most viable target to attack.

PAPI has set up an Ansiblex jump gate connection between their staging system and 3-DMQT, as the Imperium has between 1DQ1-A and 3-DMQT.  In order to gain a foothold in the system, much of the PAPI effort has been expended in attempting to bring down the Imperium Ansiblex in 3-DMQT.

The Imperium guarding the 3-D Ansiblex

PAPI has managed to reinforce the Ansiblex there several times, including during a large brawl on Saturday.  However, even when they succeed with that, the system is not cut off from 1DQ.  Imperium command simply drops the cyno jammer in 3-D and uses titan bridges to throw forces into the system.

Watching another repair cycle

The battles over the system will no doubt carry on until PAPI either takes the system or tires of the effort.  However, that effort is really only putting off the inevitable.  If you look at the constellation map, there are only two systems they can get directly into before they have to setup and fight in 1DQ1-A itself.

And they still have to turn the ihubs in those two systems in order to follow through on their usual plan of setting up jump gates and cyno jammers in order to kill the Keepstars.  The sovereignty battle won’t be easy.  They cannot jump or gate directly into the rest of the constellation and the ADMs are high enough that they have to spend most of an hour on each node in an entosis contest, while we will be able to pop nodes in a few minutes.

O-EIMK constellation ADMs

This feels like a clash that is going to carry on until one side or the other gets tired of it.  Combat alone won’t likely won’t resolve the struggle, some persistence is going to be required.  We shall see.

Other Theaters

Feythabolis continued to see contests over ihubs as The Bastion. Red Alliance, and other allies pushed into the region.

Feythabolis – May 2, 2021

Likewise, the push and pull continues in Esoteria, which connects to Feythabolis, as The Bastion and allies continue to vie with Army of Mango and Evictus.

Esoteria – May 2, 2021

Last week also saw The Initiative move on from the torched regions of Catch, Immensea, and Impass to open up an new front in the enemy backfield.  This time the target is Etherium Reach in the dronelands, where PandaFam and their associates live.

Etherium Reach – May 2, 2021

The particular target, according to Fountain Frank on the Meta Show, is Solyaris Chtonium, generally referred to by their ticket, Slyce, though Pandemic Horde holds a stretch of systems there as well.

My Participation

I managed to get into the first big fight in 3-DMQT at the start of the week, which I covered in a post.  I declared it the start of the PAPI assault based on just that first fight, so am happy enough to have been vindicated in that statement by the ongoing fighting since.  I have been through the Ansiblex into fights more than a few times… and in via a titan bridge as well.

The Ansiblex in 1DQ1-A

My lucky streak ended in a fight when Tom Flood who, in this age of “kitey bullshit,” still loves to take his fleet in close to brawl, managed to get his whole logi wing destroyed, including me in a Scimitar.  So I will add that to the loss list for the war.  My revenge was quick in coming as I managed this epic kill.  Fear the corvette plague.

My losses for the war are now:

  • Ares interceptor – 17
  • Malediction interceptor – 7
  • Crusader interceptor – 5
  • Atron entosis frigate – 6
  • Rokh battleship – 5
  • Scimitar logi – 5
  • Ferox battle cruiser – 4
  • Drake battle cruiser – 4
  • Purifier stealth bomber – 3
  • 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

EVE Online has been nominated for a Webby award for the Project Discovery work and CCP would very much like it if you could go cast a vote to support that.

CCP dropped the second part of their industry update, which added new components to all battleship and larger hulls.  This has caused uncertainty and price jumps for those hulls, as well as further mineral price increases as people scrambled to get builds in before the change, so that when I checked Jita earlier, Rokh hulls are now selling for more than what I paid for a fully fitted Rokh on contract about a month ago.  Manufactured T1 battleship hulls look to be 350 million ISK and up.  It might be a good time to try a Praxis, which appear to be much cheaper.

CCP also introduced a new set of packs, complete with game time, SKINs, and skill points.  But selling skill points for cash has already been normalized, so whatever.

The validity of the MER and its consumer price index, which includes non-player produced items like skill injectors, was both a topic of discussion at The Nosy Gamer and on The Meta Show.

And, on the peak concurrent user front, numbers remained about the same this week this week despite all the activity over the O-EIMK constellation.

  • 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
  • Week 29 – 35,996
  • Week 30 – 38,323
  • Week 31 – 38,167
  • Week 32 – 37,259
  • Week 33 – 35,886 (Saturday)
  • Week 34 – 35,626
  • Week 35 – 35,379
  • Week 36 – 35,085
  • Week 37 – 34,394
  • Week 38 – 36,319
  • Week 39 – 35,597 (Saturday)
  • Week 40 – 35,384 (Saturday)
  • Week 41 – 33,708
  • Week 42 – 33,521
  • Week 43 – 33,731

Related

The Assault on the Imperium Capitol Constellation Begins

Over the weekend several of the PAPI alliances had meetings where it was announced that those expecting a huge capital slug fest were set to be disappointed as the coalition would be attacking the remaining Imperium held space in Delve, the O-EIMK constellation, with sub caps alone.

Yesterday in late EU/early US prime time the sub cap attacks began in earnest with an attempt to bring down the Ansiblex jump bridge and the cyno jammer in 3-DMQT, which sits at the southern end of the constellation, and which is the only way into the jammed systems if attackers do not wish to come in straight through 1DQ1-A, the Imperium staging system.

Arriving at the Ansiblex mid-fight

The Imperium still has a small jump bridge network spanning the constellation to facilitate moving forces around, with the key one being the 1DQ1-A to 3-DMQT route that lets us quickly move between the two routes into the area.

As the attack commenced pings went out for more and more fleets on our side.  In addition, as an early defense, anti-sub cap dreads were dropped into the fight along with a Baltec fleet as the first line of defense, followed on by more Baltecs, Feroxes, Jackdaws, and bombers.

A Revelation explodes behind an Initiative Abaddon

Time dilation was down to 10% as more than 2,500 capsuleers began a two hour brawl over the Ansiblex.

I joined one of the Ferox fleets as I ate my lunch and was able to jump straight into the fight to start shooting targets.  The grid was crowded and there were many targets in range.  Our progress in shooting was slowed down by the tidi, though we did not seem to be pushing the server too far beyond its limits.  I had the calls diagnostic window open and nothing was lingering for minutes on end the way they were during the M2-XFE fights.

Another ship explodes

From my perspective it was just lock, shoot, then move to the next target.  We mowed down logi in the hostile Ferox fleet that was close to us, then began to burn down the Feroxes as well.  It felt one-sided enough that the FC eventually just called for us to sort by distance and shoot from closest to furthest as targets became available.

Things went well enough that by the time we were told to de-aggress and warped to the E-VKJV to see the hostiles off I had managed to get on 70 kill mails, including getting the final blow on three different ship including the one flown by Lady Scarlet.  It is always fun to get the kill mail on enemy leaders and other notables.

Kill marks on the left shoulder of the ship

Actually getting the kill mail in a huge brawl with a couple thousand players is a pretty rare thing and tends to go to the people closest to the data center, so getting three was kind of neat.

However, looking at the battle report, we were having such a free time because the hostiles were concentrating their fire on the capitals we brought along, knocking out 19 dreadnoughts and 2 faxes.  That focus tilted the ISK war well in their favor.

Battle Report Header

That arguably understates the losses on the Imperium side as, with the industry updates that were pushed with yesterdays patch, capital are now much more expensive to build and replace.

A fax that was supporting the Baltec fleet blows up as we pass through a mass of subcap wrecks

In in the end though, we won the objective and were able to take satisfaction in destroying a mass of hostile subcaps.  We hung around to shepherd the Ansiblex until it was fully repaired.

Guarding the Ansiblex as it repairs

After it was done we were able to take it straight back to 1DQ and stand down.

We survived the first major attack on the constellation and pushed the hostiles back.  But that was only the first attack.  I expect we will be battling again before too long.

Related: