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:

3 thoughts on “PAPI Battleship Failure in 3-DMQT

  1. Mailvaltar

    To be honest, I’m kind of glad that this stuff mostly happens in US TZ when I’m already sound asleep.

    What a great idea to try out new doctrines, sporting what is the most expensive subcap type right now, and welp them right into your welcoming arms. With SRP for DPS ships disabled again, no less. I’d certainly be broke by now if I’d been more active these past months…

    Liked by 1 person

  2. anypo8

    @mailvatar PAPI ended SRP for subcaps? How long can they keep it together after that? Feels to me like a lot of pilots would be sitting out battles soon…

    Liked by 1 person

  3. Mailvaltar

    @anypo8 – It was cancelled pretty much at the beginning of the war iirc, then came back for a while, now it’s cancelled again. Every now and then, after a brawl, we’re told that DPS may apply for SRP, but it’s the exception, not the rule.

    Honestly, I couldn’t tell you how much ISK the average PAPI member has, or how much they’re generating. Me, I do have a stash from selling expensive SKINs that I got by attending EVE Berlin and the like, but my running income is basically zero. I’m glad that I didn’t take any heavy losses yet during this war (I lost way, way less than Wilhelm, for example), that much is certain.

    Like

Voice your opinion... but be nice about it...

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s